KDE.org migrated to Hugo
I used Hugo some years ago[1] and my memory of it was mostly negative in terms of usability. I revisited it again this year for another project and it drove me so mad that I ended up switching to Zola[2].<p>My issue with Hugo was that it just wasn't reliable with what was in the cache so I could never trust whether what I saw was actually the state of the site and causing me to push a broken state to the remote server. Hugo is great if it works but I found it a nightmare to deal with when it doesn't.<p>There are countless options in Hugo (yes I understand it's powerful but I rather it just had half the option and they work as advertised), some of which at times are contradictory so searching for solutions took me ages. I have no affiliation with the zola project and am not even big on Rust. Zola just worked for me and seems a lot less "hacky" than hugo thanks to the Tera templating system.<p>The Author of Zola writes on his github:<p><i>> [hugo] personally drives me insane, to the point of writing my own template engine and static site generator. </i><p>a sentiment that I share very much.<p>[1] <a href="https://web.archive.org/web/20180714043311/https://iotdarwinaward.com/post/improve-your-privacy-in-age-of-mass-surveillance/" rel="nofollow">https://web.archive.org/web/20180714043311/https://iotdarwin...</a><p>[2] <a href="https://github.com/getzola/zola" rel="nofollow">https://github.com/getzola/zola</a><p>[3] <a href="https://github.com/getzola/after-dark" rel="nofollow">https://github.com/getzola/after-dark</a>