Although the manual does cover some of the basics, there is a lot left to be desired for best practices for both small and large deployments.

It would be nice to see some of the configurations suggestions that people have for small (2 servers), medium (3-10 servers) and large (11+ servers). This will benefit all of us and also the satisfaction level for the product. I am very happy with it, but I have not used a control panel before in the 6 years of hosting and ISP services that I have been doing and any suggestions for myself and other newbies to a CP would be very helpful.

In particular, settings at Server, Virtual Server, Global, etc.. Any other parameters to make life easier with any changes in the future, etc.. This may be very general, but might be a good start..

It would be better start over now, than to find out a year down the road that I screwed myself.

Thanks 

I agree, because although one might be experienced in managing web services, it doesn't mean that one can easily understand how DNP configures/manages these services.

It seems to me that the open nature of the DotNetPanel product i.e. source code, rapid development, open-source applications installations, active user community - points to a doumentation project that works along these lines.

If I really thought about, I might be able to think of others, but the most obvious suggestion is a

WIKI

FlexWiki is a good candidate. It's another Microsoft open-source web application and an comes as an installation package in DNP. 

There is so much good information being worked out in these forums - and is coming from all sorts of sources, not just the DNP team - that a Wiki would grow rapidly, would be structured and really very useful. 

Whitepapers and documents are a start, but a WIKI is alive and is more structured than the Q&A threads of this forum.

IMHO

http://flexwiki.com/

Yes, it is a good idea to install Wiki.

However, when using Forums all that you need to know for creating some content is where "Write New Post" and "Reply" buttons, but using Wiki requires some preparation (how to create a topic, how to do references, hot to format content). So, I'm just wondering if it would be convenient for the most of customers.

Btw, seems FlexWiki has poor customization abilities. I've found PHP-based MediaWiki (http://www.mediawiki.org/wiki/MediaWiki). It looks really promising.

Does anybody know other good Wiki implementations?

I was recently looking around for a good .net wiki implementation and did not find one that met my needs. I am currently using MediaWiki for a couple of my customers it has worked out very well so far.  I have not done much customization of it yet but it seems very flexible.

I actually suggested a while back that FlexWiki become a DNN module... I havent had any time to do anything with that. Someone did contact me and start, but I imagine soon discovered that - yes - it is not flexible.. so much for Flex Wiki

Media Wiki runs the Wikipedia and one would suppose that wiki is the most powerful of the Wiki's
http://en.wikipedia.org/wiki/List_of_wiki_software

there is a Community Server module for Wikipedia which perhaps could be modified for a DotNetPanel MediaWiki... come-on guys, DotNetPanel is going to be huge, think big!!! Maybe this CS module could link the DNP Forums to the DNP wiki ?? dunno.. a project like that would get interest from the CS and the Wikipedia elite. Good PR for DNP?

In terns of Wiki's that are easy-to-use and ASP.NET friendly, there is a DNN module called WWWiki. I've used in my sites, and am building my own documentation for customers in it. WWWiki uses the HTML editor of DNN and  the simple [[WikiWord]] syntax, simple versioning, page comments and rankings, search, automatic indexing, insert images...doesnt have much other functionality but it works. You can buy the source

http://en.wikipedia.org/wiki/WWWiki