Content management systems were built for a world where humans typed into boxes. AI generates, structures, and updates content directly. The CMS is now the model plus a folder of context.
For 20 years, the content layer of the internet has been a CMS, a box-and-form system that lets a non-technical person change a headline without calling a developer. WordPress, Wix, HubSpot, Webflow, Squarespace, Notion, Contentful. The CMS gave non-engineers leverage. It also locked them into someone else's design grid, someone else's roadmap, and someone else's monthly bill.
That trade is over. With AI in the loop, a non-engineer can change a headline, restructure a page, add a new component, or rebuild an entire section by describing what they want. The intermediary, the CMS, is now overhead.
For 20+ years the CMS held three jobs in one product. WordPress, HubSpot, Webflow, Squarespace, Notion are each a slightly different flavour of the same shape. Once you separate the three jobs, you can see why AI dissolves the whole category.
Take the three jobs apart and AI absorbs each one cleanly. The middleman, the CMS, becomes overhead.
Most operators still ask, what is the CMS for this site. The new question is, what is the prompt for this change. You stop choosing tools by their admin panel and start choosing them by how cleanly an agent can change them.
This shift is uncomfortable for one week and then permanent. The first time you change a price by prompt, ship to production, and watch it propagate in 45 seconds, you stop missing the CMS forever.
AI replaces the CMS, not the editor. You still need a way to make changes. The skill being learned is the editor skill in its new form: describing changes precisely enough that an agent can execute them.
A vague prompt produces a vague change. A precise prompt produces a precise change. Most of the new craft is on the prompt side, not the prose side.
You need the Hello World site from Protocol 02. If you do not have it, do that exercise first. Open Claude Code in the repo and keep your Vercel tab open so you can watch deploys land.
Tell Claude: "Change the homepage headline to read [your new headline]. Keep the existing styling." Accept the diff. This is the change you used to make in the CMS's text field.
Tell Claude: "Below the headline, add a three-column section: Who I am, What I do, Get in touch. Each column is a short paragraph." Accept the diff. This is the change you used to make with a drag-drop builder.
Tell Claude: "Change the accent color from blue to dark green, and the page background from white to cream." Accept the diff. This is the change you used to make in the theme editor.
Tell Claude: "Commit all three changes with the message: site refresh, copy + structure + colour. Push to main." Claude runs the git commands.
Switch to your Vercel tab. The build runs in under a minute. Refresh your URL. All three changes are live.
Three changes covering text, structure, and styling shipped in 15 minutes without opening a single admin panel. You just deleted the role the CMS used to play in your stack.
At the retreat you take three things you would normally do in a CMS, do them by prompt instead, and ship the changes live to your own domain in under 30 minutes.