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.
IMHO, "nested" sounds like indented, and I rarely write a long document
without using them. Also, some industries (notably aerospace) dictate that
this method be used. When I use them, I also indent the body texts (e.g.,
body 1:hdr1, body 2:hdr2) to accent the heading change. If there are many
levels, you may want to decrease your indent to .3" per heading level.
The lighter color is fluff and adds no value (IMNSHO). If a user prints a
manual page (e-docs), they may not be able to differentiate between the
header types. In some cases, the lighter colored text could become
transparent.
I use progressively smaller font sizes for lower levels (if the docs call
for it), but never going smaller than the actual body text.
Irene Wong stated that we needed to beware of inadvertantly creating
documentation that is unusable, by having the headers blend in to the text.
By moving the text over with the header, I think the chance is reduced.
Additionally, keywords or concepts are normally in your index.
And finally, I like them. It aids me in visualizing how I've organized the
writing and allows me to move information more quickly. It can give a
document a "tree" look to it, similar to a PDF bookmark hierarchy.
Just my thoughts,
Steve McDermott
Sr. Technical Writer
Business Strategy and Product Design Group
Premera Blue Cross
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at http://www.ehelp.com/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.