4 ms·

Hugo's New CSS Powers

54 points by speckx 7mo ago

brycewray 7mo ago
Author here. This post arose out of a recent thread on the Hugo Discourse: https://discourse.gohugo.io/t/hugo-v0-158-0-released/56868 https://discourse.gohugo.io/t/hugo-v0-158-0-released/56868
- giancarlostoro 7mo ago
  Good call out from that thread is he's trying to get a small change in esbuild added to help with this as well. https://github.com/evanw/esbuild/issues/4419 https://github.com/evanw/esbuild/issues/4419
  - brycewray 7mo ago
    Yes; hope that gets blessed. We shall see.
- extra88 7mo ago
  BTW, there's a glitch in your code snippet syntax highlighting; in Light mode, the 'p' selector is remaining an unreadable yellow.
  - brycewray 7mo ago
    Whoops. Thanks for the catch. I was trying to trim down some of my CSS the other day, but inadvertently forgot to leave my `--cyan-700` variable. The yellow you saw was supposed to warn me, "Hey, you missed one!" but I apparently missed that one. :-/ Fixed.
nine_k 7mo ago
Nice! (But I must say that Zola has this built-in since forever.)
- brycewray 7mo ago
  For Sass, yes[0] --- as has Hugo[1]. Hugo's recently added `css.Build` function, based on esbuild, is for post-processing vanilla CSS. [0]: https://www.getzola.org/documentation/content/sass/ https://www.getzola.org/documentation/content/sass/ [1]: https://github.com/gohugoio/hugo/releases/tag/v0.43 https://github.com/gohugoio/hugo/releases/tag/v0.43 (July, 2018)
imagetic 7mo ago
Yeah Bryce!
rheakapoor 7mo ago
[dead]
TeddyDD 7mo ago
Don't use Hugo. The maintainers are so detached from reality it's not even funny. The project is about 12 years old, has +80k stars on github and used in production by many. Despite that still no 1.0 version and they introduce breaking changes for no good reason. You website will break all the time. I made a mistake of creating few websites with it and now I have to rewrite them all in other SSG because I refuse to participate in this circus.
- yoz-y 7mo ago
  Eh. It’s written in go. I just built the binary, stuffed it in my repo and continued to use the same version for years. Then when I wanted to update I rewrote my whole theme from scratch, recompiled and now I’m set for years again.
  - TeddyDD 7mo ago
    Good idea, sounds like the only sane way to use it.
  - wiether 7mo ago
    Yes that's exactly what I did. I have a docker image with a given version of Hugo and I've been using it for years now. That's the beauty of building HTML: you don't HAVE to stay up to date to get security fixes.
    - andreashaerter 7mo ago
      Is there a reason for OCI images? It is just a binary? I have all used versions in ~/.local/bin/ ~/.local/bin/hugo0.145.0 ~/.local/bin/hugo0.148.0 ~/.local/bin/hugo0.149.0 ~/.local/bin/hugo0.150.0 [...] and a convenience symlink ~/.local/bin/hugo, pointing to my "production" version. I can easliy call whichever version I like with hugo<tab><tab>. What am I missing?
      - wiether 7mo ago
        It depends on your workflow I guess, but the advantages of having a Hugo version tagged in an image: - sharing it easily between computers/users (docker pull registry/image:tag) - having the appropriate binary version embedded in your code through a docker-compose in your repo - having custom aliases dedicated to hugo included (build/serve/run...) - using the exact same image in your CI/CD - not "polluting" your local computer with some more stuff

54 points by speckx 7mo ago

Author here. This post arose out of a recent thread on the Hugo Discourse: https://discourse.gohugo.io/t/hugo-v0-158-0-released/56868 https://discourse.gohugo.io/t/hugo-v0-158-0-released/56868

giancarlostoro 7mo ago
Good call out from that thread is he's trying to get a small change in esbuild added to help with this as well. https://github.com/evanw/esbuild/issues/4419 https://github.com/evanw/esbuild/issues/4419
- brycewray 7mo ago
  Yes; hope that gets blessed. We shall see.
extra88 7mo ago
BTW, there's a glitch in your code snippet syntax highlighting; in Light mode, the 'p' selector is remaining an unreadable yellow.
- brycewray 7mo ago
  Whoops. Thanks for the catch. I was trying to trim down some of my CSS the other day, but inadvertently forgot to leave my `--cyan-700` variable. The yellow you saw was supposed to warn me, "Hey, you missed one!" but I apparently missed that one. :-/ Fixed.

nine_k 7mo ago

Nice! (But I must say that Zola has this built-in since forever.)

brycewray 7mo ago
For Sass, yes[0] --- as has Hugo[1]. Hugo's recently added `css.Build` function, based on esbuild, is for post-processing vanilla CSS. [0]: https://www.getzola.org/documentation/content/sass/ https://www.getzola.org/documentation/content/sass/ [1]: https://github.com/gohugoio/hugo/releases/tag/v0.43 https://github.com/gohugoio/hugo/releases/tag/v0.43 (July, 2018)

imagetic 7mo ago

Yeah Bryce!

rheakapoor 7mo ago

[dead]

TeddyDD 7mo ago

Don't use Hugo. The maintainers are so detached from reality it's not even funny. The project is about 12 years old, has +80k stars on github and used in production by many. Despite that still no 1.0 version and they introduce breaking changes for no good reason. You website will break all the time. I made a mistake of creating few websites with it and now I have to rewrite them all in other SSG because I refuse to participate in this circus.

yoz-y 7mo ago
Eh. It’s written in go. I just built the binary, stuffed it in my repo and continued to use the same version for years. Then when I wanted to update I rewrote my whole theme from scratch, recompiled and now I’m set for years again.
- TeddyDD 7mo ago
  Good idea, sounds like the only sane way to use it.
- wiether 7mo ago
  Yes that's exactly what I did. I have a docker image with a given version of Hugo and I've been using it for years now. That's the beauty of building HTML: you don't HAVE to stay up to date to get security fixes.
  - andreashaerter 7mo ago
    Is there a reason for OCI images? It is just a binary? I have all used versions in ~/.local/bin/ ~/.local/bin/hugo0.145.0 ~/.local/bin/hugo0.148.0 ~/.local/bin/hugo0.149.0 ~/.local/bin/hugo0.150.0 [...] and a convenience symlink ~/.local/bin/hugo, pointing to my "production" version. I can easliy call whichever version I like with hugo<tab><tab>. What am I missing?
    - wiether 7mo ago
      It depends on your workflow I guess, but the advantages of having a Hugo version tagged in an image: - sharing it easily between computers/users (docker pull registry/image:tag) - having the appropriate binary version embedded in your code through a docker-compose in your repo - having custom aliases dedicated to hugo included (build/serve/run...) - using the exact same image in your CI/CD - not "polluting" your local computer with some more stuff