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.
You know, the more I dig into this stuff, the more I have to agree with you.
This is a complicated pathway. It will be interesting to see where it all goes.
Thanks for the info.
Steve
On Monday, October 27, 2014 12:28 PM, Robert Lauriston wrote:
Everybody I've talked with that's using DITA in the kind of environments where it really pays off (multiple products with overlapping features, docs translated into multiple languages) did a significant amount of custom development. Often they have developers on the docs team who do nothing else.
Oxygen XML works like a HAT, but as soon as you dig into the inner workings to customize things much of what's there is straight open-source code. Tweaking output means editing code, not just fiddling with settings in a GUI the way you can in Flare, WebWorks, et al.
On Mon, Oct 27, 2014 at 11:54 AM, Janoff, Steven <Steven -dot- Janoff -at- hologic -dot- com> wrote:
> "...but the reality seems to be more like you're committing to an open-ended custom software development project."
>
> Could you elaborate on that last part a little bit? I'm not sure I understand.
>
> Thanks,
>
> Steve
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
