Over the last couple of years, I’ve heard more than a couple of people say that the wiki will kill (or at least bite into) so-called traditional documentation. I’ve never subscribed to this point of view. While I could spend several thousand words explaining why, someone else has done it for me. Just read this blog post by Craig Haiss.
One complaint that’s often made about free and Open Source software is that its usability is lacking. This article by Celeste Lyn Paul (who works with a number of Open Source projects) takes a look at usability in Open Source software.
Being a designer in an open source project is not easy. For many years, usability specialists were disregarded, under appreciated, and ignored. This attitude probably sounds familiar to many of you because it was not too long ago that professional usability specialists encountered the same resistance.
That observation also applies to the development of a lot of commercial and in-house software, too. And it’s not just the designers and usability architects who face the obstacles. Technical communicators who act as user advocates (and shouldn’t we all?) often face an uphill battle against developers in this situation, too.
- Open source solutions are often a better fit
- Open source solutions are often standards-based
- Open source solutions are more transparent
While Open Source may not be the best solution for an enterprise, in any area, the solutions available are definitely worth a look.
Like them or not, wikis are becoming more and more common in various enterprises. And they’re not just a developer’s tool anymore. They’re used fairly extensively for documentation, too. The beauty of wikis is that they’re easy to use and that they’re living documents. The content on a wiki is constantly being updated and (you hope) refined.
The dynamic nature of wikis, though, can cause a few headaches when you need to baseline documentation that’s on a wiki to correspond with the release of your product. That’s the problem that we ran into at the firm at which I’m working right now.
Anne Gentle posted a very interesting piece on DITA. Part opinion, part analysis, part musing this post is definitely a must read.
This post got my, yet again, thinking not just about DITA but about one of the concepts that underlies DITA: structured, topic-oriented authoring.
A couple of days ago, I was trying to catch up on some online reading and went over a series of posts, titled Technical Writing in Transition, at Chris Borokowsi’s User Advocacy blog. If you haven’t read these post, you should. They’re interesting, detailed, and they get right to the point.