It seems like the DotNetNuke Wiki would be sufficient to start creating a usefull and up-to-date documentation set. I started using it to make a documentation mock-up for a couple of projects at my work and it is very usefull. It may become the defacto documentation.

Is the existing Wiki even working?

I am currently looking for info on validation and all I can find is the outdated and omitient ListX documentation. I have cut and paste the code from the ListX documentation and it is not working. The javascript call syntax is not documented in the documentation so I am reluctant to edit it.

A wiki would allow users who are concerned with a certain functional area could comment and submit edit proposals which could be viewed and approved online.

I have found one thread in the forums regarding validation. That seems to be to be insufficient.

Are forums really the best place to document software? Thread titles are often nearly meaningless, such as "Possible Bug?" or "It's not working. Please HEEELPPP!" These may or may not be the best way to get help, but it is massively inefficient for documentation. The question and the code to solve it is often sprinkled between the first and thirtieth post in the thread. In a wiki the pertainant info can be cherry-picked out of the thread and edited into the article body.

I would very happily contribute to a wiki by trying to update whatever I may find out about validation and several other under-clarified subjects.

I love OWS and intend to keep using it and look forward to the day when I am productive in it. But the first part of the learning curve is mottled with speed-bumps. All forms of documentation are scattered and unnecissarily opaque.

Yet I don't want to create more work for people. A documentation wiki would hopefully reduce work. One place to update documentation. One thread for each topic. An additional place to look for specific answers.

Doesn't that seem like a worthy persuit?