WordPress and Astro can build better websites when each takes on the role it is best suited to.
For a long time, building a website meant writing it by hand. HTML, CSS, PHP and JavaScript gave us direct control over every page and every detail. But they also made even small editorial changes dependent on a developer.
When WordPress evolved, it solved a real problem. Clients could manage their own content. They could publish an article, update a service, add an image or correct a detail without waiting for us. That autonomy still matters.
Then came page builders. We worked with WPBakery and moved early to Elementor. The promise was understandable: set up a library of well-designed components, give clients more freedom and make page creation easier.
In practice, most clients did not want to become web designers. They wanted to manage their content and keep control of their data. When a new page, a more considered layout or an important change was needed, they still preferred to work with us.
When one system has to do everything
WordPress can be a very good editorial tool. The difficulty starts when the same installation is expected to manage content, define every visual layout, run a growing plugin stack and generate every public page on every visit.
Over time, that can make a website heavier than it needs to be. Page builders and plugins are not automatically a problem, but a frontend built through years of additions often delivers more code, styles and scripts than a page actually needs.
The result is harder to maintain and harder to improve deliberately. That matters because the public website should be focused. It should load cleanly, communicate clearly and reflect the quality of the organisation behind it.
We kept WordPress. We changed its role.
Today, we still use WordPress for many projects. It remains a familiar and practical place for clients to manage pages, articles, media, team profiles, services and structured content.
The public-facing website is built separately with Astro. This is a headless setup: WordPress is the editorial backend, while Astro is responsible for the frontend visitors see.
That separation is useful because each part can do its job properly.
- WordPress gives editors a clear place to manage content
- Custom post types and fields keep recurring content structured
- Astro gives us precise control over layout, performance and code sent to the browser
- The frontend can be built around the project rather than around a generic theme
Most pages do not need to be generated on every visit
Some website features need to be dynamic: a client portal, real-time availability, a checkout or personalised data. But most pages on an organisation’s website do not change every minute.
A service page, a case study or an article can usually be generated when the site is deployed or updated. Astro allows us to do that while keeping dynamic behaviour for the parts that genuinely need it.
Instead of treating the whole website as a live application, we decide what needs to be live. That creates a leaner public output and gives us more control over performance, image handling, metadata, structured data and the technical foundations of SEO.
Autonomy without turning the website into a design tool
A headless setup does not take control away from clients. It makes that control more useful. Clients can still manage their content, media, SEO fields and structured information. We define the editing experience around what their team actually needs to maintain.
Some areas need freedom. Others need structure so the visual identity and the user experience remain coherent over time. Giving every editor unlimited layout control is rarely the same thing as giving them autonomy.
A practical choice, not a fashionable one
We do not use the same stack for every project. A small campaign page, a temporary site or a project with limited editorial needs may call for a simpler solution. The right architecture depends on the organisation, its content, its internal team and the role the website has to play.
But when a client needs a website that is easy to manage, visually precise and technically controlled, WordPress and Astro are a strong combination. WordPress remains the editorial workspace. Astro becomes the public-facing website.
That lets us keep what clients value about WordPress while building a cleaner frontend from the ground up.









