
1. Installing Hugo, and the Empty Build That Exits 0
Hugo installed in 7.86 seconds and rebuilt our site in 4 ms. Its first build also wrote zero HTML files and reported success, and that was the first of four silent failures.
Tag
8 pieces

Hugo installed in 7.86 seconds and rebuilt our site in 4 ms. Its first build also wrote zero HTML files and reported success, and that was the first of four silent failures.

We moved our own 128 published articles into Hugo and got clean builds in under 100 ms. The obvious route also rewrote code blocks in 8 of them, turning shell comments into headings, and exited 0.

Our 50,000 page Hugo build took 86 seconds until we moved one where filter into a cached partial, and then it took 16. We also fed it bad input on purpose: five of eight mistakes built with exit 0.

Hugo built our 10,000 article site in 2.45 seconds to Eleventy's 4.8 and won at every size we tried. It also used nearly twice the memory, and 17 of its last 42 releases flagged something breaking, deprecated or removed.

pip install zensical succeeds on a stock Mac and gives you nothing. A 1.0 kB wheel, version 0.0.2, no binary. Here is why, and the working install.

We built 220,400 words with it. Going from 3 pages to 203 made the wall clock go down, and the search index it ships to your readers is 1.4 MB.

It read our mkdocs.yml with no conversion step and built the site correctly. Then it dropped four plugins without printing a single word about any of them.

Strict mode does work, on the subcommand CI runs. But it escalates warnings, and the failures that matter most never produce one.