We work fast around here, and for the website that means continually iterating on the copy, images and content to ensure the resources available are the best possible. Unfortunately, that can take a huge toll on engineers and developers if they’re relied on for making those changes. ExpressionEngine helps us to ensure that owners of different pages and projects can easily change the website with less programmer involvement. It has definitely achieved that goal.

• Read the full interview

Next American City's previous site, which I built and launched in 2008, ran on EE1, so the staff were already familiar (and enamoured) with it. Although the site was enough of a departure that we didn't actually upgrade (but instead exported all of the old blog posts with a custom script), building on EE2 was a no-brainer. I knew we'd have to do some custom development around subscriber access and various levels of permissions, and EE's member groups and extendability made that easy.

• Read the full interview

Everyone in the company already knows how to use EE because the previous version of viget.com was on EE (version 1.6.2!), so it was an easy choice.

• Read the full interview

The wider family of Frieze websites is based on EE, so it was the logical choice for the new site. Frieze's workflow is based around publishing which fits well with EE. They have a large content editing team so EE's access control list is also a useful feature.

• Read the full interview