|
We use a wiki for internal documentation, test procedures, etc. I wasn't crazy about it at first but I have to admit it's kind of nice because anyone can add to it (this can also be a negative) and because it only needs a browser (no client software needed). I also like the fact that simple formatting is very easy to do with the markup language (some of them have a WYSIWYG editor). On the other hand, you can't always make things look exactly the way you want, like perhaps you could with a more cumbersome system. But if content is more important than style, a wiki might do just fine. Ours only has a simple text search, which is adequate for what we need it for. Like everything else, though, keeping info up to date can be a problem. People are all enthusiastic when they are adding their data for the first time, but keeping it updated is not nearly as much fun, people quit, get transferred, etc, etc, etc. -Marty
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.