Migrating From Decap CMS
Version 1.2.0
Decap CMS (formerly Netlify CMS) is Carapace's closest architectural relative — both are git-backed, both store content as files rather than database rows. This is the most natural migration on this list.
What's actually different
Decap gives you a web-based admin UI backed by git. Carapace has no admin UI at all — editing happens through a conversation with an MCP-connected agent instead. If your team specifically wants a visual, form-based editing interface, that's a real reason to stay with Decap; it's not something Carapace is trying to replicate through a different door.
Where the two diverge more: Carapace adds an enforced HTML allowlist, validated at write time and render time, and a purpose-built component system (layout primitives, embeds) discoverable by an agent before it writes. Decap's content format is more commonly Markdown with YAML frontmatter; Carapace stores allowlisted HTML with JSON metadata.
The actual migration path
Since both are git-backed, the content itself is already sitting in a repository you have direct access to — no export step required. The real work is converting Markdown to the allowlist's HTML subset (a mechanical, if slightly tedious, pass) and reshaping each Decap config field into Carapace's simpler metadata model. For a typical blog or docs site, this is usually the most straightforward migration here, precisely because the underlying philosophy — git as the source of truth — was already the same.