Ask HN: How to write good documentation as a team
In the team I work now (which works on an internal framework) there are 7 People working on features and everyone is writing some part of the docs and the difference in style is very noticeable.
Some like to write from the personal perspective (I), others in a teaching manner (we, you) [have,could,should]. Some write in an asking manner, other in a commanding manner. Then there is the debate between as concise as possible and "enjoyable to read" as possible ("Go to foo for more information." <-> "If you would like to read more about this topic, head over to the foo section.").
We have a Pull-Request guide that has some review points concerning documentation. But I feel like it's only partially effective. So I was wandering, how is HN approaching their documentation writing.