4 ms·

I guess the comparison with hugo is inevitable. It is a tough challenge, hugo is among the most popular go projects across any domain. The table indicates both

I guess the comparison with hugo is inevitable. It is a tough challenge, hugo is among the most popular go projects across any domain. The table indicates both as being "fast" so that leaves jekyll compatibility as the primary differentiating factor. Not familiar with jekyll, so cant tell what sort of pool of users that compatibility promise applies to. But here is a tip: the weak point of hugo is its documentation ;-)

monooso 3y ago
The fact that Hugo still doesn't play nicely with Tailwind 3 (2 years after T3 was released) is a real pain point. I gave up on this ever being fixed quite a while back, but still check on the issue [1] every now and then. Seems like the only activity these days is bep bumping the milestone every month. [1]: https://github.com/gohugoio/hugo/issues/8343 https://github.com/gohugoio/hugo/issues/8343
- explodingcamera 3y ago
  The latest reply in this GitHub issue links to documentation and a example repo showing that tailwind is supported though
- fbdab103 3y ago
  Still annoys me to no end that Hugo chose RSS and it requires some song and dance to make ATOM formatted feeds.
- earthboundkid 3y ago
  That issue should have been closed. This was resolved in Hugo 112. https://github.com/gohugoio/hugo/releases/tag/v0.112.0 https://github.com/gohugoio/hugo/releases/tag/v0.112.0
  - monooso 3y ago
    Praise be. Thank you, I would never have seen that.
toddmorey 3y ago
Documentation and the go templating language. I just don’t find it readable. Here’s an example from the docs {{ if (and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")) }}
- tgv 3y ago
  This project uses another templating language, apparently based on Shopify's liquid like Jekyll. (1) https://github.com/osteele/liquid https://github.com/osteele/liquid
- rjzzleep 3y ago
  I completely agree. The go templating language is a nightmare. I probably learned most when dealing with Helm, but I've always been holding out hoping that something better would replace it. Does anyone know why the templating situation is the way it is in go? In many other languages you have multiple competing templating languages, but in go this is basically what you get. Are there language specific features that make it hard? EDIT: interesting to final see active liquid templating engines for go. now if only legacy would allow for the use of these things.
  - znpy 3y ago
    > I probably learned most when dealing with Helm, My opinion is that helm does the completely wrong thing: patching text. It should instead patch objects, so that we don’t have to deal with indentation and other silly things. I don’t think it’ll ever change though :(
    - kevincox 3y ago
      I'm completely with you. Generating a data structure using a text templating language is just awkward and error prone. In fact I'm starting to think that text templates are very rarely the best option. It is usually better to have a proper emitter library or AST data structure that can be generated with "real" code. I guess one of the few places that text templates can provide value is when the template is untrusted. But maybe a sandboxed programming language is still a better option here.
dawidpotocki 3y ago
I have migrated from Jekyll to Hugo for my own website, but the whole Hugo project is just weird. It took me like a year to migrate my simple website because of all the different paper cuts that drained my will to work on it. You are only able to only use partials in HTML pages and shortcodes in Markdown pages. Why? They use 2 different syntax, so the best you can do is awkwardly wrap a partial in a shortcode. What's the point? They serve basically the same purpose. Want to set up RSS? Oh yeah, for some reason by default it will not show full content in your feed reader, instead only a small extract. The the only way to fix it is by making your own template[1]. But wait, why are we using RSS instead of Atom? Who knows, but if you want to use Atom, you have to use your template and insert some stuff to your config. Also don't look at the bug tracker, that thing is frustrates me to no end. You of course have the everyone's favourite Stalebot that you might have noticed in my previous link, but if you look at older issues, you will see the maintainer self-botting as a Stalebot[2][3] for some reason. You will also see the maintainer moving issues between milestones for years with no end in sight[4]. That's not a one-off, click on any issue. Changelogs can sometimes feel a bit, odd too: > but also a big shoutout to @dependabot[bot], […] for their ongoing contributions. And commit messages sometimes are just… a bit too long[5] (it is truncated by GitHub, you can append .patch to see the full message). Their documentation is awful to read too[6]. Oh and the templating engine? Yeah, not documented at all. Also the quick start guide will tell you to git clone some random theme, but I don't want my website to look like someone's, I want to write my own styles and have my own structure, but they don't really tell you anywhere how you should go about it. Because of it, I would search GitHub to sometimes find answers on how to do some stuff, but you would quickly find that most people had no idea how to actually use it. For example you can find a lot of people making opening and ending partials to have a common page layout instead of actually using the built-in Hugo layouts. So why have I bothered switching? i18n support, so far out of all SSG I tried, Hugo does it in the least painful way. [1]: https://github.com/gohugoio/hugo/issues/4071 https://github.com/gohugoio/hugo/issues/4071 [2]: https://github.com/gohugoio/hugo/issues/385#issuecomment-283285745 https://github.com/gohugoio/hugo/issues/385#issuecomment-283... [3]: https://github.com/gohugoio/hugo/issues/1035#issuecomment-283133088 https://github.com/gohugoio/hugo/issues/1035#issuecomment-28... [4]: https://github.com/gohugoio/hugo/issues/448 https://github.com/gohugoio/hugo/issues/448 [5]: https://github.com/gohugoio/hugo/commit/6dbde8d731f221b027c0c60b772ba82dad759943 https://github.com/gohugoio/hugo/commit/6dbde8d731f221b027c0... [6]: https://news.ycombinator.com/item?id=30527884 https://news.ycombinator.com/item?id=30527884

monooso 3y ago

The fact that Hugo still doesn't play nicely with Tailwind 3 (2 years after T3 was released) is a real pain point. I gave up on this ever being fixed quite a while back, but still check on the issue [1] every now and then. Seems like the only activity these days is bep bumping the milestone every month. [1]: https://github.com/gohugoio/hugo/issues/8343 https://github.com/gohugoio/hugo/issues/8343

explodingcamera 3y ago
The latest reply in this GitHub issue links to documentation and a example repo showing that tailwind is supported though
fbdab103 3y ago
Still annoys me to no end that Hugo chose RSS and it requires some song and dance to make ATOM formatted feeds.
earthboundkid 3y ago
That issue should have been closed. This was resolved in Hugo 112. https://github.com/gohugoio/hugo/releases/tag/v0.112.0 https://github.com/gohugoio/hugo/releases/tag/v0.112.0
- monooso 3y ago
  Praise be. Thank you, I would never have seen that.

toddmorey 3y ago

Documentation and the go templating language. I just don’t find it readable. Here’s an example from the docs {{ if (and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")) }}

tgv 3y ago
This project uses another templating language, apparently based on Shopify's liquid like Jekyll. (1) https://github.com/osteele/liquid https://github.com/osteele/liquid
rjzzleep 3y ago
I completely agree. The go templating language is a nightmare. I probably learned most when dealing with Helm, but I've always been holding out hoping that something better would replace it. Does anyone know why the templating situation is the way it is in go? In many other languages you have multiple competing templating languages, but in go this is basically what you get. Are there language specific features that make it hard? EDIT: interesting to final see active liquid templating engines for go. now if only legacy would allow for the use of these things.
- znpy 3y ago
  > I probably learned most when dealing with Helm, My opinion is that helm does the completely wrong thing: patching text. It should instead patch objects, so that we don’t have to deal with indentation and other silly things. I don’t think it’ll ever change though :(
  - kevincox 3y ago
    I'm completely with you. Generating a data structure using a text templating language is just awkward and error prone. In fact I'm starting to think that text templates are very rarely the best option. It is usually better to have a proper emitter library or AST data structure that can be generated with "real" code. I guess one of the few places that text templates can provide value is when the template is untrusted. But maybe a sandboxed programming language is still a better option here.

dawidpotocki 3y ago

I have migrated from Jekyll to Hugo for my own website, but the whole Hugo project is just weird. It took me like a year to migrate my simple website because of all the different paper cuts that drained my will to work on it. You are only able to only use partials in HTML pages and shortcodes in Markdown pages. Why? They use 2 different syntax, so the best you can do is awkwardly wrap a partial in a shortcode. What's the point? They serve basically the same purpose. Want to set up RSS? Oh yeah, for some reason by default it will not show full content in your feed reader, instead only a small extract. The the only way to fix it is by making your own template[1]. But wait, why are we using RSS instead of Atom? Who knows, but if you want to use Atom, you have to use your template and insert some stuff to your config. Also don't look at the bug tracker, that thing is frustrates me to no end. You of course have the everyone's favourite Stalebot that you might have noticed in my previous link, but if you look at older issues, you will see the maintainer self-botting as a Stalebot[2][3] for some reason. You will also see the maintainer moving issues between milestones for years with no end in sight[4]. That's not a one-off, click on any issue. Changelogs can sometimes feel a bit, odd too: > but also a big shoutout to @dependabot[bot], […] for their ongoing contributions. And commit messages sometimes are just… a bit too long[5] (it is truncated by GitHub, you can append .patch to see the full message). Their documentation is awful to read too[6]. Oh and the templating engine? Yeah, not documented at all. Also the quick start guide will tell you to git clone some random theme, but I don't want my website to look like someone's, I want to write my own styles and have my own structure, but they don't really tell you anywhere how you should go about it. Because of it, I would search GitHub to sometimes find answers on how to do some stuff, but you would quickly find that most people had no idea how to actually use it. For example you can find a lot of people making opening and ending partials to have a common page layout instead of actually using the built-in Hugo layouts. So why have I bothered switching? i18n support, so far out of all SSG I tried, Hugo does it in the least painful way. [1]: https://github.com/gohugoio/hugo/issues/4071 https://github.com/gohugoio/hugo/issues/4071 [2]: https://github.com/gohugoio/hugo/issues/385#issuecomment-283285745 https://github.com/gohugoio/hugo/issues/385#issuecomment-283... [3]: https://github.com/gohugoio/hugo/issues/1035#issuecomment-283133088 https://github.com/gohugoio/hugo/issues/1035#issuecomment-28... [4]: https://github.com/gohugoio/hugo/issues/448 https://github.com/gohugoio/hugo/issues/448 [5]: https://github.com/gohugoio/hugo/commit/6dbde8d731f221b027c0c60b772ba82dad759943 https://github.com/gohugoio/hugo/commit/6dbde8d731f221b027c0... [6]: https://news.ycombinator.com/item?id=30527884 https://news.ycombinator.com/item?id=30527884