The same page, as markdown
Markdown delivery serves a markdown twin of every page and entry. Pages and entries are never stored as markdown, they are serialized on request, so an agent reads the same content a browser reads as HTML at a fraction of the tokens.
Your stack. Your rules. Everyone moves faster.
What markdown delivery does
-
One URL, two formats
Send an Accept header of text/markdown to the canonical URL. Search engines see one page and agents get clean text.
-
A twin for every page
Every page and every entry has its own .md endpoint. Standalone markdown files sit in the same table.
-
A serve switch per row
Turn markdown on or off one endpoint at a time. A draft's switch is disabled with the reason written out.
-
Write the markdown yourself
One page can carry a hand-written override. It replaces the generated text without touching the sections.
-
llms.txt, yours or ours
Serve the generated index or replace it with your own file. Revert to the generated version whenever you want.
-
BetterCMS is headless by default and serves content over an API to any framework. It also ships a page builder, so teams that want one tool can stay in it.
-
The Migrator API maps an existing schema onto BetterCMS collections and brings entries and assets with it. WordPress, Contentful, and Sanity are covered.
-
Yes. Free includes one locale, Starter two and Pro five, and an extra locale is $8 a month per website. Translate inside the editor and publish each locale on its own schedule from the same content model.
-
There is no cap. Build models in the schema builder with your own fields, relationships, and validation rules, and change them without a migration.
-
The media library stores and organizes every asset. Images are resized, compressed, and served from a CDN, so you upload once and use the file anywhere.
-
Yes. Editors work side by side with live cursors, comments, and field locking, and every version is kept for your plan history window, 7 days on Free, 90 on Starter and 365 on Pro, so you can roll back to an earlier draft.
-
Set custom roles down to the field. Decide who can edit, who has to approve, and who is allowed to publish, then apply the same rules to your agents.
-
Content is encrypted at rest and in transit, backed up automatically, and every change is written to an audit log you can read.