Re: Task-based versus UI-based documentation
But you don't always have the opportunity to handle the hardware. I've never actually -flown- either the C-5 or the F-117 aircraft (no matter how much I begged and pleaded). (If I had, you know I'd have bored you with the stories long ago.)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
References:
Task-based versus UI-based documentation: From: Cardimon, Craig
Re: Task-based versus UI-based documentation: From: Julie Stickler
RE: Task-based versus UI-based documentation: From: Lippincott, Richard
Re: Task-based versus UI-based documentation: From: John G
RE: Task-based versus UI-based documentation: From: Lippincott, Richard
Previous by Author:
Re: Task-based versus UI-based documentation
Next by Author:
Re: Task-based versus UI-based documentation
Previous by Thread:
RE: Task-based versus UI-based documentation
Next by Thread:
RE: Task-based versus UI-based documentation
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads