Switching to Hugo
275 words — 2 min read
I’ve gone ahead and rewritten my website in Hugo🔗. This was a long-time coming change, especially after I wrote the first version of UserStyles.world in it.
In a way, I needed a semi-fresh start. While there’s a lot to like about Zola, I use Go templates a whole lot more and I find that Hugo offers a much greater flexibility in a bunch of ways. It might even get me to spend more time on a knowledge base side-project I’ve been toying with on and off in Go.
Just like in the case of the author of Zola, Go templates drove me crazy at first. Over time, I actually started to prefer them over Jinja2-like template engines. Honestly, it took a lot of trial and error to get to that point.
At this point, they seem rather easy to use. Hugo’s extensive documentation, while helpful a lot of the time, was simply too overwhelming. It has received a lot of love over the years, but it’s still not as beginner-friendly as it could be. Anyways, this is just my experience with trying to learn how things work by building things from scratch instead of copying from themes. In retrospect, it does take a while to get used to how Go templates work, but it’s worth the time.
All in all, I’m glad to have finally made the switch to Hugo. There’s one more major change that I want to implement to accommodate for the upcoming posts, but more on that at a later date. It’s something that excites me a lot. Similarly to this post, I also wanted to do it for the longest time.