Hurdles+and+Hardships+using+wikis+for+technical+documentation

In her blog-entry entitled "[|Hurdles and Hardships using Wikis for Technical Documentation"], Anne Gentle, author of //Conversation and Community: The Social Web for Documentation//, states that wikis can present numerous problems when used in conjunction with technical documentation.


 * Problems with Wikis for Technical Documentation** (Categories by Anne Gentle)

1. **Access Control**- The freedom for anyone to write in the wiki can be problematic because of differing agendas between contributors. One writer could be trying to sell the product while another is trying to communicate how awful the product is. Though good for discussion, this feature might not be conducive for good documentation. 2. **Hierarchy-** Without an agreed upon hierarchy to naturally organize topics, tech writers can have a difficult time using Wikis, especially when dealing with complex documentation sets. 3. **Version Control-** It is hard to keep track and find information when there are so many different versions of a group of topics 4. **Global Search and Replace (and Spell Check)-** Wikis are more difficult to use for these functions than programs such as Framemaker, which technical writers are much more experienced and familiar with. 5. **Search on the Site Itself-** Local search engines cannot compete with Google in effectiveness. 6. **Workflow-** Wikis, with their extra steps and distractions, interrupt the work process. 7. **Creating Collections-** It is hard to make a single source output (such as a PDF) for creating collections of articles from a Wiki. 8. **Offline Access-** Wikis require Internet access, which can be annoying in times where the internet is not easily available (such as on a plane). 9. **One-Click publishing (batch processing)-** With many wikis, you have to go to each individual page to finalize the project for publishing. There is often no way to finalize all the topics at once.

In addition, wikis require intense stewardship and attention, and this job usually falls to a very dedicated leader or a small core of lead editors. Also, since authorship on wikis is diffuse and not often credited, getting this kind of leadership and therefore successfully starting communities around wiki projects can be very difficult.

There is also the question of the knowledgeably of the person updating the wiki. Gathering information, background and experience in a particular tool or technology is incredibly time consuming. Narrowing all this information down into something that is useful to someone is a considerable task. The wiki process is really great for the evolutionary process of creating a text, but it's not particularly conducive to facilitating the kind of process that documentation must go through.

For benefits of Wikis to technical writers, go to Technical Writing-How Wikis will transform technical writers into information coordinators

Sources: Gentle, Anne.//Hurdles and Hardships Using Wikis for Technical Documentation//.Justwriteclick, 31 March 2010. Web. 5 Nov. 2011. Kleinman, Sam. [|Wikis are not Documentation]. tychoish, 14 September 2010. Web. 6 Nov. 2011.