I recently got in a Twitter ‘discussion’ where I felt like I was put in a position to defend WordPress as a superior CMS to ExpressionEngine. Not an argument I’m actually qualified to make as I’ve never used ExpressionEngine. I did consider it about three years ago and perhaps if I’d started then I’d be on the other side of the fence. But I decided over a year ago that WordPress was going to give me the juice I was looking for in a CMS and I dived in head first. The truth is I experiment on the web too much to pay an entry fee for every install (EE). I may have run 50 installs of WordPress in the last year for both client and personal projects including demos and tests. That would be a pretty serious expense on ExpressionEngine’s pricing model. Thankfully WordPress is fully open source and free to experiment with.
Here’s some interesting tweets from that Twitter conversation:
There was a bit more but hopefully you get the jist. Defending WordPress against ExpressionEngine doesn’t happen when I bid for jobs. Usually clients are more concerned with which open source CMS to use such as Joomla, Drupal or WordPress and I’ve come to see strengths in each although I’m strictly a WordPresser for the moment. I’d estimate that it’s difficult to be a master in more than one CMS as a web developer, although probably not impossible. The time one puts into developing on a CMS cannot help but create a kind of myopic point of view on how to develop for the web. So I kind of do understand where PXLated is coming from. He’s invested serious time into EE, he has control of it and intimate knowledge of how to achieve results. That’s similar to how I feel about making sites on WordPress. But not exactly. His point about surgery and makeup is actually quite true. I prefer it that way though. It can be like working on a special car. After I’ve customized a WordPress site I definitely feel like I’ve built something. Often there are moments when I feel like I’m starting from scratch with WP. It’s very rewarding to be able to assemble the right mix of code/plugins to make a site do exactly what I want.
I do have a feeling that he’s right in a way. For certain situations, building a site on EE would be easier and faster than it would on WordPress. WordPress’s native format is a blog structure. If a client is looking for a blog or publication website it’s hard to see how they would choose any other platform besides WordPress. A lot of sites are smaller and more like ‘brochure’ websites. While WordPress may be competing with other CMS’s to prove it’s the ideal platform for page based sites the truth is static content is a cakewalk on WordPress. EE has something called Channels which is extremely helpful in structuring out a website (Not everything should be categorized as a Page or a Post…the native WP formatting). WordPress lacked this kind of taxonomy until version 2.9 and thus wasn’t taken seriously as a CMS until it allowed for Custom Post Types and Taxonomies. Even now these crucial features require either extra functions or plugins to implement. I have a feeling these will be baked into the next major release of WordPress which will make it an undisputed fully functional CMS. Despite the fact that WordPress is the most used CMS on the web there are detractors.
But that’s all boilerplate. I’m not really an expert with stats or on every CMS. I’m a designer and WordPress developer who is also a user. This is important because in addition to it’s usefulness in my professional life, customizing my WordPress sites is also now a hobby for me. This blog/site is a good example. I’m sure it’s evident that I haven’t designed it despite the fact that I earn a living as a web designer. Aside from time constraints (isn’t it hard to design a site for yourself?) it’s strategic. I use this blog as a test platform for all sorts of new plugins, functions and features. I intend to make this site an archive of my entire creative life. It’s a personal project. I have various interests that range from art, tech, music and ideas. How to categorize these things? Well, I wanted to be on an evolving platform. I love that when I have an idea or have seen a new web functionality on the web I can Google around and find either the perfect plugin or function to implement on my blog. It’s actually not always as easy as it sounds. But it’s fun for me. The chase of finding that piece of code that’s going to expand the capabilities of my website. This tenacity to build and expand my personal websites for fun by experimenting has taught me so much about usability and given me great strategic insight into the functionality a site can and should have. This hobby creates useful knowledge that I then apply to client jobs. This kind of integration creates a special appreciation for the work (and play) I do.
I’ve read that some EE designers love that they don’t have to muck around with PHP code. Seeing how powerful and accessible WordPress is I feel the opposite. I’m inspired to learn more code so I can contribute something to the platform if I have my own take on a specific functionality. Seeing and experiencing the enthusiasm and vibrancy of the WordPress community (I went to my first WordCamp NYC last year) I have to say that I feel even more inspired to dig in and help WordPress grow and improve. I got the sense that WordPressers feel they’re involved in something special. Matt Mullenweg is an incredibly pure face/figurehead for the platform. Here’s someone who is arguably as important as Mark Zuckerberg (same age too) yet has chosen to vehemently adhere to the open source values he had when he first forked WordPress (at the age of 18). I doubt he’s rich (but I bet he’s comfortable) and he’s shown something vibrant and innovative can be created without monetizing the daylights out of it. More importantly he’s shown that open source success can surpass commercial products in an overwhelming way (not necessarily in a monetary way.) All these developers, designers and amateurs working and hacking at this one thing is really yielding some amazing web innovations.
Why do I use WordPress? It comes down to community, accessibility, scalability, usability, fun, freedom and yes…philosophy.