Works with
Contentcron + Sveltia CMS
The modern Decap replacement, with an AI writer attached: Contentcron ships Markdown PRs into the same collections Sveltia edits.
What Sveltia CMS is
Sveltia CMS is a fast, actively developed replacement for Netlify/Decap CMS: it reads the same configuration format, adds a modern UI and built-in i18n, and keeps the same git-based model where every piece of content is a Markdown file in your repo.
How the pairing works
Contentcron never reads your CMS config; it only writes to the content folder. So whether you are on Decap or migrated to Sveltia, the pairing is identical: point Contentcron at the collection folder, and merged PRs show up in Sveltia's admin ready to edit.
Frontmatter is inferred from your existing entries, so articles pass your collection's field definitions from the first PR.
Point it at the same folder
Sveltia CMS declares where content lives; Contentcron writes to that folder. Use the folder from your collection's folder: key — Sveltia reads the same config.yml as Decap.
- content_dir: content/postsyours to set
- extension: .md / .mdxdetected
- frontmatter: matched to your existing postsinferred
No plugin, on purpose
There is nothing to install inside Sveltia CMS. Contentcron’s integration surface is the repo itself: the GitHub App opens a pull request containing one Markdown file in your voice and your frontmatter. When it merges, Sveltia CMS sees a normal commit, and everything downstream (builds, previews, editors) behaves as if a teammate pushed it. Comment on the PR and the article revises before it ever reaches your CMS.
Using something else? All supported CMSs · any Markdown blog in a GitHub repo works.