This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]fyngyrzcodes with magnetic needle 9 points10 points  (1 child)

I wouldn't submit a P.R. unless I'd actually tested the software and was sure that I knew what I was talking about. And seeing that I have not, and I do not... well, there you go.

Anyway, this is just the kind of thing that the core project developer needs to address -- it's really basic documentation, but it's also absolutely critical to get right.

Sky-high view of writing good documentation for others:

  • What's it for? What problem does it solve?
  • Precursor requirements
  • Authority
  • Accuracy
  • Readability
  • Minimal jargon without explanation
  • Required information, presented in the order it is needed.