~/talk

The Curmudgeon’s Guide to Building Drupal Websites

links:none on file
slides:none on file

Advocates a repeatable plan: involve design early, document architecture, and list key modules and decisions (e.g., Paragraphs vs Layout Builder, Varnish VCL for e‑commerce integrations, migration scope choices). Favors a hierarchy of reuse — use core then contrib then custom — and minimizes repeated touches to the same feature. Uses concrete tooling and techniques: Composer with composer-patches, Drush php-script, git bisect, Xdebug and IDE debugging. Emphasizes peer reviews as conversational knowledge transfer, clear setup docs, and hypothesis-driven debugging.

AI-written summary · about

  1. 0:00Introduction and background
  2. 1:50Client happiness over budgets
  3. 2:53Early involvement in design
  4. 4:42Identifying project risks
  5. 6:08Tech stack and architecture planning
  6. 7:55Creating an architecture plan
  7. 11:05Guiding principles for developers
  8. 14:17Core and community modules
  9. 15:44Finding and evaluating modules
  10. 17:28Essential Drupal tools
  11. 19:55Effective debugging strategies
  12. 22:00Problem-solving approach
  13. 24:27Traits of effective teams
  14. 25:08Importance of peer reviews
  15. 28:42Code quality and maintainability
  16. 31:15Documentation best practices
  17. 32:19Continuous learning and curiosity
  18. 35:52Q&A and unconference details
~/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.