My employer uses WP Engine for a lot of varied content. I’m not directly involved with it, but it appears to be well designed for corporate use. We masquerade various WP sites behind different domains & paths on our site. For example, www.example.com/about/ is one WP environment, www.example.com/blog/ is another, and www.example.com/business/ is yet another. Only certain people in our organization can edit /about/ and /business/, but we hire external authors to provide content under /blog/ so they have access to that.
We also apparently have the ability to modify pages on a dev/test domain then migrate them to our production domain very easily. So changes can be tested & verified before going live.
All that being managed by WP Engine means we don’t have to worry about manually setting up WP, managing our users, making sure everything is properly backed up, etc.
My employer uses WP Engine for a lot of varied content. I’m not directly involved with it, but it appears to be well designed for corporate use. We masquerade various WP sites behind different domains & paths on our site. For example, www.example.com/about/ is one WP environment, www.example.com/blog/ is another, and www.example.com/business/ is yet another. Only certain people in our organization can edit /about/ and /business/, but we hire external authors to provide content under /blog/ so they have access to that.
We also apparently have the ability to modify pages on a dev/test domain then migrate them to our production domain very easily. So changes can be tested & verified before going live.
All that being managed by WP Engine means we don’t have to worry about manually setting up WP, managing our users, making sure everything is properly backed up, etc.