A Drupal Contrib-First Approach
summary
Explains a contrib-first workflow used at Nerdery: use JIRA spike tickets for discovery, pick contrib modules that solve ~80% and plan a 10–20% contrib or patch to close gaps, track feature requests in Drupal.org issue queues, and score options with a simple decision matrix plus MoSCoW priorities. Shows concrete tradeoffs (theming vs. module changes breaking contextual links/Quick Edit and cache tags), cites JSON:API security churn as a community benefit, and notes about five hours/week of hands-on coding while leading projects.
AI-written summary · about
chapters (16)
- 0:00Introduction and icebreaker
- 1:07About the speaker and Nerdery
- 2:51What is a Drupal contrib-first approach
- 7:07Engaging with the Drupal community
- 8:56Onboarding clients to the community
- 11:50Agile and Drupal values alignment
- 14:02Discovery process with spikes and personas
- 17:34Evaluating solutions with decision matrix
- 21:50Feature requests and community collaboration
- 25:21Benefits for clients and consumers
- 27:10Increasing impact and quality
- 30:45Lowering cost of ownership
- 33:58Reusability and reduced overhead
- 35:01Benefits for individual developers
- 37:09Benefits for agencies and providers
- 39:39Working definition and closing
