The London session gives Drupal practitioners an opportunity to hear about a university AI concierge and raise questions directly with its presenter.
...more
The debate over open-source infrastructure often ends at agreement. Matthew Saunders wants it to continue into budgets, governance, and contributor support.
...more
Social embeds depend on platform APIs that can change without warning. Juicer Social Feed gives Drupal site builders a block-based path while Juicer handles feed aggregation outside the site.
...more
The sessions place Drupal AI in front of service desks, editorial teams, and sensitive campaign moderation instead of leaving the discussion at roadmap level.
...more
The beta turns quiz design into a routing problem rather than a fixed sequence of questions. Site builders can now think about what happens after each answer, not only which questions appear next.
...more
The latest Drupal 11.4 patch closes a routing regression that had remained visible after the previous bugfix release. The update also gives site teams a concise set of core fixes to review as the 11.4 branch settles after its initial release.
...more
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