4 ms·
I just found that with Hugo it was really hard to get exactly what I wanted in terms of directory structure and theming. E.g. just getting a simple child page
by mattlondon 6y ago
I just found that with Hugo it was really hard to get exactly what I wanted in terms of directory structure and theming.
E.g. just getting a simple child page listing at "domain.com/something/" to automatically list all child pages took hours and hours and I still couldn't get it to work. It literally had a blank page.
It felt over-engineered and they'd crow about speed improvements or some niche new whizz-bang feature or whatever for their new releases when I was there still just trying (and failing) to get what I feel is a totally fundamental basic feature working.
I also found creating a custom theme from scratch in Hugo quite complicated with archetypes or whatever they were called.
It felt like the project was more interested in the engineering challenge of the site generator rather than making something that is usable (which is totally 100% fine for them to choose that path) - after all directory listings seems like a basic feature to me yet it was apparently impossible without considerable fiddling around with _index files or other custom nonsense. Everything just felt a little bit more complex and laborious than it should have been to get a simple 4 or 5 layer site up and running exactly the way I wanted it.
I am sure that if I kept at it and kept trawling the support forums and posting questions and hanging out on IRC someone could have helped me ... but life is too short for that and I've got things to do so it just wasn't worth fighting with.
Jekyll on the other hand is super-simple and I was able to port entire sites - complete with a from-scratch custom theme + CSS - in under a day, and have them look and act exactly how I wanted.
I only picked Hugo over Jekyll originally as at the time I was a fan of golang, so I was not really that wedded to Hugo for another reason.