# 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.

## Your client edits the page, not a form. Risky changes wait for you.

CMS Brew maps the text and images across your Nuxt Content files and components alike, and the client edits them on the page or in chat. Per-field guards decide what publishes on its own and what waits for you.

- Nuxt Content, plain components, or a mix, with nothing to migrate into
- No hosted studio for the client to learn
- New pages, layout, and code go to you, in the client's words

## CMS Brew vs Traditional headless CMS, side by side

| | CMS Brew | Traditional headless CMS |
| --- | --- | --- |
| Integration work | Connect the GitHub or GitLab 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. |

## Where the other option wins

If a site needs thousands of structured entries, localization pipelines, or content shared across several apps, a traditional 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.

## FAQ

### Does CMS Brew work with Nuxt Content, or only with components?

Both. CMS Brew maps the editable text and images wherever they live in the repository, whether that is Markdown in your Nuxt Content directory or copy inside your pages and components. It handles dynamic routes like /blog/[slug] per page, and editing a brand-new page or section is an out-of-scope request that gets escalated to you.

### Do I need Nuxt Studio or a content module to use it?

No. CMS Brew does not require any particular content setup. It reads your repository as it is, so a site using Nuxt Content and a site keeping its copy in components both work, with nothing installed in the project.

### Which hosts does CMS Brew support?

Vercel, Netlify, and Cloudflare, with live previews built into the editor. Because every publish is a plain commit, publishing works with any host that rebuilds your site from Git.

### What happens when the client asks for a new page or a redesign?

The editor refuses it and routes it to you with the client's original message attached, by email or Slack if you have escalations configured. The client gets a clear answer, and you get the work request instead of a surprise on the live site.

### Does CMS Brew also work for my non-Nuxt sites?

Yes. The same account covers Next.js, Vue, SvelteKit, Astro, Remix, Gatsby, and Hugo sites, so one tool can carry your whole client portfolio. Pricing is per connected site: $39 per month includes 5.

---

- [Home](https://cmsbrew.com/)
- [Features](https://cmsbrew.com/features)
- [Full product details](https://cmsbrew.com/llms-full.txt)