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.
One of my writers is working on a Winhelp project for an application
that may be customized for specific clients. She and the developer
have been speculating on how best to produce the customized help
without a lot of redundant effort.
What they're considering is creating separate help files for each area
of product functionality, so they can choose which help files match
the product features the specific client needs. These separate help
files will then be combined and compiled together to produce a single
help file. Kind of an object-oriented approach, with an emphasis on
information re-usability.
Has anyone done this, and if you have, what advice can you offer?
We're using Doc-to-Help 1.6 as our authoring tool, by the way.
Thanks,
Brett Peruzzi
Documentation Manager
First Data Investor Services Group
Boston, MA
Brett -dot- Peruzzi -at- fdc-invest -dot- com
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
