Works with
Contentcron + Front Matter CMS
Your editor is the CMS; Contentcron is the writer. Articles arrive as PRs in the repo Front Matter already manages.
What Front Matter CMS is
Front Matter CMS is a headless CMS that runs inside VS Code: a content dashboard for your Markdown, frontmatter forms driven by frontmatter.json, previews, and SEO checks, all operating on the files in the repo you already have open.
How the pairing works
Contentcron plays the writer in the same repo. PRs arrive, you review them in GitHub or straight from your editor, and merged articles show up in Front Matter's dashboard next to your own drafts.
Frontmatter inference matches the fields your frontmatter.json expects, because it copies the shape of the posts already in the folder.
Point it at the same folder
Front Matter CMS declares where content lives; Contentcron writes to that folder. Use the folder registered in frontmatter.json under frontMatter.content.pageFolders.
- content_dir: content/articlesyours to set
- extension: .md / .mdxdetected
- frontmatter: matched to your existing postsinferred
No plugin, on purpose
There is nothing to install inside Front Matter 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, Front Matter 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.