I believe that Jeff was probably referring to the blog post located here.

Brandon

While I have not looked at the documentation in the marketplace, I think that would be additional third party documentation.

I used to print copies of the documentation that is found on the downloads page and it has become well read and always on my desk, however it's value has declined as DotNetNuke has evolved at a fast rate and now many sections are more confusing as it is out of sync with current versions.

From time to time a few project leads will make the effort to blog about recent changes, and for me that is normally enough to review and test to get upto speed, however this is also rare.

A case in point is the latest NewsFeeds module (4.0.0) which behaves quite differently from previous versions, it made it's way into the core release of DNN and without some documentation regarding these changes, it had to be removed from our clients upgrades because it had undesirable results.

I think the original documentation was excellent, however to achieve the same quality of documentation on a regular basis would be quite a task, I would settle for just a desent blog about the changes until the documentation catches up.

When a new version of modules are released the first place I go to is the projects pages, however many times there is no real information regarding feature changes except for perhaps some bullet points.

Over recent months I have noticed a change from the core team and the organisation, I can't quite put my finger on it, but certainly getting information from core members appears diifficult, I recall when Joe Brinkman announced that 4.9.0 R1 was released to people who have access to RC's that I posted two messages asking how to get it or what qualifies a person to join the group, sadly he just chose to ignore my posts. With the lack of good information it makes it difficult to respond to clients and users of DotNetNuke in a timely manner and as a result it can devalue the project. We walk with caution with DotNetNuke since it bagan to saparate the community into various groups based on their ability to contibute financially to gain access to timely information. In some cases this has made us look at alternative solutions rather than exclusively putting DotNetNuke forward.

I don't believe it's the core doing this, I think it's a product of Lorraine's, probably the extension to DNN For Dummies.  And from the work she's done, it's worth the money.  Better than any of the DNN books out there as a general manual.

But the point is still well-taken, this is a user manaul, not program documentation.  And the core team does not do documentation well.  Barely at all.  Same goe for most of the modules.  In fact, 90% of the third party modules I've picked up have extremely poor or outdated documentation.