Ok in conclusion I think we continue the discussion on:
- Use commercial modules way

For first I ask you, and other that want to reply:

What's the better way to make mobile website:

- Create a New portal sor the mobile website
( Easy to modify, I don't know how use the same module if I want that one module is visible in more than one portal....)

- Use a different skin in the same portal
( I can use the same module, I need a commercial module for hide and show right module)

please reply your ideas
Rmartin

DotNetNuke CE has the full capability to build mobile enabled websites.  This is no different than the capability in PE.  You can use mobile skins which have full access to the mobile capabilities and can use responsive design or adaptive rendering techniques

Where DotNetNuke PE differs is that we incorporate the capability to handle detection and redirection to the mobile site depending on the user device.  This capability already exists as third party components that have been available to anyone using CE for the past couple of years.  Vendors like Salaro and Bind.pt have been including this with their mobile enabled skins for a while.  We have now provided a single API that these vendors will be able to leverage to provide more advanced capabilities over what they already provide.

Ultimately, we have to balance our efforts to benefit both our CE customers while still dedicating some resources to building out some unique capabilities for our commercial customers.  In 6.0 the vast bulk of our resources were focused on improving the core CE platform.  In 6.1 we wanted to spend more time providing additional value to the PE/EE customers while also providing hooks for our 3rd party vendors and the open source community to deliver capabilities to the CE users.

At the end of the day it is our PE/EE customers which provide the revenue that allow us to continue expanding the CE platform.  We will constantly strive to balance our efforts between the two.  Sometimes that means we'll have features that are available in all platforms and sometimes that means we'll spend some effort providing differentiated value for our commercial customers.

---

Joe Brinkman
DNN Corp.

DotNetNuke Community Edition, the open core foundation for all DotNetNuke editions, is amazing.  It does not limit users, portals, files or any functionality; it does not contain "blocks" or limits on how open source, commercial or private development can leverage it's API and capability.  I just wanted to reiterate that because I think it's easy to forget when we're facing unmet expectations, whatever they may be.  This is very unusual where commercial interests and open source come together, and it is worth remembering... it is a very strong and unique foundation.

Just to paint a bit of vision which might be helpful, our desire is to cultivate INCREASED participation in our open source Forge (free) and vendor community.  Ideally, we would have had time to work with key Forge and Store developers to ensure that there were some additional ready extensions at release time.  But the release schedule has not permitted that, and because all the press has been about features that would be exposed primarily in the Professional Edition this has led to some unmet expectations at release.

The good news is that the Community Edition is being injected with capability which continues to make it the strongest platform it can be.  I am looking forward to watching (and helping to cultivate) ingenuity in the Forge.  We have several recent examples of where Forge contributions become Community Edition features (eg. Page Management, DDR Menu, etc) and I know we will see this happen here as well.  There is still additional depth to be added to the Mobile API and we're going to need developer feedback in the next iteration.

That said, I totally understand that much of the "feature set" for Mobile in 6.1 is targeted primarily at Professional Edition users (capability is in the CE API for developers).  But our last release (6.0) was very revolutionary for Community Edition, this release contains the Client Dependency Framework (a huge benefit for CE) and our next release (with social features) will an enormous boon for CE also (bigger than 6.0, i suspect).  And in the meantime you can help us encourage your favorite vendors and Forge developers (and maybe even some new folks) to build for the 6.1 mobile experience!

We are all in this together... and we know we have to all work together to keep improving every area, all the time.  The 6.1.0 release is not the end of a journey, it is one step farther along a road that looks increasingly brighter every day!

Thanks for airing your concerns, Craig.  We learn from them and we appreciate your passion and enthusiasm... it matters!

---

Scott Willhite, Co-Founder DNN