Drupal vs Wordpress: This Is Not My Beautiful House
summary
Claim: WordPress in 2016 can replicate most Drupal features — Advanced Custom Fields, Views, page builders and workflow plugins — but its contributor market fragments functionality into dozens of single-purpose plugins that break, get abandoned or introduce backdoors. Drupal keeps core conventions and interoperable modules, making complex content models, integrations and custom applications cheaper to build and more stable; shortcodes create UX pain in WordPress while Drupal’s Paragraphs gives modular editing. Use WordPress for simple sites, publishing or tight budgets; choose Drupal for critical, custom, long-lived platforms.
AI-written summary · about
chapters (23)
- 0:00Introduction and setup
- 1:04Speaker background and focus
- 2:07Brief history of the web and CMS
- 13:25Market share and CMS landscape
- 15:31Broker’s law on CMS limitations
- 18:43Drupal’s early challenges and evolution
- 20:50Client’s WordPress preference and dilemma
- 22:37Conventional wisdom debunked
- 25:26Failed analogies for Drupal vs WordPress
- 28:59Drupal’s competitive advantages questioned
- 36:04Exploring WordPress contrib market
- 39:5742 plugins to manage content types
- 41:04Plugin instability and security risks
- 43:10WordPress shortcodes and usability issues
- 45:00Drupal’s community-driven solutions
- 46:46Custom applications and Drupal’s edge
- 48:51Drupal’s stability and reliability
- 50:16When Drupal is not the answer
- 51:43When WordPress is the right choice
- 53:08Alternatives to Drupal and WordPress
- 54:10Client update and conclusion
- 55:12Why Electric Citizen uses Drupal
- 57:20Q&A and final thoughts
