I agree - it's one of the items intended for the wiki (once it goes live), to ensure we can update content quickly when necessary.

Stephen,

for a time we experimented with the dotnetnuke wiki, but it's still a little "young" and misses features such as delegated authentication, rollbacks, transclusion, discussion etc. I experimented with a few .net wiki's and like the look of screwturn (http://www.screwturn.eu/Wiki.ashx) . At the minute the proposal is to either write an authentication provider (so that you can use your existing dotnetnuke account to add content), or else we'll port our user list to active directory - i'll probably take this on as I've been a longtime proponent of wiki's for both core and community contributed documentation.

This is part of a larger effort around documentation where we'll be creating a documents library/msdn type documentation , as well as working on updating the dnn api documentation. Whilst the plans aren't secret by any means, the scope, resources and timelines aren't in place yet, so we've not been talking about them much (though this was discussed at both openforce conferences) - i'm sure once plans firm up there will be blog posts detailing this.

Cathal

Steve, I can't put any firm timeline on it, as i've other core duties such as security that take precedence, but I'm hoping to do it during Q1 next year.

Cathal