I was asked today to do a quick write-up on DotNetNuke and it’s usefulness and limitations in comparison to other Content Managers that I’m familiar with. Because I love all of you, I thought I’d share it. And yes, I know that I am being very liberal in calling WordPress a CMS, but let’s face it, it has become one of the most popular over the last several years.
I know that I am being very liberal in calling WordPress a CMS……
The two CMS’s that I have compared DotNetNuke to are WordPress and Joomla. The majority of my experience is in WordPress, and since my expertise is in a LAMP stack environment, I’m personally biased toward WordPress and Joomla because they’re both built with PHP/MySQL.
Now, to be completely fair, DotNetNuke has a huge following. Their number of supporters could even rival those of WordPress. DotNetNuke seems to be a much heavier CMS, rich with additional features not found in WordPress or Joomla. It appears to have a stronger emphasis on security, as evidenced by version 5.4’s 7 vulnerabilities compared to WordPress 3.0’s 39 according to Secunia.
Depending on your perspective, DotNetNuke’s reliance on Windows can be a great benefit, or a huge disadvantage. On the one hand, its foundation of .NET technology allows it to integrate with Active Directory and other Window’s programs, making it ideal for an intranet for a mid to large scale company. It also has an enterprise edition which is loaded with additional features such as a Sharepoint Connector and Web Server Farm Support. On the down side, implementing a network with these tools can be timely and expensive. WordPress and Joomla however, are better suited for the LAMP environment. As most of the third party hosts, such as mine (http://www.startlogic.com), run on Linux, these two CMS’s are better suited to the smaller to low mid-sized companies who are on tighter budget restraints.
That’s all I can say with my limited knowledge. What do you think? Leave your comments and let me know!
