Some people write with a terminal open and never really left their editor. If that is you, your blog should not drag you back into a browser form every time you have something to say.
Your repo, your workflow
Posts are markdown files with a bit of front matter: title, slug, tags, and whether it is a draft. A GitHub Action watches the repo and sends the changes over on every push. The slug is what identifies a post, so pushing again updates the article instead of creating a second one, and a draft stays private until you say otherwise.
Everything git already gives you comes along for free. Review a piece in a pull request. Keep the history of every edit. Branch on the article you are not sure about yet.
See it in action
The full setup, workflow file included, lives in a post that was itself published by a git push: Publish to your blog with a git push.
Good to know
- It runs on the Writizzy API, so the same idea works from any script or CI you already use. GitHub Actions is simply the shortest path.
- Images referenced in your markdown are uploaded along with the post, so your repo stays self-contained.
- You can still open the editor whenever you feel like writing in the browser. The two get along.
- Sharing a snippet rather than a whole post? GitHub gists embed with a single link.