The most popular web content management systems (CMS) run upon a web stack that reflects their origins as having evolved out of predominant open source web-technologies. Apache, MySQL, and PHP (which generally run on Linux but are not constrained to it) are the foundation of the most widely-known CMS platforms because they were the most effective way for web enthusiasts to get working websites online as the internet was gaining mainstream popularity.
DotNetNuke is an odd player in the CMS world – it is runs on top of ASP.NET and uses SQL Server for its database backend. Using Microsoft proprietary technologies for a website is an option that many developers may have the tendency to shun, but DotNetNuke is fully-featured, available through a free community edition (with enterprise licensing options for official support and higher-grade features), and has been regarded as easy to use despite its many powerful features. As far as advantages that DotNetNuke offers in the world of CMS, we can examine its scalability, hosting options, and administration features.
By running on top of Microsoft’s server stack, DotNetNuke inherently gives itself a wide range. It is more than suitable for the type of private, small-scale website that a developer would launch with Worpress, Drupal, or Joomla, but it is also more than suitable for integrating with a corporate intranet and interacting with an array of internal enterprise systems. For instance, DotNetNuke intertwines very nicely with Active Directory memberships and roles due to its foundation of ASP.NET.
Though DotNetNuke runs on a foundation that is not as familiar to many hardcore web developers as the WAMP/LAMP stack, the proliferation of hosting providers that offer push-button installs and management of CMS instances tend to make the underlying web architecture a moot point. Similar to the major open source CMS offerings, there are a number of providers dedicated to hosting a DotNetNuke implementation.
Ultimately, an administrator is the true end-user of a CMS and the ability to manage it can be a make-or-break. Fortunately, DotNetNuke tends to get high marks in this regard. One reason for this is that it allows granular security settings, such as password protection for individual modules in a page. Another is because it allows an administrator to support multiple websites from one account.