Docs

Getting started

Contentcron writes blog content for teams that publish MDX or Markdown from a GitHub repo. It learns your voice from your site, researches topics with real web search, writes about an article a day, and opens each one as a pull request your team reviews like any other change. Articles embed real screenshots of your product and researched figures with cited sources, pulled from a library the engine maintains per project.

1. Create a project

A project is one site: one brand voice, one repo, one content calendar. Sign up, create a project, and give it your website URL (plus your blog or sitemap URL if you have one). Contentcron immediately crawls the site and drafts a brand profile: voice, company facts, writing rules, and a cover-image style built from your real palette. Everything it learns is editable under Brand voice.

2. Connect your repo

Install the Contentcron GitHub App on the repository that holds your blog. In project settings you pick the repo; Contentcron finds your content directory, reads two or three existing posts, and infers your frontmatter convention — field names, date formats, slug style. New articles match your existing posts byte for byte. No repo clones: everything runs through the GitHub API with contents and pull-request permissions only.

3. Approve topics

The topic engine researches your niche and proposes topics with a rationale; you approve, reject, or add your own under Content. Approved topics fill the queue, and the daily scheduler works through them at your cadence (default one article per day, configurable per project).

4. Review the PR

Each article arrives as a pull request: full MDX, frontmatter, and a branded cover image in the same diff. Comment on the PR the way you already review code and the article revises itself and replies with what changed. Prefix a comment with !cc-ignore to keep it out of revisions. Merge when it reads right.

Where to go next