RE: Using a Wiki for RPG documentation

I would look to automate the wiki-build process by having a program that
"reads" the rpg source, and maybe defining some standard comments that
need to be in the source, eg. javadoc.

However, I also have a concern about what you're doing in general,
unless you have really strong management support for maintaining the
documentation it's going to go out of sync w/the real application, and
wrong-documentation is much more dangerous than no documentation at all.
I actually do like documentation, but it should be driven from
comments/code in the actual source members, not maintained separately.
I've seen it too many times where a program change is made because the
documentation says the program works "this way" but the docs are out of
date and the change breaks all sorts of stuff because the program really
works "that way". :)

-Walden