I tried Hugo on a quick prototype for a API documentation site, but quickly ran into limitations in the go template engine and how Hugo handles variables.
It's great for a simple static site, but without a way to extend the template engine easily, there was no way to do what we wanted (which was to style a yaml file of service metadata into a swagger like UI).
I agree -- I have two blogs in Hugo, which I really liked, but have built the biggest site in Jekyll and the Liquid templating language is super powerful. However, Jekyll quickly got slow owing to the same powerful templating language. Always tradeoffs :)
It's great for a simple static site, but without a way to extend the template engine easily, there was no way to do what we wanted (which was to style a yaml file of service metadata into a swagger like UI).