[techwr-l] FW: Rejected posting to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU

Subject: [techwr-l] FW: Rejected posting to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
From: Dan Roberts <DRoberts -at- isogon -dot- com>
To: "TECHWR-L, a list for all technical communication issues" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 30 Aug 1999 11:06:51 -0400

it's possible, but it's more difficult to do. An app that I doc'ed recently
had several windows that provided multiple categories of information. So
going with the standard Insert/Change/Delete a Widget style approach would
not have helped much. Users were more interested in specific *aspects* of
changing a widget - updating widget status, specifying widget replacements,
adding more knobs to a widget - so I broke down the one big Changing Widget
screen into a number of smaller tasks.

In your case, where the user is bouncing all over menu choices, would it be
possible to provide a high-level *summary* of the task, then use subtasks to
provide the specific actions for a menu choice. For example, consider
changing page number format in Word.

To change a page number, you must:
Open up the header/footers
(subtask describing how to open up header/footers)
Insert your page number
(subtask describing how to insert a standard page #)
Optionally, format your page number style
(subtask describing how to click the Format button and use the db to
change page number style)
Close everything up.


Dan Roberts
droberts -at- isogon -dot- com

> -----Original Message-----
> From: Anthony Markatos [mailto:tonymar -at- HOTMAIL -dot- COM]
> In creating end user documentation for an existing (complex) software
> package, if the software was NOT designed task oriented, can
> the end user
> manual be written in such a fashion?

Sponsored by Weisner Associates Inc., Online Information Services
As a leading service provider to technical writers, we are proud to sponsor
TECHWR-L. Visit us at http://www.weisner.com or mailto:info -at- weisner -dot- com -dot-

Sponsored by ForeignExchange (http://www.fxtrans.com)
Rely on ForeignExchange for responsive and professional
software localization and technical translation services.

You are currently subscribed to techwr-l as: ejray -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-6452R -at- lists -dot- raycomm -dot- com


Previous by Author: Technical Writers or Information Developers?
Next by Author: RE: Bug tracking systems as information repositories
Previous by Thread: [techwr-l] Convert FrameMaker to PageMaker
Next by Thread: [techwr-l] Newsletter Guidance -- Summary (long)

What this post helpful? Share it with friends and colleagues:

Sponsored Ads