WordPress vs Webflow vs Framer: What's Next?
A considered review of today's platforms.
In design, the tool is rarely the point. It's the work that matters — how it
feels, how it functions, how it endures.
But in digital environments, the tool you choose does shape more than aesthetics.
It determines the performance, accessibility, and longevity of what you create.
And increasingly, the design tool becomes the development platform.
So the question becomes: which tool allows you to design with clarity — and
build with precision?
## The landscape
There's no shortage of web design tools today. Some are built for code. Others
for visual flow. Some serve professionals. Others target startups, solo
founders, or non-technical users. Here's a brief look at the current terrain.
### WordPress
Once a game-changer, now a legacy platform. WordPress remains the most used CMS
in the world, largely due to its ecosystem of plugins and themes. For blogs,
personal sites, or heavily templated business websites, it still holds relevance.
But for teams seeking precision, speed, and maintainability — it often gets in
the way. Plugins introduce risk. Performance lags. And unless it's extensively
customised, design output tends to feel heavy or generic.
### Webflow
Webflow earned its place by giving designers real control without a heavy
development cycle. Its visual canvas maps closely to how the web actually
works, its CMS is intuitive, and its SEO controls are native and clear. For
marketing sites managed by non-technical teams, it remains a strong choice.
The trade-offs appear at the edges: platform lock-in, per-site pricing that
scales awkwardly, and a ceiling on what you can build before you're writing
custom code inside someone else's environment. When performance budgets
tighten or requirements grow beyond the front layer, those edges start to
matter.
### Framer
Framer feels like a designer's playground. The interface is intuitive —
especially for those coming from tools like Figma. It's fast, collaborative,
and allows for animated, interactive experiences that are visually rich.
However, its CMS and SEO capabilities are still catching up. For high-volume
sites or structured content needs, it's less mature. Framer excels in
portfolios, landing pages, and experimental work — but is harder to scale or
adapt beyond the front layer.
### AI builders
The promise of AI-generated websites is speed: prompt in, site out. For simple
projects or early-stage explorations, they serve a role. They remove friction —
but also nuance. Customisation remains limited. Design language tends to be
templated. For businesses seeking brand distinctiveness and performance
precision, these tools often fall short.
## Why we build with code
At Point A, we've used most of these platforms — and shipped good work on
them. But our own practice has moved to building with code, using modern
frameworks like Astro, because that's where design freedom and engineering
integrity finally meet without compromise.
Building with code means every page ships as fast, clean HTML with nothing you
didn't ask for. No plugin bloat, no runtime the platform insists on, no
per-seat pricing standing between a design decision and its implementation.
Content lives in structured, version-controlled files that clients can review
and we can migrate anywhere — there is no lock-in, because there is no
platform to be locked into.
It also means the infrastructure is ours to choose. We host on robust
foundations — often Google Cloud — so performance, uptime, and scalability are
never an afterthought. And when a project genuinely needs deep backend logic
or a complex application layer, we're already in the right environment to
build it.
The honest caveat: this approach asks more of the studio than of the client.
A visual platform lets anyone drag a section into place; a codebase asks for
craft and discipline. We think that's the right trade. It's our job to carry
the complexity so the result stays simple.
## What matters most
No tool is perfect. But the best ones get out of the way.
We don't build with code because it's trendy. We build this way because it
respects the relationship between structure and expression. It allows us to
focus on what matters — clarity, craft, and the experience being created —
without wrestling the framework.
If you're building something worth lasting, choose tools that support your
intentions. Not just today, but as your needs grow.
In design, the tool is rarely the point. It's the work that matters — how it
feels, how it functions, how it endures.
But in digital environments, the tool you choose does shape more than aesthetics.
It determines the performance, accessibility, and longevity of what you create.
And increasingly, the design tool becomes the development platform.
So the question becomes: which tool allows you to design with clarity — and
build with precision?
## The landscape
There's no shortage of web design tools today. Some are built for code. Others
for visual flow. Some serve professionals. Others target startups, solo
founders, or non-technical users. Here's a brief look at the current terrain.
### WordPress
Once a game-changer, now a legacy platform. WordPress remains the most used CMS
in the world, largely due to its ecosystem of plugins and themes. For blogs,
personal sites, or heavily templated business websites, it still holds relevance.
But for teams seeking precision, speed, and maintainability — it often gets in
the way. Plugins introduce risk. Performance lags. And unless it's extensively
customised, design output tends to feel heavy or generic.
### Webflow
Webflow earned its place by giving designers real control without a heavy
development cycle. Its visual canvas maps closely to how the web actually
works, its CMS is intuitive, and its SEO controls are native and clear. For
marketing sites managed by non-technical teams, it remains a strong choice.
The trade-offs appear at the edges: platform lock-in, per-site pricing that
scales awkwardly, and a ceiling on what you can build before you're writing
custom code inside someone else's environment. When performance budgets
tighten or requirements grow beyond the front layer, those edges start to
matter.
### Framer
Framer feels like a designer's playground. The interface is intuitive —
especially for those coming from tools like Figma. It's fast, collaborative,
and allows for animated, interactive experiences that are visually rich.
However, its CMS and SEO capabilities are still catching up. For high-volume
sites or structured content needs, it's less mature. Framer excels in
portfolios, landing pages, and experimental work — but is harder to scale or
adapt beyond the front layer.
### AI builders
The promise of AI-generated websites is speed: prompt in, site out. For simple
projects or early-stage explorations, they serve a role. They remove friction —
but also nuance. Customisation remains limited. Design language tends to be
templated. For businesses seeking brand distinctiveness and performance
precision, these tools often fall short.
## Why we build with code
At Point A, we've used most of these platforms — and shipped good work on
them. But our own practice has moved to building with code, using modern
frameworks like Astro, because that's where design freedom and engineering
integrity finally meet without compromise.
Building with code means every page ships as fast, clean HTML with nothing you
didn't ask for. No plugin bloat, no runtime the platform insists on, no
per-seat pricing standing between a design decision and its implementation.
Content lives in structured, version-controlled files that clients can review
and we can migrate anywhere — there is no lock-in, because there is no
platform to be locked into.
It also means the infrastructure is ours to choose. We host on robust
foundations — often Google Cloud — so performance, uptime, and scalability are
never an afterthought. And when a project genuinely needs deep backend logic
or a complex application layer, we're already in the right environment to
build it.
The honest caveat: this approach asks more of the studio than of the client.
A visual platform lets anyone drag a section into place; a codebase asks for
craft and discipline. We think that's the right trade. It's our job to carry
the complexity so the result stays simple.
## What matters most
No tool is perfect. But the best ones get out of the way.
We don't build with code because it's trendy. We build this way because it
respects the relationship between structure and expression. It allows us to
focus on what matters — clarity, craft, and the experience being created —
without wrestling the framework.
If you're building something worth lasting, choose tools that support your
intentions. Not just today, but as your needs grow.