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.
RE: Single Sourcing: Building Modular Documentation by Kurt Ament
Subject:RE: Single Sourcing: Building Modular Documentation by Kurt Ament From:Sean Brierley <seanb_us -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 22 Sep 2003 10:09:40 -0700 (PDT)
Is your modular stuff really modular? Do you begin at
the beginning of an XML file at the top and finish at
the bottom? Do you write your discrete chunks in a
particular order or do you create a list, toss it into
a hat, mix it up, and write about your topic in the
order the you pull the chunks out?
Getting a bunch of unrelated topics and making them
relate in a printed document is, IMHO, more time
consuming and more difficult that building
random-access and non-linear navigation into content
that was written from start to finish in a linear
fashion.
That is, I think poo-pooing content because it is
"linear" shows a clear misunderstanding of how content
creation and content use can be separated.
Is that what you were looking for?
Cheers,
Sean
--- "Downing, David" <DavidDowning -at- Users -dot- com> wrote:
>
> Now, I've done linear to modular more or less by
> guess and by golly, and THAT doesn't seem to pose
> anywhere near as much of a problem as trying to turn
> modular help text into a manual.
>
> -----Original Message-----
> From: France Baril
>
> When I got to my new job, all documentation was
> linear. I am reorganizing it in modules with the
> intent to go XML (with DITA) and then single-source.
> I'm more than half way through..book?
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.