Let clients edit
the site. Not break it.

Hand a non-technical client a chat box, not your codebase. They ask in plain language; CMS Brew writes a schema-validated content patch, never code. Safe edits go live in a click. Layout, new pages, and code escalate back to you.

oakwell-bakery.com · editor
Change the phone number to 0161 555 0148
brews into
contact.phoneapplied

0161 555 0148

Validated, applied, and live in one click.

The recipe

Three steps, then it pours.

  1. 01Connect

    Point it at the site you shipped

    CMS Brew maps the delivered site's editable content into a schema. No rebuild, no plugin, no changes to how you built it. The structure becomes the list of things a client is allowed to touch.

  2. 02Brew

    The client edits in plain language

    They open a chat and ask: change the phone number, shorten this heading, swap that photo. Each request becomes one schema-validated patch, previewed live on their real site before anything ships.

  3. 03Pour

    Safe edits go live; the rest comes to you

    A valid content patch publishes to production in a click. A request for a new page, a layout change, or anything code is refused and escalated to you, with the client's words attached.

The guardrail is the feature

A client cannot break the build.

The model never writes code. It only returns a new value for a field that already exists, so a client literally cannot produce a new page, a broken layout, or a syntax error. Out-of-scope requests aren't errors, they're routed to you.

What it brews

about.headingapplied

Support that understands your situation

Validated against the field, applied live.

  • Headings, paragraphs, and button labels
  • Phone, email, and address
  • Swapping a photo for one of the same shape
  • Anything the schema marks as content

What it escalates to you

requestescalated

Add a team page with five bios

No edit made. Sent to you with the client's message.

  • New pages or sections
  • Layout, spacing, and design
  • Colours, fonts, and theme
  • Code, scripts, and integrations
  • SEO-sensitive fields, without a clear ask

Stop being the person who updates the phone number.

Give your client the keys to the content. Keep the keys to the code.