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.
Substantial dev effort would be a non-starter (isn't it always?), but communication shouldn't be a problem (I'm in the same office and chain of command).
The alternative, obviously, would be a setup like David's or Anne's, but I'm currently relatively unconstrained by existing processes (or, to put it another way, 'I have to produce a doc set from scratch and have it ready last year') so nothing's off the table for consideration, and I can at least /look/ at ideal solutions.
Sarah Blake
Technical Writer
Arieso Ltd
Office +44 (0) 1635 232470 | Fax +44 (0) 1635 232471 |
Email sarah -dot- blake -at- arieso -dot- com | Web www.arieso.com |Â
-----Original Message-----
From: Peter Neilson [mailto:neilson -at- windstream -dot- net]
Sent: 11 January 2013 14:40
To: techwr-l -at- lists -dot- techwr-l -dot- com; Sarah Blake
Subject: Re: Modular products...
Requires substantial consultation with the software engineering staff. If they are not local, or if their management is sufficiently disconnected from your chain of command, it's nearly impossible. If your own management cannot see how to get it through the company hoop-jumping, it's not worth the effort.
On Fri, 11 Jan 2013 09:32:33 -0500, Sarah Blake <sarah -dot- blake -at- arieso -dot- com>
wrote:
>> The key is to make the documentation sufficiently integrated into the
>> software, automatically configuring like any other aspect of the
>> module, such as library or database requirements.
>
> That's what I was thinking, but I don't have the technical background
> to know how difficult it is or what tools lend themselves to this kind
> of dev/product integration. Obviously I can learn the skills
> necessary, I just need a starter for ten :)
>
> Anne: is this the sort of thing you achieved with your FrameMaker books?
>
> Sarah
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Writer Tip: Create 10 different outputs with Doc-To-Help -- including Mobile and EPUB.
