We have an internal wiki here as well that people can and do make some documentation. Then we have a tool that makes documentation and puts it on the wiki. The generated documentation formatting is basic to make it fast to make. Alot of time is spent on formatting documentation. Our tool takes care of all of that its not fancy but it is better than nothing.
All of our tools are in a second menu bar in Maya. Our documentation tool goes through all of the menus and makes a documentation page that I later upload. With out the tech artist doing anything the tool uses the annotation and the command for the documentation. A first pass that starts on the road to documentation. In addition to we set up a folder structure in our source with extra documentation (How to’s, What for’s, This tool is going to…, pictures, and links). That structure is a folder for each tool and each folder contains txt’s and jpeg’s. The tool will see this extra info and generate it into the wiki along with the basic info.
The basic idea is I may not have time to make detailed documentation, but I can tell you what it is and give some pictures of what its all about. I have to for the email I send out to the team any way so with this I just save it on our source.
This is our first pass so there are issues. The option-menu box makes it accessible, but gives double-meaning to the icon. So we are working on getting a small question mark. The documentation lives on our internal-wiki and the tool that loads it up to the wiki is a bit slow and is only one-way. So there are flaws, but having even limited easily accessible documentation is really nice. I find myself using it to look up tools I’ve written a long time ago.