CMS for Nuxt sites, no studio to learn.
Whether your content sits in Nuxt Content markdown or in the components themselves, your client edits it by chat, and every publish is a plain commit your host rebuilds from.
No credit card, cancel anytime.
The Nuxt handoff problem
Nuxt gives you good content options, and none of them quite solve the handoff. Nuxt Content keeps Markdown in the repo, which is tidy, but editing it still means a developer or a form UI. Nuxt Studio adds a hosted editor over Nuxt Content, but it is one more tool the client learns, and it only reaches the content that lives in Nuxt Content, not the copy sitting in your pages and components. A headless CMS means a schema and fetch calls. Do the edits yourself and every wording tweak is your job.
CMS Brew works from the repository side and does not care which of those you used. It maps the editable text and images across your Nuxt Content files and your components alike, the client edits in chat, and each publish is one commit that triggers your normal build.
Content module optional
Nuxt Content, plain components, or a mix: CMS Brew maps the editable content from the repository either way. There is no structure to adopt and nothing to migrate into.
No editor for the client to learn
Instead of a hosted studio tied to one content source, the client describes the change in chat and sees it in a live preview. Nothing to install, nothing to teach.
Safe enough for clients
Per-field guard levels decide what publishes freely and what waits for review, and requests for new pages, layout, or code are refused in the chat and escalated to you with the client's words attached.
Side by side
CMS Brew vs Headless CMS
| CMS Brew | Headless CMS | |
|---|---|---|
| Integration work | Connect the GitHub repository. That is the setup. | Install an SDK, define a schema, rewrite pages to fetch from an API. |
| Where content lives | In your repository: Nuxt Content files, pages, and components. | In the vendor's database, behind their API. |
| What the client learns | Nothing. They type what they want changed. | The studio UI and your content model. |
| Publishing | One commit; Vercel, Netlify, or Cloudflare rebuilds as usual. | A webhook from the CMS triggers your builds. |
| Review before publish | Per-field guards and a review queue, included. | Roles and approval workflows, usually on higher tiers. |
| Cost model | $39/mo for 5 sites, unlimited editors. | Per-seat pricing that grows with every editor you invite. |
The honest trade-off
If a site needs thousands of structured entries, localization pipelines, or content shared across several apps, a real headless CMS earns its schema, and Nuxt Content is a fine fit when a developer stays in the loop. CMS Brew is for the other case: the delivered client site where the person editing is not a developer and should not have to be.
How it works
Three steps, then it's live.
- 01Connect
Point it at the site you built
CMS Brew turns it into a simple list of things your client can edit. No rebuild, no plugin.
- 02Edit
Clients edit in plain words
Your client opens a chat and says what to change: a phone number, a headline, a photo. They see it live before it ships.
- 03Publish
Safe changes go live
Safe edits publish in one click. Bigger requests, like a new page or code, come straight to you.
FAQ
What people ask before switching.
Stop being the person who updates the phone number.
Give your client the keys to the content. Keep the keys to the code.
Prefer to talk first? Book a 30-minute call