WordPress might not always need to be the frontend. Perhaps its future is being the backend to everything else.
There seems to be a growing feeling that WordPress is on its way out. AI can build websites in minutes, Astro and other modern frameworks can deliver incredibly fast static sites, and the traditional WordPress approach is starting to look increasingly outdated.
I understand the argument. In some respects, I even agree with it.
But I'm not giving up on WordPress just yet.
And I think there's a fairly significant difference between recognising that something needs to change and deciding that everything you've spent years building is suddenly worthless.
£10,000 of Reasons Not to Walk Away
I've invested somewhere in the region of £10,000 in WordPress plugins, lifetime deals and the capabilities that come with them.
That's before we even begin to put a value on the knowledge I've accumulated, the workflows I've developed and the ability to sit down with WordPress and know exactly how to build something.
I'm not particularly interested in throwing all of that away because AI can generate an Astro site faster than I can build something in WordPress.
Speed is useful. It isn't everything.
I can launch a WordPress website tomorrow morning and potentially be selling products by lunchtime.
Not a basic brochure website. A functional e-commerce operation with payment processing, memberships, restricted content, automations and whatever else I need.
Depending on the project, I could build that around Easy Digital Downloads, WooCommerce, SureCart or FluentCart.
I've already got the tools. I understand how they work. And with some of those options, I can operate without additional platform transaction fees beyond payment processing and the hosting I'm already paying for.
That has real value.
It might not be exciting. It might not make for an impressive AI-generated demonstration.
But it works.
The Problem With the Next Shiny Thing
One thing I've noticed about this new AI-powered, static-first world is just how quickly we're encouraged to abandon our existing stacks.
There's always another platform. Another framework. Another premium subscription that promises to simplify everything.
And quite conveniently, another reason to abandon the lifetime deals we've already purchased.
I'm increasingly wary of that.
Just because something is new doesn't automatically make it better. Just because AI can generate it doesn't mean it's easier to maintain. And just because a modern stack looks cleaner on paper doesn't mean it's more appropriate for every project.
There is technical debt in WordPress.
I'd be an idiot to pretend otherwise.
Years of backward compatibility, competing plugin approaches, legacy architecture and an ecosystem that hasn't always moved in the same direction have created genuine problems.
But technical debt isn't unique to WordPress.
Building a collection of AI-generated applications, external services, custom integrations and monthly subscriptions can create its own technical debt.
The difference is that we haven't necessarily lived with that debt long enough to appreciate what it looks like.
We shouldn't confuse starting again with making progress.
I Want AI to Support Me, Not Necessarily Lead Me
This is probably one of the biggest differences in how I'm approaching things.
I'm comfortable with WordPress.
I understand PHP reasonably well. I understand the WordPress architecture, how plugins interact, how to approach problems and where things are likely to go wrong.
I can use AI as an agent to support what I'm doing without needing it to lead every decision.
With Astro, that's different.
I know considerably less about Astro than I do about WordPress, and I'm comfortable admitting that.
If I'm building something with Astro, I'm much more dependent on an AI agent. It can do the work, and often do it extremely well, but there's a difference between using AI to accelerate something you understand and depending on AI to manage something you don't.
Neither approach is inherently wrong.
I'm perfectly happy being agent-led when I'm experimenting with technologies I don't know particularly well.
But I don't see why I should voluntarily abandon an environment where I already have years of experience simply because being agent-led is becoming the fashionable way to build software.
Sometimes, knowing what you're doing is still an advantage.
Maybe WordPress Doesn't Need to Be the Frontend
This is where my thinking has started to change.
For a long time, WordPress has been presented as the complete solution. The content management system, the frontend, the theme, the plugins and everything else sitting together.
And perhaps that's the part of WordPress that needs to evolve.
Maybe WordPress doesn't always need to be the frontend anymore.
Maybe it becomes the back office.
The content management system. The e-commerce engine. The membership platform. The automation centre. The place where the complicated things happen.
And the frontend?
That could be Astro. It could be static HTML. It could be something generated by AI. It could be whatever makes sense for the particular project.
I've been working with Simply Static for a long time, so this isn't an entirely new concept to me.
The idea of using WordPress to create and manage something while delivering a static frontend is something I've been interested in for years.
More recently, I've experimented with making FluentCart work in a static environment.
And in some respects, I think that experiment proves just how much life there is left in WordPress.
Rather than proving that WordPress is unnecessary, it demonstrates that we can take the considerable capabilities of the WordPress ecosystem and use them in different ways.
We don't necessarily need to throw away the backend to modernise the frontend.
Static Doesn't Have to Mean Starting Again
Let's say I want a static website.
That's fine.
I can build one.
I can use Simply Static to generate it from WordPress, or I can use a completely different frontend.
But what happens when I want a contact form?
I could use a WordPress-powered form built with Craft Forms.
What if I want to automate what happens when somebody submits it?
I've already got FlowMattic.
What if I need e-commerce functionality, membership management, restricted content or a more complicated workflow?
Well, I've already got an entire WordPress ecosystem capable of handling those things.
And if WordPress is sitting behind the scenes, properly secured and separated from the public frontend, I can potentially reduce the exposed attack surface while keeping many of the capabilities I've spent years accumulating.
It isn't automatically secure simply because it's headless, of course. The APIs, integrations, authentication and backend still need protecting.
But it gives me options.
I can have a lightweight static frontend without necessarily sacrificing everything that makes WordPress useful.
That's the part I find interesting.
Not WordPress versus Astro.
Not traditional websites versus AI-generated websites.
But the possibility of combining them.
The Things That Look Simple Until You Need Them
I think there's another issue that sometimes gets lost in the excitement around modern frontend development.
A lot of things that WordPress makes relatively straightforward become considerably more complicated when you're working with a static-first architecture.
Take memberships.
Or restricted pages.
Or selling digital products with different access rights.
Or integrating payments with customer accounts, email automations and content permissions.
All of those things are achievable without WordPress. I'm certainly not suggesting otherwise.
But there's a difference between something being technically possible and something being practically convenient.
Within WordPress, I can often solve these problems using tools I already own, understand and trust.
Outside WordPress, I may find myself building custom functionality, connecting multiple services or taking on another subscription.
And suddenly that wonderfully simple static website isn't quite so simple anymore.
The frontend might be simpler.
The overall system might not be.
WordPress Needs to Adapt, Not Pretend Nothing Has Changed
None of this means I think WordPress can carry on exactly as it is.
It can't.
I've seen platforms fail to adapt before, and MODX comes to mind when thinking about how a capable CMS can lose ground as the wider market changes.
WordPress has a much larger ecosystem and a different position in the market, but that doesn't make it immune.
AI is changing how websites are built.
Modern frontend frameworks are changing what people expect.
And the idea that every website needs WordPress controlling the entire experience is becoming increasingly difficult to defend.
WordPress needs to work with AI rather than against it.
It needs to become easier for agents to interact with, easier to use through APIs and easier to separate from the frontend.
Perhaps it needs to stop presenting itself primarily as the thing that builds your website and start presenting itself as the engine that powers whatever website you want to build.
That's quite a significant change in positioning.
But I think it's one worth considering.
WordPress already has so many of the difficult parts solved.
Content management. Users. Permissions. E-commerce. Extensibility. Integrations. Automations.
Those things still matter.
And I suspect they'll continue to matter long after we've moved on to the next fashionable frontend framework.
There's Value in Being Comfortable
I'm not sure we talk enough about the value of familiarity.
There's a tendency in technology to treat comfort as something negative.
If you're comfortable with an existing stack, perhaps you're not moving quickly enough. Perhaps you're resisting change. Perhaps you should abandon everything and embrace the latest approach.
I don't particularly agree.
Being comfortable with WordPress doesn't mean I'm incapable of recognising its weaknesses.
It means I know what I can achieve with it.
It means I can make informed decisions about when to use it and when not to.
And it means that when somebody needs a website with complicated functionality, I can often get something working without spending days working out which external services need connecting.
There's a real commercial advantage to that.
I'm not blindly using WordPress for everything.
I'm increasingly interested in static websites, AI-driven development and modern frontend technologies.
I've been experimenting with them, and I intend to keep experimenting.
But I don't feel any particular urgency to force myself away from something that's still delivering value.
I'm Not Giving Up on WordPress Yet
I could be completely wrong about all of this.
I frequently am when it comes to predicting exactly how technology will develop and which approaches will eventually win.
Perhaps AI-driven development will make traditional content management systems largely irrelevant.
Perhaps platforms like Astro will continue to take more of the work that WordPress historically handled.
Perhaps the next generation of tools will make the capabilities I've accumulated through WordPress plugins available in entirely different ways.
All of that is possible.
But I'm not convinced the answer is to abandon everything today.
WordPress still has an extraordinary ecosystem. It still solves complicated problems. It still allows me to launch capable websites quickly, and it still gives me a level of control and flexibility that I value.
More importantly, it doesn't have to remain the centre of the frontend experience to continue being useful.
I increasingly think its future might be behind the scenes, powering static sites, modern frameworks and AI-generated frontends through APIs and integrations.
A more protected, less exposed WordPress installation doing the complicated work while something else handles what visitors actually see.
It's not a perfect solution.
There are compromises, architectural challenges and limitations that need to be acknowledged.
But there's also an awful lot of potential.
I don't think WordPress is dead. I think the role WordPress plays might be changing.
And until I have a genuinely compelling reason to give up the tools, experience and capabilities I've already invested in, I'm in no rush to walk away.
I'm happy to use AI.
I'm happy to build with Astro.
I'm happy to create static websites.
And I'm equally happy to let WordPress sit quietly in the background, doing what it's always been rather good at.
Because the future doesn't necessarily have to involve throwing away the past.
Sometimes, it just involves finding a better way to use it.