Drupal vs. ExpressionEngine

We developed a corporate website using Drupal, which features a large number of static pages and several dynamic functions, including a contact us form, location finder, and job posting. We utilized Drupal with some customization to achieve the desired functionalities. We have also worked on e-commerce sites using Drupal, and there is a scope for improvements, specifically in cataloging.

Incentivized

For someone with a limited budget, it's hard to recommend ExpressionEngine simply because of the cost of the license and any add-ons just to get up and running. As a developer, the budget needs to be a certain amount before I can even consider ExpressionEngine - no matter how appropriate it is for the site. Besides that, I recommend ExpressionEngine for those who have a lot of content, have a need for a certain level of flexibility, or who have special feature requests. There are a number of ExpressionEngine add-on developers who are willing to help build (for a fee) custom add-ons to fulfill that need.

Incentivized

• Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
• Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
• Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.

Incentivized

• ExpressionEngine has no preconceived ideas about how your content should look or what code is generated.
• A robust template engine makes integrating designs and content a breeze.
• The control panel can be customized to control what content managers have access to.

Incentivized

• Security and new release notifications are a hassle as they happen too often
• Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
• Steep learning curve, but worth it

Incentivized

• Can be too cumbersome for smaller projects, takes time to pair down the built in functionality so our clients have to sift through unused features
• Large queries take significant processing power, recommended use of a cache module to store this data and speed up page load
• Backend can be overwhelming for clients, lots of things to manage in the control panel
• No way to repeat custom page fields or groups of fields, meaning page layout must be pretty established and not customizable from the control panel

Incentivized

I really like Drupal, and besides the one major issue with not being able to update from version 6 to version 7 and I am happy to continuing using it. Hopefully as time goes on they will make it easier to upgrade or provide better tools for mid-level web designers like myself to build out new sites without the help of expensive 3rd party's.

I'm satisfied with the way that my site runs on EE. My primary concern is that support is now a profit center for EE's publisher and so they've consequently gutted their community support boards. However, a good EE community is developing at StackExchange. At this stage, I don't think that EE is a good choice for an individual site owner. WordPress or SquareSpace would be a better choice unless you have a budget for support.

It has a very steep learning curve. When starting with Drupal, the functionality and setup have to be learned, which is complex in comparison to tools like WordPress. Drupal is more powerful and can create a wider range of applications, but it definitely has a learning curve. I would recommend it to anyone who wants to make a dynamic web application bigger than the scale of a WordPress blog.

Incentivized

ExpressionEngine is very powerful and flexible. With this flexibility comes a bit of a learning curve. There are some great online resources for getting up to speed with EE, but the control panel can be a bit daunting. A lot of EE's installation process involves settings, configurations and flipping of switches. It is tedious, but well worth it as you ultimately have a very robust, secure and scalable CMS. Also, as of version 2.9.2, the control panel isn't responsive natively. You'll want to have a big enough screen to see the full control panel UI. Personally, I think the control panel would benefit from a major overhaul. It would be nice to see the colors and UI controls "modernized" and be able to more effectively customize the layout. Yes, some of this is built-in, and there are third-party add-ons to help, but maybe we'll see more refinement in future versions.

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

Never experienced an issue like this with it

Incentivized

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

The admin section would slow to a crawl the larger the tag section grew. There were many areas where better pagination would've helped improve performance. Nothing complicated, which made the lag so frustrating

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I have personally never found any complications when trying to receive support from EllisLab in regards to ExpressionEngine when using the support plans they offer. I have always been responded to promptly and received satisfactory help with whatever my needs were in an extremely timely manner. This makes rating the support offered an easy job for me

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

After installing the system a few times, you can see a pattern of things that have to be done to work the way you want them (settings, paths, etc.). By knowing what you want, you can put together some scripts that prepare the file system for installation, adjust post installation configuration settings, and install initial templates.

Drupal's capabilities outpace WordPress by miles. Drupal is more customizable, scales better for larger companies and has advanced content types. If you own a small business or work at a startup company, I would recommend WordPress but if your firm is trying to scale and you have more than 50 employees I would recommend Drupal.

Incentivized

ExpressionEngine outweighs most all of its competitors by being so flexible. If you can imagine it, then you can build it with EE (ExpressionEngine). Most competitors lock you in with certain ways to build your website or use only their tools; ExpresionEngine gives you the freedom to build how you would like and decide how you want your site to run and operate. The ease of use for clients to go in and edit their content is great, and I am able to control the way they edit that content to make it the easiest for them. The feature set and plugins for EE are great, and I am able to provide top service for my clients by using EE.

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

Maybe it's scale-able from the content user perspective, but it was very limited from the programmers perspective. So many custom hacks were necessary that it reached a point it would be impossible to upgrade to a newer version

Incentivized

• Drupal helped us launch a creative, marketing- and product-focused website with custom coding integrations tailored to our goals.
• Drupal allows us to rely on secure and consistently updated core code.
• Drupal's code taxing on the server does start to get a bit heavy as you go along with customizations, so at some point, we decided to stop. We want to ensure our Google Page Score remains high, including paying close attention to page load speed.

Incentivized

• Being able to be recognized as a leader within the ExpressionEngine development community has led to us being sought out by those customers seeking expert guidance.
• We tend to specialize in using ExpressionEngine for our customers, so it has been easier to ramp new resources up on our development process, as well as be able to seek out independent experts to use as sub contractors or freelancers.
• As we have been using ExpressionEngine almost exclusively for a number of years, we have built a reusable repository of proprietary code that makes our development process much more efficient and decreases the effort required for our projects.

Incentivized