The future of the Jekyll static-site generator


My blog here has been rendered with the Hugo static site generator since at least 2016. Having all my blog posts stored as plain text files, wrapped with a simple enough theme, and generated on a server makes so many things easier. Hugo cuts through my almost 8,000 blog post archive like butter, rendering it in fewer than 20 seconds. My web server is the most basic thing imaginable, because all it has to do is deliver HTML.

But my first experience with static site generation—as opposed to server-site software like WordPress or a homebrew Rails app—was Jekyll. Its upending of how sites were created spawned a cottage industry of static-site generators, and a renewed interest in simplicity over what software like WordPress had become.

Jekyll got a boost when it was used to power GitHub Pages, GitHub’s static page hosting service. Suddenly anyone could upload text to a public repo, and have a rendered site on the other side.

I loved Jekyll. I made the switch in 2013, and it forever changed how I write. The Liquid template system was a joy to use, and having all my posts in plain text meant I could use basic *nix shell tools to edit, search, organise, and process posts. I’m good with SQL, but sometimes raw text is just easier.

But why the nostalgia trip today? Unbeknownst to me, media outlets are reporting that the writing has been on the wall for Jekyll for a while. Tim Anderson reported for the Register that one of the former core developers Frank Taillandier (rest in peace) described the project as being “in frozen mode and permanent hiatus”. GitHub Pages is also stuck at version 3, despite the 4.x branch being available for years.

The official repo is still being updated though, and active discussions are ongoing, so I wouldn’t be quick to rdiscount it yet. Get it? Because that Markdown renderer that Jekyll used to use was called… oh shaddup. Much of the Register article was lifted from a blog post about the maintainer of a new Jekyll fork, so I take it with a grain of salt.

Dare I say, there’s also something to be said for mature software that does its job not needing such regular updates. I know people who continue to run and maintain Jekyll sites successfully for large clients today. I’m willing to reserve judgement for now.

Author bio and support


Ruben Schade is a technical writer and infrastructure architect in Sydney, Australia who refers to himself in the third person. Hi!

The site is powered by Hugo, FreeBSD, and OpenZFS on OrionVM, everyone’s favourite bespoke cloud infrastructure provider.

If you found this post helpful or entertaining, you can shout me a coffee or send a comment. Thanks ☺️.