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.
I am running into a challenge with our documentation concerning archiving or
single-sourcing. Indeed, are these two processes even synonymous?
Up until recently, our documentation was archived/single-sourced in MS Word.
From this, we were able to create two outputs, WinHelp and printed
documentation, with minimal fuss. We have now added another output to the
mix - HTML/web-based documents that incorporate Javascript and CSSs.
Is anyone else putting a process into place that allows authoring and
maintaining HTML documentation and that also permits conversion to a
printable medium for publishing as a manual?
What archive/single-source processes are others using?
Looking forward to your thoughts and ideas....
Diane
Diane Burke
DataMerchant Publications
Cognos Inc. (613) 738-1338, ext. 3531
E-mail: diane -dot- burke -at- cognos -dot- com
