Hugo

This blog started with Jekyll, the static site generator historically associated with GitHub Pages. After a few months of use, I decided to migrate to Hugo. Here’s why, and how it works. Jekyll vs Hugo: why switch? Jekyll is a solid tool, but it carries a few constraints that become painful over time. Jekyll Hugo Language Ruby Go (single binary) Installation Ruby + Bundler + gems One single binary Build speed Slow (seconds to minutes) Very fast (milliseconds) Dependencies Many (gems) None Themes Via gems or fork Local directory or module Native drafts Partial Native (draft: true) Future dates Not handled natively Native (buildFuture) The point that motivated me most: Hugo is a single binary compiled in Go. No Ruby to install, no gem version conflicts, no bundle install failing depending on the environment. Download it, run it, done. ...