In a world full of multiple options, picking the right CMS can be quite a task at times. Each CMS comes with its own share of good and bad points, thus making the selection process even more difficult. How does one pick the ideal CMS? Which features does one require? These are only some of the questions that every user asks before he or she decides to use a particular CMS.
Two of the most talked-about CMSs in the current computing scenario are
WordPress and
ExpressionEngine. Each has its own loyal user base, multitudes of extensions and features, as well as drawbacks. Both WP and EE are often compared, debated and discussed all across the internet.
So, among WordPress and ExpressionEngine, which one beats the other? We shall attempt to answer this question in this article.
However, before we go any further with the actual comparison, let me first take a moment to clarify my reasoning behind each category or sub-category of comparison.
WordPress and ExpressionEngine: The Comparison
What And How?
In writing this article, I have attempted to compare the two wonderful CMSs under the following heads:
- Usability and User Experience
- Community and User Base
- Support and Documentation
- Miscellaneous
Note that, however,
the free versus paid rhetoric has not been considered. Why? Simply because you will consider a paid EE over a free WP only if you can afford it. Now, since you can already afford to pay for your CMS, you should definitely shell out money if you think the said CMS can bring an additional edge to your website, and you should not if you feel that the said CMS will not be worth the investment -- in this case, this article might prove useful for you. On the other hand, if one cannot afford to pay for EE, he or she will likely settle with a free option such as WordPress anyway, and there will not be much need for such a comparison.
Furthermore, the first point, usability and user experience is by no means an absolute answer: what is usable for you may not be usable for me. I have tried to provide an exhaustive opinion on this point, because most likely, you will not use either EE or WP just for your website, but will also be passing it on to your clientbase.
Lastly, it must also be noted that in this article, I have refrained from citing any concrete technical examples. Bluntly put, both WP and EE are not competing entities and thus, a purely technical comparison (such as doing
this on
that) will not be fruitful (if it were WordPress vs Drupal, the story would've been the opposite).
With that said, let us see how each CMS fares!
1. Usability and User Experience
Let’s take up WordPress first. Is the CMS usable? Definitely yes. However, what sort of user experience does it provide?
Ideally speaking, usability need not simply refer to the interface and appearance, though a good interface is almost always a preliminary requirement. WordPress brings to its users a great level of simplification and abstraction: no matter where and what I write about WP, this is one point I often find myself repeating:
WordPress deserves a pat on its back for bringing simplicity to the end users’ lives. Agreed, I am openly biased in favor of something light-weight such as
Habari or something more refined, such as
Concrete5. However, the abstraction that WordPress offers is in a league of its own! Yet, what about the advanced users? What if you wish to migrate domains or change the URL of your blog? What if you ‘like’ tweaking the database? In its crude form (sans plugins and extensions), can WP serve your purpose in that case? This is where the simplification of WordPress acts against it: Concrete5 gives me a sitemap editor and SEO settings without installing any plugins or playing around with the code; WordPress does not.
ExpressionEngine, on the other hand,
assumes that you know what you’re doing (allow me to be blunt: if someone is shelling out over $200 for a single-license of a CMS, he or she should know the software well anyway). The CMS gives you channels, and each channel is given its own categories, custom fields and behavior. Thus, EE is not the CMS for your everyday blog or hobby site about osteopathy. In fact, EE is the option you should consider if your website is in need of multiple modules and features which are otherwise semi-hidden (or absent) in WordPress. In terms of user experience, ExpressionEngine will make your life very easy if you know how to treat it properly.
2. Community and User Base
WordPress is the world’s most popular CMS -- make no mistake about it, this piece of software has its own loyal following. You have the official
forum, along with the
plethora of websites all across the internet that offer your content related to WordPress. Basically, if you are looking for fellow WP users to share some knowledge and a cup of coffee, you will not have to look long and hard: there are just too many of them out there!
This is one area where ExpressionEngine lags slightly behind. That said, it must be clarified that EE has its own
loyal user base and a decent
community. However, in terms of numbers, the community is less populated as compared to that of WP. Furthermore, you will not be able to find many blogs related solely to EE. Perhaps the biggest reason for the smaller community is the fact that EE is a paid software, as compared to the totally free WP. Lastly, before you fall prey to the numbers’ game, it must also be pointed out that some of the biggest names in the industry use and trust EE, so just in case you decide to use it simply for the sake of good company, you won't be a loner!
3. Support and Documentation
Again, WordPress has its own
Codex, coupled with the third-party blogs. There isn’t much to talk about here beyond that.
Coming to ExpressionEngine.
Ellis Lab have a
user guide at your service: however, the biggest plus is the
support. Now, expecting such support from WordPress will be unfair, because all said and done, WP is not a paid software. However, irrespective of that, ExpressionEngine has a support desk, specialized paid support (starting at $49 per month, paid in addition to the $299 CMS pricing), and other related sections. To sum up EE’s performance in this section, just two words:
professional support.
4. Miscellaneous
Let us now try to sum it all up.
WordPress is ideal for end users and PHP developers. ExpressionEngine, on the other hand, seems apt for designers and front-end developers.
If you wish to just play around and create a blog, or wish to extend its functionality by means of tweaking, look no further than WordPress. If, however, you’d like extensive control right from the beginning and are not the type who’d employ PHP skills simply to extend a CMS, ExpressionEngine is definitely worth the money.
Conclusion
Here is something I used to repeatedly ask myself, years ago when I was still experimenting with CMSs:
WordPress lets you install themes at will; why can’t ExpressionEngine do that?
Later on, as I got accustomed to EE and other CMSs, I realized that at times, WP needs to be tweaked to get a certain task done, whereas EE does that very task in a comparatively lesser amount of time. Naturally, both CMSs have their own pros and cons, and the more I used both of them, the more I fell in love with their respective strengths and weaknesses.
Anyway, nostalgia apart, what do you think of WordPress and ExpressionEngine? Which of these two tools do you use and prefer? Have your say in the comments!
(dpe)
I am a volunteer on a small local library board. Because of my background in graphic design, I’ve offered to oversee the redesign of our “antique” website to bring it into the 21st century in both appearance and functionality. I have very limited web experience and have been exploring the CMS options, trying to educate myself before hiring a designer/firm to do the redesign.
Our director would like to use WP. She says it will be easiest to manage once it is in our hands. But I find it limiting design wise. To me websites built on WP templates look like blogs masquerading as websites. EE sounds more versatile from a designer’s perspective. Then there are other librarians who have recommended Drupal or Joomla. Those sites look very institutional, though I’m not informed enough to know if this is due to the CMS or the designers working with them.
Is there anyone in this community who, taking the particular needs and requirements of a library’s website into consideration, could make a recommendation as to which CMS would offer the functionality needed and yet allow for dynamic, exciting, smart, graphic design? And be user friendly enough for staff to maintain once it is completed?
Thanks!
I can develop a site running with EE within 2 days. I can implement concepts exactly from a Photoshop design into EE without evening needing to think whether that design is possible.
For WP, I need to throw the design back to the designer because the design is simply not possible with WP.
Need to add a user defined field into a website? Easy does it in a few minutes with EE. WP, will take years
Howdy! Do you know if they make aany plugins too protect against hackers?
I’m kinda paranoid about losing everything I’ve worked
hard on. Any suggestions?
We like how Expression Engine supports carving down the back-end to as simple a set of controls as possible. In our experience – users with an immensely simplified task publish and edit more frequently.
Also – this simplified learning experience is then easier to pass on to new employees and to remember or relearn after a period of inactivity. This too extends the life of the CMS aspect of the site.
I wish the license and plugin costs were a bit cheaper. However we believe the additional cost is justified if the customer looks at the long term value of actually using the system and publishing content.
If the CMS isn’t used – what’s the point?
—
For web saavy end users who want to do more than JUST publish and edit content, WordPress is a great choice.
For the rest of the humans, Expression Engine makes it easy to help the customer focus on content and keeps the site designed intact. It’s easier for us to establish a simple workflow that users actually take advantage of with Expression Engine.
.02
I never understand this debate. WordPress is a blogging platform, EE is a content management system. You can shoehorn WordPress to handle content and create complex taxonomies but it’s not intuitive and it’s not easy. Expression Engine’s Channel->Channel Groups->Channel Fields structure is not comparable to anything in WordPress or Drupal (Joomla, gimme a break, not even mentioning that here). I have used both WP and EE for years and Expression Engine, every time, wins hands down when a client requires any kind of custom data structure which is, pretty much, every time.
We stopped building on WP and Joomla about 3 years back and hardly get any support calls for our EE sites, even on quite complex ecommerce jobs. Training on smaller sites is now done over the phone rather than on site and the usual response at the end is “Is that all?”
Just have a look at what happens when you try and offer an open source addon with EE to get a grasp of the EE community.
http://aaronrussell.co.uk/legacy/expressionengine-matrix-showdown/
“Comments like “don’t shit where you eat” and “this is a tight knit group” and an echoing chorus of “take this down immediately” have flooded the inter-webs today. To be frank, it all sounds very cliquey – this pitchfork-wielding mob want blood!”
Wow since 2012 this post still great!
My personal thing is that WordPress will be great ONLY if you find a Template that do everythings you need quickly, Expression engine still my favorite development CMS !
WordPress is for cheap sites, at the expense of losing theme HTML control and functionality and being tied to third party plugin functionality, whereas Expression Engine gives complete control at the expense of more time to develop (so higher cost).
WordPress does allow bespoke themes and plugins to be developed of course, but in that situation you may as well use Expression Engine.
We always choose EE because we want complete control. We want our own optimised code and functionality and so its easier to support then. No wants to make bespoke changes to a third party WordPress add-on!
Pretty intense debate, its been a few years and its still raging. Adding my 2 cents and 15+ years experience as a web progammer and developer, my veredict is: EE sucks! it has a super complictaed admin for clients, an imposible to use database structure, and the code cannot do anything beyond the simplest blog functionality, you cant even use a variable to store a value and use it later. If you dare to use php inside your templates then youll have to deal with the weirdest parsing order in history, its super slow, youll spend thousands on support, plugins, specialty developers, and if you need something just a bit complicated to happen youll need a custom plugin, which will have to be made in codeigniter which luckily is an awesome framework. You´d be better off buiding with that, or if you need something simple, and dont want to spend a fortune just use wp! it has the best support comunity ever. well thats my view, anyway