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 10:36:29 -0700
A wiki is by definition free-form. You can impose (or superimpose) a
form, but it's a lot of work, and if you get it wrong at the
beginning, reorganizing can be difficult or impossible. The more
important organizational structure is, the less sense it makes to use
a wiki.
Crowd-sourcing is the main reason you'd want to use a wiki rather than
a help authoring tool. How big is your crowd? In particular, how big
is the crowd of people who will be heavy contributors? If your crowd
is small and organizational structure is important, a wiki could be a
lot more work to maintain than a Flare / RoboHelp / FrameMaker /
whatever project.
If I were evaluating a wiki for documentation purposes, I'd look
closely at the wiki's own documentation.
On Wed, Aug 3, 2011 at 9:27 AM, Matt Moore <MMoore -at- connectwise -dot- com> wrote:
> I am not sure I understand "Any time a table of contents would be helpful". I have seen several wiki's that have table of contents. I am not intending to argue, I just want to understand. I do believe from my research that mediawiki does not have a TOC out of the box and it requires extensions to implement a TOC. There are other wikis that seem to provide it out of the box and some with documentation in mind.
>
>http://help.mindtouch.us/
>http://confluence.atlassian.com/display/ALLDOC/Atlassian+Documentation
>
>
>
> -----Original Message-----
> From: techwr-l-bounces+mmoore=connectwise -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+mmoore=connectwise -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Robert Lauriston
> Sent: Wednesday, August 03, 2011 11:57 AM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: Wiki for Customer Facing documentation?
>
> 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.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-
