Drupal.Org

Drupal CMS is narrowing the path to wider adoption: make professional builders successful first, then improve the experience delivered to content teams. ...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

The batch presents three response paths to Drupal site teams: uninstall unsupported projects, patch active modules, and review where untrusted or generated content reaches the rendering layers. ...more

ECA’s reported growth shows how far configuration-based automation has moved into Drupal site-building practice. The milestone also raises the stakes for a project that many sites now rely on for workflow decisions, integrations, and operational logic. ...more

Drupal.org usage data shows that several long-running contributed modules still appear prominently in Drupal 11-compatible project rankings. The list is useful for planning and dependency audits, but it should not be read as a simple recommendation list. Token remains valid because the contributed module still adds practical functionality around Drupal’s core token system, while jQuery UI and Field Group require clearer maintenance and technical-debt caveats. ...more

The Drupal Association has launched the Drupal Sustaining Members program, a funding initiative for organizations that rely on Drupal and want to support shared project infrastructure. Annual donations begin at $5,000 USD and support systems including Drupal.org, code repositories, software packaging, issue tracking, testing workflows, security tooling, and community programmes. ...more

Drupal CMS 2.1 introduces Site Templates, a feature intended to reduce the initial configuration work involved in launching Drupal websites. In an Acquia blog post, Martin Anderson-Clutz argues that pre-configured templates can help organisations start with working content models, roles, workflows, and design foundations instead of a blank installation, while Drupal.org release notes confirm installer-level support for template selection and site export. ...more

A proposal to introduce “Module Families” on Drupal.org aims to help users compare contributed modules that solve similar problems through structured comparison pages and ecosystem signals. The proposal argues that Drupal’s challenge is not excessive choice but insufficient context, an issue that becomes more important as Drupal CMS introduces curated module selections and opinionated workflows. ...more

A recent DrupalEasy quicktip examines practical workflow adjustments contributors may encounter as Drupal.org project issue queues move to GitLab. The post highlights notification settings, issue-tracking differences, and subscription behaviour that may affect how contributors follow and manage work across Drupal projects. The article also identifies areas where GitLab workflows currently differ from long-established Drupal.org issue queue habits. ...more

Drupal.org has revised how project maintainer permissions sync with GitLab, introducing a two-way mapping that aligns roles across both platforms. The update affects how access is granted and revoked, with a planned bulk update set to standardise permissions for existing projects. Maintainers are being advised to review membership changes as the new system may alter roles more broadly than expected. ...more

The Drupal module Changelogify has reached a milestone with the addition of security advisory coverage, reflecting its progression through the project review process. The update highlights growing interest in automating changelog generation to improve transparency and communication around site updates. ...more

Victor Jimenez argues that teams miss upstream Drupal changes not because information is unavailable, but because signal is buried under noise. He proposes a structured, owner-driven triage workflow that converts upstream development activity into concrete team actions before upgrade risk escalates. ...more