Works with
Your CMS keeps the keys
Contentcron ships articles as Markdown commits through pull requests, so every git-based CMS reads them natively. No plugins to install — the repo is the integration.
Web framework for content-driven sites
Contentcron + Astro
Astro renders the Markdown; Contentcron writes it. A researched article lands in your content collection as a pull request, ready for the next build.
How it fits →
Open-source git-based CMS (formerly Netlify CMS)
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.
How it fits →
Open-source git-based CMS, Decap-compatible
Contentcron + Sveltia CMS
The modern Decap replacement, with an AI writer attached: Contentcron ships Markdown PRs into the same collections Sveltia edits.
How it fits →
Git-based CMS with visual editing
Contentcron + TinaCMS
Tina edits Markdown in your repo; Contentcron writes it. Articles arrive as PRs and open in the visual editor the moment they merge.
How it fits →
Git-based CMS with TypeScript schemas
Contentcron + Keystatic
Keystatic defines the collection; Contentcron fills it. New articles land as reviewable PRs in the same GitHub repo Keystatic edits.
How it fits →
Open-source CMS for Next.js
Contentcron + Outstatic
Outstatic's dashboard lives in your Next.js app; Contentcron ships articles into its content folder as pull requests.
How it fits →
Open-source GitHub-based CMS
Contentcron + Pages CMS
Pages CMS edits your repo through one .pages.yml; Contentcron adds a daily article to the same content folder, PR first.
How it fits →
Commercial git-based CMS with visual editing
Contentcron + CloudCannon
CloudCannon syncs and builds your site from GitHub; Contentcron feeds that same repo a reviewed article a day.
How it fits →
CMS inside VS Code
Contentcron + Front Matter CMS
Your editor is the CMS; Contentcron is the writer. Articles arrive as PRs in the repo Front Matter already manages.
How it fits →
Not listed? If your CMS stores content as Markdown or MDX in a GitHub repo, it already works: point Contentcron at the content folder and the first PR proves it. Headless CMSs that keep content in a database behind an API (Contentful, Sanity, Strapi, WordPress) are the one category that doesn’t fit — there’s no file to open a pull request against.