Hi,

One of the main challenges the DNN ecosystem faces is a fragmented functional and visual UX.  Many third party modules have their own paradigm for a) user feature access b) module configuration and c) branding, graphics, heading, etc.  Even simply things like using the Head and SubHead classes are often overlooked. Most modules, even the core, don't support templating so you just get what you get. The result is a hodge podge UX with different layouts, fonts, link colors, etc.  This make pitching DNN as an 'integrated' solution a hard sell sometimes.

With the release of DNN 6.x DNN Corp started advocating Design Patterns for the UI.  This would be a huge benefit.  Over time third party module developers could bring their layout, fonts, submit buttons, CSS for setting tabs, etc. into conformance with the official Design Patterns.  We started moving the UI for our LMS to conform.

DNN 7 came out with an updated set of Design Patterns and substantial changes to the CSS - just ask any skin maker. The 'painfully hip' black theme has degraded the experience for people who are visually oriented.  Admin icons, instead of suave gray text, are much easier for me to scan and locate. Many admin features now take me more clicks and time than before.  There seem to be more different types and colors of submit buttons, etc.

With the release of 7.0.2 an advanced RadTreeView feature, Load on Demand, that we use to load huge TreeViews in our LMS no longer loads checkboxes properly because the checkboxes are images instead of actual HTML inputs.  Unless this feature is removed, then we will have to provide a work around in our code and this could substantially degrade performance.  More work, less performance, for what?  A sexier checkbox?
http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=25309&PROJID=2

I understand that some change is necessary, but the increasing parade of UI changes seem to be more gratuitous to eager young developers than of real benefit to solution providers trying to deliver an 'integrated' product. Does DNN really need a new look and feel every year to become a market leader?  If DNN would stabilize the UI then:

• our skins don't have to be updated between versions
• we don't have to spend weeks updating our product for each new version
• we don't have to explain new admin UI paradigms to our customers
• Design Patterns can be honored and adopted over time.

 What do other people think?  Am I just too 'old school'?

Thanks,
Chris