Think about the kind of documentation you like to read, and write that. If people don't like it, you can be sure they'll let you know.
Find out how Read the Docs aims to make documentation a little easier.
Your first pull request doesn't need to be a major one. Learn how to contribute to an open source project on GitHub in three easy steps.
Three considerations and accompanying resources to keep in mind as you write documentation.
Written in Perl, Plerd can be told to watch a Dropbox-synched directory with the plerdwatcher daemon, which will republish files as it sees changes.
Six non-code opportunities for contributing to open source software code and communities.
In this interview, Dru Lavigne explains how Sphinx is different from other open source solutions, and what kinds of projects should consider migrating their docs.
We look at the 7 rules for writing world class technical documentation and which projects are getting it right.
When I talk to college students who are working on their first open source projects, the message I emphasize over and over and (yes, one more time) over again is the importance of working openly. And yet, as I discovered myself while writing this post, working openly is harder than it sounds.
Learn how three tests can help you improve the readability of your documentation.