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.
Hi Whirlers,
My company started a major facelift of the web-based management utility
of our products (datacom HW) and I need to come up with a suitable help
system. Since the products act as web servers, the major problem is lack
of memory in the products, so the 3-pane help is out of question due to
its memory-expensive overhead. I looked at some other vendors to see how
they implemented different solutions and I basically saw 2 approaches:
many small topic-based html files or feature-based html files. The idea
is that each time, only 1 file is opened, while the rest stay compressed
in the product. To further complicate things, users will be able to
customize their interfaces, so I can't really know what they see on the
screen at any given time. Did anyone deal with this sort of thing?
Ideally I'd like to set up an automatic system that transforms
pre-marked portions of our Word manuals into html files. And this is the
easy part of the project. When it comes to field tooltips, I'm really
clueless.
Help, please!
TIA
Erika
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l