I fully agree with supporting doxy/luadocs code docs. I think this should be a requirement for all future activity.
One option would be to not post any code documentation for the public until all the code has been documented, then post those doxy/luadocs along side the wiki information. Another option would be to post the code docs in chunks as they are completed.
) works very well and has a very similar style for creating the comments in code as doxygen does.
My thoughts were that the new wiki would be used for describing the t-engine internals (map generation, SDL UI, item generation, AI, etc), how to code using the C/Lua interface, how to write modules for ToME using the modified Lua system (I'd love to change that too, btw), how to debug a module, etc. All wiki talking points would be on the forum.
I'd leave the current wiki be. I'd think that locking out users from being able to add to it would not go over well. It's a poor-man's forum, so to speak. Starting fresh has a nice feel to it.