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.
Opinion on outline numbering for chapters/sections?
Subject:Opinion on outline numbering for chapters/sections? From:Geoff Hart <ghart -at- videotron -dot- ca> To:TECHWR-L List <techwr-l -at- lists -dot- techwr-l -dot- com>, Gina Jones <gina -dot- techwriter -at- gmail -dot- com> Date:Wed, 11 Jun 2008 14:12:27 -0400
Gina Jones wondered: <<I need some opinions on my numbering sequence
in a User Guide. My client specifically requested that I embed the
Quick Start into the manual and provide more details. I'm not a fan
of outline numbering in user guides, but must follow their corporate
style guide. Below is this particular numbering sequence.
2.2*** Software Quick Start
2.2.1 Set Up Software Web Appliance
2.2.1.1 A) Configure the Web Appliance
<Step/Action table here>
2.2.1.2 B) Configure the Analyzers
<Step/Action table here> >>
The first thing I'd note is that the first two headings serve little
or no useful purpose, particularly if they are only headings and have
no text between them and the next headings. Why not simplify collapse
the hierarchy as follows:
2.2 Quickstart guide for the [name] software
2.2.1 Configuring the Web Appliance
2.2.2 Confguring the analyzers
And so on. Better still, if you can convince them to bundle the
quickstart guide separately, move that information to the title page,
and the structure then becomes:
Quickstart guide for the [name] software
1. Configuring the Web Appliance
2. Confguring the analyzers
Even if the client requires outline numbering, it should be possible
to convince them to let section headings exist without numbers, as I
proposed in my second example.
----------------------------------------------------
-- 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-