Publish to GitHub as Markdown
For sites built from a code repository: Next.js, Astro, Hugo, Eleventy, Jekyll and the like. Each article is committed as a Markdown file with front matter to the folder and branch you choose, and your existing deploy takes it from there.
How to connect
- 1
Add your website. Content Autopilot reads it and plans the first two weeks of articles.
- 2
Open Settings, go to the Publishing tab and choose GitHub.
- 3
Fill in the 4 required fields below and press Connect. The connection is tested before it is saved, and you are told what GitHub answered if it fails.
- 4
From then on, each article is published there on its scheduled day. Switch on "Hold articles for my approval" first if you want to read each one before it goes out.
What you will be asked for
- Repository
- Access token
- A fine-grained token with Contents: read and write on this repository.
- Branch
- Folder for articles
- Public URL of the blogoptional
Worth knowing first
- Use a fine-grained access token limited to this one repository, with Contents set to read and write. Nothing else.
- Commit to a branch other than your main one if you want to review articles as pull requests.
- The front matter carries the title, description, date and image. Check its field names against what your site's content loader expects.
What arrives
One article a day by default: a title, a slug, the body with headings and links to your own pages, a meta description, and a cover image when images are switched on. The same article is always published to your hosted blog too, so there is a copy with a sitemap and structured data whatever your CMS does with it.