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