Quality content is tip-toeing to the front lines as something that's not only valuable for users, but to contributors as well. If good docs can help new users learn your software, it also can help new contributors get involved with your open source project.
Nigel Babu offers 10 tips for taking your project's documentation to the next level.
Reporting from OSCON 2015, Nicole Engard offers an overview of a keynote from Una Kravets, who spoke about ways open source communities can recruit designers to enhance their projects.
Learn about the benefits of applying DevOps principles to open source documentation.
How does OpenStack merge over 900 documentation changes in less than three months? We treat docs like code and continuously publish reviewed content from multiple git repositories.
Holding a successful doc sprint requires some thought and planning. Here are five lessons learned from years of both organizing sprints and observing other people's sprints at Open Help.
This week, Opensource.com began two new series. A couple from our OSCON speaker interview series made it into the Top 5 this week, but none quite hit the mark from our Mid-Year series. The Mid-Year series is comprised of some fun roundups, so here's the full collection for your reading pleasure.... Read more
Translating documentation takes time and effort, but not nearly as much as starting over from scratch. With a few tips, you can streamline the translation process and get readable, useful results.
Which came first, the program or the documentation? Therein lies the dilemma.
In part one of a three-part series, we explore how to apply content strategy principles to technical documentation, so that we can create the right content, for the right users, and deliver it to them at the right place and at the right time.