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.
>
>Alternatively, you could do diffs to compare the previous vs. the
>current versions (Your management DOES save old versions, right?)
>
>
That brings up an interesting issue. Our site content consists mostly of text stored in a database. When we overwrite the content of a database cell, poof! The old content is gone. (If it were our database server, presumably we could journal any changes; but our database sits on a massive server with hundreds of other sites, and we do not have administrative privileges.)
Nobody has asked me to document changes, so my interest in this question is strictly hypothetical.
But the question remains, what is the best way to document changes in this situation. One thing that has occurred to me is to capture the site as a PDF from time to time. But doing that every time there is a change on the site would be burdensome. Even doing it once a day seems like extreme overkill.
There is the Wayback Machine, but that misses a lot, too, especially if you've got a robots.txt file on your site.
---
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.
