Creating Nimble Drupal Systems: Transforming a Drupal Team in 6 Months
summary
A six‑month engagement with the Minnesota Department of Health delivers concrete changes: three audits (technical, UX, accessibility), a prioritized roadmap, and iterative fixes that keep strict AWS security and on‑prem constraints rather than moving to Pantheon. The team retires a bulky Bitnami image in favor of FlightDeck Docker containers, enables multi‑developer multibranch workflows with ddev, migrates unmanaged legacy PDFs to Drupal to avoid deletion, tightens image and cache settings, and reduces tags from thousands to <100 while adding a daily diff content moderation cron for lightweight governance.
AI-written summary · about
chapters (19)
- 0:00Introduction to talk
- 1:26Speaker background
- 4:16Project overview
- 6:44Defining Nimble Drupal
- 8:08Project genesis and empathy
- 9:36First month challenges
- 10:43Team's Drupal experience
- 12:08Listening and audits
- 13:58Four months of improvements
- 16:47Technical Drupal updates
- 18:59UX and accessibility work
- 20:27Content moderation strategy
- 22:33Tag and content cleanup
- 23:40Accessibility fixes
- 24:46Transformation approach
- 25:06Asking for help challenges
- 27:35Q&A team buy-in
- 29:45Leaky bucket analogy
- 30:06Ongoing engagement status
