http://tc.eserver.org/dir/Articles/Documentation/Technical-Writing/Wikis A listing of the most recently indexed works about Articles and Documentation and Technical Writing and Wikis in the field of technical communication (and technical writing). en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Articles/Documentation/Technical-Writing/Wikis http://tc.eserver.org/33635.html http://tc.eserver.org/33635.html Many people have predicted that wikis will replace traditional help in the future. Ok, I can buy that. But I've also heard that technical writers will surrender content control to SMEs and users, and will move into other roles such as merely editing wiki content, or switching to programming, training. Sorry. I just can't see that happening. In the world of wikis, technical writers will still be kings of content. http://tc.eserver.org/32816.html http://tc.eserver.org/32816.html Learn about theoretical and practical examples of merging DITA (Darwin Information Typing Architecture), a structured authoring methodology, and wiki’s freeform authoring and editing capabilities. http://tc.eserver.org/32817.html http://tc.eserver.org/32817.html So how did the wiki become a seemingly permanent fixture in the landscape of today’s Web? Which wikis have succeeded as technical documentation, and how can we replicate their success? http://tc.eserver.org/31107.html http://tc.eserver.org/31107.html The dynamic nature of wikis can cause a few headaches when you need to baseline documentation that's on a wiki to correspond with the release of your product. This blog post looks at some ways in which you can try baselining wiki content. http://tc.eserver.org/31109.html http://tc.eserver.org/31109.html User-generated documentation is a big issue in technical communication circles. If properly done, tapping into the knowledge of users can improve the quality and breadth of your documentation.