Re: content structure/strategy
Try to focus on the purpose of the software, and the need for a workflow and how it will be used.
Then refocus the documentation on tasks.
Dem guten Herr sei Dank! Someone who has actual advice, not just cynicism.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
Follow-Ups:
- Re: content structure/strategy, sharipunyon
References:
content structure/strategy: From: jopakent
Re: content structure/strategy: From: sharipunyon
Previous by Author:
Re: content structure/strategy
Next by Author:
Re: Using "Fences" as File Management Tool?
Previous by Thread:
Re: content structure/strategy
Next by Thread:
Re: content structure/strategy
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads