What are your pros and cons of using Hugo? It has been frustrating 60 hours moving a site to Hugo from Jekyll. The documentation is unusable for a beginner and the docs are so interlinked it is like going down a rabbit hole. |
What are your pros and cons of using Hugo? It has been frustrating 60 hours moving a site to Hugo from Jekyll. The documentation is unusable for a beginner and the docs are so interlinked it is like going down a rabbit hole. |
Pros:
- TOML syntax for Frontmatter data in markdown content
- The `data` folder which can contain JSON, TOML, CSV, and YAML
- The layout system, once you get used to it is pretty straightforward
- Go templating, I wish I had Jinja2 or the Django engine
- Partials can't be used as shortcodes and vice-versa, this makes reusability tricky
- URLs not ending with / use a redirection to the trailing / URL, which is not SEO friendly
- I'm not using the pipeline system for assets, I use sass (scss) and lunr.js (search engine) separately to generate files in the `static` folder
- For reusability, I'm using a homemade lib[0] to build web components
- I've found themes and archetypes to be pretty useless
[0] - https://github.com/link-society/micro-web-component