Hugo! I stick with Hugo for all things SSG these days. I like how it's a single binary, runs uber-fast, and compiles down to a nice clean set of HTML, CSS, and

Hugo! I stick with Hugo for all things SSG these days. I like how it's a single binary, runs uber-fast, and compiles down to a nice clean set of HTML, CSS, and JS (if needed - for my needs it usually isn't). My one mark against it is the learning curve is sharp. That's okay for me, since I plan to use it to the end of my days, and so I can amortize the cost of learning it once against many decades of productivity. I have an old GitHub page for people struggling to get to base camp on its learning curve: https://github.com/Siilikuin/minimum-viable-hugo https://github.com/Siilikuin/minimum-viable-hugo And here are some sites I run in it: https://andrew-quinn.me/ https://andrew-quinn.me/, my barebones personal blog. https://hiandrewquinn.github.io/til-site/ https://hiandrewquinn.github.io/til-site/, my much more frequently updated TILs. Think of this as halfway between a blog and Twitter. https://hiandrewquinn.github.io/selkouutiset-archive/ https://hiandrewquinn.github.io/selkouutiset-archive/, a daily updating news archive for the Simple Finnish broadcast, happily running since 2023. The pipeline for this one is interesting, since it uses not only Hugo but Git submodules under the hood. One Git repo exists purely to curl the page I'm watching every night, and I try to mess with that one as little as possible because messing up might mean a night goes unarchived. An intermediate one submodules repo #1 and cleans up the HTML to Hugo-friendly Markdown with pandoc and sed. The final one imports this slimmed down, Markdownified version directly into its content/ directory as a Git submodule and redeploys the whole shebang every night. So far we're up to over a thousand unique HTML pages and this refinery has continued to work with only minimal changes, because we've stuck with such reliable and slow-changing tooling.