Hugo

Updating Hugo is hard. Here’s what I did to help the upgrade process.

I think I’ve discovered my development environment equivalent to nirvana. code-server fronted by Caddy on a box with Tailscale installed. I maintain a lot of Hugo websites. Hugo has been my go-to content management system (CMS) since discovering it in 2017 (I got my first Hugo site at GopherCon 2017). I’ve lost count of the number of domains I own (a common nerd problem). But, I know I have a handful of websites I update regularly. For years I’ve used the Settings Sync extension in VScode to make things consistent across machines. But something was always missing (for example, shell integration, fonts, etc.). ...

Git submodules are cumbersome to manage. In my opinion, git submodules are a sort of anti-pattern for Hugo (I know many themes suggest using git submodules). There’s a better way to manage your Hugo site’s theme: Hugo Modules. Suppose you have a Hugo site and use a theme that supports Hugo Modules. I think the theme would need to require a minimum of Hugo v0.55.0. But, more features are available in later versions. Regardless, your mileage may vary: ...