20 Jun 2025

feedDrupal.org aggregator

Joshuami: Recipe Unpack: This Blog Is No Longer on Drupal CMS, and That's a Good Thing

Recipe Unpack: This Blog Is No Longer on Drupal CMS, and That's a Good Thing joshuami

With the release of Drupal 11.2, the Recipes feature gets an important new capability. You can now "unpack" recipes after they are run so that your composer.json will have the direct dependencies from the recipe rather than a dependency on the recipe itself.

20 Jun 2025 9:00pm GMT

The Drop Times: Meet Matt Glaman — Candidate for the 2025 Drupal Association Board Election

Matt Glaman outlines how a Drupal template marketplace could reshape sustainability and create real opportunities for solo developers.

20 Jun 2025 4:54pm GMT

The Drop Times: Meet J Matthew Saunders — Candidate for the 2025 Drupal Association Board Election

Matthew Saunders discusses responsible AI, neuroinclusion, and how Drupal can model ethical governance in open source.

20 Jun 2025 4:36pm GMT

The Drop Times: Meet Carlos Ospina — Candidate for the 2025 Drupal Association Board Election

Carlos Ospina outlines strategies to make Drupal more accessible in underrepresented regions through regional events, adjusted pricing models, and localized contribution programs. His focus is on ensuring that financial and structural barriers do not limit global engagement with Drupal.

20 Jun 2025 4:11pm GMT

The Drop Times: Meet Alexander Varwijk — Candidate for the 2025 Drupal Association Board Election

Learn how Alexander Varwijk aims to enhance entry points for new contributors and promote community-led sustainability within the Drupal ecosystem.

20 Jun 2025 3:31pm GMT

Drupal Core News: 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.

Drupal core will adopt Gin admin theme to replace Claro

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?

Although Claro will not be the default theme anymore for new sites, it will remain in Drupal 11 for use on existing sites. Claro is planned to be removed from core in Drupal 12, at which point it may become available as a contributed theme outside of core.

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.

20 Jun 2025 8:43am GMT

DevCollaborative: Building Websites That Last: The Open Source Superhighway

One of the things that decision-makers in nonprofits fear most is that they'll their limited energy and funding into a project that will need to be scrapped within a few years. We minimize this needless risk by building collaboratively in open source software.

A car on a highway peeling off, smoke billowing from its screeching wheels, choosing an off ramp labeled "Bespoke artisanal code" instead of following the sign ahead, "Common Open Source Patterns."

20 Jun 2025 7:06am GMT

The Drop Times: Your Vote, Their Vision: 2025 Drupal Board Election Candidates

Seven candidates are running for the 2025 Drupal Association Board. In exclusive interviews with The Drop Times, they share their priorities-from regional growth and contributor support to AI policy and community sustainability. Read what each candidate stands for before casting your vote.

20 Jun 2025 6:10am GMT

The Drop Times: Meet Will Huggins — Candidate for the 2025 Drupal Association Board Election

Will Huggins explains his vision for aligning commercial growth with community values and how Drupal can thrive through trust and balance.

20 Jun 2025 5:46am GMT

The Drop Times: Meet Vladimir Roudakov — Candidate for the 2025 Drupal Association Board Election

Vladimir Roudakov brings academic and open-source experience to his campaign, focusing on targeted documentation reform, contributor recognition, and deeper engagement with universities. His platform aims to make Drupal more approachable for students, educators, and non-technical users worldwide.

20 Jun 2025 5:31am GMT

The Drop Times: Meet Maya Schaeffer — Candidate for the 2025 Drupal Association Board Election

Maya Schaeffer focuses on creating space for marketers, designers, and strategists within the Drupal ecosystem. Her platform calls for clearer contribution pathways, tailored community programs, and expanding Drupal's presence in non-technical sectors-without losing its technical depth.

20 Jun 2025 5:18am GMT

19 Jun 2025

feedDrupal.org aggregator

Evolving Web: Support Maya's Candidacy for the Drupal Association Board Elections

I'm resharing my recent interview with The Drop Times about my platform for the Drupal Association 2025 Board Election because I want to give our community a clear look at where I stand, what I believe Drupal needs next, and how I'd approach my role if elected to the Drupal Association Board. From making events and contribution pathways more inclusive to strengthening Drupal's brand while reaching new audiences, I hope these ideas spark conversation and reflect the practical, community-first mindset I'd bring to the board.

Voting is now open and will be until July 11 23:59 UTC. You need to have been a Drupal Association Ripple Maker 24 hours before voting opened on June 18 in order to be eligible to vote. Ripple Makers be sure to look out for the email from the Drupal Association with your voter id, password and instructions.

Below you will find my interview with Ben Beter of the DropTimes and my vision for the future of Drupal:

1. You've welcomed 40% of attendees from outside Drupal at EvolveDrupal-what concrete steps would you take as a board member to ensure that those first-time or non-technical participants feel empowered to contribute beyond in-person events?

What we've seen at EvolveDrupal is that getting someone through the door is only step one. A good event might spark someone's interest-but what they really need afterward are clear, approachable next steps.

If I were on the board, I'd push for things like regular beginner-friendly webinars, ideally led by agency folks who can break things down in a way that's not intimidating. I'd also love to see more storytelling-hearing from people who work in marketing, UX, content, etc., who are already using Drupal, so newcomers can actually see themselves in this space.

On the practical side, we could build out a non-technical contributor guide on drupal.org. Right now, the site is very developer-focused, and it's not always easy for someone from a design or communications background to know where they fit in.

I'd also like to see a post-event "what's next" guide-a simple follow-up email with curated links, a breakdown of contribution options, and how to join the community or a working group. And at events like Digital Collegium or Educause, the DA should absolutely have a presence. These are the types of places where we can reach non-technical people who are using-or could use-Drupal every day.

2. Running events in six North American cities post-pandemic showed incredible momentum. How would you advise the Drupal Association to scale that model globally, balancing centralized strategy and local autonomy, without diluting what makes each gathering unique?

I think the key is to support, not control. What made EvolveDrupal work is that we kept things lightweight, flexible, and community-focused. The DA could definitely help other organizers by offering a basic playbook-just something that outlines what's worked for us, especially around getting non-Drupal folks in the door, and tips for outreach and sponsorship.

Templates, branding assets, or just having a shared doc of what speakers or formats worked well-that would go a long way. But at the end of the day, each region should have the freedom to do what fits their audience. What works in Ottawa might not land in Lagos or São Paulo-and that's okay.

Also, the DA could make a real difference by offering even small sponsorships or in-kind support-like signal boosts, intros to speakers, or even just showing up. And there's already an event organizer group-I'd love to connect more with that crew and share what we've learned.

Lastly, I think it would be really helpful to build a community of practice-just a way for organizers around the world to share ideas, speakers, and lessons learned. That way, we keep the energy up without trying to clone the same event everywhere.

3. You aim to be a voice for marketers, designers, and communicators. What is one current board decision or policy that you believe doesn't adequately engage non-technical contributors, and how would you address that imbalance if elected?

Honestly, I think a lot of DA programs are still geared toward developers. Even something like the "Ripple Maker" term-it's clever, but it doesn't really speak to folks in marketing or comms. And while I do think the Drupal.org rebrand was a great step forward, we're still missing content that's actually tailored to non-technical people.

For example, Supporting Partner benefits mostly focus on things like commit credits and developer recognition. If I were on the board, I'd push to also highlight contributions in areas like accessibility, UX, design systems, and community outreach.

We also need to be more present in non-Drupal spaces-but not just with a booth. Booths are fine, but what matters is what happens at them. If we show up to conferences like Educause or HighEdWeb, we should be doing live demos, sharing case studies, and talking to people on their terms. That part is often missing.

Another thing: we should ask agencies to help spread the word. I know GDPR limits how we share contact info, but we can still create referral-friendly content, like newsletter templates or event invites that agencies and end-user organizations-like universities-can pass on internally.

I also think DrupalCon could do more to intentionally invite marketers. Maybe a marketing track, or something like a dedicated Marketing & Comms Summit, just like we do for government or higher ed. And, of course, keeping event prices low is key to getting more diverse voices in the room.

4. Your growth of EvolveDrupal into EvolveDigital signals openness beyond Drupal. In the context of the Promote Drupal initiative, how would you ensure Drupal maintains brand identity and technical depth while engaging broader audiences and digital disciplines?

EvolveDigital isn't about stepping away from Drupal-it's about making space for the broader ecosystem around it. The reality is, Drupal doesn't exist in a vacuum. It's always used alongside other tools and strategies. So rather than trying to wall it off, we should lean into that and show how Drupal fits into modern digital teams.

I think Promote Drupal can support this with a two-track approach:

  1. Keep speaking to technical folks-architects, CTOs, site builders-with deep case studies and strong messaging around flexibility, scalability, and performance.
  2. At the same time, create sector-specific narratives for content teams, marketers, and digital strategists-stories that highlight accessibility, ownership, integration, and total cost of ownership.

We should also make sure that people from these roles are involved early in the process-not just reviewing messaging, but helping shape it.

At the end of the day, I don't think widening the conversation weakens Drupal's brand. If anything, it shows how versatile and future-proof it is. We just need to get better at telling that story to all the right people.

Conclusion

If I were on the board, I'd focus on helping Drupal grow beyond its current edges-by making the project more welcoming to non-technical contributors, easier to access for new users, and more visible to sectors that don't yet realize how much Drupal can offer. My experience organizing EvolveDrupal (now EvolveDigital) has shown me what's possible when we create spaces that are inclusive, cross-functional, and community-powered. I'd bring that same mindset to the DA-supporting meaningful events, clearer contribution pathways, and smarter communication that reflects the full diversity of our ecosystem.

In short, if elected, I would:

I'm excited about what's ahead for Drupal-and I'd love to help shape that future from a place of inclusion, energy, and practical momentum.

If my vision resonates with you, I'd be honoured to have your support in this election.

+ more awesome articles by Evolving Web

19 Jun 2025 4:13pm GMT

The Drop Times: SPARC: Solar Powered Advanced Renewable Control

Jasper Lammens explains how SPARC helps homeowners optimize solar energy use by combining Solcast forecasts, InfluxDB storage and Drupal ECA rules to send Discord notifications with ideal appliance schedules. Its best-fit, worst-fit and first-fit algorithms boost on-site solar consumption and cut grid reliance.

19 Jun 2025 3:37pm GMT

DrupalCon News & Updates: DrupalCon Vienna 2025: Where Business Meets Technology

In today's fast-paced digital economy, successful organizations must align their technical architecture with strategic business goals. DrupalCon Vienna 2025 isn't just a gathering of developers, it's a dynamic intersection where business leaders, marketers, technical architects, and product managers come together to explore how Drupal drives innovation and delivers measurable impact.

Whether you're launching global digital platforms, scaling personalization, improving time to market, or enhancing user experience this year's DrupalCon is where you'll find the insights, tools, and partners to make it happen.

Bridging the Gap Between Vision and Execution

Modern digital strategies depend on a solid technical foundation. At DrupalCon Vienna, you'll hear directly from digital leaders and enterprise teams who have successfully:

  • Modernized outdated platforms

  • Integrated Drupal with CRM, CDP, and analytics tools

  • Delivered omnichannel content at scale

  • Aligned marketing, IT, and product teams for cohesive execution

Case studies, panel discussions, and solution showcases will provide practical takeaways that go beyond buzzwords from project planning and governance to content strategy and performance optimization.

Drupal as a Strategic Business Platform

Drupal has evolved far beyond a CMS. It's a flexible, enterprise-ready digital experience platform (DXP) capable of powering everything from campaign websites to enterprise portals. At DrupalCon Vienna 2025, sessions will explore:

  • Composability: How modular architecture lets businesses adapt quickly

  • Integration-first thinking: Making Drupal the backbone of your digital ecosystem

  • Scalability: Supporting millions of users while maintaining performance and agility

  • Data and analytics: Building data-driven content strategies

If you're leading digital transformation efforts, this is your opportunity to see how Drupal is enabling organizations to innovate with confidence.

Business + Tech Networking That Matters

DrupalCon Vienna provides unmatched opportunities for networking with people who share your challenges and ambitions from digital directors and CTOs to agency leaders and product strategists.

You'll meet:

  • Enterprise users running Drupal at scale

  • Solution architects building custom platforms

  • Technology vendors and service providers

  • Decision-makers planning their next investment

These conversations often spark partnerships, ideas, and collaborations that last long after the event ends.

Workshops and Strategy Sessions

For teams focused on long-term planning, DrupalCon offers curated content designed to guide your strategic roadmap. Attend workshops and sessions on:

  • Project architecture for growth and flexibility

  • Governance models for distributed teams

  • Digital asset management, personalization, and localization

  • Open source procurement and risk mitigation

Whether you're managing your first Drupal rollout or optimizing a mature platform, there's content here for every stage of your digital journey.

Ready to Align Your Business and Tech Strategy?

DrupalCon Vienna 2025 is more than a conference, it's a catalyst for growth, innovation, and alignment. Join us to discover how forward-thinking organizations are leveraging Drupal to unlock digital success across departments and markets.

Mark Your Calendars

🗓️ Dates: October 14-17, 2025
📍 Location: Austria Center Vienna, Vienna, Austria
🌐 Official Website & Registration: https://events.drupal.org/vienna2025/registration-information
🐦 Follow the buzz: #DrupalConVienna #DrupalCon2025

Stay Tuned!

This blog is just the beginning. Over the next few weeks, I'll be sharing:

  • Technical spotlights on Drupal CMS features
  • Speaker highlights and session previews
  • Tips for first-time technical attendees and contributors

So bookmark this space, and get ready to experience DrupalCon Vienna 2025 like never before.

Are you coming? Let's connect!

By Iwantha Lekamge

Technical Lead
WSO2

19 Jun 2025 8:05am GMT

The Drop is Always Moving: Drupal 11.2.0 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. https://www.drupal.org/blog...

Drupal 11.2.0 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. drupal.org/blog/drupal-11-2-0

19 Jun 2025 6:14am GMT

Drupal blog: 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.

Drupal 11.2.0 now available

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:

GIF animation of installing 60 modules in Drupal 11.1 and 11.2

.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 #[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.

19 Jun 2025 5:05am GMT