<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Colophon blog</title>
    <link>https://colophon.404human.dev/blog/</link>
    <atom:link href="https://colophon.404human.dev/rss.xml" rel="self" type="application/rss+xml" />
    <description>How Colophon proves what it published.</description>
    <language>en</language>
    <item>
      <title>Headless CMS glossary: terms in plain words</title>
      <link>https://colophon.404human.dev/blog/headless-cms-glossary/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/headless-cms-glossary/</guid>
      <description>Plain definitions of headless CMS terms, from cache tags and webhooks to releases, receipts and rollbacks, each linked to the post that goes deeper.</description>
      <pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Give AI agents CMS access, not the publish button</title>
      <link>https://colophon.404human.dev/blog/ai-agents-cms-permissions/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/ai-agents-cms-permissions/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Using Colophon as a headless CMS for Astro</title>
      <link>https://colophon.404human.dev/blog/astro-headless-cms/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/astro-headless-cms/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What happens to your draft when the CMS crashes</title>
      <link>https://colophon.404human.dev/blog/cms-lost-edits/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/cms-lost-edits/</guid>
      <description>How Colophon keeps an acknowledged save from being lost or doubled when the server dies, two editors collide, or the network drops mid-save.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Colophon vs Directus: an honest comparison</title>
      <link>https://colophon.404human.dev/blog/colophon-vs-directus/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/colophon-vs-directus/</guid>
      <description>Colophon and Directus compared on publish receipts, release history, review, scheduling, permissions, licensing and AI agents, with dated sources.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Colophon vs Payload CMS: an honest comparison</title>
      <link>https://colophon.404human.dev/blog/colophon-vs-payload/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/colophon-vs-payload/</guid>
      <description>Colophon and Payload compared: schema as data or code, publish receipts, whole-site history, review, permissions and AI agents, with dated sources.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Colophon vs Strapi: an honest comparison</title>
      <link>https://colophon.404human.dev/blog/colophon-vs-strapi/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/colophon-vs-strapi/</guid>
      <description>Colophon and Strapi compared on publish receipts, release history, review, scheduling, permissions and AI agents, with dated, linked sources.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Content modeling that checks your stored entries</title>
      <link>https://colophon.404human.dev/blog/content-modeling-in-colophon/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/content-modeling-in-colophon/</guid>
      <description>Colophon's content types: 19 field types, references that can't dangle, page-builder blocks, and schema changes checked against every stored entry first.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Field-level permissions in a headless CMS</title>
      <link>https://colophon.404human.dev/blog/field-level-permissions/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/field-level-permissions/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What a headless CMS should be able to prove</title>
      <link>https://colophon.404human.dev/blog/headless-cms-publishing-checklist/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/headless-cms-publishing-checklist/</guid>
      <description>Six questions about publishing that a headless CMS should answer with evidence, not a spinner, and how Colophon answers each one today.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Colophon's load tests, with the caveats</title>
      <link>https://colophon.404human.dev/blog/load-testing-a-cms/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/load-testing-a-cms/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Rollback is a change too: reverting a release</title>
      <link>https://colophon.404human.dev/blog/roll-back-a-bad-publish/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/roll-back-a-bad-publish/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Scheduled publishing that survives downtime</title>
      <link>https://colophon.404human.dev/blog/scheduled-publishing-pitfalls/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/scheduled-publishing-pitfalls/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to see what your website said on a past date</title>
      <link>https://colophon.404human.dev/blog/website-history-past-date/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/website-history-past-date/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why your site shows old content after publishing</title>
      <link>https://colophon.404human.dev/blog/website-not-updating-after-publish/</link>
      <guid isPermaLink="true">https://colophon.404human.dev/blog/website-not-updating-after-publish/</guid>
      <description>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.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
