Blog
Notes on publishing you can check
How Colophon works and why, written from the code that does it. The failures go in the build log.
Headless CMS glossary: terms in plain words
Plain definitions of headless CMS terms, from cache tags and webhooks to releases, receipts and rollbacks, each linked to the post that goes deeper.
Give AI agents CMS access, not the publish button
How Colophon's MCP server lets AI agents read, draft and propose content while the API refuses any token's approval of what a token submitted.
Using Colophon as a headless CMS for Astro
Build a static Astro site from Colophon's public delivery API: page through a collection at one release, mark pages with it, and rebuild on publish.
What happens to your draft when the CMS crashes
How Colophon keeps an acknowledged save from being lost or doubled when the server dies, two editors collide, or the network drops mid-save.
Colophon vs Directus: an honest comparison
Colophon and Directus compared on publish receipts, release history, review, scheduling, permissions, licensing and AI agents, with dated sources.
Colophon vs Payload CMS: an honest comparison
Colophon and Payload compared: schema as data or code, publish receipts, whole-site history, review, permissions and AI agents, with dated sources.
Colophon vs Strapi: an honest comparison
Colophon and Strapi compared on publish receipts, release history, review, scheduling, permissions and AI agents, with dated, linked sources.
Content modeling that checks your stored entries
Colophon's content types: 19 field types, references that can't dangle, page-builder blocks, and schema changes checked against every stored entry first.
Field-level permissions in a headless CMS
Roles down to a single field or an editor's own entries in Colophon: which checks the API runs, and which rules PostgreSQL itself refuses to break.
What a headless CMS should be able to prove
Six questions about publishing that a headless CMS should answer with evidence, not a spinner, and how Colophon answers each one today.
Colophon's load tests, with the caveats
Load results for a Rust CMS server: warm and cold reads, a cache stampede, outages and a failed 24-hour run. Laptop numbers, labelled as such.
Rollback is a change too: reverting a release
Rolling back published content in Colophon opens a normal publish request: it is reviewed, lands as a new numbered release, and history only moves forward.
Scheduled publishing that survives downtime
How Colophon schedules a publish: a local time and time zone, explicit choices at daylight-saving edges, a full recheck when it runs, and a delayed label.
How to see what your website said on a past date
Version history per entry can't show what your whole site said on a given day. The options on any stack, and how numbered releases make it one lookup.
Why your site shows old content after publishing
The CMS says published, the site shows the old page. Check each layer in turn (API, build, CDN, browser), fix the one at fault, and make it visible.