Is WordPress a CMS?
So, here’s a question…is WordPress a CMS?
And be careful how you respond.
The debate hit Twitter tonight triggered by a relatively harmless Tweet from Dirk Shaw:
I’ve been a part of similar discussions on how WordPress can or can’t scale to support larger sites. It wasn’t until another vendor and a CMS evangelist piled on in unanimous agreement that I felt the need to offer a brief reply in disagreement:
I’m not one to defend any one vendor, but it’s a silly argument.
Of course WordPress is a content management system. It’s technology that manages website content. And it manages quite a few websites I may add. I know plenty of fairly robust sites that get along just fine with WordPress. There’s of course a legitimate debate on what types of sites are best suited for WordPress.
But apparently I hit a third rail in the CMS world, because the comments kept flowing.
A number of other folks weighed in, including several that agreed that WordPress should be considered a CMS.
In the grand scheme, this is a relatively trivial debate. Even the folks siding against WordPress as a CMS were for the most part arguing for a different label or pointing out that it wasn’t “enterprise” enough to be considered a true CMS. Toss in a few open source fans and the debate can get religious in a hurry.
This is where the CMS world goes sideways. It’s insider baseball at the expense of the end user trying to make heads and tails of their web publishing strategy.
It still remains a vendor and consultant dominated landscape of folks trying to frame the space based on the tools and put up artificial walls based on product price points or analyst quadrants/waves. And yes, I lump myself into that bucket, although I try my hardest to stay on the outside.
Don’t even get us started on what to call our space (ECM, WCM, CMS, CM).
So, should WordPress be called a content management system? Absolutely.
Does it matter? Not really.