RE: Marcom as TechCom

["Anita Legsdin" <anita -dot- legsdin -at- watchmark -dot- com>]

Isn't this what's commonly referred to as "task-oriented documentation"?
We receive requirements documents from our customers, and that's what I
use as a foundation for our user documentation. The user guide does not
consist of a list of windows and explanations of fields, it consists of
process maps and procedures that tell how they can implement FeatureA or
FeatureB, to accomplish task1 and task2 of their daily job. Context
help, of course, is screen-oriented, and cross-references topics in the
other user guides. Even in screen-oriented context help, you can provide
an "Example" paragraph that provides a glimpse of nifty ways you can use
the tool/window/feature. 

I can see how this would be totally different were I writing a Fortran
or C# manual. But even in those cases, sample programs can provide the
"why should I care" portion. 

> -----Original Message-----
> 
> >Tell me why I'd want to use it
> 
> We used to refer to this (internally) as the "Why
> should I care" section of our Feature Notes.  
> 
> 

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 and receive a $100 mail-in rebate, plus FREE
RoboScreenCapture, WebHelp Merge Module and iMarkupSoftware, for a total
giveaway value of $473! Order here: http://www.ehelp.com/techwr-l

   Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....

---
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.