- Drupal can be troublesome if development is not planned.
- Drupal is more of a framework than a CMS.
- Most Drupal “developers” are not really developers.
- Drupal is not meant for brochureware websites.
- Drupal is not a WordPress alternative (and vise-versa).
In my experience I’ve found Drupal to be a highly scalable web platform. Majority of the Drupal projects I’ve worked on seem to be working on existing Drupal installation(s) that needs lots of work to bug fixes / architecture redesign. While Drupal has an intelligent MVC design… it seems most “Drupal Developers” don’t fully grasp the underlying architecture so the one-off “modules” they build are prone to conflict with other modules. Drupal is built on the LAMP stack (PHP) so you really need to be a PHP Engineer to built out good modules. Drupal has a robust administration that gives developers the ability to configure an application through a WYSIWYG interface yet too much reliance on this could cause havoc when bugs occur and the administrating developer is unfamiliar with the underlying PHP code of the connected modules/views/blocks/etc.
Here are some Drupal projects I’ve worked on:
MassChallenge.org – Worked with the CEO and CTO to redesign (backend and front-end) their website, intranet, and CMS as the existing Drupal was developed by multiple interns which caused lots of bugs and technology limitations.
ViaSat.com – Redesigned website (backend and front-end). Converted website from a custom built website to a new Drupal installation.
Verizon vCommons (Intranet) – Developed several internal social media apps to promote improved communication and collaboration for 270,000+ employees.
Verizon CAB (customer portal) – Developed a customer portal for Executives of high-end clients.
TheWrap.com – Converted a legacy Drupal environment of thousands of news articles to WordPress VIP with supporting applications in a new Drupal install.