4 ms·
I've built two client sites with Hugo recently with great success: https://www.halorestorationservices.com/ https://www.halorestorationservices.com/ and http://
by justajot 10y ago
I've built two client sites with Hugo recently with great success: https://www.halorestorationservices.com/ https://www.halorestorationservices.com/ and http://www.laviagelaw.com/ http://www.laviagelaw.com/. Both are fairly extensive in their use of templates and Hugo's features.
That said, I typically grab from site templates and don't do a lot of css/js manipulation myself. Though, if I did, I'd just set-up Grunt or Gulp to handle automatic regeneration of the final asset files.
For those asking why should you switch? Well, exactly, why should you? If you are happy with your current toolset and are productive using it, isn't it all about the final product anyway? Who cares what you use. But if you aren't happy with your toolset, or are just keeping an eye out for something that might be better ...
Hugo is known most for its speed. If you have a site with many, many pages that needs to be built quickly, strongly consider Hugo. It really is super fast. I'm actually considering building out a very large sample site with various engines to demonstrate just how fast it is. I'll try to find this post on Hacker News again and post if I ever get around to it.
Layout of content is extremely nice in Hugo. Basically, you just organize everything in directories how you want it to be rendered in the end. This can be overridden if necessary.
Documentation is also really nice. I'm actually about to build another client site and considered using Jekyll (you know, just to see), but found the documentation lacking compared to Hugo. It also seems to needlessly complicate things, but that's probably just personal opinion based on prior experience with Hugo.
There are a few downsides obviously. You get what you get, unless you want to add functionality and recompile. But now you have to maintain your own version.
As parent5446 mentioned, variables can be a bit confusing. They are not as idiot proof as I'd like them to be.
- nathancahill 10y agoI agree with you about everything except the documentation being very nice. I was stuck on somewhat of an edge case, and the tutorial style documentation doesn't help for that. I ended up wading through the forum, which is cool to have, but not the same as authoritative docs.
- spf13 10y agoThanks for this feedback. We are striving to make the docs as good as we can. We would love to hear more about your experience so we can improve the docs further.
- justajot 10y agoI would agree that the doc quality has been steadily improving.
- justajot 10y agoI too am curious about your edge case. I have had to wade through the forums, or even check out blogs for a few things myself. Though, I'd be surprised if this wasn't the case with another tool.
- dimovich 10y agoCan I ask you, what libs do you use for the layout and theme?
- justajot 10y agoThe Halo site was built with a modified version of the Assan template available on WrapBootstrap.com - so Bootstrap, jQuery and the like. It's not perfect, but I strip out unnecessary plugins and combine most of the assets to minimize resource loading. Ideally most of the unused CSS and JS would be stripped out too to further reduce load times, but this becomes a lot more complicated and is usually not worth it for a variety of reasons. The lawyer site was done with the Elevation theme from Templated.co. Less manipulation here, other than a few changes of tags for SEO purposes. No CSS framework (that I know of anyway), skel.js and jQuery.
- dimovich 10y agoThank you.
- Rapzid 10y agoOh man, I just have to comment. These sites are blazing fast. This is to be expected with static sites, but.. You just don't see them like this much(WP FTL). Props!
- StavrosK 10y agoIs Hugo very blog-oriented, like Jekyll? I started using Lektor and quite like its data-agnostic model, but I would like something more actively developed.
- spf13 10y agoHugo is not blog oriented and works well with any site structure. A good way to a lot of different ways of how people are using Hugo is with the site showcase. http://gohugo.io/showcase/ http://gohugo.io/showcase/
- StavrosK 10y agoThat looks great, thank you! It also looks pretty actively developed, so I'm going to have to give it a look!
- duckmysick 10y ago> I'm actually considering building out a very large sample site with various engines to demonstrate just how fast it is. I'll try to find this post on Hacker News again and post if I ever get around to it. That would be fantastic. Do you have any shortlist of engines you are going to test? Also, I have a question about the two website you've built. Did you also write the copy (content) yourself or was it sourced from the client/a third-party?