2 out of 5.0, Reviewed Dec 2, 2016
The process slows down productivity.
Open source can be expensive.
Accessible where there is an internet connection.
Poor workflow. Only has minimal page control. WYSIWYG is poor. Module were poor and had to hire a programmer to create modules for website. There are too many steps to update maintain webpages. Example, a simple link requires several steps Company has not had a conference/collaborative in over 5 years.
Provide better functional, innovative and supportive modules.
Ensure modules are supported and built by the company instead of external developers.
4 out of 5.0, Reviewed Oct 18, 2016
DNN were very good to work with - we opted to use a licensed version of the software rather than the open-source release, and professional services as well as client services were very responsive. We ultimately chose to move off the DNN platform but this was due to the desire to consolidate some technologies, mainly a move to a LAMP stack running Drupal. We found the process of migrating from one server environment to another to be quite a bit more complicated with DNN than with Drupal, as was performing security patching and updates.
Budget time to get your team up to speed on doing DNN development in-house, even if you farm out some of the tasks initially. Research whether you need to spend the money on licensed versions of DNN, or if Community Edition will meet your needs, especially if you plan on being in a cloud-hosted environment where you plan to have some kind of auto-scaling in place.
End users seemed to find the product relatively easy to use. Having several editions (including Community) was useful. There is an active and enthusiastic community out there using DNN, which means finding answers to question is not a challenge. Lots of free training videos on YouTube. DNN is supported in PaaS in the Microsoft Azure environment.
Process of patching and performing updates is somewhat complicated, with no easy means of performing a rollback, although this is more a factor of being Windows-based than anything else. Migrating to a new server environment also seems fairly complex, at least compared with Drupal (which we are moving to).
No real complaints against DNN organization. They were responsive when we needed help, even when we made it clear we were transitioning away from licensed versions of their products. I'd love to see a more simplified path for applying patches and upgrades to the products - as it was, performing upgrades was always slightly fear-inducing.
We could have probably gotten by with using only the community (open-source) edition instead of Professional or Enterprise editions. Support was very good but I'm not sure we used it enough to justify in hindsight. Also our selection of 3rd party vendors to develop several of our sites could have been better, and the end results left something to be desired. When our team did the development, our results were much better.
Support with Professional and Enterprise editions was very good. Tickets and emails were responded to quickly. There is a fairly large and active DNN community out there, so finding information is not too hard.