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.
OK I'm getting lost. Peter, to whom is your response directed?
The entire reason behind our move to single source is focussed (is/was/will
continue to be!) on the user, the reader of our documentation. To better
serve them, to provide them with up-to-date information in a variety of
different styles, formats and groupings, and to make sure the information we
provide to them is consistent we need a better way to write information, and
a quicker way to manipulate it into those sets and formats. Single source
fits the needs of our readers, hence my request.
Thanks for the reminders, I've done the research, I am gathering the
requirements, and everything is pointing towards single source as a possible
solution. WITH THAT IN MIND, I need to find out the availability and price
of training the team in this new approach, and be able to provide
justification as to why that training AS PART OF THE SOLUTION is required.
The justification of a single source solution is the bigger part of this,
agreed, but that was not my question.
From: techwr-l-bounces+gordon -dot- mclean=grahamtechnology -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+gordon -dot- mclean=grahamtechnology -dot- com -at- lists -dot- techwr-l -dot- c
om] On Behalf Of Peter Neilson
Sent: 20 June 2007 12:35
Subject: Re: Writing structured content
Single-sourcing through document re-use in its lesser forms used to present
the text of the printed manual's pages as help screens, or perhaps
vice-versa. It was justified as being easier to maintain than constructing a
user-targeted help system.
Allow me to quote myself from yesterday:
"The key is to focus on the user view and not on the technology. ... Any
time that implementation is put ahead of design, or design ahead of
requirements, the wrong minds are in control."
Does single-sourcing help meet the customer's needs? Perhaps it makes
revised documents available faster. Or perhaps it inserts non-sequiturs into
formerly comprehensible text. Perhaps it does both.
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. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-