I agree with a lot of what Jay is saying. In my business I need to train people on using DNN and few of them ever really get it, but 7 is looking much better. Here are a few more thoughts:

When adding a module, there are three categories, "Admin", "Common" and "All". It is very seldom that you need to add an admin module to a page so the categories should be:
- Admin Modules
- Content Modules - All modules that are not Admin modules (could find a better name)
- Common Modules - Could also be called Favorites
- All Modules

When adding a module to a page a user is presented with so many modules, it is overwhelming. When adding a module to a page it should be easier to determine what content pane to add it to. Perhaps when adding a module and you click on the module tile, you are shown the content panes and you click on the one where you want the module to go.

This is a suggestion that you might find unorthodox, but I think the word "modules" should be dropped in favour of "apps". When I explain conceptually how DNN works, my student seems to understand the word App, where module makes them initially confused until I tell them "Modules are like Apps". Wordpress uses Plugins, I think that is also a better description of what modules are.

We are quickly exiting the cursor age (mouse pointer). All hover actions should be replaced with click to view drop-down. Look at the big sites: Google, Bing, Twitter, Facebook, you don't find hover, it is all but gone. If you stay with all these hover actions, DNN will look a generation behind. The DnnRadEditor does not use hovers, be consistent.

Back to naming, "Pages" is a bit confusing too, because when adding a page my students expect that the page will actually do something where it does not do anything until you add a module to it. Perhaps it should be called "Menu Administration" or "Navigation" because often when you add a page it is not even a page but a link to another page.

I understand what modules and pages are and what they do, but I have been in deep with DNN since version 3. It is hard to understand how difficult it is for new people to grasp until you spend an hour teaching them and then watching over their shoulder.

Deploying a solution as multiple modules was a work around that evolved over time BECAUSE there is no way to instantiate a single definition of a module package.   To get around the issue I am stating, module developers instead started creating multiple modules, each with a single definition!  This is precisely the issue!  That is not how the architecture (multiple module definitions) was intended to be used, but that is how it has evolved over the last 10 years.

So again, as long as DNN supports the concept of multiple definitions within a single module package, it would nice if there was a way to instantiate a single definition without instantiating all of them. 

I'm not sure if your trying to make a point or just playing devil's advocate, but it seems like you are arguing against the idea that a user should be able to select a single definition to be instantiated and I fail to see why you are arguing that way.