Works with
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.
What TinaCMS is
TinaCMS pairs a visual editor with a typed content API generated from a schema you define in tina/config.ts. Content stays as Markdown or MDX files in your repo whether you run Tina locally or use TinaCloud, so the git history is the CMS history.
How the pairing works
Contentcron writes plain MDX with frontmatter shaped like the documents already in your collection, so new files validate against your Tina schema. Because Tina reads from the repo, an article merged from a Contentcron PR is immediately editable in the visual editor.
Your team can run the loop entirely in GitHub (comment on the PR, the article revises) and use Tina for the touch-ups after merge.
If your schema requires a field your older posts don't carry, add it to the frontmatter template in project settings so generated articles always validate.
Point it at the same folder
TinaCMS declares where content lives; Contentcron writes to that folder. Use the path of the collection in tina/config.ts.
- 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 TinaCMS. 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, TinaCMS 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.