One might also consider that the documentation for PE is so far an intangible item that is only mentioned as a bullet point in marketing material. 

Why assume it will be so much better than what is currently available either for free or for purchase?

My guess is that for $2,000 they could include several published books and the PDF version of the online help and that would easily satisfy the intangible marketing we have heard so far for PE.

It doesn't make sense to jump to conclusions from marketing hype, and even if they put a full time staffer on the documentation why not have that be something you can only get if you pay for it? 

I have no doubt that the community will continue to document with their own wikis, pdfs, blogs, community forums, videos, etc., etc.

Keep in mind that nothing is really free.  We all pay some price to get the things we want.  If we decide to use some of our time searching for an answer using google, or if we decide that a single knowledge base can be the holy grail, then we have still committed some portion of our resources to gaining that knowledge.

Agreed, and it also needs to be a well-thought-out  *structured* wiki so that both core and module versions are catered for.  Sadly, I don't believe that the current dnn wiki module is suitable.

It would be nice if DotNetNuke had a builtin free module which would handle a task like this, but it doesn't. We could all wait around for one to exist, but that doesn't solve the problem today. While we wait for either, a public source code repository of the development trunk of all the projects that encompass DotNetNuke, or a stable wiki-like module, we can start the articles, the initial organization and layout of the support for the community edition in the wiki i've posted. When the "offical" bits are ironed out, I will move the information we have gathered into that system if they want it. If you guys don't like Redmine, find me what you would like to use and I'll install and maintain it.

Personally I think we should let them focus on the core and the professional edtion, and we should pick up the slack on the community edition to free up some precious time of the core team members that have been doing all the heavy lifting. Just because it's not a tab on dotnetnuke.com doesn't mean it can't grow into an excellent support guide.