Don’t we all? But we can’t expect @bep deal with that single-handedly, can we? Not with the number of the open issues in the repository…
That person you quote from claims to love Hugo, claims to see the big issue with its documentation, and claims to have impressive background in writing documentation, so obviously is capable of helping fix that issue, at least to some extent. It’s really great to have someone like that on board as an active member of the community, I’m sure he contributed a lot to the hugoDocs repository since he wrote that piece, let me just check… Oh, yeah, nevermind.
It isn’t. What is actually necessary is:
- identify the issue (you already kind of did that),
- find someone who knows how to fix it and cares enough about it to share the knowledge,
- find someone who can do what needs to be done based on the abovementioned knowledge (not necessarily the same person as above) and cares enough to do it for the community.
You see, there are no SSG folks up there on Olympus Mountain doing their coder/devs things without caring much about Joe User. It’s just people who care enough to dedicate their spare time. Everybody is welcome to join. Every contribution matters.