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.
Hello All,
I have a question regarding using multiple help (.hlp) files or a single
help file with multiple .RTF files.
Here's the situation:
Our company maintains several software products, all of which can work
in conjunction with the "parent" product. However, some of those
products can also work on a standalone basis. Our dilemma is that when
these products work together, they share certain processes.
We want to be able to link each of the products together so you can find
help on a certain topic without having to go into the other product and
access Help.
Our question is how we should structure our Help Files:
One Help/multiple .RTFs
Or
Multiple Help files.
What kind of experience do any of you have in this area. Our company is
pretty new to online help, so any input would be greatly appreciated. I
didn't have time to check the archives, and I apologize if this was
covered there.
Thanks in advance,
Aaron W. Morrison
Technical Writer
Medic Computer Systems, Inc.
My views are my own and not those of Medic.
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
