I know I'm fanning the flames but I tend to agree with Tim here. There has never been any type of comprehensive documentation for DNN. Sure we've made a ton of progress here in the past few years in regards to updating documenation but most of it is seriously outdated. Slapping a new date and revision on the documentation with new DNN releases just doesn't cut it. As a matter of fact, I find several items in the documentation for DNN5 that never have applied to version 5.
Now I've been using DotNetNuke for close to five years now hosting client's websites. I'm not a developer, nor designer but have made a pretty good living at converting static HTML or proprietary websites to DNN so that the client's themselves can update the content (the whole purpose of a CMS). I've chosen to use DNN simply because: 1) I am a very small business and cannot afford any commercial CMS, 2) I am most comfortable with Windows and IIS. Having said that I seriously believe that DNN is behind the curve, compared to other open source CMS systems. We need better
I understand that the developers and designers are volunteering their time, and certainly appreciate everything they've done here, but good documenation, training, and end-user support is the foundation for any succesful software project. We simply need better documentation.
As far as the website being down yesterday; yes I know DotNetNuke easts their own dogfood, but I was attempting to show a client the Guided Tour yesterday. Needless to say, they weren't impressed.