RE: using a wiki as your primary authoring tool & delivery mechanism

Subject: RE: using a wiki as your primary authoring tool & delivery mechanism
From: "Simon North" <Simon -dot- North -at- quintiq -dot- com>
To: "'TECHWR-L'" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 07 Jan 2008 12:19:03 +0100

Hi,

I introduced a wiki here about 2.5 years ago as a primary authoring
tool, though not for all documentation.
It's taken me a long time to nursemaid it into full adoption but now
(helped along by my persuading the
CEO to start a blog on it too) it has now become mainstream. It's a
wonderful place for FAQs and HowTos
and for assembling documentation.

About 3 months ago, we started to port part of the internal wiki to an
extranet and it is now available to
customers. Later this year I plan to extend the external wiki and give
customers write access.

I use dokuwiki because it's flat (non-database) structure enables me to
swap files in and out more
easily and it has a much lower threshold than most other wiki (for me
that was an issue as I wanted
non-technical staff to be able to contribute as well).

For me, this has been almost as big a milestone as when I introduced an
Intranet at a previous employer
back in 1994.

The most important factor is to evangelize.

Simon





Simon North, Technical Writer.
Quintiq Application Software BV
's Hertogenbosch, The Netherlands

---
"Computer interfaces and user interfaces are as different as night and
1".



This message contains information that may be privileged or confidential
and is the property of Quintiq. It is only intended for the person to
whom it is addressed. If you are not the intended recipient, you are not
authorized to read, print, retain, copy, disseminate, distribute or use
this message or any part thereof. If you have received this message in
error, please notify the sender immediately and delete all copies of
this message. Please note that e-mails are susceptible to change,
therefore they are not binding.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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.


References:
using a wiki as your primary authoring tool & delivery mechanism: From: Fiona Krycek
Re: using a wiki as your primary authoring tool & delivery mechanism: From: Sandy Harris
RE: using a wiki as your primary authoring tool & delivery mechanism: From: Gordon McLean

Previous by Author: Re: Including PDF Bookmarks for Tables and Figures
Next by Author: Re: TECHWR-L Digest, Vol 27, Issue 15
Previous by Thread: RE: using a wiki as your primary authoring tool & delivery mechanism
Next by Thread: Re: using a wiki as your primary authoring tool & delivery mechanism


What this post helpful? Share it with friends and colleagues:


Sponsored Ads