RE: Wiki as a documentation delivery system?

["Matt Horn" <mhorn -at- adobe -dot- com>]

Geoff Hart wrote> 
> So if you do use something interactive, make quite sure that 
> you provide strong access control. The ideal is a something 
> like a two-phase commit: in the first phase, someone provides 
> comments and suggestions; in the second phase, you or someone 
> you delegate vets the new material and decides whether to add 
> it to the wiki. 

If you make it difficult to add or collaborate, then it isn't a wiki. I
would guess there's an inverse relationship between the difficulty of
adding content and the amount of content added.

Matthew J. Horn
Sr. Technical Writer
Adobe Systems, Inc.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy.  Watch the demo at http://www.DocToHelp.com/TechwrlList

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -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%40infoinfocus.com


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

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