Oct 26

Simon Collison - Five Years Of Quiet Revolution

Categories:
ExpressionEngine
Tags:
colly, community, erskine design, expressionengine
Published:
10:10am on Monday 26th October, 2009

Simon Collison is the Creative Director of Erskine Design, and discussed his personal history of using ExpressionEngine.

Watch or download Simon’s slides from Slideshare.

My EE History

  • ExpressionEngine lets us meet wishlists from clients. As a tool it creates possibilities
  • Background is from building static sites, then using Mambo and MovableType (“crap”)
  • Moving to a dynamic, database-driven site for the first time is exciting
  • Became a designer at Agenzia, using and hacking pMachine a lot
  • Sold the use of EE 1.x for the Libertines website on the strength of the possibility for community interaction
  • As EE was developed, the tools we needed started to come out in each release. EllisLab were listening
  • Convinced Friends of ED to include ExpressionEngine in the Blog Standards Solutions book
  • Agencies and individuals such as Solspace and Mark Huot started to use it as the backbone of their work
  • Jamie Pittock launched the first EE fansite, Jambor-ee, and Mike Boyink’s Train-EE was providing tutorials. We started to have places other than the official forums where the community could share their knowledge
  • The Frieze magazine project was a big test of EE; sixteen years of magazine archives, complex content models, and demonstrated the power of the Multiple Site Manager module
  • EEInsider and Devot:ee appeared to share more community information
  • Some add-ons become indispensable - Erskine need Playa and other commercial add-ons in their work
  • When building a website, it’s wrong to be limited by the technology you use. With EE, we can design sites with an awareness that we can make it happen
  • The ability to (re)design the admin interface ourselves is important
  • We are building our own Ad Server module
  • EllisLab hired Erskine Design to design and develop the demo site that will be included with 2.0
  • The tools coming out in EE 2.0 are what we’ve been waiting for, but we need to spend time with 2.0 before we’ll be comfortable using it for client work

The future of ExpressionEngine

The future of EE should be to meet the needs of developers and clients. Simon covered the points he believes EE should consider as it grows past the 2.0 milestone.

  • Adopt common developer methods
  • Have robust first-party modules
  • Provide on-going support for vital add-ons
  • Enable development staging and delivery
  • Provide Un-Simple Commerce!
  • Reintroduce the Advisory Board
  • We need more demos and better example sites

“The quiet revolution is over. If we work smart as a community, we’re in for a great ride.”

I'd love to hear what you think - please use the form below to leave your comments. Anything I consider too offensive, off-topic, or spammy will be deleted at my discretion. Some HTML is permitted, or you can use Textile.

Commenting is not available in this weblog entry.
  1. Nobody has commented on this article yet - why not be the first?