In Part 1 of “How I Learned to Love WordPress and Stop Worrying” I focused on web site design and management and the accompanying people problems.
Often, a web site that has been built using a content management system or arcane “easy” web site design platform causes either:
1) a continuity issue – the tribal knowledge of managing that particular web site goes missing
2) a growth issue – the existing web site can not handle new desired features or capability
So, Why WordPress?
These are the two big reasons I’ve found that WordPress makes sense for most organizations. People who know – or are at least familiar with WordPress – are easy to find. Plugins are plentiful. And, in a worst case scenario if you have to contract with a PHP programmer to develop some custom plugin for your organization, they also are easy to find.
WordPress was initially designed as a blogging platform for our increasingly content hungry digital culture. Since then, it has evolved into what most would consider a web site platform. As a result, WordPress makes sharing blog and content duties very easy. And, that helps satisfy the delegation issue – the number one web site related people problem.
All of this ties into the blurring of lines between what exactly it means these days to “blog” versus “build a web site.” But, I explore this in future posts on the subject of content marketing. (See what I mean?)
Not So Fast
WordPress isn’t without its share of problems. For example, a bad plugin, failure to back up data, or an ill-chosen opportunity to upgrade the core files can bring about another kind of shock and awe. Moreover, layers and layers of custom features and functionality installed via plugins can create new tribal knowledge scenarios for an organization.
However, there are ways though of getting around all of the downsides of a WordPress implementation. And, for most, the advantages far outweigh any disadvantages.
Got a web site or WordPress horror story? Please, tell me about it.
