Works with
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.
What Astro is
Astro is a web framework built for content-heavy sites: pages ship as static HTML by default, and blog posts live as Markdown or MDX files in a content collection, each validated against the schema you define in src/content.config.ts. The repo holds every post, so the git history is the content history.
How the pairing works
Contentcron writes Markdown with frontmatter inferred from the posts already in your collection, so new articles pass your collection's schema without touching config. Merge the PR and the next build renders the article like any hand-written post.
Your deploy pipeline is the publish button: merging to main triggers the same Vercel, Netlify, or GitHub Pages build you already run. No webhook, no API, nothing new to maintain.
If your collection schema requires a field your existing posts don't carry, add it to the frontmatter template in project settings so generated articles always validate.
Point it at the same folder
Astro declares where content lives; Contentcron writes to that folder. Use the folder your collection reads — the base of its glob() loader in src/content.config.ts (or src/content/<collection> on older versions).
- content_dir: src/content/blogyours to set
- extension: .md / .mdxdetected
- frontmatter: matched to your existing postsinferred
No plugin, on purpose
There is nothing to install inside Astro. 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, Astro 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.