Hacker News new | ask | show | jobs
by rsolva 1574 days ago
I have brought up this exact point on the Hugo forum before [0]. Hugo would become much more accessible if the documentation would be split into the four categories mentioned in the link you provide.

This way of thinking about documentation should be the default, and any open source project (or closed for that matter) would benefit hugely by adhering to these simple principles!

0: Discussion: https://discourse.gohugo.io/t/feature-overall-ease-of-use/34...

1 comments

I tried to start a discussion about documentation as reference vs. tutorials on the forums too: https://discourse.gohugo.io/t/discussion-of-hugo-theme-from-...

I think the problem is just that no one wants to bell the cat. :-(

> no one wants to bell the cat. :-(

Never heard this refrain before! What does it mean? No one wants to get on leadership's bad side?

https://en.wikipedia.org/wiki/Belling_the_Cat

> Belling the Cat is a fable ... In the story, a group of mice agree to attach a bell to a cat's neck to warn of its approach in the future, but they fail to find a volunteer to perform the job. The term has become an idiom describing a group agreeing to perform an impossibly difficult task.

Of course a quick web search answers your question. The fable is that all the mice would like to have the cat wear a bell, but despite the obvious benefits, there are no volunteers for the dangerous task.
I really like the saying 'bell the cat' as well. Anyway, came here to say that I started to do this (create the missing documentation that would've been helpful for me) - it is by no means ready ( on mobile this site looks almost unreadable ) but it is a start: www.hugotutorial.com - if you have any feedback, I would love it!