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.
Steven Ovadia takes a look at AsciiDoc, an alternative to markdown.
Six tips for tech writers from Stephen King.
This article is for the English majors, the bookworms, the lovers of literature, and the people with humanities backgrounds who sometimes struggle with the question, "Do you ever use your liberal arts degree?" If you ever write code, the answer is yes.
How do you know when your documentation needs screenshots? Ben Cotton shares some helpful tips.