Development Approach
Decisions from the dev meeting (30 June 2026):
| Decision | Details | Reference |
|---|---|---|
| Yes to AI | Unanimous. Start from André’s TDD multi-agent pipeline + shared playbook. | — |
| GitLab-first | Write epics & issues in GitLab now; skip the old d.o queue to avoid a migration. | Using GitLab to contribute to Drupal |
| Minimize dependencies | ”As much Drupal core as possible.” Discuss before any non-standard library. | Using Composer with Drupal |
| Yes to HTMX | In core since 11.3 (Drupal 11.4 is current); use it for live interactions like comments. | HTMX API documentation |
| Reuse components | Base the UI on the new d.o / “bluecheese” components; discuss before custom ones. | Using Single-Directory Components |
| Ship fast, review at the end | Devs run independently, no mandatory peer review; a larger review gate before hand-off. | — |
Work split: John → Matrix · André → infra/AI + remainder · Nico + Salman → picking areas.
Architecture Decision Records (ADRs)
Section titled “Architecture Decision Records (ADRs)”The project records significant technical choices as Architecture Decision Records (ADRs). These are stored in the repository under docs/decisions/ (browse the docs/decisions/ tree in GitLab) rather than published as site pages, so each decision stays a versioned repo record next to the code it affects. We follow the MADR format, a common ADR standard building on Michael Nygard’s original ADR concept.
Groups Initiative — Rebuilding Drupal's community Groups platform on Modern Drupal.