Obelism Content Docs

A headless CMS where every organization models its own content. Model it, edit it on your own site or by prompt, and read it from the delivery API with the Content SDK.

3 min read

Obelism Content is a headless CMS. Each organization models its own content per space, edits it in the dashboard, on its own site or through an agent, and its sites read it from the delivery API. These pages are for the people building those sites.

What can you do with Content?

Model your own content

Page types for anything with a URL, data types for everything else, and block types for the parts pages are built from. Every space has its own content model, and you can keep it in your repository, reviewed in pull requests like your code.

Edit on the page

Editors see every page of your site on the canvas and click a block to change it, or sign in on the site itself and change it by prompt: "make the hero heading shorter".

Read it from any stack

The delivery API answers JSON for a path, an id or a content type, in one locale or all of them, with references and assets inlined. The SDK wraps it for JavaScript and React.

Develop, staging and production

Every space has three environments, each with its own model and content. Build in develop, check on staging, then promote to production.

A/B tests in your content

Any blocks field takes the built-in improve block: different blocks per variant of an Obelism Improve test or flag.

Shopify products and collections

Connect a space's Shopify store and editors pick its products and collections in content, link to them, and give the ones that need it a page of their own. Your site reads live prices and stock from Shopify.

Work as a team

Editors comment on entries and see who else has one open. Production can be reviewed, so an admin approves what goes live, and anything can be scheduled. People get a role per space, and Activity shows who changed what.

Every language

A space publishes in as many locales as it needs, with fallbacks, URLs per language, and AI translation for one entry or the whole space.

From a design or an agent

Turn a Claude Design page into a draft built from your own blocks, or let an agent model, write and publish content through MCP.

How it works

  1. Create a space for the site, and set its locales.
  2. Model the content under Content model, or keep the model in Git.
  3. Write content in the dashboard, on the canvas, or through an agent.
  4. Read it from the site with a delivery token: GET /api/delivery/v1/pages?path=….
  5. Rebuild on publish with a webhook.
  6. Promote content and the model from develop to production.

Get started

On this page

Marks in the margin

  • Note
  • Watch out
  • Updated

Scribes marked doubtful lines in the margin. That practice is called obelism.

Stuck on a step?