Re: Going Wiki for documentation?

[Jay Maechtlen <techwriter -at- covad -dot- net>]

At my current gig, there are at least two Wiki platforms on at least
three servers and at least two (apparently separate)Wikis on one of the
servers.
These for a company of 600+ employees (growing fast!)

Oh, yes- they are also deploying a new Intranet, based on Sharepoint.

It seems to take quite some effort to keep people using a Wiki. It has
to be substantially better than other options available to them, and it
better be easier too.

The Wikis we have (the ones that I've seen, anyway) are ok- for simple
stuff. As a site grows, ir can either sprawl (terrible long pages) or
fragment (a zillion pages, hard to find)

Tagging can help, probably other things too.

Seems to me like a really poor medium with which to document an API.

ymmv
Jay

Jay Maechtlen

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.