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: website tech pubs, etc. From:Fox Cole <foxcole -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 22 Jan 2010 14:20:42 -0600
. . . In addition to a PDF that gives the entire manual, you might also set
> up separate PDFs for each chapter. . . . It would be a blessing to the user
> to be able to download only the one part he really needs instead of the
> whole thing. I know that would complicate document management, so I don't
> know if you could get away with it.
On a bit of a tangent, could you explain a little more about how it might
complicate document management? I know I must be overlooking quite a number
I've used the separate-chapter approach for quite a while as a solo tech
writer, using OpenOffice to create chapter documents to be pulled together
by a master document. This way I could easily (and inexpensively) create a
different look for the individual chapters versus the whole book, as needed,
and print each chapter to PDF format.. nothing more to it than that.
Version numbers in the page style header meant each chapter could have its
own version level that wouldn't appear in the complete book, and the change
log for each chapter became part of the change log for the whole.
But that's just in my own little microcosm... what more would chapter
document management involve?
If the world were a logical place, men would ride sidesaddle. -- Rita Mae
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/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-