Keene Systems, Inc.

DotNetNuke vs. WordPress: Which CMS Fits Your Business?

WordPress is the most popular content management system in the world. That makes it the default choice, and the default choice is not always the right one. If your website is more than a brochure, DotNetNuke, now called DNN, deserves a serious look. Here is how the two compare, from a team that builds on both.

The short answer

If your site is mostly pages, articles and a contact form, use WordPress. It is very good at that and there is no reason to make life harder.

If your site has to know who is logged in, show different people different things, hold business data, enforce your rules and talk to your other systems, DNN is the stronger foundation. WordPress can be pushed into doing those jobs. DNN was designed for them.

Think of a pickup truck and a box truck. Both will get a sofa across town. If you move furniture every day, you want the one that was built for it.

DNN vs. WordPress at a glance

DNN (DotNetNuke)WordPress
Built onMicrosoft ASP.NET and SQL ServerPHP and MySQL
Designed forPortals, member sites and business applicationsPublishing: blogs, articles and marketing sites
Users, roles and permissionsBuilt in, down to the individual page and moduleBasic roles built in; finer control needs plugins
Several sites from one installationBuilt in from the startAvailable through the multisite feature
Add-onsModules: fewer, mostly commercial and supportedPlugins: a vast number, of very mixed quality
Custom developmentC# modules, the same tools as a full .NET applicationPHP plugins and themes
Fits a Microsoft environmentNaturally: Windows Server, SQL Server, Active Directory, AzurePossible, but it is not home ground
Finding people who know itHarder. It is a specialty.Easy
LicenseOpen sourceOpen source

Where WordPress wins

Credit where it is due. Our own website runs on WordPress, because it is a marketing site and publishing is what WordPress does best.

  • Publishing. For writing, editing and organizing articles, nothing is easier.
  • Choice. There is a theme or a plugin for almost anything you can think of.
  • People. Designers, writers and marketers already know it, so training is short and help is easy to hire.
  • Marketing tools. Search engine optimization and page-building plugins are mature and widely used.

If that list describes everything you need from a website, you can stop reading and choose WordPress with a clear conscience.

Where DNN wins

Permissions are part of the foundation

DNN was built as a portal, so it has always assumed that different people should see different things. You can decide who may view or edit each page, and each module on a page, by role. Staff see the internal pages, customers see their own area and the public sees the rest, all on one site with one login system. In WordPress that level of control comes from plugins, and each plugin is one more thing to keep compatible and up to date.

It can grow into a business application

This is the big one. A DNN module is a real ASP.NET application sitting on a real SQL Server database. That means a DNN site can manage orders, patients, permits, deliveries or product catalogs with proper business rules behind them. We built a portal on DotNetNuke that managed more than 16,000 products through 70+ custom modules, tied into accounting and sales systems. That is a long way from a website, and DNN took it in stride.

WordPress can be extended too, but a system like that is working against the grain of a publishing tool. The usual result is a business system assembled from a couple of dozen plugins that were never designed to work together.

It belongs in a Microsoft shop

If your company already runs on Windows Server, SQL Server and Active Directory, DNN speaks the same language. Your IT people can back it up, secure it and report from it with tools they already use. It can be set up so staff sign in with the accounts they already have. Your website data sits in the same kind of database as the rest of your business data, which makes joining the two far simpler.

A smaller, steadier set of add-ons

WordPress has an enormous number of plugins, and that is both its strength and its weak point. Many are written by one person, abandoned without notice, and left installed for years. Outdated plugins are among the most common ways WordPress sites get broken into.

The DNN module market is smaller and mostly commercial. The vendors we rely on have been selling and supporting the same products for many years. Fewer moving parts from fewer suppliers is easier to keep safe. To be fair, no CMS is safe if nobody updates it, and that goes for DNN as much as WordPress. See DNN upgrade services.

One site that does both jobs

Companies often end up with a WordPress site for marketing and a separate custom system for customers or staff, with two logins and two sets of data. DNN lets the public website and the logged-in portal be the same site. Your marketing person edits pages in a Word-like editor, and your customers log in to the same address to do business with you.

How to decide: five questions

  1. Do visitors need to log in? If yes, and different groups need different access, lean toward DNN.
  2. Will the site hold business data, beyond pages and blog posts? If yes, lean toward DNN.
  3. Does it need to exchange data with accounting, a CRM or another database? If yes, lean toward DNN.
  4. Is your company a Microsoft shop? If yes, lean toward DNN.
  5. Is the site mainly for publishing and marketing? If yes, and you answered no to the rest, choose WordPress.

Two or more answers in DNN’s favor and it is worth a conversation before you commit to anything.

Already on DNN and thinking of switching to WordPress?

People often suggest it, usually because WordPress developers are easier to find. Before you agree, look at what your site does. Pages and articles can be moved. Custom modules, logins, permissions and business data cannot be moved. They have to be rebuilt, and that is where the time and the budget go.

If the real problem is that your DNN developer has left, that problem has a simpler fix than rebuilding the site. See DNN support and site takeover and DNN migration options.

Who we are to say

Keene Systems has built custom business software since 1987 and has worked in DNN since 2004. We build on DNN and on WordPress, so we gain nothing by steering you toward the wrong one. Our 50+ professionals include the developers, designers and database people that either platform needs.

If you are choosing a platform, or wondering whether to stay on the one you have, book a 20-minute call and we will tell you which way we would go and why. For more on what we do with the platform, see our DotNetNuke development services and content management systems pages.

Frequently asked questions

Is DNN better than WordPress?

For portals, member sites and business applications, yes. For blogs and marketing sites, WordPress is the easier choice. The right answer depends on what the site has to do.

Is DotNetNuke more secure than WordPress?

DNN builds user management and permissions into its core and typically runs with fewer third-party add-ons, which leaves fewer places for things to go wrong. Either platform is only as safe as its last update.

Can a DNN site be moved to WordPress?

The content can. Custom modules, logins and business data have to be rebuilt, so sites that rely on them are usually better kept on DNN and brought up to date.

Is DNN still being developed?

Yes. The open-source DNN Platform continues to receive new releases and security fixes.

Do you build WordPress sites as well?

Yes. We build on both, and recommend whichever fits the job.

Previous Post
Next Post

Book an Appointment

Whether you are interested in starting a conversation around your current IT challenges or just have some questions about Keene Systems, please fill out our contact form below. We will respond within one business day.