The breaking changes in #Hugo do drive me crazy if you're not using it on an almost daily basis. I wanted to update one page in my blog, and since I last used Hugo it's gone from version 0.159.0 to 0.163.0, this now means the following things don't work:
- Raw .html pages, I have to add a new config option to allow what is now considered insecure files to be added (0.162)
- I can't use
.Paginateon my 404 template page either (can't see the changelog for that) - At least there's a deprecation warning for
.Site.LanguageCodebeing deprecated.
I wish they'd finally adopt semantic versioning, so you can prepare yourself and know when you're going to have to do extra work to get things to work again.
@hl When we needed a static site for https://shield.tib.eu I decided to go with Hugo since I've been wanting to learn it for a while, but I can echo that four months into my tenure I'm already doubting whether the abstraction is even worth it. I'm also already getting warnings that some of the stuff we're doing is deprecated. 🫤
SHIELD / SciOp