Developing software with documentation future programmers and collaborators will benefit from

See this talked about a lot—given lip service—in terms of the importance of “documentation”, but have best practices in transferability.

From Brian Dominick’s Codewriting:

  1. Lots of people in different roles can readily contribute to documentation efforts.
  2. Content is managed as discrete components of a whole, instead of merely at the document level.
  3. All content can be single-sourced, meaning tech writers and engineers maintain one canonical source of truth, no matter how many places that content needs to appear in the generated docs.

Over and over again, FarmOS has the best practices.

Best practice is to focus on how to get involved from the perspective of a new potential participant.

An example:

See for more best practices and