Wordpress

“Whenever you see a successful business, someone once made a courageous decision.”
― Peter F. Drucker 

Whether you love it, hate it, or feel nothing about it. Whether you use it every day or only sporadically, it’s become part of your work environment. Whatever your relationship to it is, you must surely feel something as it approaches the end of its life, and you need to decide what to do about it. It’s your Drupal 7 site, and it sunsets next year.

As someone who has worked professionally with WordPress websites for 15 or so years, the most common question I have heard from clients, coworkers, and even other colleagues in digital is some variant of: “Is WordPress secure?” 

We're proud to have been recognized by Clutch in their annual listing of the top creative, design, and development companies in 2018.

Last week I attended the HTML5 Dev Conference in San Francisco. While reasonably priced, the conference offered excellent workshops full of cutting-edge techniques and geeky humor. I enjoyed learning about new technologies and tools, as well as receiving confirmation of some best practices that I’ve been using.

It's been a couple of weeks since Kalamuna ushered in a new era of peace and harmony by running Wordpress on Pantheon.  However, even as the people rejoiced in celebration of this momentous discovery, not all was right in the CMS kingdom.  Was this blissfull new marriage between Pantheon and Wordpress in danger?

Turns out no, but the hook was too much to resist.

Kalamuna doesn’t dabble in theology, so we tend not to participate in debates over CMS superiority. From our perspective, Wordpress and Drupal were created equal, solving similar problems in different ways for different people. It thus saddened us to think that Pantheon, our favorite hosting provider, might separate our client’s Drupal site from its Wordpress-powered blog. Fortunately, no such CMS sin was committed. Read on to grasp true content management nirvana!