We use it for our own website, but we also host and use it to develop websites for our Clients. Our business model is a SaaS to the MLM / Network Marketing industry.
We write a lot of our own modules in C# and also buy a few from other developers.
Clients like to control the content and look and feel of their website, with DNN they have the ability to do so but then leave all of the heavy lifting to us to manage the Hardware, Programs, SQL Server and provide the necessary Reporting to them.
- If a Client needs to add a page for a special Event, they can do so without having to contact us.
- If a Client needs to add or change content, text or images at any time day or night they have the ability to do so without having to contact us.
- Our Clients do not have to know anything about HTML, ASP.Net, C#, SQL Server etc. If they know how to use a Word Processor then they can do most anything they need from a Content standpoint by just using their favorite Browser.
- If they need a special Module to do accomplish a certain task and we don't have one then we can provide one of hundreds developed by another developer from the DNN Store. Most modules are less than $100.
- Because DNN uses Skins that are a layer on top of the platform architecture they can have different skins for different pages or departments etc. On the DNN Store there are literally thousands of Responsive Skins available that range in price from $40 - $200.
- The platform is scalable and of course SQL Server is as well. So no matter how large a company gets DNN can handle the task ahead.
- I really only have 2 complaints and they are minor with DNN. First I think that DNN might need to do a better job of certifying Developers that sell modules. Create a standard if you will, much like Apple does with Apps, as not all developers are created equally and support on some modules is lacking with some developers.
- The second thing is I would like to see DNN keeping Developers more informed about upcoming changes to the platform and better co-ordination with developers on time schedules of new releases. Many times it seems the Developers have to play catch up when a new version is released and all of a sudden you may have some Modules that don't play nice with the changes.
- Neither of these are really a major problem as DNN and the community has evolved tremendously over the years and it is fairly easy to find solutions from the community.
If you just need to implement a website that is dynamic but not real big in Data Processing almost anyone can do so with very limited knowledge as long as you know how to use a Word Processor and your Browser.
If you don't have experience with setting up a Server to run a website there are Companies like PowerDNN, Rackspace and WinHost that can help and I recommend them in that order if you are using DNN.
If you need a more sophisticated e-commerce website and don't have much experience with Servers, SQL Server etc. then you should find a consultant to help you install and setup not just the DNN Platform but also select the proper Modules to accomplish what you want to do.
If you need a highly customized website that is very data intensive and you are not experienced then be sure to save yourself the time and money by finding a qualified Consultant to help you. The beauty of DNN is that it can handle as simple or as complicated of an Application as you need depending on what your needs are and how far you want to take it.
- From my side DNN makes it very easy to manage everything we need to publish for users
- Implementation of our custom modules is very simple
- On version 6 of DNN, there are problem using multi-language settings for the portal and switching between languages when we try to use iFinity Url Master. The problem is with querystringsparameters with diacritic values
- DNN is easy to install, configure and administer
- DNN is a full-scale content management system that offers many options for managing blogs, photo galleries, files and communication
- DNN is secure and offers flexible role-based security architecture
- DotNetNuke integration with Active Directory can be improved
- Ability for DNN modules to communicate (send-receive data) is missing and can be helpful if in place
- DNN could offer wizard-type tools for custom modules development
- DNN is a feature-rich, open-source project with a flexible license. This let us use it without licensing costs for custom solutions or as-is with no custom code just plug-in modules.
- DNN is written in Microsoft .NET C#. This allows our developers and our customers to use their existing skill set to install and maintain the solution.
- DNN is made for Windows platform, allowing us and our customers to deploy solutions to existing Windows servers or in some cases hosted platforms.
- DNN integrates with Windows authentication allowing us to deploy intranet solutions and use single sign-on for improved user experience and security.
- DNN is developed with Microsoft Visual Studio, which is great if your developers already know and use it, but switching to it can be expensive in terms of licensing (for paid versions) and training costs.
- DNN module creation is powerful for custom solutions but more complex, time consuming, and error prone than some other open-source solutions based on open-source scripting languages that can be edited without needing to be compiled.
- DNN has a rich 3rd-party ecosystem of modules and themes but it pales in comparison to a CMS such as WordPress.
- DNN's foundation on Microsoft technologies is a strength if you need it but a potential limitation if your organization is not entrenched in the Microsoft ecosystem. For example, a quick search on some freelancer sites shows that WordPress developers outnumber DNN developers 10 to 1.
- Modular capabilities in term of software development and solution. The use of .NET platform further enhanced its power.
- Skin development relatively easy to make, however, some specific knowledge of DNN platform is required.
- DNN store provides a fast amount of effective, value of money solution. Most of the time, purchasing from the store is more than enough.
- Skin customization has room to be improved.
- Mobile friendly platform, e.g.: make use of the Bootstrap as default skin
- DNN is more into software developer. It will nice to have some tools for web designers.
- Lacking of complete facilities for disabled people (see WCAG). In this case Sitecore is much more powerful.
- DotNetNuke makes it easy to edit content on a website. Clients can log in to the site, click on the "Edit Page" button in a convenient menu at the top of the page and then edit specific sections (or modules) on a page. They have the ability to upload images and other documents (PDF, Word, etc) and also can add links. The HTML editor provides options to paste from word and also the ability to edit the HTML directly for the more tech-savvy users.
- DotNetNuke makes it very easy to allow users to sign up as members on a website and also makes managing those users via site Administrators easy. It is also very easy to set up other ways for users to log in (via Facebook, Twitter, Google, etc).
- DotNetNuke is extremely extensible. There is an app store where you can find many free or low-cost modules that can be installed to utilize applications such as event calendars, news, blogs, and many other web application types. It is also quite easy to build your own custom modules if you have a little development experience.
- DotNetNuke is extremely easy to get started. There is a simple install screen that comes up the first time you visit your site that will allow a site up and running in seconds.
- Overall DNN is a great platform, but there is room for improvement. They could provide more tutorials and help for developers and designers to integrate with DNN. It is very easy to build basic skins and modules but if you need to do more advanced things, there really is no help for this at all. You pretty much have to just learn by trial and error.
- Some of the design standards built in to DNN are inconsistent and difficult to work with. Some core DNN modules use 1 way of styling the module while other modules use different styles. HTML tables are not properly used and overall there are times you have to jump through hoops to make some DNN components look the way you want.
- While there are a lot of apps on the DNN store, there is virtually no developer support. DNN developers seem to keep their secrets, well, secret. There are a large amount of WordPress tutorials out there, but not a lot (of free) DNN tutorials.
- Evoq is very extensible. As long as you can program in ASP.NET, you can customize it for any solution you may need.
- It has great user controls and granular permissions for users allowing you to control access not whole sections of the site, individual pages, or even parts of a page.
- Some of the modules you can purchase allow you to derive far more value than what you pay.
- It can be a bit heavy-handed when it comes to styling. It's sometimes necessary to spend a little extra time to overcome styling issues.
- Up until version 8 of the core DNN platform, implementing single page applications (SPAs) required extra efforts.
- It is very difficult to split a site across multiple servers for load balancing
There were other modules that I have personally written while I worked on DNN when it first came out. They were all related to securing DNN while DNN was really new to the scene.
- Minimal code writing to create new basic modules.
- Good ASP.NET integrated user authentication and authorization
- Plenty of free and paid modules available to create DNN site.
- DNN should really create good tutorials for beginners. It takes a while before one can understand on how to get started in writing modules and their implementation
Evoq Content Scorecard Summary
Feature Scorecard Summary
About Evoq Content
Evoq Content Competitors
Evoq Content Technical Details