Supporting Drupal-as-a-Service: Providing Tech Support to Drupal Devs
summary
University of Minnesota runs support for 500+ custom Drupal sites and 1000+ Drupal “Gardens”, split into a constrained Drupal Lite offering and a full-featured Drupal Enterprise; the team manages core and module updates, SSL certificates, GitHub-based custom code, backups and nightly cloning, Ddev local dev docs, drush operations, and a “module bouncer” to prevent stale copies. Support uses tiered help lines, walk‑in labs, self‑help guides, and a new merged continuum between Lite and Enterprise to reduce migrations.
AI-written summary · about
chapters (12)
- 0:00Introduction to Drupal-as-a-Service
- 2:52Drupal Lite vs Enterprise platforms
- 6:25Requesting and setting up a new site
- 8:53Launching a Drupal website
- 12:25Maintaining launched Drupal sites
- 17:01Tools and resources for site owners
- 23:22Support channels and communities
- 26:13Balancing flexibility and constraints
- 31:31Future of Drupal light and enterprise
- 34:59Support tiers and escalation
- 38:11Where to draw the line in support
- 40:16Q&A
