Applications Documentation Question

[judbasiner at gmail.com]

I am working on a project that requires me to write white paper-ish
documentation on extremely dynamic applications. So dynamic that the
developers will move them from one server to another during the
day/week/month/etc. The developers created a wiki to assist their team as
well as other departments at the company. That is fine for real-time
documentation updates, but what can I do to document these applications for
the "official" company documentation?

We have SharePoint, but there are a number of people who are unable to
access it. My manager is very unlikely to consider any expensive platforms
and I  do not have the time to update the PDF's I have written and will
write every time the development team decides to move an application.
Besides, being the first tech writer at the company, I have tons of other
stuff than needs doing.

I am at wits end on this. I am not a big fan of the wiki idea being
"official" documentation. While I have not voiced my opinion very loudly
yet, I really think there needs to be something more stable than the wiki
idea for documenting these applications the next time the auditors come
through--and they will!

Any ideas?

-- Kelly
"Don't forget that no matter how many "No's" you
hear, it only takes one "Yes" to make your career."
-Mike Straka-