There is indeed not always a need for WordPress. I have been using ProcessWire (1) for over a decade. Open-source, zero dependencies, no-nonsense CMS — and when it comes time to build a new website, I go back to it even in 2026, because you make it once and it works for 10 years and counting.

Cloudflare is just jealous that most of their customers are actually running WordPress, but this is not something they will be able to solve with AI hype.

1. https://github.com/processwire/processwire

The same way coding agents don’t replace the need for an IDE, content generation needs to support arbitrary human-to-agent handoffs, where the human can say “this is the wrong direction, I sketched this change of what I want it to look like, see how it’s different and apply that pattern.”

And, in the broadest sense, that human interface is a CMS; the agent is just another editor, albeit one that happens to read and write raw data rather than using a WYSIWIG (or similar) editor.

I’m not sure that I buy all the points made. I can imagine an AI centric CMS where the technical interface (implement this site on MySQL, host it there, use Next.js, etc) is distinct from the content interface (change store hours) or even the design (change the background).

I have used Wordpress a lot (too much) and came to the view that for most websites it is just overkill. So I built https://harcstack.org and vowed to write all my new sites in actual code.

HTMX to the rescue since you can write server side code in a sensible way and still have quite a dymanic UX.

I never really understood the argument, you can design the frontend with AI anyway and then use WordPress as the CMS for clients. Clients want to be able to log in, update CPTs, edit a calendar, post pictures, things like that. Surely the idea isn't to vibe-code an admin panel/cms from scratch for every project?

> Joost de Valk, founder of Yoast SEO, wrote about how he migrated his personal blog from WordPress to Astro, the hottest new JavaScript framework in town, and suggested the blasphemous idea that not all sites need a CMS (he’s since migrated again to EmDash, which I talk about later)

That's a weird thing to read. (Not criticism for the author or the article)

> Migrated his personal blog

Is that a thing worth mentioning? I did that over a decade ago.

> Astro, the hottest new JavaScript framework in town

I thought it's 2026 now, not early 2010s. People still do that?

> the blasphemous idea that not all sites need a CMS

Is it? People still haven't accepted this?

I expect the bigger risk to dynamic database-backed CMS platforms right now is that AI assistance makes static site generator tools run against a version controlled repository of content less intimidating for most users... and static sites are cheaper to run (especially in this era of badly coded scrapers flooding the internet) and much less likely to fall vulnerable to security problems.

I expect we'll see a further wave of CMS interfaces which provide a nicer editing experience on top of flat files stored in Git.

Maybe the strategic move for platforms like WordPress (and maybe Django too! The Django admin remains a very popular CMS platform) is to invest more in separation of admin editing from serving, such that there's an obvious path to edit your content in the CMS but deploy it as static files.

My own blog uses the Django admin and serves the site via Django (albeit behind a 15m Cloudflare cache to handle traffic spikes) but I have a scheduled GitHub Action that backs up the content to a Git repository: https://github.com/simonw/simonwillisonblog-backup - it's not much of a stretch from that to having the Git repository feed content to a static site generator.

CMS is pretty much alive, even if most of them are now headless, oriented towards MACH deployments and AI based workflows.

> But that idea is old enough to drink

Nice turn of a phrase! I was surprised it was a GoogleNope except for you, op.

Wordpress, like SQL, is probably immortal.

But it needs a better headless capability. Most separate front ends appear to be grafted on relying on plugins. Which doesn’t make a whole lot of sense.

I have built a product which uses AI to built Astro sites. LLM builds the sites in steps and make sure that they get 100/100 scores in pagespeed insights. These sites are served with a CDN. You can edit the sites with LLM interface, or use markdown editor to edit sites, or edit texts directly on a dashboard. These sites are static. There is no vendor lock in. If you want to migrate and manage yourself, just go to cloudflare or github pages. These sites cost 0 eur to run, and they always score better in all benchmarks compared to sites that are built on top of a separate CMS server.

I know WordPress is going nowehere and if there is some special backend functionality, that is needed. But 95% of web does not need it.

A static site is always cheaper, and the bottleneck has always been that editing code is indimidating. Therefore, AI actually resolves a big problem here, and this is going to alter the future of platforms like WP.