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:What shall I do when faced with this situation From:Simon <wingman1985 -at- yahoo -dot- com -dot- cn> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 8 Jul 2013 12:48:33 +0800 (CST)
I have been asked to attend developers meeting(non-software industry) and to help with their documentation effort(They are also responsible for producing manual which is much of an annoyance to them). I collect as much information as I can(their meeting memo and everything I can get such as drawings and so on) .
For those who work in the manufacturing side of technical doc world, can you offer some advice on how I can collect necessary input and "help" (verbatim from the engineering director)with the doc.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.