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.
Suggestions on how to "hide" UI-based topics in online Help TOC?
Subject:Suggestions on how to "hide" UI-based topics in online Help TOC? From:Geoff Hart <ghart -at- videotron -dot- ca> To:techwr-l List <techwr-l -at- lists -dot- techwr-l -dot- com>, Donna Barbieri <deebeema -at- yahoo -dot- com> Date:Mon, 24 Mar 2008 16:25:56 -0400
Donna Barbieri reports: <<I am working as a contractor at a company
that had a Tech Writing intern... This intern produced an entire
WebHelp system for the application. However, the Help system is 100%
UI specific. Topics such as "using XYZ" really include information
about what is on a particular screen. I have been tasked with
creating "usable" Help for first time users AND with keeping the
existing Help for a release in the next two weeks.>>
That's not hard to do: simply create a new master topic that groups
all the existing help as a "Reference" section, organized based on
the dialog box or field names, then add a new "Tasks" master topic
that you will create to group all the high-level tasks. You can then
link from the task to the corresponding reference material wherever
it's necessary for readers to learn the details of a particular
dialog. From the reader perspective, they'll see the two obvious
entry points into the help system: task-based if they need to learn
how to do a task, and reference-based if they already know the task
but need details of individual steps or fields or whatever.
It's less efficient than combining the two into a seamlessly
integrated system, but (a) you state that you don't have a choice
about retaining the reference information in its present form and (b)
you only have two weeks to get the job done, so you don't have time
to fight this particular battle. For subsequent revisions, you may be
able to persuade them to merge the two sections, but for now, this is
at least a workable alternative.
---------------------------------------------------
-- Geoff Hart
ghart -at- videotron -dot- ca / geoffhart -at- mac -dot- com
www.geoff-hart.com
--------------------------------------------------
***Now available*** _Effective onscreen editing_
(http://www.geoff-hart.com/home/onscreen-book.htm)
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-