I have written about it before (i think) but in a technical job you never can have enough documentation. We take it for granted. In a smaller company you also know everyone who did work, so you just go ask the source of information for help. That is not a good way to do things.
My department has been attempting to write documentation for most day to day issues, and some more routine server / network issues.
The next step is to put that in a database of some kind. Gus likes Wiki’s. Not sure if what we want to do will be perfect for that software or not. There are tons of other forum or idea posting systems that we can use on linux.
For now I am content with just getting everything as a word document and worry about putting a UI on it later. Right now I need content. This process is really two separate ones with the same goal, but different content. What I mean is I am gathering how to’s from the support department at the same time as I am building a FAQ so to speak for the company at large. One will be very technical and for my departments use only. The other will be for everyone’s use and will answer simple questions about where or who to goto for information or how something is done in the company. Both projects are related because it is information gathering. Putting down on paper what has only been in peoples heads for so long.
Documentation is a slow difficult process. Unfortunately most technical documentation is not that good!