CaretCMS

How editing works

Add data-caret to a template element. After signing in, click the rendered element, edit its content, and save.

<h1 data-caret="pages::home::headline">Welcome to my site</h1>

That’s the authoring API. Your template text is the default until someone overrides it. Collections are created on first save — no schema files required.

Already rendering .md content collections? CaretCMS can mark supported paragraphs, headings, lists, and quotes automatically and publish edits back to the source file without a separate content database.

On server delivery, visitors see published changes on the next request. On static delivery, publish locally and rebuild so the update lands in deployed HTML. See Static delivery.

Read in this order

These pages are written as a path. If you’re new, read them top to bottom — each builds on the previous.

QuickstartInstall, tag an element, ship the first edit.

Static deliveryCDN deploy — bake content at build time.

Caretize CLIWire CaretCMS and auto-tag existing markup.

Inline editingEvery option for the data-caret attribute.

Markdown body editingEdit rendered prose and publish it safely back to .md files.

SchemasThree sources — registered, dynamic, inferred.

Content StudioStructured editing at /admin/cms with history.

Dynamic collectionsNew collections from the UI without redeploying.

Live collectionsQuery CMS data through astro:content.

Storage adaptersFilesystem, in-memory, Cloudflare KV, custom.

AuthenticationSessions, CSRF, production hardening.

ConfigurationEvery caret() option in one place.

ThemingStudio chrome tokens and theme packages.

DeploymentStatic CDN, Node, Vercel, Fly, Cloudflare Workers.

API referenceHTTP routes, mutation commands, responses.

Two-minute path

If you only have a few minutes: Quickstart plus Inline editing. Adding CaretCMS to an existing site? Start with Caretize instead.