It's exactly like I thought from the title: The author lives with good and bad documentation every day so he can say clearly the requirements of a good documentation and what he's missing. The problem is that the topic says "this is a how to do it better" and that is not done by saying the requirements.

Of course it's hard to say how to do it better, which is exactly the reason why most people don't do it better: the good people often can't say why they are doing it better, just that they are doing it better. So what the author wants to teach here is something the author needs to learn first himself.

I feel a little disappointed for not getting that how to but wish good luck to the author, because he seems to be on the right path.