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.
Re: Numbered versus unnumbered heads in very technical reference guides
Subject:Re: Numbered versus unnumbered heads in very technical reference guides From:Julie Stickler <jstickler -at- gmail -dot- com> To:tech2wr-l <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 18 Jun 2013 16:33:19 -0400
>From what I've been told, numbered headings are a legacy from the days when
documentation lived in three ring binders. And when a documentation
updated happened, it was "replace section 5.1.3 with this new section
5.1.3." Which seems to me to be the only benefit of numbered headings.
Leonard asked a good question. How would the numbers help the user? In my
case, they don't.
My personal preference is NOT to number headings. But that may be in part
because I have a touch of dyslexia when it comes to holding a random string
of numbers in my head. It doesn't matter if you're writing print(able)
documentation or online Help, I find that having numbers in the headings
can hinder navigation as much as it helps. If I'm looking for topic
"22.214.171.124 Configuration Settings", my eyes will be scanning for
"Configuration Settings" not the string of numbers. And since the TOC pane
in a PDF or Help is often narrow, if the first several characters of a
heading are numbers, it makes it harder for me to navigate the TOC, because
I'm looking for the words, not the numbers. If the TOC pane doesn't
resize, you've made the navigation almost impossible for me because I'm
trying to navigate a sea of similar numbers.
When I'm writing print docs, I try to avoid headings that wrap in my TOC.
Again, if the first several characters of my heading are a string of
numbers, that makes it a challenge to keep my headings to a single line.
YMMV, I know there are probably industries that still require numbers in
headings. I don't happen to work in one.
On Tue, Jun 18, 2013 at 8:14 AM, Erika Yanovich <ERIKA_y -at- rad -dot- com> wrote:
> With some already good answers being given, reference material is usually
> arranged alphabetically or by meaningful categories and alphabetically
> inside categories. The only value numbers have is if they appear in the
> system, for example error message number.
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
> Learn more: http://bit.ly/ZeOZeQ
> You are currently subscribed to TECHWR-L as jstickler -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Julie Stickler http://heratech.wordpress.com/
Blogging about Agile and technical writing
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.