TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Wiki for Customer Facing documentation? From:Robert Lauriston <robert -at- lauriston -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 3 Aug 2011 08:57:25 -0700
I think wikis are appropriate only when there's no hierarchy or
logical sequence for the topics. Any time a table of contents would be
helpful, a wiki is probably the wrong tool.
A wiki can be a good tool for a knowledge base so long as you can and
do set up permissions and approvals so that everything runs past an
editor before customers see it.
On Wed, Aug 3, 2011 at 6:42 AM, Matt Moore <MMoore -at- connectwise -dot- com> wrote:
> As we are evaluating documentation solutions (moving from a failed content management solution), we are also considering the use of a wiki such as mediawiki or mindtouch. It does appear that wikis are commonly used for this purpose and do present many benefits over a HAT but of course HATs provide benefits as well.
>
> What are your thoughts on using a wiki over a HAT or vice versa?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
