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.
Martha Silverspring asks:
<silverspring9235 -at- go -dot- com> =====
>So I'm just documenting the configurations and settings that need to be made
to the 3rd party products to make our product run.
>But all the developers and testers (in another state) are complaining that I
haven't documented enough; they want me to document everything that needs to
be installed. >How the heck do you handle this no-win situation?>
I worked on one of those products years ago, you have my sympathies.
What I did was create a section that listed all the 3rd party software and
what needed to be changed from the standard install. I did not document the
installation of the 3rd party software, but assumed the user installed it
I think you're on the right track. You shouldn't be responsible for
documenting 3rd party stuff, only the changes that are required by your
Your web site localized into 32 languages? Maybe not now, but sooner than
you think. Download ForeignExchange's FREE paper, "3 steps to successful
translation management" at http://www.fxtrans.com/3steps.html?tw.
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.