Still have Drupal 7 (D7) website? That’s okay for now. But let’s be honest: in today’s threat landscape, security is not optional. With D7 reaching its official end-of-life, staying protected means relying on more than just luck or legacy systems. That’s where Extended Support comes in, and why it matters now more than ever.
Why security should be your #1 Priority
Cyber threats have evolved. So have regulations. Older platforms like D7 are prime targets if not properly maintained. Without official support, vulnerabilities go unpatched, and your organization could face:
Data breaches or theft
Damage to your brand reputation
Compliance issues (GDPR, PCI, HIPAA, etc.)
Unexpected downtime and recovery costs
Technical problems (e.g. unsupported modules affecting your website’s SEO)
Complete lack of updates
In short: no security = high risk.
Extended Support: your digital safety net
With Extended Support (ES), you're not left in the dark. At Dropsolid, we’re one of only three official D7 ES partners worldwide and the only one based in Europe.
From day one, we have focused primarily on Drupal. Many of our senior developers have worked with D7 for years. Unlike many young developers, they do have the deep knowledge to keep your website secure and performing. This makes us part of a highly specialized group with the tools, access, and knowledge to keep your site secure long after official support has ended.
Here’s how we protect your D7 site:
Proactive security patches
We receive enterprise-grade patches before release, backed by a bug bounty program and ethical hackers
Continuous vulnerability monitoring
We proactively scan for threats and respond before damage can occur
Infrastructure hardening
Whether you stay on your current hosting or migrate to our Experience Platform, we secure your environment at every level
Expert D7 knowledge
Our ISO 27001-certified team, with thousands of Drupal contributions, ensures that patches are applied correctly and modules remain compatible
Custom code support & compliance auditing
We help maintain your custom functionality and monitor GDPR/accessibility compliance
Sticking with D7 doesn’t mean compromising on safety. With ES, your platform stays stable and protected, buying you valuable time to plan a thoughtful migration without rushing under pressure. And let’s face it: nothing beats peace of mind when your digital presence is at stake.
What’s next? From security to innovation
Extended Support is not forever, but it is your strongest shield in right now. At Dropsolid, we help you stay secure today while preparing you for what’s next. We can help you with:
Drupal 7 Extend Support to stay secure today
Seamlessly migrate to a newer Drupal version
Unlock future innovation through Drupal AI, helping you automate content, personalize user experiences and streamline workflows
As a founding partner of the Drupal AI Initiative, Dropsolid is helping shape the future of AI in Drupal. From training to implementation, we bring the tools and expertise to turn AI into real value for your organization.
Get in touch
Get in touch with us and have a call with our Drupal experts. We’ll assess your current setup, explore your goals, and help you choose the smartest path forward.
Contact us: https://dropsolid.com/en/contact
Drupal core will adopt Gin admin theme to replace Claro
Drupal effectively has two default administration themes: Claro for core, and Gin for Drupal CMS. This causes difficulty for UX designers and product managers, because new features must work well with both themes.
Gin is no longer an experimental fork of Claro to experiment with new ideas. It has matured into a state-of-the-art admin theme, while Claro has fallen behind, as evident by the decision to use Gin as the admin theme for Drupal CMS. As a result, we feel it is time for Gin to become the default theme for Drupal core.
We are aspiring to have this work completed by November 2025 in order to get Gin into core for the release of 11.3 in December.
What's next?
A core-ready version of Gin will be developed outside of core in a 6.x branch of Gin. Our goal is for the Gin maintainers to collaborate with the Drupal Core Product, UX, Release, and Frontend Framework Managers to identify which issues are blockers for Gin in core.
Once the identified blockers are completed, the result would be merged into core for Drupal 11.3 by the beta deadline in November 2025. The most important step for including Gin in core is to remove its dependency on Claro, since Gin will replace Claro as the default admin theme.
Other work will include removing features that are not needed for core; simplifying the code now that Gin only needs to support the version of core that includes it; and other tasks like adding necessary test coverage to ensure a smooth transition from contrib to core.
What happens to Claro?
Claro will no longer be the default theme for new sites, but it will remain in Drupal 11 for use on existing sites. When Gin becomes the default admin theme of Drupal core, Claro will be removed from the next major version. Claro may then be available as a contributed theme to provide sites an upgrade path.
How can I get involved?
This is a big job with an ambitious timeline, so we will need many contributors to meet it. For contribution, you can get started with the two meta issues (#3530849 Gin 6.x and #3530852: Admin theme modernisation) to track this work, one for core tasks and one for Gin tasks. These will be updated and many new tasks created as the scope of work is clarified.
The Gin maintainers are also seeking sponsors for their time, which is a great way to contribute to this effort if you want to see this happen but are not able to work on tasks directly.
All those interested, please join us in the #admin-ui Drupal Slack channel for collaboration.
Gin is no longer an experimental fork of Claro to experiment with new ideas. It has matured into a state-of-the-art admin theme, while Claro has fallen behind, as evident by the decision to use Gin as the admin theme for Drupal CMS. As a result, we feel it is time for Gin to become the default theme for Drupal core.
We are aspiring to have this work completed by November 2025 in order to get Gin into core for the release of 11.3 in December.
What's next?
A core-ready version of Gin will be developed outside of core in a 6.x branch of Gin. Our goal is for the Gin maintainers to collaborate with the Drupal Core Product, UX, Release, and Frontend Framework Managers to identify which issues are blockers for Gin in core.
Once the identified blockers are completed, the result would be merged into core for Drupal 11.3 by the beta deadline in November 2025. The most important step for including Gin in core is to remove its dependency on Claro, since Gin will replace Claro as the default admin theme.
Other work will include removing features that are not needed for core; simplifying the code now that Gin only needs to support the version of core that includes it; and other tasks like adding necessary test coverage to ensure a smooth transition from contrib to core.
What happens to Claro?
Claro will no longer be the default theme for new sites, but it will remain in Drupal 11 for use on existing sites. When Gin becomes the default admin theme of Drupal core, Claro will be removed from the next major version. Claro may then be available as a contributed theme to provide sites an upgrade path.
How can I get involved?
This is a big job with an ambitious timeline, so we will need many contributors to meet it. For contribution, you can get started with the two meta issues (#3530849 Gin 6.x and #3530852: Admin theme modernisation) to track this work, one for core tasks and one for Gin tasks. These will be updated and many new tasks created as the scope of work is clarified.
The Gin maintainers are also seeking sponsors for their time, which is a great way to contribute to this effort if you want to see this happen but are not able to work on tasks directly.
All those interested, please join us in the #admin-ui Drupal Slack channel for collaboration.
Drupal 11.2.0 is now available
New in Drupal 11.2
The second feature release of Drupal 11 improves backend and frontend performance and scalability, completes the introduction of OOP support of hooks, adds JSON Schema support, includes AVIF image format capability, supports SDC variants, and more.
Extension and site installation is three to four times as fast as Drupal 11.1.0
Thanks to various optimizations to container rebuilding and the installer, installing Drupal itself or extensions is now three to four times as fast. There are similar improvements when using the user interface, but it is more apparent when using Drush. In this video, we show Drupal 11.2 installing 60 modules in 5.7 seconds while Drupal 11.1 takes four times as much to do the same:
.module files are not needed anymore!
Starting with Drupal 11.2, the last APIs that needed .module files can be implemented as object-oriented hooks too! Developers can make use of [#RemoveHook] attributes to remove hooks, [#ReOrderHook] to change hook ordering and #[Hook('preprocess')] attributes to declare object-oriented preprocess hooks. Now there is no need for a .module file if all of the hooks are on classes in the Hook namespace.
Built-in JSON Schema generation for content entities
When working with Drupal entities over an API, it is important for developer experience to have a schema for the data structure of a particular entity. This allows clients to know, for instance, what acceptable values may be sent or received for the value and format properties of a formatted text field.
Drupal core can now generate JSON Schemas for content entity types. The typed data, serialization and field APIs have been enhanced to allow field-level schemas to be generated based on their storage configuration.
All field types shipped by core now provide JSON Schemas out of the box through their default normalizers. In addition, all the core typed data plugins provide JSON Schemas as well. This means that all core fields can generate JSON Schemas for their properties out of the box. Additionally, most field types provided by contributed projects or custom modules will generate JSON Schemas automatically so long as they do not provide a custom normalizer or depend on non-core typed data plugins.
Native variant support added to Single-Directory Components
In design systems, a variant allows grouping multiple component properties into a predefined set. The variant can then be used as a shortcut to render a component. Front-end developers could previously define a variant as a prop, but this approach did not support custom titles or descriptions to convey the variant’s purpose.
Now, you can use variants as a property at the root of your component declaration:
name: Card
variants:
primary:
title: Primary
description: ...
secondary:
title: Secondary
description: ...
props: {}
slots: {}
AVIF support added with fallback to WebP
Drupal 11.2 now supports AVIF in our image toolkit. AVIF offers better compression and image quality than WebP, especially for high-resolution images and HDR content. However, not all servers support conversion to AVIF. For that reason, a fallback mechanism was added to convert to WebP when AVIF support is not available.
CSS page weight improvements
Drupal core has long supported component-based CSS organization and conditional loading that depends on page elements. Using this system, the default CSS added to every page by Drupal core has been reduced from around 7 KB to 1 KB. This will improve bandwidth requirements and page rendering times for all but the most highly customized sites running on 11.2.
Navigation improvements
The modern Navigation module now automatically enables the built-in top bar functionality as well. An "overview" link is now shown when a menu item is a container for child items, making it easier to find the right page. Numerous other blockers have also been resolved, and this experimental module is close to becoming stable in a future minor release.
Recipe dependencies are now unpacked
Drupal recipes are special Composer packages designed to bootstrap Drupal projects with necessary dependencies. When a recipe is required, a new Composer plugin "unpacks" it by moving the recipe's dependencies directly into your project's root composer.json, and removes the recipe as a project dependency. This makes it possible to update those dependencies later and to not have the recipe as an active dependency of the site anymore.
Changes to Update Status module to better support modern workflows
Update Status now checks the status of uninstalled extensions, making your site even more secure.
Updating themes and modules in the Update Status module with authorize.php was not Composer-aware. This could cause various serious problems for sites and site deployment workflows. Therefore, this legacy feature has now been removed. Projects should generally be updated on the command line with Composer. The experimental Update Manager (Automatic Updates) will also be used for this in the future.
Cache efficiency improvements
Significant improvements have been made to Drupal's render cache performance due to optimizations in placeholder processing and cache tag invalidation checks. This results in smaller cache entries with fewer cache dependencies in the dynamic page cache, leading to higher cache hit rates and reduced cache storage requirements. The reduction in cache tag lookups reduces round trips to persistent cache storage backends on every HTML response. This applies whether the cache tag backend is using database, memcache, or redis, and leads to slightly faster page rendering performance on both dynamic page cache hits and misses. There is also a significant reduction in queries per second (QPS) for high-traffic sites, which should allow caching servers to handle more traffic with lower hardware requirements.
PHPUnit 11 support added
PHPUnit 11 can now be used for testing. While the default version remains PHPUnit 10, it's possible to update to PHPUnit with the command composer update phpunit/phpunit --with-dependencies. Drupal core testing on PHP 8.4 requires PHPUnit 11 as a minimum.
Core maintainer team updates
Since Drupal 11.1, Emma Horrel and Cristina Chumillas were announced as UX Managers.
Griffyn Heels joined as a provisional Core Leadership Team Facilitator. Juraj Nemec and Drew Webber were added as general core committers, and Pierre Dureau was added as a provisional Frontend Framework Manager. Check out their announcement.
Six people stepped up to become subsystem maintainers! Nic Laflin became a maintainer of the Extension API, Lee Rowlands became a co-maintainer of the Form and Render APIs, Adam Bramley became maintainer of Node module, Jean Valverde became a co-maintainer of Single-Directory Components. Mark Conroy became the maintainer of the Stable 9 theme and Brad Jones became a co-maintainer of Serialization. Many of the improvements above are thanks to leadership from these new maintainers!
Three subsystem maintainers stepped back. We thank Claudiu Cristea, Christian Fritsch, and Daniel Wehner for their immense contributions.
Finally, there have also been changes in the mentoring coordinator team: James Shields joined, while Mauricio Dinarte, AmyJune Hineline and Tara King stepped back from the role. Many Drupal contributors are thankful to have been mentored by them!
Drupal 10.5 is also available
The next maintenance minor release of Drupal 10 has also been released. Drupal 10 will be supported until December 9, 2026, after the release of Drupal 12. Long-term support for Drupal 10 is managed with a new maintenance minor release every 6 months that receives twelve months of support. This allows the maintenance minor to adapt to evolving dependencies. It also gives more flexibility for sites to move to Drupal 11 when they are ready.
This release schedule allows sites to move from one LTS version to the next if that is the best strategy for their needs. For more information on maintenance minors, read the previous post on the new major release schedule.
Want to get involved?
If you are looking to make the leap from Drupal user to Drupal contributor, or you want to share resources with your team as part of their professional development, there are many opportunities to deepen your Drupal skill set and give back to the community. Check out the Drupal contributor guide. Join us at DrupalCon Vienna in October 2025 or DrupalCon Nara in November 2025 to attend sessions, network, and enjoy mentorship for your first contributions.
The second feature release of Drupal 11 improves backend and frontend performance and scalability, completes the introduction of OOP support of hooks, adds JSON Schema support, includes AVIF image format capability, supports SDC variants, and more.
Extension and site installation is three to four times as fast as Drupal 11.1.0
Thanks to various optimizations to container rebuilding and the installer, installing Drupal itself or extensions is now three to four times as fast. There are similar improvements when using the user interface, but it is more apparent when using Drush. In this video, we show Drupal 11.2 installing 60 modules in 5.7 seconds while Drupal 11.1 takes four times as much to do the same:
.module files are not needed anymore!
Starting with Drupal 11.2, the last APIs that needed .module files can be implemented as object-oriented hooks too! Developers can make use of [#RemoveHook] attributes to remove hooks, [#ReOrderHook] to change hook ordering and #[Hook('preprocess')] attributes to declare object-oriented preprocess hooks. Now there is no need for a .module file if all of the hooks are on classes in the Hook namespace.
Built-in JSON Schema generation for content entities
When working with Drupal entities over an API, it is important for developer experience to have a schema for the data structure of a particular entity. This allows clients to know, for instance, what acceptable values may be sent or received for the value and format properties of a formatted text field.
Drupal core can now generate JSON Schemas for content entity types. The typed data, serialization and field APIs have been enhanced to allow field-level schemas to be generated based on their storage configuration.
All field types shipped by core now provide JSON Schemas out of the box through their default normalizers. In addition, all the core typed data plugins provide JSON Schemas as well. This means that all core fields can generate JSON Schemas for their properties out of the box. Additionally, most field types provided by contributed projects or custom modules will generate JSON Schemas automatically so long as they do not provide a custom normalizer or depend on non-core typed data plugins.
Native variant support added to Single-Directory Components
In design systems, a variant allows grouping multiple component properties into a predefined set. The variant can then be used as a shortcut to render a component. Front-end developers could previously define a variant as a prop, but this approach did not support custom titles or descriptions to convey the variant’s purpose.
Now, you can use variants as a property at the root of your component declaration:
name: Card
variants:
primary:
title: Primary
description: ...
secondary:
title: Secondary
description: ...
props: {}
slots: {}
AVIF support added with fallback to WebP
Drupal 11.2 now supports AVIF in our image toolkit. AVIF offers better compression and image quality than WebP, especially for high-resolution images and HDR content. However, not all servers support conversion to AVIF. For that reason, a fallback mechanism was added to convert to WebP when AVIF support is not available.
CSS page weight improvements
Drupal core has long supported component-based CSS organization and conditional loading that depends on page elements. Using this system, the default CSS added to every page by Drupal core has been reduced from around 7 KB to 1 KB. This will improve bandwidth requirements and page rendering times for all but the most highly customized sites running on 11.2.
Navigation improvements
The modern Navigation module now automatically enables the built-in top bar functionality as well. An "overview" link is now shown when a menu item is a container for child items, making it easier to find the right page. Numerous other blockers have also been resolved, and this experimental module is close to becoming stable in a future minor release.
Recipe dependencies are now unpacked
Drupal recipes are special Composer packages designed to bootstrap Drupal projects with necessary dependencies. When a recipe is required, a new Composer plugin "unpacks" it by moving the recipe's dependencies directly into your project's root composer.json, and removes the recipe as a project dependency. This makes it possible to update those dependencies later and to not have the recipe as an active dependency of the site anymore.
Changes to Update Status module to better support modern workflows
Update Status now checks the status of uninstalled extensions, making your site even more secure.
Updating themes and modules in the Update Status module with authorize.php was not Composer-aware. This could cause various serious problems for sites and site deployment workflows. Therefore, this legacy feature has now been removed. Projects should generally be updated on the command line with Composer. The experimental Update Manager (Automatic Updates) will also be used for this in the future.
Cache efficiency improvements
Significant improvements have been made to Drupal's render cache performance due to optimizations in placeholder processing and cache tag invalidation checks. This results in smaller cache entries with fewer cache dependencies in the dynamic page cache, leading to higher cache hit rates and reduced cache storage requirements. The reduction in cache tag lookups reduces round trips to persistent cache storage backends on every HTML response. This applies whether the cache tag backend is using database, memcache, or redis, and leads to slightly faster page rendering performance on both dynamic page cache hits and misses. There is also a significant reduction in queries per second (QPS) for high-traffic sites, which should allow caching servers to handle more traffic with lower hardware requirements.
PHPUnit 11 support added
PHPUnit 11 can now be used for testing. While the default version remains PHPUnit 10, it's possible to update to PHPUnit with the command composer update phpunit/phpunit --with-dependencies. Drupal core testing on PHP 8.4 requires PHPUnit 11 as a minimum.
Core maintainer team updates
Since Drupal 11.1, Emma Horrel and Cristina Chumillas were announced as UX Managers.
Griffyn Heels joined as a provisional Core Leadership Team Facilitator. Juraj Nemec and Drew Webber were added as general core committers, and Pierre Dureau was added as a provisional Frontend Framework Manager. Check out their announcement.
Six people stepped up to become subsystem maintainers! Nic Laflin became a maintainer of the Extension API, Lee Rowlands became a co-maintainer of the Form and Render APIs, Adam Bramley became maintainer of Node module, Jean Valverde became a co-maintainer of Single-Directory Components. Mark Conroy became the maintainer of the Stable 9 theme and Brad Jones became a co-maintainer of Serialization. Many of the improvements above are thanks to leadership from these new maintainers!
Three subsystem maintainers stepped back. We thank Claudiu Cristea, Christian Fritsch, and Daniel Wehner for their immense contributions.
Finally, there have also been changes in the mentoring coordinator team: James Shields joined, while Mauricio Dinarte, AmyJune Hineline and Tara King stepped back from the role. Many Drupal contributors are thankful to have been mentored by them!
Drupal 10.5 is also available
The next maintenance minor release of Drupal 10 has also been released. Drupal 10 will be supported until December 9, 2026, after the release of Drupal 12. Long-term support for Drupal 10 is managed with a new maintenance minor release every 6 months that receives twelve months of support. This allows the maintenance minor to adapt to evolving dependencies. It also gives more flexibility for sites to move to Drupal 11 when they are ready.
This release schedule allows sites to move from one LTS version to the next if that is the best strategy for their needs. For more information on maintenance minors, read the previous post on the new major release schedule.
Want to get involved?
If you are looking to make the leap from Drupal user to Drupal contributor, or you want to share resources with your team as part of their professional development, there are many opportunities to deepen your Drupal skill set and give back to the community. Check out the Drupal contributor guide. Join us at DrupalCon Vienna in October 2025 or DrupalCon Nara in November 2025 to attend sessions, network, and enjoy mentorship for your first contributions.
Drupal 11.2.0 is now available
New in Drupal 11.2
The second feature release of Drupal 11 improves backend and frontend performance and scalability, completes the introduction of OOP support of hooks, adds JSON Schema support, includes AVIF image format capability, supports SDC variants, and more.
Extension and site installation is three to four times as fast as Drupal 11.1.0
Thanks to various optimizations to container rebuilding and the installer, installing Drupal itself or extensions is now three to four times as fast. There are similar improvements when using the user interface, but it is more apparent when using Drush. In this video, we show Drupal 11.2 installing 60 modules in 5.7 seconds while Drupal 11.1 takes four times as much to do the same:
.module files are not needed anymore!
Starting with Drupal 11.2, the last APIs that needed .module files can be implemented as object-oriented hooks too! Developers can make use of [#RemoveHook] attributes to remove hooks, [#ReOrderHook] to change hook ordering and #[Hook('preprocess')] attributes to declare object-oriented preprocess hooks. Now there is no need for a .module file if all of the hooks are on classes in the Hook namespace.
Built-in JSON Schema generation for content entities
When working with Drupal entities over an API, it is important for developer experience to have a schema for the data structure of a particular entity. This allows clients to know, for instance, what acceptable values may be sent or received for the value and format properties of a formatted text field.
Drupal core can now generate JSON Schemas for content entity types. The typed data, serialization and field APIs have been enhanced to allow field-level schemas to be generated based on their storage configuration.
All field types shipped by core now provide JSON Schemas out of the box through their default normalizers. In addition, all the core typed data plugins provide JSON Schemas as well. This means that all core fields can generate JSON Schemas for their properties out of the box. Additionally, most field types provided by contributed projects or custom modules will generate JSON Schemas automatically so long as they do not provide a custom normalizer or depend on non-core typed data plugins.
Native variant support added to Single-Directory Components
In design systems, a variant allows grouping multiple component properties into a predefined set. The variant can then be used as a shortcut to render a component. Front-end developers could previously define a variant as a prop, but this approach did not support custom titles or descriptions to convey the variant’s purpose.
Now, you can use variants as a property at the root of your component declaration:
name: Card
variants:
primary:
title: Primary
description: ...
secondary:
title: Secondary
description: ...
props: {}
slots: {}
AVIF support added with fallback to WebP
Drupal 11.2 now supports AVIF in our image toolkit. AVIF offers better compression and image quality than WebP, especially for high-resolution images and HDR content. However, not all servers support conversion to AVIF. For that reason, a fallback mechanism was added to convert to WebP when AVIF support is not available.
CSS page weight improvements
Drupal core has long supported component-based CSS organization and conditional loading that depends on page elements. Using this system, the default CSS added to every page by Drupal core has been reduced from around 7 KB to 1 KB. This will improve bandwidth requirements and page rendering times for all but the most highly customized sites running on 11.2.
Navigation improvements
The modern Navigation module now automatically enables the built-in top bar functionality as well. An "overview" link is now shown when a menu item is a container for child items, making it easier to find the right page. Numerous other blockers have also been resolved, and this experimental module is close to becoming stable in a future minor release.
Recipe dependencies are now unpacked
Drupal recipes are special Composer packages designed to bootstrap Drupal projects with necessary dependencies. When a recipe is required, a new Composer plugin "unpacks" it by moving the recipe's dependencies directly into your project's root composer.json, and removes the recipe as a project dependency. This makes it possible to update those dependencies later and to not have the recipe as an active dependency of the site anymore.
Changes to Update Status module to better support modern workflows
Update Status now checks the status of uninstalled extensions, making your site even more secure.
Updating themes and modules in the Update Status module with authorize.php was not Composer-aware. This could cause various serious problems for sites and site deployment workflows. Therefore, this legacy feature has now been removed. Projects should generally be updated on the command line with Composer. The experimental Update Manager (Automatic Updates) will also be used for this in the future.
Cache efficiency improvements
Significant improvements have been made to Drupal's render cache performance due to optimizations in placeholder processing and cache tag invalidation checks. This results in smaller cache entries with fewer cache dependencies in the dynamic page cache, leading to higher cache hit rates and reduced cache storage requirements. The reduction in cache tag lookups reduces round trips to persistent cache storage backends on every HTML response. This applies whether the cache tag backend is using database, memcache, or redis, and leads to slightly faster page rendering performance on both dynamic page cache hits and misses. There is also a significant reduction in queries per second (QPS) for high-traffic sites, which should allow caching servers to handle more traffic with lower hardware requirements.
PHPUnit 11 support added
PHPUnit 11 can now be used for testing. While the default version remains PHPUnit 10, it's possible to update to PHPUnit with the command composer update phpunit/phpunit --with-dependencies. Drupal core testing on PHP 8.4 requires PHPUnit 11 as a minimum.
Core maintainer team updates
Since Drupal 11.1, Emma Horrel and Cristina Chumillas were announced as UX Managers.
Griffyn Heels joined as a provisional Core Leadership Team Facilitator. Juraj Nemec and Drew Webber were added as general core committers, and Pierre Dureau was added as a provisional Frontend Framework Manager. Check out their announcement.
Six people stepped up to become subsystem maintainers! Nic Laflin became a maintainer of the Extension API, Lee Rowlands became a co-maintainer of the Form and Render APIs, Adam Bramley became maintainer of Node module, Jean Valverde became a co-maintainer of Single-Directory Components. Mark Conroy became the maintainer of the Stable 9 theme and Brad Jones became a co-maintainer of Serialization. Many of the improvements above are thanks to leadership from these new maintainers!
Three subsystem maintainers stepped back. We thank Claudiu Cristea, Christian Fritsch, and Daniel Wehner for their immense contributions.
Finally, there have also been changes in the mentoring coordinator team: James Shields joined, while Mauricio Dinarte, AmyJune Hineline and Tara King stepped back from the role. Many Drupal contributors are thankful to have been mentored by them!
Drupal 10.5 is also available
The next maintenance minor release of Drupal 10 has also been released. Drupal 10 will be supported until December 9, 2026, after the release of Drupal 12. Long-term support for Drupal 10 is managed with a new maintenance minor release every 6 months that receives twelve months of support. This allows the maintenance minor to adapt to evolving dependencies. It also gives more flexibility for sites to move to Drupal 11 when they are ready.
This release schedule allows sites to move from one LTS version to the next if that is the best strategy for their needs. For more information on maintenance minors, read the previous post on the new major release schedule.
Want to get involved?
If you are looking to make the leap from Drupal user to Drupal contributor, or you want to share resources with your team as part of their professional development, there are many opportunities to deepen your Drupal skill set and give back to the community. Check out the Drupal contributor guide. Join us at DrupalCon Vienna in October 2025 or DrupalCon Nara in November 2025 to attend sessions, network, and enjoy mentorship for your first contributions.
The second feature release of Drupal 11 improves backend and frontend performance and scalability, completes the introduction of OOP support of hooks, adds JSON Schema support, includes AVIF image format capability, supports SDC variants, and more.
Extension and site installation is three to four times as fast as Drupal 11.1.0
Thanks to various optimizations to container rebuilding and the installer, installing Drupal itself or extensions is now three to four times as fast. There are similar improvements when using the user interface, but it is more apparent when using Drush. In this video, we show Drupal 11.2 installing 60 modules in 5.7 seconds while Drupal 11.1 takes four times as much to do the same:
.module files are not needed anymore!
Starting with Drupal 11.2, the last APIs that needed .module files can be implemented as object-oriented hooks too! Developers can make use of [#RemoveHook] attributes to remove hooks, [#ReOrderHook] to change hook ordering and #[Hook('preprocess')] attributes to declare object-oriented preprocess hooks. Now there is no need for a .module file if all of the hooks are on classes in the Hook namespace.
Built-in JSON Schema generation for content entities
When working with Drupal entities over an API, it is important for developer experience to have a schema for the data structure of a particular entity. This allows clients to know, for instance, what acceptable values may be sent or received for the value and format properties of a formatted text field.
Drupal core can now generate JSON Schemas for content entity types. The typed data, serialization and field APIs have been enhanced to allow field-level schemas to be generated based on their storage configuration.
All field types shipped by core now provide JSON Schemas out of the box through their default normalizers. In addition, all the core typed data plugins provide JSON Schemas as well. This means that all core fields can generate JSON Schemas for their properties out of the box. Additionally, most field types provided by contributed projects or custom modules will generate JSON Schemas automatically so long as they do not provide a custom normalizer or depend on non-core typed data plugins.
Native variant support added to Single-Directory Components
In design systems, a variant allows grouping multiple component properties into a predefined set. The variant can then be used as a shortcut to render a component. Front-end developers could previously define a variant as a prop, but this approach did not support custom titles or descriptions to convey the variant’s purpose.
Now, you can use variants as a property at the root of your component declaration:
name: Card
variants:
primary:
title: Primary
description: ...
secondary:
title: Secondary
description: ...
props: {}
slots: {}
AVIF support added with fallback to WebP
Drupal 11.2 now supports AVIF in our image toolkit. AVIF offers better compression and image quality than WebP, especially for high-resolution images and HDR content. However, not all servers support conversion to AVIF. For that reason, a fallback mechanism was added to convert to WebP when AVIF support is not available.
CSS page weight improvements
Drupal core has long supported component-based CSS organization and conditional loading that depends on page elements. Using this system, the default CSS added to every page by Drupal core has been reduced from around 7 KB to 1 KB. This will improve bandwidth requirements and page rendering times for all but the most highly customized sites running on 11.2.
Navigation improvements
The modern Navigation module now automatically enables the built-in top bar functionality as well. An "overview" link is now shown when a menu item is a container for child items, making it easier to find the right page. Numerous other blockers have also been resolved, and this experimental module is close to becoming stable in a future minor release.
Recipe dependencies are now unpacked
Drupal recipes are special Composer packages designed to bootstrap Drupal projects with necessary dependencies. When a recipe is required, a new Composer plugin "unpacks" it by moving the recipe's dependencies directly into your project's root composer.json, and removes the recipe as a project dependency. This makes it possible to update those dependencies later and to not have the recipe as an active dependency of the site anymore.
Changes to Update Status module to better support modern workflows
Update Status now checks the status of uninstalled extensions, making your site even more secure.
Updating themes and modules in the Update Status module with authorize.php was not Composer-aware. This could cause various serious problems for sites and site deployment workflows. Therefore, this legacy feature has now been removed. Projects should generally be updated on the command line with Composer. The experimental Update Manager (Automatic Updates) will also be used for this in the future.
Cache efficiency improvements
Significant improvements have been made to Drupal's render cache performance due to optimizations in placeholder processing and cache tag invalidation checks. This results in smaller cache entries with fewer cache dependencies in the dynamic page cache, leading to higher cache hit rates and reduced cache storage requirements. The reduction in cache tag lookups reduces round trips to persistent cache storage backends on every HTML response. This applies whether the cache tag backend is using database, memcache, or redis, and leads to slightly faster page rendering performance on both dynamic page cache hits and misses. There is also a significant reduction in queries per second (QPS) for high-traffic sites, which should allow caching servers to handle more traffic with lower hardware requirements.
PHPUnit 11 support added
PHPUnit 11 can now be used for testing. While the default version remains PHPUnit 10, it's possible to update to PHPUnit with the command composer update phpunit/phpunit --with-dependencies. Drupal core testing on PHP 8.4 requires PHPUnit 11 as a minimum.
Core maintainer team updates
Since Drupal 11.1, Emma Horrel and Cristina Chumillas were announced as UX Managers.
Griffyn Heels joined as a provisional Core Leadership Team Facilitator. Juraj Nemec and Drew Webber were added as general core committers, and Pierre Dureau was added as a provisional Frontend Framework Manager. Check out their announcement.
Six people stepped up to become subsystem maintainers! Nic Laflin became a maintainer of the Extension API, Lee Rowlands became a co-maintainer of the Form and Render APIs, Adam Bramley became maintainer of Node module, Jean Valverde became a co-maintainer of Single-Directory Components. Mark Conroy became the maintainer of the Stable 9 theme and Brad Jones became a co-maintainer of Serialization. Many of the improvements above are thanks to leadership from these new maintainers!
Three subsystem maintainers stepped back. We thank Claudiu Cristea, Christian Fritsch, and Daniel Wehner for their immense contributions.
Finally, there have also been changes in the mentoring coordinator team: James Shields joined, while Mauricio Dinarte, AmyJune Hineline and Tara King stepped back from the role. Many Drupal contributors are thankful to have been mentored by them!
Drupal 10.5 is also available
The next maintenance minor release of Drupal 10 has also been released. Drupal 10 will be supported until December 9, 2026, after the release of Drupal 12. Long-term support for Drupal 10 is managed with a new maintenance minor release every 6 months that receives twelve months of support. This allows the maintenance minor to adapt to evolving dependencies. It also gives more flexibility for sites to move to Drupal 11 when they are ready.
This release schedule allows sites to move from one LTS version to the next if that is the best strategy for their needs. For more information on maintenance minors, read the previous post on the new major release schedule.
Want to get involved?
If you are looking to make the leap from Drupal user to Drupal contributor, or you want to share resources with your team as part of their professional development, there are many opportunities to deepen your Drupal skill set and give back to the community. Check out the Drupal contributor guide. Join us at DrupalCon Vienna in October 2025 or DrupalCon Nara in November 2025 to attend sessions, network, and enjoy mentorship for your first contributions.
Drupal AI 1.1.0 is out and brings major new features!
A huge joint stable release of AI was made yesterday, where 10 modules were updated to 1.1.0. This is a major milestone in the Drupal AI brings a host of improvements and significant new features.
Some technical facts of the AI release:
105 issues fixed on AI Core, 75 issues fixed on AI Agents and roughly 25 issues on providers.
90 unique contributors on AI Core
244 files changed, 6500 lines added, 15044 lines removed on AI Core.
The most important update is function calling and a new agent framework, but here is a list of some other new features:
Custom Operation Types
Drush command to run AI
Make the chatbot tell it what its doing, while its doing it
Make it possible to add autocomplete fields to AI Automator Chains on CKEditor
AI Content Suggestion can be based on the rendered HTML of the entity
Normalized Structured Response
Any many more
Some things directly connected to it:
Drupal CMS AI agents have been updated and are now 90% effective up from 80%.
A new test framework has been created so can see their effectiveness more clearly and non developers can create new tests.
Improvements to AI search making use of function calling means they will more accurately search when you ask it to.
Over 1000 people in the #ai slack
An officially funded AI position and a Strategic initiative with multiple companies to make this sustainable
4600 installs of AI up from 3000 at Atlanta
Full details of Drupal AI 1.1.0
🚀 Major New Feature: Agentic Framework
The by far largest feature is the new Agentic framework where anyone can build agents without writing a single line of code. They are stored as configurations, meaning that you can build once, export and ship anywhere. And you can trigger them from anywhere you want - Chatbot, CLI, widgets, via an API etc.
Because Drupal is such a flexible and stable CMF, it will be the perfect agent runner. It adheres automatically to your contents permissions, files etc. while also keeping humans in the loop.
With the announcement of the new AI Initiative the future looks bright for Drupal and AI, the announcement is here if you haven't seen it.
🔧 Standards-Based Tooling
We’ve implemented the tooling in a MCP-standardized way, which opens the door for seamless integration with external tools—and makes it easier to share and reuse agents and tools across systems and languages.
🧠 Visual Tools for Everyone
Outside of this we have also added a visual AI Agents Testing Tool where you can setup complex scenarios and retest them over and over, without having to be a developer. An advanced agent tracing tool is also in the pipeline!
And in the 1.1.0 release we also have the possibility to setup the agents via the modeler api and BMPN.io in a graphical way thanks to Jürgen Haas! He also has a visual way of building tools on the way.
The hope is that everything we build, should be possible to use directly from the browser!
🙌 Thank You
I thought I would thank a list of people that have contributed to this, but I checked the unique contributors via git and got 90 people. So I will not try to list everyone, because I will surely forget someone - but special thanks to James Abrahams and FreelyGive Ltd for giving me the opportunity to work with this full time (and more :) )!
It will be really exciting what kind of agents people will build, we have already tried everything from agents that checks configuration diffs for you, to agents that builds components from images. Hopefully your imagination, and not the framework, will be the limit ;)
We have a MR that can be tested for using this within Drupal CMS as well.
For anyone interested in the new agent framework I did a presentation on it at Drupal Days Leuven and also have a longer developers preview. More videos and documentation to follow.
Some technical facts of the AI release:
105 issues fixed on AI Core, 75 issues fixed on AI Agents and roughly 25 issues on providers.
90 unique contributors on AI Core
244 files changed, 6500 lines added, 15044 lines removed on AI Core.
The most important update is function calling and a new agent framework, but here is a list of some other new features:
Custom Operation Types
Drush command to run AI
Make the chatbot tell it what its doing, while its doing it
Make it possible to add autocomplete fields to AI Automator Chains on CKEditor
AI Content Suggestion can be based on the rendered HTML of the entity
Normalized Structured Response
Any many more
Some things directly connected to it:
Drupal CMS AI agents have been updated and are now 90% effective up from 80%.
A new test framework has been created so can see their effectiveness more clearly and non developers can create new tests.
Improvements to AI search making use of function calling means they will more accurately search when you ask it to.
Over 1000 people in the #ai slack
An officially funded AI position and a Strategic initiative with multiple companies to make this sustainable
4600 installs of AI up from 3000 at Atlanta
Full details of Drupal AI 1.1.0
🚀 Major New Feature: Agentic Framework
The by far largest feature is the new Agentic framework where anyone can build agents without writing a single line of code. They are stored as configurations, meaning that you can build once, export and ship anywhere. And you can trigger them from anywhere you want - Chatbot, CLI, widgets, via an API etc.
Because Drupal is such a flexible and stable CMF, it will be the perfect agent runner. It adheres automatically to your contents permissions, files etc. while also keeping humans in the loop.
With the announcement of the new AI Initiative the future looks bright for Drupal and AI, the announcement is here if you haven't seen it.
🔧 Standards-Based Tooling
We’ve implemented the tooling in a MCP-standardized way, which opens the door for seamless integration with external tools—and makes it easier to share and reuse agents and tools across systems and languages.
🧠 Visual Tools for Everyone
Outside of this we have also added a visual AI Agents Testing Tool where you can setup complex scenarios and retest them over and over, without having to be a developer. An advanced agent tracing tool is also in the pipeline!
And in the 1.1.0 release we also have the possibility to setup the agents via the modeler api and BMPN.io in a graphical way thanks to Jürgen Haas! He also has a visual way of building tools on the way.
The hope is that everything we build, should be possible to use directly from the browser!
🙌 Thank You
I thought I would thank a list of people that have contributed to this, but I checked the unique contributors via git and got 90 people. So I will not try to list everyone, because I will surely forget someone - but special thanks to James Abrahams and FreelyGive Ltd for giving me the opportunity to work with this full time (and more :) )!
It will be really exciting what kind of agents people will build, we have already tried everything from agents that checks configuration diffs for you, to agents that builds components from images. Hopefully your imagination, and not the framework, will be the limit ;)
We have a MR that can be tested for using this within Drupal CMS as well.
For anyone interested in the new agent framework I did a presentation on it at Drupal Days Leuven and also have a longer developers preview. More videos and documentation to follow.
Accelerating AI innovation in Drupal
This blog has been re-posted and edited with permission from Dries Buytaert's blog.
Drupal launches its AI Initiative with more than $100,000 in funding and a dedicated team to build AI tools for website creation and content management.
Imagine a marketer opening Drupal and with a clear goal in mind: launch a campaign for an upcoming event.
They start by uploading a brand kit to Drupal CMS: logos, fonts, and color palette. They define the campaign's audience as mid-sized business owners interested in digital transformation. Then they create a creative guide that outlines the event's goals, key messages, and tone.
With this in place, AI agents within Drupal step in to assist. Drawing from existing content and media, the agents help generate landing pages, each optimized for a specific audience segment. They suggest headlines, refine copy based on the creative guide, create components based on the brand kit, insert a sign-up form, and assemble everything into cohesive, production-ready pages.
Using Drupal's built-in support for the Model Context Protocol (MCP), the AI agents connect to analytics tools and monitor performance. If a page is not converting well, the system makes overnight updates. It might adjust layout, improve clarity, or refine the calls to action.
Every change is tracked. The marketer can review, approve, revert, or adjust anything. They stay in control, even as the system takes on more of the routine work.
Why it matters
AI is changing how websites are built and managed faster than most people expected. The digital experience space is shifting from manual workflows to outcome-driven orchestration. Instead of building everything from scratch, users will set goals, and AI will help deliver results.
This future is not about replacing people. It is about empowering them. It is about freeing up time for creative and strategic work while AI handles the rest. AI will take care of routine tasks, suggest improvements, and respond to real-time feedback. People will remain in control, but supported by powerful new tools that make their work easier and faster.
The path forward won't be perfect. Change is never easy, and there are still many lessons to learn, but standing still isn't an option. If we want AI to head in the right direction, we have to help steer it. We are excited to move fast, but just as committed to doing it thoughtfully and with purpose.
The question is not whether AI will change how we build websites, but how we as a community will shape that change.
A coordinated push forward
Drupal already has a head start in AI. At DrupalCon Barcelona 2024, I showed how Drupal's AI tools help a site creator market wine tours. Since then, we have seen a growing ecosystem of AI modules, active integrations, and a vibrant community pushing boundaries. Today, about 1,000 people are sharing ideas and collaborating in the #ai channel on Drupal Slack.
At DrupalCon Atlanta in March 2025, I shared our latest AI progress. We also brought together key contributors working on AI in Drupal. Our goal was simple: get organized and accelerate progress. After the event, the group committed to align on a shared vision and move forward together.
Since then, this team has been meeting regularly, almost every day. I've been working with the team to help guide the direction. With a lot of hard work behind us, I'm excited to introduce the Drupal AI Initiative.
The Drupal AI Initiative builds on the momentum in our community by bringing structure and shared direction to the work already in progress. By aligning around a common strategy, we can accelerate innovation.
What we're launching today
The Drupal AI Initiative is closely aligned with the broader Drupal CMS strategy, particularly in its focus on making site building both faster and easier. At the same time, this work is not limited to Drupal CMS. It is also intended to benefit people building custom solutions on Drupal Core, as well as those working with alternative distributions of Drupal.
To support this initiative, we are announcing:
A clear strategy to guide Drupal's AI vision and priorities (PDF mirror).
A Drupal AI leadership team to drive product direction, fundraising, and collaboration across work tracks.
A funded delivery team focused on execution, with the equivalent of several full-time roles already committed, including technical leads, UX and project managers, and release coordination.
Active work tracks covering areas like AI Core, AI Products, AI Marketing, and AI UX.
USD $100,000 in operational funding, contributed by the initiative's founding companies.
For more details, read the full announcement on the Drupal AI Initiative page on Drupal.org.
Founding members and early support
Some of the founding members of the Drupal AI initiative during our launch call on Google Hangouts.
Over the past few months, we've invested hundreds of hours shaping our AI strategy, defining structure, and taking first steps.
I want to thank the founding members of the Drupal AI Initiative. These individuals and organizations played a key role in getting things off the ground. The list is ordered alphabetically by last name to recognize all contributors equally:
Jamie Abrahams (FreelyGive) – Innovation and AI architecture
Baddý Breidert (1xINTERNET) – Governance, funding, and coordination
Christoph Breidert (1xINTERNET) – Product direction and roadmap
Dries Buytaert (Acquia / Drupal) – Strategic oversight and direction
Dominique De Cooman (Dropsolid) – Fundraising and business alignment
Marcus Johansson (FreelyGive) – Technical leadership
Paul Johnson (1xINTERNET) – Marketing and outreach
Kristen Pol (Salsa Digital) – Cross-team alignment and contributor engagement
Lauri Timmanee (Acquia) – Experience Builder AI integration
Frederik Wouters (Dropsolid) – Communications and outreach
These individuals, along with the companies supporting them, have already contributed significant time, energy, and funding. I am grateful for their early commitment.
I also want to thank the staff at the Drupal Association and the Drupal CMS leadership team for their support and collaboration.
What comes next
I'm glad the Drupal AI Initiative is now underway. The Drupal AI strategy is published, the structure is in place, and multiple work tracks are open and moving forward. We'll share more details and updates in the coming weeks.
With every large initiative, we are evolving how we organize, align, and collaborate. The Drupal AI Initiative builds on that progress. As part of that, we are also exploring more ways to recognize and reward meaningful contributions.
We are creating ways for more of you to get involved with Drupal AI. Whether you are a developer, designer, strategist, or sponsor, there is a place for you in this work. If you're part of an agency, we encourage you to step forward and become a Maker. The more agencies that contribute, the more momentum we build.
Update: In addition to the initiative's founding members, Amazee.io already stepped forward with another commitment of USD $20,000 and one full-time contributor. Thank you! This brings the total operating budget to USD $120,000. Please consider joining as well.
AI is changing how websites and digital experiences are built. This is our moment to be part of the change and help define what comes next.
Join us in the #ai-initiative channel on Drupal Slack to get started.
Drupal launches its AI Initiative with more than $100,000 in funding and a dedicated team to build AI tools for website creation and content management.
Imagine a marketer opening Drupal and with a clear goal in mind: launch a campaign for an upcoming event.
They start by uploading a brand kit to Drupal CMS: logos, fonts, and color palette. They define the campaign's audience as mid-sized business owners interested in digital transformation. Then they create a creative guide that outlines the event's goals, key messages, and tone.
With this in place, AI agents within Drupal step in to assist. Drawing from existing content and media, the agents help generate landing pages, each optimized for a specific audience segment. They suggest headlines, refine copy based on the creative guide, create components based on the brand kit, insert a sign-up form, and assemble everything into cohesive, production-ready pages.
Using Drupal's built-in support for the Model Context Protocol (MCP), the AI agents connect to analytics tools and monitor performance. If a page is not converting well, the system makes overnight updates. It might adjust layout, improve clarity, or refine the calls to action.
Every change is tracked. The marketer can review, approve, revert, or adjust anything. They stay in control, even as the system takes on more of the routine work.
Why it matters
AI is changing how websites are built and managed faster than most people expected. The digital experience space is shifting from manual workflows to outcome-driven orchestration. Instead of building everything from scratch, users will set goals, and AI will help deliver results.
This future is not about replacing people. It is about empowering them. It is about freeing up time for creative and strategic work while AI handles the rest. AI will take care of routine tasks, suggest improvements, and respond to real-time feedback. People will remain in control, but supported by powerful new tools that make their work easier and faster.
The path forward won't be perfect. Change is never easy, and there are still many lessons to learn, but standing still isn't an option. If we want AI to head in the right direction, we have to help steer it. We are excited to move fast, but just as committed to doing it thoughtfully and with purpose.
The question is not whether AI will change how we build websites, but how we as a community will shape that change.
A coordinated push forward
Drupal already has a head start in AI. At DrupalCon Barcelona 2024, I showed how Drupal's AI tools help a site creator market wine tours. Since then, we have seen a growing ecosystem of AI modules, active integrations, and a vibrant community pushing boundaries. Today, about 1,000 people are sharing ideas and collaborating in the #ai channel on Drupal Slack.
At DrupalCon Atlanta in March 2025, I shared our latest AI progress. We also brought together key contributors working on AI in Drupal. Our goal was simple: get organized and accelerate progress. After the event, the group committed to align on a shared vision and move forward together.
Since then, this team has been meeting regularly, almost every day. I've been working with the team to help guide the direction. With a lot of hard work behind us, I'm excited to introduce the Drupal AI Initiative.
The Drupal AI Initiative builds on the momentum in our community by bringing structure and shared direction to the work already in progress. By aligning around a common strategy, we can accelerate innovation.
What we're launching today
The Drupal AI Initiative is closely aligned with the broader Drupal CMS strategy, particularly in its focus on making site building both faster and easier. At the same time, this work is not limited to Drupal CMS. It is also intended to benefit people building custom solutions on Drupal Core, as well as those working with alternative distributions of Drupal.
To support this initiative, we are announcing:
A clear strategy to guide Drupal's AI vision and priorities (PDF mirror).
A Drupal AI leadership team to drive product direction, fundraising, and collaboration across work tracks.
A funded delivery team focused on execution, with the equivalent of several full-time roles already committed, including technical leads, UX and project managers, and release coordination.
Active work tracks covering areas like AI Core, AI Products, AI Marketing, and AI UX.
USD $100,000 in operational funding, contributed by the initiative's founding companies.
For more details, read the full announcement on the Drupal AI Initiative page on Drupal.org.
Founding members and early support
Some of the founding members of the Drupal AI initiative during our launch call on Google Hangouts.
Over the past few months, we've invested hundreds of hours shaping our AI strategy, defining structure, and taking first steps.
I want to thank the founding members of the Drupal AI Initiative. These individuals and organizations played a key role in getting things off the ground. The list is ordered alphabetically by last name to recognize all contributors equally:
Jamie Abrahams (FreelyGive) – Innovation and AI architecture
Baddý Breidert (1xINTERNET) – Governance, funding, and coordination
Christoph Breidert (1xINTERNET) – Product direction and roadmap
Dries Buytaert (Acquia / Drupal) – Strategic oversight and direction
Dominique De Cooman (Dropsolid) – Fundraising and business alignment
Marcus Johansson (FreelyGive) – Technical leadership
Paul Johnson (1xINTERNET) – Marketing and outreach
Kristen Pol (Salsa Digital) – Cross-team alignment and contributor engagement
Lauri Timmanee (Acquia) – Experience Builder AI integration
Frederik Wouters (Dropsolid) – Communications and outreach
These individuals, along with the companies supporting them, have already contributed significant time, energy, and funding. I am grateful for their early commitment.
I also want to thank the staff at the Drupal Association and the Drupal CMS leadership team for their support and collaboration.
What comes next
I'm glad the Drupal AI Initiative is now underway. The Drupal AI strategy is published, the structure is in place, and multiple work tracks are open and moving forward. We'll share more details and updates in the coming weeks.
With every large initiative, we are evolving how we organize, align, and collaborate. The Drupal AI Initiative builds on that progress. As part of that, we are also exploring more ways to recognize and reward meaningful contributions.
We are creating ways for more of you to get involved with Drupal AI. Whether you are a developer, designer, strategist, or sponsor, there is a place for you in this work. If you're part of an agency, we encourage you to step forward and become a Maker. The more agencies that contribute, the more momentum we build.
Update: In addition to the initiative's founding members, Amazee.io already stepped forward with another commitment of USD $20,000 and one full-time contributor. Thank you! This brings the total operating budget to USD $120,000. Please consider joining as well.
AI is changing how websites and digital experiences are built. This is our moment to be part of the change and help define what comes next.
Join us in the #ai-initiative channel on Drupal Slack to get started.
June Drupal for Nonprofits Chat
Join us THURSDAY, June 12 at 1pm ET / 10am PT, for our call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)
We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google doc: https://nten.org/drupal/notes!
All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.
This free call is sponsored by NTEN.org and open to everyone.
Please note that, since the meeting was moved a week early due to the Juneteenth holiday, the Zoom link for this month's call is different. Please use the following link for June’s call:
Join the call: https://us02web.zoom.us/j/87657453970?pwd=naknkSONquhpyIAIR5zLaHcroNbQvi.1
Meeting ID: 876 5745 3970
Passcode: 507410
Follow along on Google Docs: https://nten.org/drupal/notes
View notes of previous months' calls.
We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google doc: https://nten.org/drupal/notes!
All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.
This free call is sponsored by NTEN.org and open to everyone.
Please note that, since the meeting was moved a week early due to the Juneteenth holiday, the Zoom link for this month's call is different. Please use the following link for June’s call:
Join the call: https://us02web.zoom.us/j/87657453970?pwd=naknkSONquhpyIAIR5zLaHcroNbQvi.1
Meeting ID: 876 5745 3970
Passcode: 507410
Follow along on Google Docs: https://nten.org/drupal/notes
View notes of previous months' calls.
Voices of Pride: A Reflection from Fei Lauren
This Pride Month, the Drupal Association invited community members to share their voice, story, and perspective through a short questionnaire, an open-hearted call to celebrate who we are and where we belong.
In a time when many in the queer community may not always feel seen or safe, we want to reaffirm that the Drupal Association is a space rooted in inclusion, care, and visibility. Our goal is to spotlight the strength, joy, and diversity within the LGBTQ+ community around the world. Through shared stories like the one below, we hope to reflect the beauty of our global community and remind each other: you belong here.
This is a space where all identities are respected, celebrated, and uplifted, not just in June, but always. As stated in the Open Web Manifesto, the open web thrives on inclusion: everyone in the world, regardless of background, identity, wealth, or status, has a home on the open web.
Today, we’re honored to share reflections from Fei Lauren, an inspiring human, community-elected at-large board member and a Drupal Diversity & Inclusion initiative lead. Their story explores moments of vulnerability, history, solidarity, and global connection, reminding us of the power in simply being seen.
How is Pride celebrated in your city or country?
West Coast Canada is known as one of the best places in the world to live for the LGBTQIA+ community. But it’s a very common practice here to include ‘2S’ before the other letters. 2S stands for Two-Spirit, and it goes first to acknowledge and honor that Indigenous Peoples were here first.
Otherwise, Pride celebrations in many communities are very family-oriented. Face painting is popular, and I’ve also seen things like bouncy castles.
Can you share a moment when inclusion really stood out to you, a personal story or memory?
I am genderqueer, and when I was first exploring neutral pronouns, the idea of putting pronouns in our Slack profiles came up at work. I didn’t realize it at first, but one of the managers I really liked and respected also used they/them pronouns.
We talked about it privately, and then they added their pronouns just before I did. I’ll never forget the anxiety I felt, followed by an incredible sense of relief that I wasn’t alone. I always try to be visible now. Sometimes, it just takes one person to shift that sense of vulnerability and make opening up feel safer.
What’s your favorite Pride-related fact, tradition, or symbol?
I recently learned that until the AIDS epidemic, the commonly used acronym was GLBT. Many medical professionals refused to treat patients who were HIV-positive, but the lesbian community stepped up as nurses and caregivers to provide support.
Changing the order of letters in the acronym, and the many variations used since, is done to honor this act of care and solidarity.
Is there a queer voice, an author, creator, or activist who has inspired or supported you?
I love Ivan Coyote. They have a book of letters from fans and their responses. I don’t cry easily, but some of the letters are so raw it’s impossible not to.
Pride celebrations here can sometimes feel like we’ve lost touch with our history and the ongoing struggle for respect, safety, and equality.
It feels important and powerful to tell those stories and make sure we don’t lose sight of how much work there is still to do in this world.
What’s one thing you love about the queer community you’re part of (in or outside Drupal)?
In Drupal, I love that the community is so global. I have learned a lot about what’s happening around the world. It’s easy to only see your own community and the struggles you and your friends face, the violence and heartbreak right in front of you.
But I love getting to celebrate wins and hold space for people globally. I’ve learned so much from the Drupal community. It has changed my relationship with queer activism and reminded me what I have to be grateful for. It also makes me feel like we really aren’t alone, and that gives me an incredible amount of hope.
Thank you, Fei, for your vulnerability, care, and presence in Drupal community. Your voice reminds us why representation matters and how simply showing up as yourself can make space for others to feel safe, seen, and supported.
To LGBTQ+ and queer members of our community, and to everyone reading, if you feel inspired to share your story this Pride Month, we welcome you with open arms. Every contribution helps build a more inclusive and loving web, one story at a time.
Want to share your own story? Submit your response here.
We also invite you to get involved with the Drupal Diversity & Inclusion (DD&I) initiative. Join the #diversity-inclusion channel on Drupal Slack and say hello! Learn more at drupaldiversity.com/get-involved.
In a time when many in the queer community may not always feel seen or safe, we want to reaffirm that the Drupal Association is a space rooted in inclusion, care, and visibility. Our goal is to spotlight the strength, joy, and diversity within the LGBTQ+ community around the world. Through shared stories like the one below, we hope to reflect the beauty of our global community and remind each other: you belong here.
This is a space where all identities are respected, celebrated, and uplifted, not just in June, but always. As stated in the Open Web Manifesto, the open web thrives on inclusion: everyone in the world, regardless of background, identity, wealth, or status, has a home on the open web.
Today, we’re honored to share reflections from Fei Lauren, an inspiring human, community-elected at-large board member and a Drupal Diversity & Inclusion initiative lead. Their story explores moments of vulnerability, history, solidarity, and global connection, reminding us of the power in simply being seen.
How is Pride celebrated in your city or country?
West Coast Canada is known as one of the best places in the world to live for the LGBTQIA+ community. But it’s a very common practice here to include ‘2S’ before the other letters. 2S stands for Two-Spirit, and it goes first to acknowledge and honor that Indigenous Peoples were here first.
Otherwise, Pride celebrations in many communities are very family-oriented. Face painting is popular, and I’ve also seen things like bouncy castles.
Can you share a moment when inclusion really stood out to you, a personal story or memory?
I am genderqueer, and when I was first exploring neutral pronouns, the idea of putting pronouns in our Slack profiles came up at work. I didn’t realize it at first, but one of the managers I really liked and respected also used they/them pronouns.
We talked about it privately, and then they added their pronouns just before I did. I’ll never forget the anxiety I felt, followed by an incredible sense of relief that I wasn’t alone. I always try to be visible now. Sometimes, it just takes one person to shift that sense of vulnerability and make opening up feel safer.
What’s your favorite Pride-related fact, tradition, or symbol?
I recently learned that until the AIDS epidemic, the commonly used acronym was GLBT. Many medical professionals refused to treat patients who were HIV-positive, but the lesbian community stepped up as nurses and caregivers to provide support.
Changing the order of letters in the acronym, and the many variations used since, is done to honor this act of care and solidarity.
Is there a queer voice, an author, creator, or activist who has inspired or supported you?
I love Ivan Coyote. They have a book of letters from fans and their responses. I don’t cry easily, but some of the letters are so raw it’s impossible not to.
Pride celebrations here can sometimes feel like we’ve lost touch with our history and the ongoing struggle for respect, safety, and equality.
It feels important and powerful to tell those stories and make sure we don’t lose sight of how much work there is still to do in this world.
What’s one thing you love about the queer community you’re part of (in or outside Drupal)?
In Drupal, I love that the community is so global. I have learned a lot about what’s happening around the world. It’s easy to only see your own community and the struggles you and your friends face, the violence and heartbreak right in front of you.
But I love getting to celebrate wins and hold space for people globally. I’ve learned so much from the Drupal community. It has changed my relationship with queer activism and reminded me what I have to be grateful for. It also makes me feel like we really aren’t alone, and that gives me an incredible amount of hope.
Thank you, Fei, for your vulnerability, care, and presence in Drupal community. Your voice reminds us why representation matters and how simply showing up as yourself can make space for others to feel safe, seen, and supported.
To LGBTQ+ and queer members of our community, and to everyone reading, if you feel inspired to share your story this Pride Month, we welcome you with open arms. Every contribution helps build a more inclusive and loving web, one story at a time.
Want to share your own story? Submit your response here.
We also invite you to get involved with the Drupal Diversity & Inclusion (DD&I) initiative. Join the #diversity-inclusion channel on Drupal Slack and say hello! Learn more at drupaldiversity.com/get-involved.
