1. Because WordPress is an open source platform clients think they can do everything themselves. How do you manage your and their expectations?
    1. I don’t stop them. I give over any access they request (with good backups) and let them “try”. It doesn’t take long for them to realize that they can’t figure out how to do anything but post/edit. I also charge for training outside of an agreement.
    2. I’m a big advocate for not holding client data hostage. If I’m doing my job right, I have nothing to fear. I always have plenty of work.
  2. What is the worst mistake you have ever made in WP development?
    1. Building too large in WordPress. – WordPress can be used as a large platform, but I don’t recommend it. I know the New York Times uses it, but it just was not made to function efficiently with that much data and images.  You will pay a fortune in hosting to stabilize the environment.
    2. Ie..We had built an 86,000-page site in a WordPress. We had to have 3 dedicated servers (1 base and 2 load bearing server), CDN and major on-site cache to support the load time, and we still couldn’t get it under 12 second load time.
    3. I also tried building a 15k product e-commerce in WordPress. A bit easier to manage load time, but still buggy. – Ended up having to change platforms only 1 year later. womp womp.
  3. What is the biggest issue with WordPress in 2015?
    1. Security. Hands down, it is one of the most hackable platforms out there. Western Groups are even told to exploit WP vulnerabilities to hack faster. I spent a big chunk of time this month cleaning WP sites and adding better security.
  4. What predictions do you have for WordPress in 2016?
    1. Other CMS platforms will begin to have better weight on Google rankings. Sad to say, but the more widely used the platform becomes, the more vulnerabilities it has, and Google is well known for adding factors that move away from the general “norm.” If this happens, make sure to start hiding your WordPress tags.
  5. When do you know when you should update WordPress, plugins and theme?
    1. There is no special trick to this. My philosophy for upgrading is “stay up-to-date, and you will have fewer cracks” You have to think of it like an earthquake. Things have to move and shift around…All you can do is be prepared, and fix when damage is done. Of course, that’s easier for a web-developer.
    2. I setup auto-backups, and set my server to allow WordPress to auto-update when there is a “stable” release. The first release is almost always buggy. A few weeks later they will release a less buggy upgrade. I buy into that version. My security plugins, and server alert me when a file is changed. I then check the site to see if anything has “cracked.”  It’s rare that something “cracks”, but if it does I fix it free for clients that host with me. Their business is worth a little trouble.
    3. For those of you that don’t have a web developer on call. Maybe be a bit more conservative. Upgrade everything one to three times a year, etc.. But, don’t go under that.
    4. I rarely upgrade themes, unless something buggy is happening. It’s rare that it would break. It’s almost always plugins that cause issues.
      1. When in doubt, start deactivating plugins one by one.

By Erin Gordon of