Works with
Contentcron + Decap CMS
Keep Decap as the editing desk. Contentcron files a researched article into the same collection folder, as a pull request, every day.
What Decap CMS is
Decap CMS is the longest-running git-based CMS: a single-page admin panel configured from one YAML file, with collections that map to folders of Markdown in your repo. Editors sign in with GitHub and every save is a commit, so the repo stays the only source of truth.
How the pairing works
Decap already treats your repo as the database, which means Contentcron needs no integration at all. It writes to the same folder your collection points at, with frontmatter inferred from the entries already there, so new articles satisfy your collection's fields without touching admin/config.yml.
Review happens on the pull request. Once merged, the article appears in Decap's admin like any hand-written entry, and your editors can tweak it from the UI whenever they like.
Point it at the same folder
Decap CMS declares where content lives; Contentcron writes to that folder. Use the folder from your collection's folder: key in admin/config.yml.
- content_dir: content/blogyours to set
- extension: .md / .mdxdetected
- frontmatter: matched to your existing postsinferred
No plugin, on purpose
There is nothing to install inside Decap 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, Decap 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.