~/talk

A Drupal Contrib-First Approach

links:none on file
slides:none on file

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

  1. 0:00Introduction and icebreaker
  2. 1:07About the speaker and Nerdery
  3. 2:51What is a Drupal contrib-first approach
  4. 7:07Engaging with the Drupal community
  5. 8:56Onboarding clients to the community
  6. 11:50Agile and Drupal values alignment
  7. 14:02Discovery process with spikes and personas
  8. 17:34Evaluating solutions with decision matrix
  9. 21:50Feature requests and community collaboration
  10. 25:21Benefits for clients and consumers
  11. 27:10Increasing impact and quality
  12. 30:45Lowering cost of ownership
  13. 33:58Reusability and reduced overhead
  14. 35:01Benefits for individual developers
  15. 37:09Benefits for agencies and providers
  16. 39:39Working definition and closing
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.