Jekyll is a Ruby based static site generator created by Github that I have been using for many many years. It pains me to say goodbye but today is the day where I moved my blog off Jekyll for good. It was a fun ride and most notably, I created jekyll-dash, a custom theme for Jekyll that had all the fancy features one would love to see from an SSG generator: tags, fontawesome, cool animations... and all that jazz. I did maintain that for many years but eventually, the fun turned into annoyance.
Working with Jekyll can be rather annoying, especially when trying to get it running on Github Pages. Yes, Github automatically deploys your Jekyll page without you having to worry about anything, unless you are trying to use anything other than these versions. Oh, you want to use Jekyll 4? Tough luck, you gotta roll your own workflow to deploy + build things.
To make matters worse, you cannot just "install" Jekyll and get started. You need to setup Ruby first, which itself has different versions, should you install Ruby 2? Should you install Ruby 3? People in the past stumbled on issues where using Ruby 3 did not work with Jekyll.
Then, there is the gem system: this is not a Jekyll concept but comes from Ruby. The idea sounds neat: you can build a theme for Ruby and then bundle it into a "gem". Then, you can publish the gem and others can download it and use your Jekyll theme, without having to worry about checking out dubious git repositories or running some dodgy commands. Instead, in your Gemfile
you can define dependencies like so:
source 'https://rubygems.org'
gem 'jekyll-dash', '~> 2'
gem 'jekyll-sass-converter', '~> 2.0'
gem 'liquid-md5'
gem 'jekyll-tagging'
The jekyll-dash
there is my own theme I created. You may notice something, though: it has a ~> 2
, meaning that the version is 2.0—no, this is not because it is so advanced! I wanted to upgrade my blog to latest Jekyll features (Jekyll 4) and unfortunately, all jekyll gems stopped working and had to be upgraded, too. This was quite a pain to maintain and keeping track of which gems I can use under which circumstances made this whole setup rather cumbersome. The whole point of using Static Site Generation to me is to have a clean and elegant and minimal setup without any databases, without any annoyances. Just some files hosted in a repository and Bob's your uncle.
I went and researched what is trendy in 2025 and discovered some interesting alternatives:
I browsed their themes and was impressed. The boring theme was exactly what I was looking for. Also, the way it works is rather brilliant: you just use a binary to generate the page and that's it. Heck, it even comes with its own Github action!
I'm excited to use this light-weight technology.