Works with
Contentcron + Outstatic
Outstatic's dashboard lives in your Next.js app; Contentcron ships articles into its content folder as pull requests.
What Outstatic is
Outstatic is a CMS that lives inside your Next.js app: a dashboard served from your own routes that commits Markdown to outstatic/content/<collection> in your GitHub repo. No external service and no database — the repo holds everything.
How the pairing works
Point Contentcron at the same collection folder and the pairing is complete. Frontmatter (title, publishedAt, status and friends) is inferred from your existing documents, so generated articles look exactly like ones written in the dashboard.
Merged articles appear in Outstatic's collection list, editable like any other document.
Point it at the same folder
Outstatic declares where content lives; Contentcron writes to that folder. Outstatic stores collections under outstatic/content/<collection>.
- content_dir: outstatic/content/postsyours to set
- extension: .md / .mdxdetected
- frontmatter: matched to your existing postsinferred
No plugin, on purpose
There is nothing to install inside Outstatic. 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, Outstatic 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.