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: Documents I'd like to see... From:Maggie Secara <MSecara -at- NILS -dot- COM> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 17 Jul 2001 13:15:14 -0700
I agree. I'd like to know what this puppy can do, not just how to do
something I've thought of and can't figure out. What is it FOR? When would
I use this feature? I used to learn a lot about Word, for example, just by
picking up the manual and paging through that. Back when there *was* a
manual. Now that everything is reduced to generalized on-line help, if you
don't already know, it's hard to find out.
Maggie Secara
NILS Publishing Company
(818) 734-3570
-----Original Message-----
From: R. Johnson [mailto:rjayz -at- yahoo -dot- com]
Sent: Tuesday, July 17, 2001 1:00 PM
To: TECHWR-L
Subject: Documents I'd like to see...
I'd like to see more documentation that illustrates
potential real-world solutions based on the functionality
of particular software applications. For example, I'd be
interested in seeing how others have used mail merge in
ways other than creating form letters; or how to create a
knowledge base that enables you to maintain, update or
generate an entire policy and procedures manual at the
click of a button; or how (and why) to create an animated
movie using layers in PhotoShop; or creating CBTs in Power
Point.
Why is there such a dearth of "solution" based
documentation? Everything seems to be "process-oriented"
rather than "results-oriented." Reference manuals and user
guides are fine, but sometimes I'd like to see an example
of the functionality in actual use, rather than
"Select-File-Click-OK." Am I alone in this or do others
feel this way too?
*** 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
TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com
---
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.
