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.
Re: Configurable On-Line Documentation: Tools and Technologies
Subject:Re: Configurable On-Line Documentation: Tools and Technologies From:Amanda_Abelove -at- toyota -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 2 Mar 2005 16:21:49 -0800
Hi--
Here's how I did it... If anyone has a less painful solution, please set
him straight... Don't want to send him up a fjord without a longboat!
I hit this problem with Island Pacific's retail solution and did it with
help from the nice folks at eHelp. The hardest part is figuring out
within each module, what the different combinations are, especially if the
config file is set at the system level and there is no
function/component/table traceability... The total possible combinations
are finite. Once you map that out, id 2 names for the feature: on or off.
Choose whether it is organized by task or function...Then:
1. Design the help so that each module has it's own master help project
and per module the UI points to the layout for it based on the config
file.
2. Create sets of tasks or sets of functions according to how the config
file is set
3. Flag them at the topic level as to which ones they "belong" to when
"on"
4. Sort it down from that level. Try to avoid having the flags set at the
text level if possible.
5. Create layouts for each possible combination.
6. QA it. Use the "Off" setting to get around problems.
7. Publish it.
This is a nightmare to implement. I was able to do 2-6 before management
changed. The developers had the hardest time doing #1 because there was
no way to do it without the web interface which was coming out in a
planned iteration.
Tip: The script that points to a help URL should pull the URL from a table
b/c future versions will require additional layouts. Don't hardcode the
help URL into the GUI.
Thanks!
---Amanda
Amanda Abelove
Technical Writer, (562) 468-6678
amanda_abelove -at- toyota -dot- com
amanda -at- abelove -dot- com
Cell: 310-430-0049
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
Doc-To-Help 7.5 Professional: New version with new features, improved performance and reliability, plus much more! Download your free trial today at www.componentone.com/techwrlfeb.
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -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.