most of the initial wiki documentation is adequate. sometimes you need to clarify. if a modder finds a description in the wiki vague or insufficient, they should feel free to fix the description. perhaps it would be a good idea for coders to start putting their names on their features in the wiki in cases where documentation is so poor its useless, so that the feature coder(s) can be contacted and the wiki clarified. i put up basic documentation for all my non-scripting features. the scripting features are somewhat self documenting through scripting.html, though i think we need to come up with some better scripting documentation. scripting.html is good for a function reference but really doesnt do much to explain hooks or hook variables and the like. dont need to document lua, or the built in libraries, as there are plenty of tutorials for that. information about how to put the freespace specific libraries to work is somewhat lacking.
im not really a big fan of tutorials. most of the time its 'look what i can do! heres the code! im not gonna tell you how or why it works!'. tutorials are also too specific to a topic. your better of explaining theory of operation, paradigms and conventions with nice little flowcharts explaining how stuff works. explaining basics like timing, working with files (in the engine's context), talking with missions, operating on built-in (userdata) structures, how to write easy to debug code.
