RE: Writing structured content [recap]

Subject: RE: Writing structured content [recap]
From: "Gordon McLean" <Gordon -dot- McLean -at- GrahamTechnology -dot- com>
To: "'Troy Klukewich'" <tklukewich -at- sbcglobal -dot- net>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 22 Jun 2007 08:28:45 +0100

Thanks to everyone who has chosen to respond to my question.

The information mapping topics, whilst interesting, aren't really answering
my question. I asked, specifically, about "structured writing" or "writing
for single source", I also mentioned that I'm more interested in how best to
shift a docs team from writing chapters, to writing distinct chunks of
information. Hence why I titled my email "Writing structured content" not
"What is structured writing"... Too subtle, right?

The planning of those chunks is a separate exercise, with which I am already
au fait; I've read Hackos, Ament, Glushko and McGrath, and listened to
various speakers at X-Pubs a few weeks back, I've also implemented an
AuthorIT based single source system in the past. Of course, I should've
stated all that upfront but I thought my question was distinct enough.
Apparently not.

So, as part of a move to single source, as well as deciding which method to
use, auditing the content, planning the breakdown of said content into
reusable chunks, deciding on tools, CMS (maybe) and so on... There is part
of that project which requires:

A. the rewriting of existing content
B. a distinct method of writing content in the future, which allows for
maximum re-use.

A couple of replies offlist suggested CherryLeaf and Mekon, both of which I
know and will be contacting soon.

I'll let the InfoMap crowd continue their spat but I'm dropping out. Thanks
to everyone who responded.


This email (and any attachments) is private and confidential, and is intended solely for the
addressee. If you have received this communication in error please remove it and inform us via
telephone or email. Although we take all possible steps to ensure mail and attachments
are free from malicious content, malware and viruses, we cannot accept any responsibility
whatsoever for any changes to content outwith our administrative bounds. The views represented
within this mail are solely the view of the author and do not reflect the views of the organisation
as a whole.
Graham Technology plc
Registered in Scotland company no. SC143434
Registered Office India of Inchinnan, Renfrewshire, Scotland PA4 9LH


Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

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-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.


Re: Writing structured content: From: Troy Klukewich

Previous by Author: RE: Writing structured content
Next by Author: RE: Tips for Second Interview
Previous by Thread: Re: Writing structured content
Next by Thread: RE: Writing structured content [recap]

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

Sponsored Ads