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: Automating docs compilation in the software build process
Subject:Re: Automating docs compilation in the software build process From:"Richard G. Combs" <richard -dot- combs -at- voyanttech -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 16 May 2003 12:54:38 -0600
David Handy wrote:
> My developer colleagues are keen to incorporate the docs source files into
> the Build Process -- y'know, the process whereby the development files are
> assembled into installable software. Currently I provide all docs in a
> finished state, i.e. I compile the master help file from several HTML Help
> projects, build the PDFs from Framemaker, apply relevant security
settings,
> and check the lot into VSS for inclusion in the build. The developers
> dislike this because the whole shooting match takes me a half-hour,
whereas
> with automated scripts it could be done in moments -- they contend -- on
our
> Build machine.
They want to produce your deliverables, e.g. PDFs and Help, from your Frame
files as part of the build process (when they create the shippable CDs)?
Without a human checking the output (PDFs and Help)? Well, with the right
tools, you could automate/script those processes, but I think it's a bad
idea.
You say that it takes you half an hour to do this manually (which implies
that you're not doing much output checking, such as link testing, yourself)
and that the developers dislike this. It sounds like you don't produce the
deliverables until someone calls you and says "We're ready to build now.
Where are the docs?" Why not? Maybe some simple workflow adjustments would
satisfy the critics.
Surely, releases aren't built with no warning on the spur of the moment.
Unless you're changing the docs up until the last possible second, it should
be possible to have the deliverables complete and checked in well before the
scheduled build. Of course, once in a while, you do have those last-minute
emergency changes to make, but that should be the exception, not SOP. :-}
My 0.02
Richard
------
Richard G. Combs
Senior Technical Writer
Voyant Technologies, Inc.
richardDOTcombs AT voyanttechDOTcom
303-223-5111
------
rgcombs AT freeDASHmarketDOTnet
303-777-0436
------
---
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.