Drupal’s Scariest Things
summary
Lists specific failure modes and fixes: live updates and Composer breaks; deployments require practice deployments (deploy several dry runs before go‑live); legacy D7 config and migrations stall teams moving hundreds of sites or 200 websites on one database; Paragraphs and Layout Builder create confusing content models; headless setups force rebuilding core Drupal behaviors so headless Drupal often increases work; caching layers, integrations and unexpected user loads (200 artists froze a site) need rehearsed rollbacks, CI, training and focused discovery.
AI-written summary · about
chapters (5)
- 0:00Introduction to scary Drupal things
- 10:10Common fears about Drupal updates
- 20:36Legacy systems and Drupal 7
- 30:59Long-term project sustainability
- 41:15Q&A and closing thoughts
related talks
01h 04mImproving your Drupal 8 development workflow
51mDrupal DevOps 101: Customize Your Drupal Like a Harley
27mFAIL: The Best Ways To Bring Down Your Website
41m12 Factors of Pain and Suffering
01h 08mPrinceton Site Builder: Behind the Scenes
01h 00mDevops @ Princeton: How we track, maintain, and deploy hundreds of sites
39mSecurity, Drupal 9, and Navigating the Changing Web Landscape
45mDrupal.org Infrastructure Update