Works with
Contentcron + Pages CMS
Pages CMS edits your repo through one .pages.yml; Contentcron adds a daily article to the same content folder, PR first.
What Pages CMS is
Pages CMS is a free, open-source CMS that runs entirely against your GitHub repo: a single .pages.yml describes your content types and media folders, and the editor commits Markdown straight to the branch you choose.
How the pairing works
Contentcron writes to the folder your content type points at, with frontmatter inferred from existing entries. Because Pages CMS reads the repo directly, a merged PR is instantly visible in the editor.
The PR step adds the review gate Pages CMS itself doesn't impose: nothing reaches the branch until someone approves the article.
Point it at the same folder
Pages CMS declares where content lives; Contentcron writes to that folder. Use the path of the matching content entry in .pages.yml.
- 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 Pages 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, Pages 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.