I saw a post on LinkedIn the other day from a self-proclaimed 20 year agency veteran of WordPress saying that was it, they’re moving the entire agency off of WordPress and onto AI. Now, because I, too, am a 20 year veteran of WordPress, this kind of story catches my attention. He posted that they just rebuilt his agency’s site in a fraction of the time and he was never again going to use WordPress. It doesn’t matter who this person was because, honestly, this is a story that’s been cropping up a lot lately. The idea was that they can use Claude Code or other AI tools to build sites to spec faster than they ever could with WordPress, so they’re pivoting their entire businesses to this model.
In the midst of this, longtime WordPress icon 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). And it seems like for some folks, that idea means that you should shift your entire WordPress business, your personal WordPress sites, to some AI-generated thing where it’ll be so much easier because rather than having to log into an admin panel to change your store hours, you can just use an AI tool like Claude Desktop or ChatGPT (which you’re obviously already using daily) and tell the AI to make the change for you. Your interface into managing your site is through an AI interpreter. This is the future we wanted, right?
Joost isn’t wrong. Not every site does need a CMS. But that idea is old enough to drink. Ever since CMSes came into existence, we’ve been saying “not every site needs a CMS,” so putting a coat of paint on an old adage and proclaiming that AI is the answer from on high with a pair of stone tablets is not unique. It’s riding on the coattails of the AI hype train. A landing page, a simple portfolio, a personal blog — these never needed a CMS with a database, a PHP runtime and a plugin ecosystem. I will still personally argue that a CMS makes them easier to manage, but they never needed a CMS.
And Joost is careful to point out that just because his blog is running on Astro doesn’t mean he’s abandoning WordPress. WordPress is still his tool of choice for more complex projects. And he’s been around long enough to know what the tradeoffs are. For a long while, just having a CMS was maybe a bit of potentially expensive icing on the cake of having a website. And maybe if there’s a faster way to edit content, via Google Docs (e.g. Pantheon Content Publisher) or Markdown, you never actually need a CMS backend.
Fine.
But the idea that AI can migrate your entire site away from your current stack seems incredibly shortsighted.
I’ve spent the last month building next.jazzsequence.com — a Next.js-based reimplementation of jazzsequence.com that’s entirely headless without any loss of functionality. I think it’s great and I genuinely hope that you are reading this post on that site. but the thing that occurs to me, as someone who’s been doing this for 20 years is…
Have we actually learned nothing?
Because sure, AI can spit out a new, modern site and migrate everything out of WP or Drupal. But…to what? A new JavaScript-based site using the latest framework du jour?
Have we forgotten how quickly the JavaScript landscape changes? How many frameworks have risen and fallen in the last 10 years?
Have we forgotten dependency hell? When you want to keep your packages up to date, but Package A depends on Package B and Package B can’t be updated because Package C is a subdependency that didn’t get updated recently and now you’ve got a security vulnerability in your stack that’s unresolvable because of conflicting package dependencies.
Just because AI can (maybe) manage that stuff and Dependabot is a thing that exists doesn’t make those problems go away. It just hides them under a layer of sycophantic chatbot-induced security. Do you really think users are going to want to manage NPM dependencies? Even the people celebrating AI-powered dependency management are proving the point: one blog found 22 outdated packages including major breaking changes on an Astro blog that was left alone for a year.
The first video I recorded for the Pantheon YouTube channel after becoming a Developer Advocate asked the question “is more Gutenberg really the future we want?” Now I have a new question: is working in an AI tool really the editing solution that we’re looking for? One that’s superior to the admin panel of WordPress or Drupal?
For all of the WordPress admin dashboard’s apparent flaws, it does succeed in giving publishing and editing power to people who don’t want to learn code (or Markdown, or Git) in a way that the Drupal ecosystem is trying to adapt to now with a more simplified admin user experience and curated recipes and templates. If the core premise is “your IDE will be Claude Desktop,” I have to ask, is that really what we want? When a non-technical person changes their store hours in a WordPress site, they can hit Save and look at the site and see that something happened. When you’re sending your command through a chatbot, you’re fundamentally trusting the chatbot to perform the action you requested, in the way that you requested it, correctly and accurately. That’s actually handing the keys to the castle to your robot butler and hoping nothing weird happens. If we’ve learned anything since the initial release of ChatGPT, LLMs are great at making weird shit happen. And you still need to verify the AI did the thing you asked. You just successfully moved the complexity to a different part of the stack.
WordPress is not absent in the AI-powered future, either. You don’t need to throw away your CMS if you do want an AI to change your store hours. MCP server support in WordPress core exists (I should know, I implemented it on this site). There will be more and more of this built into core in the coming releases, making it easier, not harder, to connect your AI brain to your WordPress site if you so desire.
So, what’s really underneath the pitch to migrate your site away from WordPress to an AI-generated, modern, JavaScript-infused site? Could it be that these vendors that are jumping on the “I’ll migrate your site away from WordPress/Drupal for you” bandwagon are really just creating demand for their own businesses, riding the hype train of AI and taking a lowest common denominator solution, misrepresenting the trends and actual conversation, vilifying the actual projects that are helping people and locking themselves in as a vendor of choice because they’re the only ones who know how to maintain your AI-generated site now?
That’s just vendor lock-in in a trenchcoat. If you hire someone to migrate your WordPress site to an AI-generated site on the cheap and you need to change or update something? In WordPress you just log in, or hire any of a thousand developers to do the thing for you. Your bespoke, artisanal AI-generated Astro/Next/Whatever.js site? You’re calling the agency that built it. Builder.ai collapsed and clients lost access to everything. That’s the extreme end of the spectrum of when your site depends on a specific vendor’s knowledge and tooling.
I’ve spent a month with Claude Code, slowly reimagining this site. In fact, I hope you’re reading this on the reimagined version of this site. But the conclusion I came to wasn’t “I need to get rid of the CMS parts” it was “abso-fuggin-lutely KEEP the CMS.”
I started blogging when it was still called a web log. It was hand-coded HTML FTP’d to a server in San Francisco. Eventually this site evolved into using a blogging platform called sBlog, and that eventually migrated into WordPress. I kept every post — even the hand-coded HTML ones — and migrated every one. There is, no shit, 24 years worth of content on this site. I’m sure it’s not difficult for an AI to take all that data and turn it into markdown or whatever, but it’s inevitable that with something that’s evolved over the course of 20+ years, you’re not going to collect everything. Instead, I wanted to preserve everything I could. My weird games page. The personalization I added to the homepage on a whim. The articles and speaking appearances for other sites. I wanted a modern presentation layer on top of the thing that was working rather than blowing everything up.
AI doesn’t make your CMS obsolete. I’d argue that AI can (but it doesn’t have to) make your site more powerful by allowing you to build on top of native WordPress primitives like the REST API, Abilities API and MCP adapter capabilities shipping in modern WP. The latter two mean that AI can interact with your site directly without losing 20 years of architectural history that went into building this thing.
Yes, I signed myself up for dependency hell, too, by implementing a headless front-end based on a JavaScript framework. But I did that because I know what that hell looks like. I’ve been there before. And I’m not saying you should do it, too — especially if you don’t want to be managing dependencies until you wish you could claw your eyes out. It’s not abstract, it’s a familiar pain. And I didn’t rebuild this site over 10 days, either. It’s taken over a month of careful migration, architectural decision making, testing and developing best practices.
The magic triangle is still a lie. You can’t build fast, cheap and good. You need to pick two. If someone is telling you otherwise, it means they’re prioritizing “how fast can you ship” over “how long will this last.” The part of WordPress that’s always been most interesting to me isn’t necessarily the presentation layer. It’s the APIs and permissions and workflows and data and extensibility in the code of a project that’s evolved and grown for 24 years.
Who actually benefits from the wave of sales pitches to migrate your site off of your CMS? Not end users, who now need a developer (and/or an AI subscription) to update their hours. Not site owners, who traded a well-understood maintenance burden for a poorly-understood one. Obviously the agencies and consultants and LinkedIn posters that are building a business on the back of the AI hype cycle.
On April 1, Cloudflare introduced EmDash, “the spiritual successor to WordPress,” in TypeScript and Astro with a sandboxed plugin architecture for security. They could have built a static site generator or something distinctly not a CMS for human use if they thought that that’s where the wind was blowing. Instead, they built something that is fundamentally architected in a way that AI can consume and operate, but with a human interface because it’s built for humans to actually use it. Instead of saying “ditch your CMS,” they said “no, actually, migrate your CMS to this new, better CMS.” In fact, that’s exactly what Joost did two weeks after saying he was done with CMSes. Because there’s still a place for a CMS.
We’re still having the same conversation we’ve been having for 20+ years: use the right tool for the job. The factors that determine the “right tool” vary — from what your team is fluent in to the easiest thing to maintain on a long timeline. History and impetus matters. I have never been interested in migrating my blog away from WordPress because there’s so much content — in a variety of different forms — that I’ve built into this Frankenstein machine that I don’t want to lose. But if all I had was a website advertising for my development agency, yeah, that’s something I probably don’t need all of WordPress to maintain.
I’m not saying don’t migrate your site away from WordPress (or Drupal, I’m equal opportunity) to Astro or EmDash or some other framework with AI embedded into its guts if that’s what you want to do. I just think that the grass isn’t necessarily greener on the other side of the fence. When it comes down to it, human labor is ultimately the weak link whether we’re talking about a human that’s managing WordPress plugin or Drupal module updates or a human that’s accepting code changes from an AI agent or Dependabot to update JavaScript dependencies. There will probably be a future where humans are taken out of that loop. But I don’t even think that, when that day comes, it will be particularly obvious which implementation is actually superior, because in the end, an AI can update WordPress plugins as easily (or easier) as it can bump an NPM package dependency. So, I call “bullshit” on the idea that CMSes — and specifically WordPress — are dead.
Leave a Reply