A key driver for the change was my desire for simplicity. I don’t update this website frequently, or at least, less frequently than I’d like to. As a result, when I’ve come back to it and try to do updates it was a struggle to manage all the breaking changes in the NPM ecosystem. Whereas with a tool more straightforward like Hugo, the scope for churn is much lower.
HTML templates & Markdown go in, website comes out!
This extends into the tooling as well. On top of Hugo, I only use the Tailwind standalone CLI which suffices for my needs. That means my build environment is very simple: two binaries and that’s it. No
node_modules, just bliss.
The other side of the equation is speed, also known as vanity metrics. I had no real need for NextJS, I didn’t use any fancy features, and I certainly wasn’t interested in the newer hybrid modes of rendering. The static generation mode of NextJS worked well enough, but it still ended up sending 100s of KBs down the wire to render a static page. Why? There’s no need.
Perhaps this will renew my interest in developing this website? Perhaps not - but it was a fun exercise in any case!