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.
Should table of contents be organized by functionality or by menus and context-sensitive help topics?
Subject:Should table of contents be organized by functionality or by menus and context-sensitive help topics? From:karin -at- kgcreations -dot- com To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Tue, 25 Nov 2008 14:01:14 -0500
Our technical writing team disagrees about how to handle the TOC.
Currently, our product's help file centers on context-sensitive help
and the TOC is based on the software's menus rather than functions or
procedures. These are not general menus like File or View.
To me, using the menu names to organize help makes it hard for someone
who is looking for procedures to find what they need. If you don't
know which feature to use to do something, how would you know where to
look in the TOC? (Okay maybe you would search, but the search isn't
that great either--that's another topic.) A couple of us think the
help TOC should list functions based on what the user needs to do.
It's okay to have context-sensitive topics and menus listed, but not
as the primary structure of the TOC.
The third writer believes the TOC has to be based context sensitive
help and menus, and insists that is the norm everywhere. But when I
look at the help files for the programs I use, the TOCs are function
based. A few help files have an interface or menus section, but they
don't organize topics by the software's menus.
Here is an example:
Context sensitive:
MENU
--System Setup
-----XXXX
-----XXXX
-----XXXX
--Administration
-----Application Setup (These are not the same as system setup)
--Reports
-----Report Formats
-----Report Selector
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-