For documentation, an approach that works for me is to think of all the questions someone might reasonably have about the software, and start with those as sect

For documentation, an approach that works for me is to think of all the questions someone might reasonably have about the software, and start with those as section headings: * What is this? * How do I install it? * How do I use it? * Is there a change log? * What license is it released under? etc At some point when doing that, the content starts to flow and it gets easy to just naturally edit the whole thing into a doc that makes sense.