Which CMS fits a website built with Claude Code?

Claude Code is very good at building a website and has nothing to say about what happens next. The site it writes is a folder of files: HTML, CSS, maybe an Astro or Next.js project. There is no login, no admin screen, no "edit page" button. That's fine until the first message from the client: "Can I change the opening hours myself?"

This guide compares the realistic ways to add editing to a site built with Claude Code (or any other AI tool that writes code), what each one needs from you, and what it costs as of November 2026. Prices and plan limits come from the vendors' own pages.

Key takeaways

• More and more sites ship without a CMS. In our 2026 study of new companies, 36% of the websites we could verify were built as code with no CMS or website builder behind them.
• A Git-based CMS is the cheapest add-on, but it edits content files, not your pages. Expect to restructure the site first.
• Visual editing on plain HTML is rare. CloudCannon and managed platforms do it. Most other tools need a static site generator.
• A headless CMS is usually overkill for a ten-page business site.
• Decide before you hand over: if you keep changing the code with Claude while the client edits in a CMS, you both write to the same files.

Why this question keeps coming up

The share of websites without any content management system is not small. In our 2026 study of 1,536 new German companies, 36% of the 203 websites we could verify were built as code, with no WordPress, no Wix and no other system behind them. A quarter showed no recognisable system at all. Between 2.5% (a clear fingerprint of an AI site builder such as Lovable or v0) and 15% (modern code in exactly the style AI tools write) were very likely made with AI. Among established businesses the share is far lower: in our study of 2,538 small-business websites, 0.4% were made with an AI site builder and at most 3.1% look AI-written.

Every one of those sites gets the same request sooner or later. Somebody who doesn't open a terminal wants to change a price, swap a photo, or add a page.

What the editor actually has to handle

Before you pick a tool, look at what a small business site really contains. When we copy websites to move them, our copier records the interactive parts it finds on each one. Across the sites we copied in 2026:

ShiftPress data, 2026: elements our site copier detected on the websites we copied for moves in 2026, mostly WordPress. Share of sites, one site can have several.

The lesson: most editing is text, pictures and the odd new page, but the text often sits inside something interactive. A CMS that only manages blog posts in Markdown won't help with the answer inside the third accordion on the services page. And whatever tool you choose must not break the form, because a broken contact form costs the client enquiries without anyone noticing.

The five options compared

1. Keep editing with Claude Code

The honest default. If you built the site and you will keep making the changes, you don't need a CMS. Claude Code edits the files, you check the result and push it. It breaks down the moment the client wants to do it themselves, or when you have twenty client sites and every small change becomes a ticket for you.

2. A Git-based CMS: Decap or TinaCMS

Decap CMS (formerly Netlify CMS) is an open source editor that runs in the browser and commits every change to your repository through the GitHub, GitLab or Bitbucket API. It works with most static site generators. TinaCMS is also Git-backed and edits content stored as Markdown, MDX or JSON files, with visual editing for React sites. Its free plan covers 2 users; the Team plan costs $24 per project a month.

The catch for a Claude Code site: both tools edit content files, not finished pages. If Claude wrote your homepage as one long HTML file, there is nothing for the CMS to grab. You first ask Claude to split the content out (see the prompt below), and you need a login setup for every editor.

3. CloudCannon: visual editing on top of the code

CloudCannon is a Git-based CMS with visual editing, built for agencies. It supports the common generators (Astro, Eleventy, Hugo, Next.js and others) and, according to CloudCannon, also plain static files. Plans start at $49 a month billed yearly ($55 monthly) with 3 users, after a 21-day trial. We compared it in detail in CloudCannon vs ShiftPress.

4. A headless CMS: Contentful or Sanity

A headless CMS stores content in its own database and hands it to your site through an API. Sanity's free plan includes up to 20 seats and 10,000 documents; Contentful's free plan includes up to 10 users. Powerful, but your site has to be rebuilt to fetch its content from that API, and someone has to model every content type first. For a ten-page business site that is a lot of machinery. More in Contentful vs ShiftPress.

5. A managed platform: upload the finished pages

The last route skips the CMS question. You build the site with Claude Code, export the finished HTML pages, and upload them to a platform that turns them into editable pages. This is what ShiftPress does: upload a ZIP of plain .html pages (or a Claude Design export, up to 30 pages per file), and each one becomes a real page.

• Click to edit: the client clicks a text and types. It's plain text only, so they can't break the layout. Images are swapped the same way.
• Bigger changes by chat: "add a team page" or "move the prices above the contact form" is described in a sentence, and the AI builds it for review before it goes live.
• Shared header and footer: a change to the menu can be applied to every page at once.
• Safety net: every page has a version history with one-click restore, and forms send enquiries to a leads inbox.
• No lock-in: you can download the whole site's code as a ZIP at any time.

The trade-off: you stop developing the site in Claude Code. The platform becomes the place where the site lives.

How to choose: three questions

1. Who edits? Only you: keep Claude Code. A client who is comfortable with a form: Decap or TinaCMS. A client who wants to click on the page itself: CloudCannon or a managed platform.
2. What do they change? Blog posts and team members are collections, which every Git CMS handles well. Text inside accordions, tabs and hero sections needs visual editing on the page.
3. Will you keep coding? If you keep changing the site with Claude Code while the client edits in a Git CMS, you both commit to the same files. Pull the client's changes before every Claude session, or agree who owns which files.

Making a Claude Code site CMS-ready

If you go the Git CMS route, let Claude do the restructuring. A prompt that works:

Move all editable content out of the page templates into content files:
    one Markdown file per blog post and team member, and one JSON file per page
    for headings, texts and image paths. Keep the header and footer in a single
    shared component. Then add a Decap CMS config with a collection for each
    content type. Don't change the design.

Check the result page by page before you hand it over. Our guide to building a website with Claude Code covers the setup around it, and how to edit a static HTML website covers editing without any CMS. For the wider market, see our CMS comparison. The quickest version of all this is to let ShiftPress build the first draft and spend your time on the facts only you know.

Building sites for clients? Web designers who hand sites over to clients can join our partner network.

Frequently asked questions

The bottom line

A site built with Claude Code doesn't need a CMS until someone else has to edit it. When that day comes, a Git CMS is the cheapest add-on if the content can live in files, CloudCannon is the agency tool for visual editing, and a headless CMS is for bigger projects. If the client simply wants to change their own site, moving the finished pages to a platform built for that is usually less work than building an editor around the code.