Technical+Writers+and+Wikis+for+Documentation

Some Technical Writers feel threatened or unimpressed by the recent trend of using Wikis for documentation. However, Wikis can be incredible helpful to Technical Writers.


 * Why Wikis Can Be Good for Technical Writers and the Industry**

The Pix/Atlassian article, [|Technical Writing in a Wiki-Technical Communicators Explain How and Why] includes a serious of comments from the Atlassian technical writing team regarding Wikis for technical writing purposes.


 * Wikis and Technical Writing** (Categories by Pix/Atlassian)

Wikis are helpful when it comes to the multistage process of technical writing. They are easier to edit than most HTML or XML editors, which allows the technical writer to simply focus on the writing**.** Wikis are also great for communication among team members and is helpful in information exchange and collaboration among developers. Writers can also get a preview of new ideas, both confirmed and rumored, that will be added to the product. (Pixsoftware, 2010)
 * 1) Wikis are good for technical writers**

Wikis are easy to search through and can offer a customer more than traditional documentation could in that Wikis can include videos, embedded help, and other features that can aid the user. Also, many Wikis can be exported as documentation in a variety of formats, such PDF and HTML. Customer support is better because Wikis can provide instant feedback, up to date information, alerts, and comments (Pixsoftware, 2010).
 * 2) Wikis are good for customers**

Brand loyalty and good feeling among customers can come out of the community functions of a Wiki. Customers can help other customers, outside sources can write documentation, and external developers can add code samples. Also, Wikis can help you save a lot of money when it comes to the documentation process as they are easy to install, access, use, and learn (Pixsoftware, 2010).
 * 3) Wikis are good for companies**


 * Benefits of Wikis for Technical Writers** (Categories by Dr. Akinci)

In his blog post [|Technical Writing- How Wikis will transform technical writers into Information Coordinators], Dr. Ugur Akinci looks at how Wikis can be beneficial to technical writers.

For starters, a Wiki is a place where marketing, sales, developers, writers, and every other area can easily see what the other members of their team are doing and communicate with each other in one document that lives online, but it is not a webpage. Wikis give technical writers the ability to [|keep all of their documentation for one project in one area], and then allow the engineers, editors, project managers and others come in and read, leave comments and feedback and do their part, all in one place.

1. **Wikis allow for a collective knowledge base** Many high-tech companies have begun using Wikis for their documentation because it can allow for authors from many different areas of the company to exchange information. Technical writers, engineers, field technicians, managers, clients, and many other personnel can utilize the same Wiki and put their individual knowledge into it.

Wikis provide an easy way to track each member's productivity and add to the efficiency of the entire project development process. This allows for efficient and quick communication exchange among departments and people. Dr. Akinci also cites that this is helpful during the editing process, for technical writers can edit the work of others easily and effectively. He believes that the role of technical writers may look more like Wiki monitors or conductors in the future.
 * 2. Wikis can increase workflow and productivity**

The Helpscribe.com blog post entitled [|Why Wikis Won't Kill Technical Writing]adds another great reason for why Wikis are beneficial to technical writers, and that is that technical writers will always be needed. Editing, crafting, cross-referencing, and other technical writing skills are essential to a good Wiki. Already having extensive experience with organizing print and help documentation, technical writers are essential and important in the building and maintenance of a Wiki.
 * 3. Wikis require organization, and technical writers are the best at it** (Helpscribe.com)

For difficulties that Wikis present to technical documentation, go to Hurdles and Hardships using wikis for technical documentation.

Sources: Akinci, Ugur. //Technical Writing: How Wikis will transform technical writers into information coordinators.// Technicalcommunicationcenter.com. web. 7 Nov. 2011. //Why Wikis Won't Kill Technical Writing.// Helpscribe.com. web. 7 Nov. 2011. //Technical Writing in a Wiki: Technical Communicators Explain How and Why//. Pixsoftware.nl.guestblogs, 20 Oct. 2010. Web. 7 Nov. 2011. Mason, Will. //Wiki Discussion//. Drexel University. Web Conference. 19 Oct. 2011. Odell, David. [|Using a Wiki in Technical Documentation]. Technical Communication Center, 17 Feb. 2010. Web. 8 Nov. 2011.