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.
Subject:Re: Structuring a project From:Robert Lauriston <robert -at- lauriston -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 17 Dec 2009 10:16:34 -0800
Do you have a contractual obligation to provide the source to any of
your clients?
On Wed, Dec 16, 2009 at 11:49 PM, Claudine Chausson
<claudine -dot- chausson -at- jwaretechnologies -dot- com> wrote:
> Hi everyone
>
> I have an issue with the structure of my project. I use DITA, Oxygen to edit
> it, and ClearCase for version control. I output to pdf.
>
> I’m writing the same manual for 2 different clients. Many topics are common,
> some are specific and some are of a mixed type. I could use metadata to tag
> the information and then use DITAVAL to include or exclude topics; it works
> well. But how can I do if I need to create a manual for a new client and
> then another new one, and so on?
> I figured I could use different folders and follow a structure similar to
> this:
>
> ManualName
> Client1
> Client1 Images
> (list of files specific to Client1 + Client1 project + Client1
> ditamap)
> Client2
> Client2 Images
> (list of files specific to Client2 + Client2 project + Client2
> ditamap)
> Images
> (list of common files)
>
> Is it feasible (and viable) to work like this? What about mixed type topics?
> How can I manage those? With DITAVAL?
>
> Any insight will be appreciated.
>
>
> Claudine CHAUSSON
> Technical writer
> JWARE Technologies
>
> Mail/to: claudine -dot- chausson -at- jwaretechnologies -dot- com
> http://: www.jwaretechnologies.com
>
> Please consider the environment before printing this email.
>
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Are you looking for one documentation tool that does it all? Author,
> build, test, and publish your Help files with just one easy-to-use tool.
> Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at:
>http://www.doctohelp.com/
>
> Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
> generate 8 different formats and as many different versions as you need
> from just one project. Fast and intuitive. http://www.helpandmanual.com/
>
> ---
> You are currently subscribed to TECHWR-L as robert -at- lauriston -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/robert%40lauriston.com
>
>
> 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
>http://www.techwr-l.com/ for more resources and info.
>
> Please move off-topic discussions to the Chat list, at:
>http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
generate 8 different formats and as many different versions as you need
from just one project. Fast and intuitive. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-