Hugo was a lot harder to learn, the template engine from Hugo felt very strange for myself coming from Django, Twig and the Jekyll template engines. The template lookup order is complex and for small website this complexity is unnecessary.
When building a large website (kde.org has more than 1400 pages) all these features make sense. I can organize my template in directories, enjoy fast generation time, separating the templating part from the content, create SCSS files for each pages that needs a special layout. There is also a (fast) JS bundler integrated into Hugo. Afaik Zola also doesn't support i18n and Jekyll has a few plugins for that but this is not a build-in functionality.
I settled on Hugo because it ticked all the boxes and even had org mode support.
The next three nights were horrible. I'm a professional web dev, full stack, I've used dozens of langs, frameworks, probably hundreds of tools. It took me three nights to set up a basic home page for an academic CV and some publication lists. Nothing more. And even then the whole thing was wonky and super unreliable for inscrutable reasons. Big red flag.
I was angry and frustrated, and I started doubting myself. So I pulled the plug. Tried Zola, I was done in 1.5hrs. Start to finish, just done. Zola is great.
Hours and days struggling with getting Hugo to do what I wanted until I gave up and had a Jekyll site up and running exactly how I wanted it within a few hours.
Who cares about saving 5 seconds site generation time when you lose days pulling your hair out just trying to get the damn thing to do what you want?
I've never felt that site generation time has been a problem for me, although I've only worked on things with 10s-100s of pages, not thousands... But then part of me wonders who it is out there who is doing site-wide updates to x,000 page sites who needs it to happen in 2 seconds? What kind of workflow on a site of that scale can't wait 30 seconds?
That said, Hugo is the only piece of software I remember that makes me feel stupid.
It must be a awesome if you use it frequently, but I only make changes to my sites maybe once per year. I often struggle for hours to make simple changes or to figure out why it's not working. Two examples:
https://discourse.gohugo.io/t/raw-html-getting-omitted-in-0-... https://discourse.gohugo.io/t/comprehensive-hugo-tutorial-fo...
Sharing the feeling of others in this thread and happy to discover Zola! :)
[0]: https://github.com/getzola/zola/issues/635#issuecomment-5245...
It's already got lots of plugins, but it's fairly easy to add your own as well. It's in the mature / complete category of projects in my opinion (although there's still some development happening)
One thing that's nice about having dozens of actively-developed static site generators is that if you don't like one you'll probably like a different one.
Zola is less powerful, but does the job and feels much more stable.
Did you report these bugs anywhere? Can you be more specific? What were you caching?
If you're caching partials for example, you need to make sure you provide correct caching keys so are you sure it wasn't misuse?
The “disable fast renderer” option (for local development) is indeed a must have, or weird things happen indeed.
My students also found the documentation difficult to grasp in particular regarding the content types and related features (section, bundles, archetypes, ...).
I actually like go templates, so it was never an issue for me.
but IIRC not all of its image features were available in the theme's zola port https://github.com/getzola/after-dark
Just when you think you've handled every edge case, you have to account for screen pixel densities, better ways to infer sizes and srcSet attributes on picture tags, browsers with or without modern features for loading images in better.. it's no small task!
(I'm obviously biased but I think Gatsby's solution is pretty good now)
Can you explain this a bit further? Why would what is/isn't in the cache cause issues? I must be missing something here. I have used Hugo before but not sure what this means exactly.
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.
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.
The Author of Zola writes on his github:
> [hugo] personally drives me insane, to the point of writing my own template engine and static site generator.
a sentiment that I share very much.
[1] https://web.archive.org/web/20180714043311/https://iotdarwin...
[2] https://github.com/getzola/zola
[3] https://github.com/getzola/after-dark