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.
Suggestions welcome for this brief online help sample
Subject:Suggestions welcome for this brief online help sample From:Karen <ekarenski-techwrl -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 3 Nov 2005 09:25:46 -0800 (PST)
Please forgive the widget example; however, I'm
working on help screens for unreleased software.
To add a widget
1. Click Define A New Widget.
2. Type the new widget name in the text box.
3. Click Enter.
4. A Color dialog box opens.
5. Click the color of your choice from the Basic
colors, Custom colors, or the Color matrix.
6. To save a color to the Custom colors, click Add to
Custom Colors.
7. Click OK.
8. The new widget is now displayed in the list box
preceded by the assigned color.
9. By default, the new widget is active.
10. To deactivate the widget, click on the name and
clear the Active check box.
First, the customer does want "Click OK" in there.
(They use non-standard interfaces where there are OK
and DONE buttons.)
Steps 4, 8, and 9 are not procedures that the user has
to perform. Should they be considered steps or
possibly notes?
Steps 6 and 10 are optional. Is this the approach you
would take?
I've been using the Microsoft Manual of Style for
Technical Publications as a guide. Unfortunately, the
section on procedures is very limited. Also, when I
review help screens in different Microsoft programs,
each program is distinctly different (and don't even
use the MSTP standards).
Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here: http://www.webworks.com/techwr-l
Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
