The discussion turns a technical dependency into a governance question: how Drupal can share infrastructure risk without weakening the Association that keeps Drupal.org running.
...more
Open source adoption is only part of the sovereignty question. The harder issue is whether the institutions that depend on shared software also help maintain it.
...more
Drupal site security rarely stops at core and module updates. Canonical’s survey shows why package provenance, Linux maintenance, and patch ownership remain part of delivery risk.
...more
AI can make code appear faster, but it cannot make a contributor understand what the code does. For Drupal developers, the harder question is whether AI-assisted work can be reviewed, maintained, and trusted.
...more
Accessibility failures often surface after budgets, architecture, and delivery plans are already fixed. Mike Gifford argues that public agencies can reduce that pattern by contributing fixes upstream.
...more
Editors often rely on developers for simple display variations. ERVMS moves those decisions into the editorial workflow without changing Drupal's existing display architecture.
...more
For Drupal teams using Layout Builder, the harder problem is often not creating inline blocks, but finding them after they leave the editor’s immediate view.
...more
Architecture choices become clearer when the CMS is not the whole application. Yii3 helps frame where Drupal should lead and where a separate PHP service may belong.
...more
AI systems need more than models. Matthew Saunders argues that Drupal’s existing content controls offer a useful foundation for governed AI workflows.
...more