I've been thinking about this a lot in the context of open-source software projects
I can't tell you how many times, when I've across one that really took off, a key component in its success -- maybe *the* key component -- was the quality of its documentation
Random users could dive in and try it out without getting stuck and needing wait on help (or snarky abuse) from forums
Those projects *soar*
@clive @shannonmattern Yes, yes, 1000x yes. Clive, I'm going through this right now, falling down a rabbithole of Docker, npm, Linux, node, dependencies and conflicts, and when you find a man page or a readme file that is clear and well-thought-out and well-designed, you feel like you're being taken care of.
Shannon, my feeling is that there is this expectation of academic writing that it has to "sound official" which often is at the expense of being clear and concise.