Adopting a Drupal Contrib-First Approach
summary
Argues a contrib-first workflow adopted at Nerdery: onboard clients to drupal.org and organizational attribution, monitor issue queues, submit patches, and prioritize contrib or core solutions over custom code. Uses a decision matrix for core vs contrib vs custom tied to weights like time, cost, maintainability and roadmap compatibility. Cites practical pitfalls (missing template attributes, render arrays, cache tags, Drupal behaviors, Varnish) and wins (JSON:API security, faster reuse, lower ownership cost), plus checklist items for agile discovery, contribution, and client onboarding.
AI-written summary · about
chapters (9)
- 0:00Introduction and audience
- 1:27What is a contrib-first approach
- 4:59How to engage the community
- 8:34Collaborating with clients
- 13:24Evaluating solutions with clients
- 16:17Benefits for consumers and clients
- 21:43Lowering cost of ownership
- 24:41Benefits for individuals and providers
- 27:16Adopting the approach in practice
related talks
55mFirst-time Contributor Workshop
47mThe Great Adventure of Open Source Contribution
27mHow to start contributing to Drupal without Code
37mGet more contributors! Lessons from the Drupal Ladder
45mOpen Source Contribution Panel
31mSupporting Innovation through Contribution
01h 05mDrupal Contributions - A Pragmatic Approach to the Issue Queue
24mSo You Want to Contribute to Open Source: ...