Re: Resources for learning Structured Writing?

Subject: Re: Resources for learning Structured Writing?
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: "Janoff, Steven" <Steven -dot- Janoff -at- hologic -dot- com>, Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 27 Oct 2014 12:28:10 -0700

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
>
> -----Original Message-----
> From: robert -dot- lauriston -at- gmail -dot- com [mailto:robert -dot- lauriston -at- gmail -dot- com] On Behalf Of Robert Lauriston
> Sent: Monday, October 27, 2014 9:43 AM
> To: Janoff, Steven
> Cc: Techwr-l
> Subject: Re: Resources for learning Structured Writing?
>
> On Mon, Oct 27, 2014 at 9:23 AM, Janoff, Steven <Steven -dot- Janoff -at- hologic -dot- com> wrote:
>> Couple of questions, if you don't mind.
>>
>> What made you decide the migration would not be cost-effective?
>
> We couldn't identify any benefits. The docs were distributed only in English and there was very little need / opportunity for topic reuse.
>
>> How many such investigations have you been involved in?
>
> I've considered it at two other companies but the situations were similar.
>
> I love the idea of using standard source that's compatible with multiple off-the-shelf tools but the reality seems to be more like you're committing to an open-ended custom software development project.
>

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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:

References:
Re: Resources for learning Structured Writing?: From: Stuart Burnfield
Re: Resources for learning Structured Writing?: From: Stuart Burnfield
RE: Resources for learning Structured Writing?: From: Janoff, Steven
Re: Resources for learning Structured Writing?: From: Robert Lauriston
RE: Resources for learning Structured Writing?: From: Janoff, Steven
Re: Resources for learning Structured Writing?: From: Robert Lauriston
RE: Resources for learning Structured Writing?: From: Janoff, Steven

Previous by Author: Re: Resources for learning Structured Writing?
Next by Author: Re: Is this the future of technical writing?
Previous by Thread: RE: Resources for learning Structured Writing?
Next by Thread: RE: Resources for learning Structured Writing?


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

Sponsored Ads


Sponsored Ads