The 2025 recruitment drive added maintainers across a dozen vacancy areas, but Drupal core’s current roster shows how later departures and module changes have altered that picture.
...more
A Drupal core issue opened in 2010 has led to a more explicit way for Views plugins to request routing and plugin-cache work after a View is saved.
...more
Earlier PHP 8.6 builds have already exposed Drupal deprecations and dependency warnings. The final beta gives maintainers another checkpoint before the runtime moves into release candidates.
...more
Editors can be allowed to view an unpublished node and still be unable to select it in a reference field. The current proposal would close that access gap without requiring broader bypass permissions.
...more
The module already turns prompts into Drupal pages. Its next development direction reaches further upstream, where design tools and tokens could become inputs to the site-building workflow.
...more
Maintainers finally have a tagged Drupal 12 build to put real projects against. Some compatibility work will need another pass, however, because the dependency target is not yet frozen.
...more
Twig has lacked the automated standards enforcement already available for PHP, JavaScript and CSS. The shared GitLab CI job brings contributed projects closer to the same checks now running in Drupal core.
...more
An HTMX interaction does not always need Drupal's full page output. Duncan shows how core can return the requested content and required assets while keeping cache variants separate.
...more
Coding agents working on one repository can miss evidence scattered across Drupal core and contrib. Drupal Code Query now exposes its wider code and compatibility dataset through MCP.
...more
The experiment puts AI in a planning role rather than a code-writing one, using it to organise a large issue backlog before contributors commit to an implementation.
...more