The big CMSes take AI dead seriously. Since 2025 WordPress has been working on official AI building blocks for the whole ecosystem — an SDK, an Abilities API, an adapter for AI agents. Drupal has its own AI initiative with dozens of partners and a roadmap that literally states that every action a user can take must also be doable by an AI agent. That's not marketing talk; it's really being built. And that's exactly where the discomfort is: they're building AI into a structure that only exists because AI wasn't around.
What a CMS is actually for
A content management system bundles three things: a place where the content lives, a screen to edit that content, and a layer that turns it into pages. Two of those three are indispensable — content has to live somewhere and appear somewhere. But the screen in between exists for exactly one reason: people can't write directly into storage. Databases are unreadable, code is scary, so along came a dashboard with input fields, previews, media libraries and an update button.
Everything else hangs off that screen. Roles and permissions exist because there's a login. Plugins exist because the dashboard has to be extensible. Updates exist because all those layers have to be maintained. It's scaffolding around one limitation — and that limitation is disappearing.
What WordPress and Drupal are building now
Look at what the platforms themselves are doing and you see the same move everywhere: AI becomes an extra user of the existing system. The agent gets the same buttons you have. It can create a post, add alt text to an image, start a workflow — neatly within the permissions and approval steps designed for people. Drupal names that explicitly as a design principle: AI under the same governance as the human editor.
That's defensible. WordPress runs on more than forty per cent of the web; those installations aren't switching to a different architecture because something more elegant is possible. Anyone dragging along hundreds of editors, approval workflows and twenty years of content can only add AI as a layer on top of what's there.
But notice what's happening too: the overhead is being automated instead of removed. The AI fills the input fields that existed because people needed input fields. An assistant is being built to operate the scaffolding — while the question should be why the scaffolding is still standing.
The reversal
Turn it around. An AI can write directly into storage. Structure isn't an obstacle for an agent but a foothold: the tighter the content is structured, the more reliably it works with it. The moment the editor no longer needs a screen, the screen isn't a feature any more but ballast — and so is everything hanging off it. No dashboard, so no login. No login, so a lot less to hack. No plugins, so no updates. What's left is the content itself, the structure it lives in, and a log of changes you can roll back. And because there's no longer a system between visitor and content, every page can sit ready-made — as good as static, with the speed that comes with it.
This isn't a distant future. For an informational site — company site, brochure site, portfolio — this works today, and it works remarkably well. The site you're reading this on is managed this way: there's no dashboard to log into.
From CMS to CMS instructions
So a layer disappears, but something comes back in its place — and that's where the real work of the coming years sits. If the agent no longer has the buttons that bound it, the boundaries have to live somewhere else: on paper. What may change and what may not. In what tone things are written. What structure a new page follows, what has to happen with the menu, breadcrumb and sitemap. Where in a classic CMS those rules are locked into field definitions and plugin settings, they now become a readable document that both human and machine follow.
Call it CMS instructions. The centre of gravity of site management shifts from operating screens to drawing up agreements — and the quality of those agreements determines the quality of the site. That also changes what you should assess when you have a website built: not what the dashboard looks like, but how good the structure and the rules are that get worked with afterwards.
What doesn't disappear
Fair is fair: the middle layer has places where it really does work. Five editors working in the same content at once, a web shop with stock and orders, an editorial process with approval steps — there the management layer isn't scaffolding but a tool, and there it will stay. So WordPress and Drupal aren't disappearing. But note what their own roadmaps say: if every action can also be done by an agent, the screen has officially become optional. And what's optional gets left out where it can be. For the large middle segment — single-owner sites that occasionally want to change something — the question isn't whether that layer goes, but when.
What this means for you
If a new website is on the cards, ask a different question than "which CMS will it be". Ask what the management looks like when you want something said rather than clicked. For informational sites, Braaf. already delivers that today as AI CMS: a site without a management system that you then update in plain language — every change recorded and reversible, findability and structured data baked in. No waiting for the roadmap of a platform that first has to tear down its own scaffolding.