I enjoy reading about the processes used by other technical communicators and those working on various types of projects. Not everyone will tackle a project in the same way, and there’s often something to learn (or at least to get me thinking) by studying someone else’s approach.

While the Free/Libre/Open Source (FLOSS) community is sometimes seen as a bunch of unguided missiles heading towards the same target, it’s actually more structured than that. This guide, from the Fedora Project, is a detailed look at one approach a FLOSS project uses to develop documentation.

Related posts:

1. Learning from each other
2. Developing knowledge base articles
3. Conversations about community documentation