[atishay811]

Hugo’s documentation is a great reference and very well articulated. If you are looking for a tutorial and want to grow understanding, a book might be much better. I am the author of Hugo In Action (https://hugoinaction.com) and the objective of my book is to introduce the concepts slowly and with a running example for easily trying out.

[svnpenn]

> Hugo’s documentation is a great reference and very well articulated

No its not, and not its not. Hugo it easy to install and/or build, I will give it that. But the documentation has always been poor in my mind, with gaping holes for common uses that are maybe outside of the opinionated "norms".

[wink]

It's been a while, but I'd sum it up as:

I want to do A, B, C. Now I need to find out how A,B,C are called in hugo, how they relate to each other, which mandatory concepts D,E they depend on, how those relate to each other and then, if everything would be perfectly written, I might understand it.

I actually think it's a good reference. If you know what an archetype is and what you can do with it, just forgot the syntax? Bingo. To grasp what its good for? Not so much.

Maybe if someone collected a bunch of actual problems of "How do I ...?" and made them into a really good FAQ, that might help?

That said, I also don't have a solution - I think they've succumbed to feature creep a little too much. In the quest to let every non-programmer be able to tweak every single thing, now the non-programmer needs to learn a DSL.