I agree with everything you said. I would like to add…

Where I see DotNetNuke fitting in (my own personal opinion, not the official opinion). Currently websites do these basic things:

• Show you stuff
• Allow you to do stuff
• Keep track of you so they can be better at showing you stuff

I think this covers every website from Amazon, to YouTube, to MySpace, To Google. In all these cases you can jump start your development by using DotNetNuke. Even if all you wanted to do was have a site that returned search results like Google, You would be better served by building it on top of DotNetNuke because then you could:

• Run multiple versions as separate portals
• Have an admin section with security levels for your advertisers
• Expand it using modules
• Easily Skin it
• Leverage existing modules to save coding

“Leverage existing modules to save coding” is the big one. Microsoft would like Web Parts to provide this functionality but nothing integrates as well as a DotNetNuke module that conforms to the DotNetNuke API. A proper DotNetNuke module is easily altered to easily work with everything else you have already going on in your portal.

DotNetNuke is really just starting to catch on as it matures, however I predict that in a few years it will be something that vast numbers of .Net developers will automatically use for the majority of their projects.