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.
Subject:RE: Using "tip" and "note" in procedure writing? From:"Walters, Christian (CCI-Atlanta)" <Christian -dot- Walters -at- cox -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 1 May 2001 13:52:58 -0400
Geoff Hart sez: <<I would note <g> that you do have to preserve a clear
distinction between warnings and the other types of information; if warnings
share the same look or feel as the notes, you risk having users ignore them
amidst all the other clutter.>>
I agree there. In fact, that's another issue we're working with -- making
the Warnings stand out a little more. We're experimenting to find a format
that sets it apart but doesn't make the page ugly or hard to read.
<<At the risk of sounding repetitive, I'd suggest the most useful study you
could possibly find would be one that involves your audience--even at the
risk of disproving your own hypotheses about what works. Ask them! Although
you can generally discern important overall principles from published
studies, you have to be very careful to ensure that those studies are
applicable to your specific audience; the devil's always in the details.>>
Certainly good advice. Fortunately, all our documentation is internal, so
getting access to our users is fairly easy. Unfortunately, my experience
with asking them about things like this tells me that they simply don't read
the manuals enough to really have an opinion. The general non-usability of
our documentation is part of what precipitated a rewrite of our styles :)
Once we get our styles down, our next step is to reorganize our manuals away
from these 900-page compendiums, and towards smaller, more targeted books.
(We've been shifting to XML-based single-sourcing over the last few months,
with an eye towards ultimately having customized documentation. I can't
wait.)
Thanks for all the help and suggestions, folks. You guys are the coolest :)
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Information Mapping, Inc., a professional services firm
specializing in Knowledge Management and e-content solutions. See http://www.infomap.com or 800-463-6627 for more about our solutions.
---
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.