Re: content structure/strategy

Subject: Re: content structure/strategy
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 1 Dec 2017 12:26:45 -0800

1. Host the docs on a web server. That way you can manage your docs
even if engineering has given up on managing their releases. After
each release, go through the changed UI and update as necessary.

2. Rewrite everything as task-oriented topics. Then UI changes will
require less revision, plus users will find instructions that relate
to how they use the product rather than how it's designed. Google
task-oriented documentation, there's lots of stuff out there.

3. Find a new job.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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:

Previous by Author: Re: Using Word as an Authoring System
Next by Author: release notes for "new" product and cloud-based products
Previous by Thread: Re: Using Word as an Authoring System
Next by Thread: Re: content structure/strategy


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

Sponsored Ads


Sponsored Ads