One of the ways that we encourage non-coders to contribute to Open Source projects is by writing documentation. And sometimes, as developers, we tend to look down on writing documentation. Personally, I think it's one of the most critical part of a project. If the documentation is hard to sort through or hard to read, there's going to be a whole bunch of frustrated users and contributors.
How can you write good documentation? Last July, I attended an unconference called "Write the Docs" in Berlin and we had an open discussion about how to create an environment for building good documentation. In this talk, I'm hoping to present some of the ideas that we came up with during those conversations and also talk about what we did in the CKAN project to make our documentation far better than it used to be.
Track: Main Conference