Few days ago I came across an article describing how to create a blog using GitHub pages and Jekyll. The idea of creating a blog post by committing it into your Git repo looked kind of fun to me, so I decided to give it a try. This post is the place where I will keep the journal of the experiment.

10/28/2014:

My first blog post and the first issues. Default markdown parser does not understand GitHub style fenced blocks for code snippets. Fixed the issue using the Liquid tag for highligting {% highlight %}. This is not an ideal fix because that breaks GitHub’s own Markdown preview. Will try to find a better solution.

10/29/2014:

Jekyll automatically generates posts excerts. Want to display full posts on the main page. Found a way to controll excerts generation here.

10/30/2014:

Switched to Redcarpet for Markdown processing. This way I can get GitHub style fenced blocks with Pygments highlighting for code snippets.

01/02/2015:

Reinitialized the repo to remove Jekyll Now commits history.

04/16/2016:

Switched back to kramdown as a part of GitHub’s Jekyll 3.0 upgrade. New syntax highlights CSS from mojombo.

05/30/2026:

Time for a long overdue revival. Upgraded to Jekyll 4 and now build/deploy through GitHub Actions instead of the legacy GitHub Pages build that was frozen on Jekyll 3. Dropped a few things that had quietly died over the years: a custom Pygments plugin that never actually ran on GitHub Pages, and a Google Analytics snippet pointing at Universal Analytics (which stopped collecting data back in 2023). Replaced Disqus with giscus, so comments now live in GitHub Discussions. Also moved the RSS feed to the jekyll-feed plugin and switched everything over to HTTPS.