Works with
Contentcron + CloudCannon
CloudCannon syncs and builds your site from GitHub; Contentcron feeds that same repo a reviewed article a day.
What CloudCannon is
CloudCannon is a commercial git-based CMS: it syncs two-way with your GitHub repo, gives editors visual and structured editing over your Markdown and data files, and builds your Jekyll, Hugo, Eleventy, Astro, or Next.js site on every commit.
How the pairing works
Contentcron's PRs merge into the synced branch; CloudCannon pulls the change, rebuilds, and the article is live — and editable in the visual editor. Writers who never open GitHub still see every article Contentcron ships.
Engineers keep the PR gate, editors keep their visual workflow, and neither has to adopt the other's tools.
Point it at the same folder
CloudCannon declares where content lives; Contentcron writes to that folder. Use the folder your CloudCannon collection is configured for (collections_config in cloudcannon.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 CloudCannon. 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, CloudCannon 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.