Item: Drupal
Rating: 7
Author: Verified User

Use Cases and Deployment Scope

We currently do not use Drupal. We used to in the past but have gone to a in-house built CMS platform. We have a very specific clientele and Drupal was just too much for our needs.

Pros and Cons

Large community of other developers building plugins for the CMS
Site can easily expand when needed, so it makes it semi-futureproof.
When built correctly, Drupal allows the client/admin to easily update/change/add content on the site.

Has a very large learning curve. Especially with Drupal 8, which is a big change from previous versions.
With the amount of plugins available by numerous developers it is harder to make sure your site is secure.
The back-end UI has always very felt confusing and clunky.

Return on Investment

I have moved from Drupal to WordPress (version 4+) because of how long it takes to set up a new Drupal site. This was always the downside to Drupal. I can build a completely custom WordPress site in 3/4 the time.

As previously stated, I have moved from using Drupal to using WordPress because of project timelines. Also the company I work at has also stopped using Drupal and WordPress and gone to using a custom in-house CMS.

Other Software Used

WordPress

Likelihood to Recommend

Not really... Drupal can be built to suit whatever needs you have. Whether that is a large site with thousands of pages or a small site with only a handful. I have built very straight and structured sites for provincial/state governments as well as very artistically abstract sites for art studios.

Drupal. The CMS beast.

Overall Satisfaction with Drupal

Use Cases and Deployment Scope

Pros and Cons

Return on Investment

Alternatives Considered

Other Software Used

Likelihood to Recommend

Drupal Feature Ratings