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.
Randall Larson-Maynard asked about how to handle change pages.
Dan Brinegar <vr2link -at- VR2LINK -dot- COM> writes:
> "Nobody *ever* posts change-pages."
(and provides some good reasons for his circumstances, which may be common)
Well, there are at least a few of us who post change pages, but
you really need a good mechanism to disseminate changes, and a
well-thought out page numbering scheme to counter some of the
problems Dan mentions.
The software I document includes a method for customers (who
have purchased support) to download (in a fairly automatic manner)
program changes and documentation changes. As we provide
many program enhancements on a given release, it is critical to
keep up-to-date on documentation. At the very least, downloading
the documentation updates keeps on-line documentation current.
In terms of extra pages messing up chapters, we number pages in
the format chapter number - page number (e.g., 3 - 1), so a
complete chapter might need to be reprinted, but the next chapter
is unaffected.
