Developers and API

How do developers work with BetterCMS?

Developers work with BetterCMS through its content API, its SDKs, a CLI and an MCP server, and shape the content model in the schema builder. BetterCMS is headless by default and serves content to any framework over the API. It also ships a page builder, so a team that wants one tool can stay inside it rather than build a front end first.

The split most teams settle on is that a developer owns the content model and the components, and a marketer owns the pages composed from them.

Four surfaces, four jobs

The content API is for reading and writing content from anywhere. The SDKs wrap it for the common frameworks so you are not hand rolling fetch calls. The CLI is for the things you want in a script or a pipeline. The MCP server is for letting an AI assistant use the same tools a person uses.

None of them is the primary one. Which you reach for depends on whether the caller is your build, your app, your terminal or your assistant.

The division that survives a redesign

A developer owns the content model and the components. A marketer owns the pages composed from them. The reason to draw the line there is that a redesign changes how content looks and not what it is, so it lands entirely on the components and leaves the model and the content alone.

The opposite arrangement, where the model has fields called things like hero left column text, turns every redesign into a content migration.

Where to start

The schema builder, before any front end code. A model you can look at is a conversation you can have with the people who will fill it in, and it is much cheaper to move a field then than after the components are built against it.

Also in developers and api

All of developers and api All questions

Still have a question left

Thirty minutes with the product team, and a straight answer.