Maybe you don't need a headless CMS
A headless CMS gives editors forms for structured content. If what your team really wants is to change the site itself, editing the code by chat with a developer review can be simpler.
$1.00 of free credit on every new project. No subscription.
Headless CMS: what it solves, and what it costs
Great for structured content
Blog posts, product catalogs and content reused across channels are what a headless CMS is built for.
Upfront work
Content models, API integration, preview mode and editor training all need a developer before anyone edits a page.
Editors are still limited
A new section, a layout change or anything outside the fields still goes back to the developers.
How does it work?
No install, no terminal. Everything in your browser, on your phone, laptop, tablet.
- 1
Your developer, or anyone with GitHub access
Connect the codebase
Pick the GitHub repository of the project.
- 2
The project owner
Invite your team
Add collaborators by email and choose what each of them can do.
- 3
Your team
Chat, check, submit
Ask for a change in the chat, check it in a live preview of the real app, and submit it when it looks right.
When AI editing on the code is the better fit
And when it is not.
Marketing sites and landing pages
When most changes are copy, sections and layout, editing the code directly avoids modelling content you change twice a year.
Developers keep control
Rules per file, review for sensitive parts, and every change is a commit in your repository.
Keep a CMS for volume
For hundreds of articles or products, a CMS is still the right tool. The two can coexist: content in the CMS, everything else by chat.
Questions
- Is MakeThemCode a CMS?
- No. It edits your code through an AI agent, with a live preview and commits on your repository. There is no content database.
- Can it edit content stored in a CMS?
- It works on files in your repository. Content stored in a CMS stays edited in the CMS.
- What does it cost compared to a CMS?
- No subscription: you pay for the tokens used per request. See the pricing page for estimates.
Pay per request, with spending limits per project and per member. Developers keep control of the repository.
Try editing your site by chat.
Connect your repository and spend your first $1.00 on real changes.