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:WIKI to produce customer documentation From:"Cheryl Webber" <CWebber -at- seagull -dot- nl> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 24 Oct 2003 08:10:26 -0600
Hi all,
Noticed that WIKI has popped up here as well! :)
Background
----------
Company has 100 users -IT staff/dev/consultants etc. Our internal
documentation produced by developers/consultants are kept on the intranet
but hardly maintained. User documentation (uncompiled CHMs) is vice
versa-kept in wincvs,maintained by 2 writers.
Been put to us that WIKI might serve both the internal docs and user docs
as a 'repository' since it allows edits by everyone. When i mean user
docs, mgt wants ALL customer documentation to be in WIKI to allow support
to view/edit customer documentation if necessary. Bit leery of :
-having user docs being edited by all since there's no way to control the
amount of updates esp since there is a nightly build every day.
-placing all customer docs into WIKI requires a whole lot of re-formatting
(all cust docs are in HTML) ,plus the fact WIKI is not exactly printout
friendly,..
While i agree with using WIKI as a place for internal documentation -
project specs/dev notes/etc since it's quite handy for
-keeping up to date with developer's ideas/changes
-accuracy of info is current
my question is:
1. Can WIKI be used as a tool to output customer docuemtnation?
2. Should WIKI instead be used as a process tool e.g. placing parts of the
customer documentation on WIKI to be edited and then the new updates are
placed back into RoboHTML and re-compiled to create the final CHM?
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
