Skip to main content

A case for WordPress; or, not your own CMS

I've worked at several major companies thus far in my career; and, at each of those companies, I've had to use an in-house Content Management System (CMS) to create and modify digital content.  For a long time, I couldn't understand why those companies would choose to allocate time, resources, and ultimately money to create a customized CMS in spite of having functionally equivalent, open source solutions readily available in the marketplace.  What was their rationale for doing so, I often wondered?  Was their businesses so unique that an off-the-shelf CMS simply wouldn't cut it; were the security risks associated with an open source CMS too great of a burden to bear; or, was it because the software engineer(s) in charge at the time simply wanted to showcase their PHP, Java, Python, etc. programming skills by building yet another CMS from scratch.  Well, in the years since I first pondered that question, I've come to realize that the answer is often the latter reason.

Don't get me wrong, there are legitimate security concerns with open source or off-the-shelf products.  However, I've found that most of those concerns can be easily mitigated with sensible access controls and regular vulnerability patching policies.  What's more, I've found that leveraging a dedicated open source community or third-party vendor whose sole focus is a given product often produces a more secure product than anything else a "regular" company could build on their own.  The same can be said for bug fixes and new feature development from open source or off-the-shelf products -- be it a CMS, Project Management Software (PMS), or Application Performance Management (APM) solution.

And yet, many companies continue to go down the "let's build it ourselves" path instead of choosing to use open source ones.  Such a decision, in my experience, usually ends up being bad for the vast majority of companies.  In fact, I've yet to encounter a situation in which it's made sense for a company to build their own CMS from scratch.  To be clear, I'm not saying that it can never make sense to build one's own CMS; just that it rarely does!  Thus it should be the default position of most companies to simply buy or use an open source CMS whenever possible.

Having said that, a common refrain I still hear is that a particular business' operations are too unique to use an off-the-shelf product like a CMS.  I think that line of argument is laughable!  The truth be told, there's nothing particularly unique about the way company "A" creates and publishes its content from that of company "B".  Rather, a company's true value proposition is in its proprietary product line(s) and not its digital content and/or User Experiences (UX).

But let's say I've managed to convince you, which CMS do you choose?  Well, there are so many out there, i.e. WordPress, Drupal, Joomla, dotCMS, Crafter CMS, etc.  My recommendation, in a word, is to use WordPress.  Why?  Because WordPress has been around for close to two decades; it's chock-full of features, plugins, and themes; and, it powers close to half the web, including such companies as Facebook, Etsy, BBC America, MTV News, and The New Yorker - just to name a few.  What's more, WordPress' security notification and self-patching systems are best-in-class and a breeze to use.  So, do yourself and your company a favor and choose WordPress; it's very unlikely that you'll never regret the decision.  Or, if WordPress isn't your cup of tea, then just choose some other random CMS -- just don't build yet another one yourself.


  1. EasyUEFI Enterprise Crack owns comprehensive EFI/UEFI boot option management functions, such as create, delete, edit, clean up, backup and.EasyUEFI Enterprise With Crack Free Download

  2. God Bless Quotes residence of the pious is blessed by God. He invariably can bless your and grant you what you merit if you follow His commands.God Bless Quotes For Friends

  3. Fans of NFL underdog teams, for instance, will choose to guess on their teams at even odds than to guess on the favourite, whether or not the guess is $5 or $50. Gamblers may exhibit a 우리카지노 number of|numerous|a variety of} cognitive and motivational biases that distort the perceived odds of events and that affect their preferences for gambles. Gloria Mundi, or The Devil addressing the sun, a cartoon displaying the British politician Charles James Fox standing on a roulette wheel perched atop a globe displaying England and continental Europe. The implication is that his penniless state, indicated by turned-out pockets, is due to of|as a end result of} of} playing.


Post a Comment

Popular posts from this blog

A better UI/UX for Cookie consent banners

I'm sure you've seen them before; those pesky, inescapable  Cookie consent banners !  They typically appear at the top or bottom of websites -- often obscuring important content.  For example, if you were to visit  CNN ,  Zara , or  Unicef  today; or, any other news, e-commerce, or charitable website for that matter -- especially those with an international presence -- you'd likely see one; a UI / UX eyesore.  Such Cookie consent banners, ubiquitous and omnipresent, have become the defacto solution for complying with an important part of the European Union's (EU) ePrivacy Directive  (ePD). If you're unfamiliar with the ePD, it basically mandates that websites first obtain a user's consent before storing and/or retrieving any Personally Identifiable Information  (PII) about them in and/or from HTTP cookies.  ( HTTP Cookies are small pieces of data stored by websites in a user's web browser for easier retrieval later.)  The Cookie Law, as the ePD has becom

The Crucial Role of Service Level Agreements (SLAs) and Service Level Objectives (SLOs) in Software Applications

In today's digital era, software applications are at the heart of business operations and customer experiences. From e-commerce platforms to enterprise solutions, the performance and reliability of software applications can make or break an organization's success. To ensure seamless operations and meet customer expectations, having robust Service Level Agreements (SLAs) and Service Level Objectives (SLOs) in place has become paramount. In this blog post, we will explore the importance of SLAs and SLOs and how they contribute to the success of software applications. Defining SLAs and SLOs A Service Level Agreement (SLA) is a contractual agreement between a service provider and a customer that defines the level of service expected. It outlines the metrics and targets the service provider commits to achieving, such as uptime, response times, and resolution times. SLAs establish a mutual understanding between the parties involved and provide a framework for measuring and managing s

Using HTML tables for website layout

I first became a front-end web developer in the year of our Lord, 1998.  Back then, the HTML specification had just reached version 4.0; Internet Explorer 7 was the dominant browser; and, the mantra of separation-of-concerns  was still being preached to web developers.  (Back then merely uttering the phrase CSS-in-JS  would've gotten you killed, professionally speaking.)  What's more, back then, HTML tables were still de rigueur; in fact, many websites used them for layout purposes ( DIV-itis hadn't caught on with the masses as yet; that would happen several years later.) Yes, it was the stone ages of the web -- in comparison to today.  Today, there's a wealth of newer technologies for developers to choose from when building websites, i.e. HTML5 , CSS4 , ES9 , etc.  Long gone is the mantra of separation-of-concerns and in its place sits CSS-in-JS, mockingly.  And, long gone are table-based layouts too; they gave way to the aforementioned DIV-itis phenomenon and t