My blog, powered by Jekyll and GitHub Pages

I keep notes for myself — mostly technical problems I’ve hit, topics I’m digging into, and the occasional event worth remembering. Lately I’ve been writing more, and it has shifted from notes-for-me into something I might actually share. I’m in a book club that runs on Notion, but when I compared the options for my own space, I went with GitHub Pages and Jekyll. I’m more of a builder than a blogger, and the toolchain matters to me.

Why not the others?

• Notion — great for collaboration, weak as a public publishing platform.
• Medium — clean reader experience, but the content lives on someone else’s terms.
• Substack — newsletter-first; I don’t want to optimise for an inbox.
• WordPress — too much surface area for what I need.

GitHub Pages + Jekyll wins for me on one axis the others can’t match: full ownership of the site structure, source files, and publishing workflow. The repo is the blog. Version control, diffs, PRs, and deploys are the same workflow I already use every day.

What is Jekyll?

Jekyll is a simple, blog-aware, static site generator perfect for personal, project, or organization sites. Think of it like a file-based CMS, without all the complexity. — jekyll/jekyll

It’s Ruby-based and tightly integrated with GitHub Pages — push to main, GitHub builds and serves the site. No CI to wire up, no server to maintain.

What’s next?

I’ll keep writing here, directly in this repo. I also want to migrate some old notes over, which will take time. And I’m tempted to try a GitHub Pages + Astro setup at some point, just to see how it compares. We’ll see.

Stay tuned.