Completed Drupal site or project URL: https://yalesites.yale.eduA new era of digital collaboration and brand unity for Yale

Yale University challenged itself to change the game in how it creates, manages, and publishes content. The result was YaleSites: a user-friendly, accessible, and highly customizable digital platform designed for the Yale community. Built on Drupal and open-source tools like Emulsify, YaleSites revolutionizes the digital landscape for the Yale community while giving them more flexibility and control over their content.

Here’s how Yale, through a strategic partnership with Four Kitchens, uses open-source solutions like Drupal to redefine digital collaboration and brand unity across its community.

New in Drupal 11.1

The first feature release of Drupal 11 improves the recipe system, introduces support for hooks written as classes, makes Workspaces more flexible and enhances performance.

Recipe system improvements

The Recipe system allows packages to be configured with dependencies in a repeatable way. Drupal 11.1 now allows recipes to take user input (for example, API keys for remote services). Recipes can now also use configuration actions to add new blocks, enable layout builder for content types, clone configuration entities, and so on.

Hooks can be written as classes

Drupal's unique hook system allows modifying forms, data updates, site processes, render structures, and even the ordering of other hooks. After long-running efforts by many contributors, it is now possible to also define hooks and hook implementations with object-oriented techniques that are more in line with modern PHP code design practices. This will also make Drupal's code easier to understand for PHP developers familiar with other projects. All runtime core hooks have been converted to object-oriented implementations.

With this new functionality, magic global functions like the following will no longer be needed:

function hook_entity_insert(EntityInterface $entity) { // DO STUFF }

Instead, developers can use the new Hook attribute on methods:

class ExampleHooks { #[Hook('entity_insert')] public function entityInsert(EntityInterface $entity): void { // DO STUFF } } New icon management API

A dedicated API has been added to allow modules and themes to define icon packs. Within each pack is a series of icons each with a unique identifier that the system can then use. Modules and themes can alter icon packs.

Workspaces user interface separated into its own module

As part of a larger plan to use workspaces for content moderation, the user interface of the Workspaces module was moved to a separate Workspaces UI module. For new sites, if you want to enable Workspaces with the user interface, you now need to install this module.

Improvements to the initial experience after installation

We revisited Drupal core's default configuration to better reflect most user's needs. In this release, date formats were made easier to read. The user registration process also now defaults to administrator-created accounts, in order to avoid new sites being flooded with spam accounts in the moderation queue. When creating a new node type, Drupal core will no longer automatically add a body field, allowing site builders to choose their own content model without having to delete defaults they don't want first and reducing potential conflicts for platforms built on Drupal core such as Drupal CMS and the upcoming Experience Builder.

New views entity reference filter

A new generic entity reference views filter has been added, which makes it possible to render exposed views filters as a select list or autocomplete of available entities. This may now be used by contributed modules and will be enabled for core entity types in future releases.

Render caching for forms

Forms built with form API can now opt-in to render caching, improving page loading performance in a variety of situations. We will be gradually opting forms into Drupal core into render caching, and may opt-in all forms to render caching by default in a future major release.

Improved browser and CDN caching for JavaScript and CSS

Drupal's asset aggregation algorithm has been improved to reduce variation in CSS and JavaScript aggregates. Differences between pages which may have produced different but similar aggregates in the past, for example because libraries were requested in a different order, will now result in a single file instead. This improves CDN cache hit rates and reduces the amount of JavaScript and CSS that visitors will download when visiting multiple pages on a site. This builds on several previous recent improvements to Drupal core's asset aggregation since Drupal 10.1 and also unblocks further improvements which are planned for future minor releases.

PHP 8.4 is supported

The PHP team is doing a fantastic job of improving the language and performance of PHP. PHP 8.4 was released in November, and Drupal 11.1 fully supports it.

Drupal CMS 1.0 will be based on Drupal 11.1

Drupal 11.1 will be the basis of Drupal CMS 1.0, which will be released on January 15 on Drupal's 24th birthday. Many of the underlying improvements introduced in Drupal core will help compose an improved user experience in Drupal CMS. The first release candidate of Drupal CMS was already based on Drupal 11.1 RC. Stay tuned!

Drupal 10.4 will be available soon

The next Long-Term Support (LTS) release of Drupal 10 will be released this week. Drupal 10 will be supported until the release of Drupal 12 in mid- to late 2026. 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. And it gives more flexibility for sites to move to Drupal 11 when they are ready.

The same will happen when Drupal 10 is end-of-life and Drupal 12 is released: Drupal 11 will transition to Long-Term Support, with its own maintenance minors every six months. This release schedule allows sites to move from one LTS version to the next if that is the best strategy for their needs..

Core maintainer team updates

Since Drupal 11.0, Adam Hoenich has stepped down from being a Migrate subsystem maintainer as he moved on to be a key committer for Drupal CMS. We thank Adam for his contributions!

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 opportunitzies to deepen your Drupal skill set and give back to the community. Check out the Drupal contributor guide. You are more than welcome to join us at DrupalCon Atlanta in March 2025 to attend sessions, network, and enjoy mentorship for your first contributions.

Completed Drupal site or project URL: https://atendesigngroup.com/work/drupal-website-redesignUser- and Revenue-Driven Drupal Website Redesign

Recently ranked as the nation’s No. 1 large airport for customer satisfaction according to J.D. Power, Tampa International Airport (TPA) has built a reputation as a traveler- and community-friendly destination. While TPA hosts 21 million passengers annually, its website serves not only travelers but also employees, businesses, partners, airlines, and more.

Given the airport’s traveler-friendly reputation, TPA hoped to mirror its user-focused and easy-to-navigate airport experience via a redesigned website. Additionally, stakeholders wanted to not only drive concessions pre-ordering and parking revenue but also ensure they understood and then met the needs of the airport’s myriad user groups.

Aten launched the project with an in-depth discovery phase meant to identify the needs of multiple user groups and craft a clear reference point to drive decision-making. Using the resulting insights, we devised an intuitive and easy-to-navigate Drupal 10 website hosted on Acquia. We put diverse user needs top of mind, baked revenue drivers into the navigation, and featured the same bright and open aesthetic that greets TPA visitors every day.

Completed Drupal site or project URL: https://www.concept2.com/

DIGITAL TRANSFORMATION IN ECOMMERCE

Concept2 Rising above the competition — Pursuing superior digital commerce in the fitness industry. Ecommerce Success Depends on Your Website

Hampered by an ineffective user experience, Concept2 needed a new website to

• Improve user experience with a modern, responsive design and clear conversion paths.

• Minimize admin effort and overhead by using streamlined processes and newer technologies.

• Maintain stability and security by migrating to an up-to-date, modern, supported platform.

Concept2's new technical infrastructure is composable, and its flexible decoupled nature is future-ready and scalable, allowing them to adapt to their evolving needs.

World Class Fitness Experts

Concept2 has been the global leader in the innovation and production of rowing oars since 1976. Their oars won 98% of rowing medals at the Tokyo Olympics. 

In addition to the Concept2 RowErg, which has become a fixture in rowing clubs, homes, gyms, CrossFit boxes, and schools around the world, the company's range of sports-based ergometers now includes the SkiErg and the BikeErg.

Time for Healthy Change

The pandemic significantly changed the fitness equipment market, shutting gyms and driving more people to purchase in-home fitness equipment to reach their goals. 

With retail stores and their distributor network affected by quarantine closures, it became apparent that having an updated and integrated online sales channel for their B2B and D2C customers would make a substantial difference in a changing marketplace.

Concept2's new website would provide comprehensive information and support, reflect the company’s position as the market leader, and allow it to promote new offerings, such as ErgData, their free app for iOS and Android. Connecting these services and products through their website enhances customer experience and improves brand consistency.

Sink or Swim: The Effects of an Outdated Website

When Concept2 examined its website closely, it admitted that its current infrastructure must be updated to improve scalability and promote growth. The limitation of their current setup had the potential to impact their bottom line significantly: 

• Not mobile-friendly—According to Forbes, mobile commerce sales, or sales made from a smartphone, are expected to account for 62% of all retail sales by 2027. Without a mobile-friendly and responsive site, Concept2 was leaving a lot of sales on the table for competitors to snap up.

• Limited content management capabilities—The cornerstone of marketing is sending the right message to the right audience at the right time. Concept2's marketing team was handcuffed because it could not easily edit or add new content and had restricted content and visual storytelling options.

• Unrefined user experience—Their current site navigation was not user-friendly, lending to a clunky shopping experience. With today’s sophisticated online shoppers and Concept2’s premium brand, upgrading the user experience is influential in maintaining their elite brand awareness.

• Restricted functionality and system security—The inability to link replacement parts to machines, the lack of centralized content or codebase for subsidiary sites, and the susceptibility to server overload mean that manual labour to maintain content and the site is a constant resource issue.

In addition to these hurdles, Concept2 has subsidiaries in the UK, Australia, Germany, Austria, Switzerland, and Benelux. Each subsidiary would need its own version of the site, which it could customize according to its market. Thus, they needed a multi-site experience that works globally.

Building the Future One Stroke at a Time Create a modern ecommerce website experience using a decoupled infrastructure for maximum flexibility and future scalability.

Concept2 decided the new site should be built on Drupal 10 using Drupal Commerce to achieve this. Without in-house development resources, Concept2 needed a partner agency that could handle the scope of the build and bring it to life in a quick turnaround time.

Using our decoupled accelerator, Gesso, and our agile development process, we established a communication and development cadence with Concept2’s internal team and stakeholders, ensuring full Acro Commerce support from discovery through development to launch, starting with their US site, which launched in June 2024.

Gesso, our development accelerator, made C2 a reality.

Advantages of a decoupled accelerator

• Optimized reducing development time.

• Control of brand across multiple sites.

• Swap platforms without impacting customer experience

• Reduced time-to-market for future development

The dual-core setup of Drupal Commerce and Drupal CMS is a powerful combination that empowers Concept2’s non-technical resources, such as marketers and administrators, to build and maintain an unrivalled customer experience, propelling their online presence and maintaining leadership in their industry.

Completed Drupal site or project URL: https://www.equalopp.org/

Equal Opportunity Community Initiative (EOCI) is an international nonprofit dedicated to providing education-based programming to children in underserved communities. With a vision of granting all children equal access to education, EOCI uses its platform to connect at-risk children with vital educational and life resources, including training programs and volunteering opportunities. Faced with an outdated website that no longer reflected their expanded mission, EOCI enlisted OPTASY to redesign their digital presence on a new, modern Drupal platform.

Completed Drupal site or project URL: https://www.newport.gov.uk/

Zoocha worked with Newport City Council (NCC) on the redesign and development of their new LocalGov Drupal (LGD) platform. As one of the largest local authorities in Wales, NCC required a user-centred platform transformation that would meet the needs of the local community and also improve ease of use for the web team. 

Newport City Council were seeking a new platform that would provide:

• Seamless multilingual functionality
• Ease of use for the website management team
• A refreshed look and feel that reflected the modern aspirations of the Council
• Improved accessibility and usability 
   

Completed Drupal site or project URL: https://www.ubicquia.com/

With SEO-optimizing features like Webp, customizable meta tags, SEO-friendly URLs, automatic sitemap generation and more, Drupal proved to be the perfect solution for Ubicquia in enhancing their organic SEO.

Ubicquia is a leading technology company dedicated to making existing infrastructure smarter through easy, scalable, and innovative solutions. With a customer base of over 700 spanning the US, Canada, and Latin America, They excel in providing services to cities, utilities, and communications service providers, showcasing consistent progress in its projects.

The Result

Phase 1 delivered remarkable outcomes, significantly boosting the website's overall health score from 75 to an impressive 95. Embarking on Phase 2, Specbee prioritized Ubicquia’s user behavior analysis, aligning areas with user intent and optimizing content for enhanced performance.

New in Drupal 10.3

The third and final feature release of Drupal 10 ships with a new experimental Navigation user interface, stable Workspaces functionality, stable Single-Directory Components support, simplified menu editing, taxonomy moderation support, new recipe and access policy APIs, performance improvements and more.

New experimental Navigation module

The new Navigation module provides a redesigned collapsible, vertical navigation sidebar for the administrative user interface. Sub-menus open on a full height drawer that can accommodate deeper navigation levels. On smaller viewports, the toolbar is placed on top of the content, and opens with an overlay.

The Navigation module allows multiple types of customization, like adding new custom menus or changing the default Drupal logo provided. It also uses the Layout Builder module, so that site builders can easily add or reorder these menu blocks.

The Navigation module includes a new content creation and management menu, which allows quick access to content-related tasks to increase usability for content users.

Stable Workspaces module

The Workspaces module allows Drupal sites to have multiple work environments, enabling site owners to stage multiple content changes to be deployed to the live site all at once. It has long been available in Drupal core as an experimental module. Following the module's use in live projects, the remaining stable blocking issues have been resolved, so now it is available to all!

Workspaces are sets of content changes that are prepared and reviewed separately from the live site. This is a differentiating feature for Drupal that is important for many large organizations' websites. An organization might use Workspaces to ensure all relevant content goes live simultaneously for a new product launch, or with the outcomes of sporting or election events.

Stable Single-Directory Components

Single-Directory Components (SDCs) are Drupal core’s implementation of a user interface components system. Within SDC, all files necessary to render the user interface component are grouped together in a single directory. This includes Twig, YAML, and optional CSS and JavaScript. SDC support was added to Drupal core in 10.1 as an experimental module. The solution has been very well-received and is now part of the base system. No need to enable a module to use this feature.

Simplified content organization

Menu item editing is now simplified. Advanced options are displayed in a sidebar to help content editors focus on what is most important for the menu item. Taxonomy terms also now have both a dedicated user interface to edit earlier revisions and content moderation support.

New Recipes and Default Content APIs

Drupal recipes allow the automation of Drupal module installation and configuration. Drupal recipes are easy to share, and can be composed from other Drupal recipes. For example, Drupal 10.3 includes a Standard recipe providing the same functionality as the Standard install profile. It is a combination of 16 component recipes that can be reused in other recipes.

Recipes provide similar functionality to install profiles but are more flexible. With install profiles only one can be installed on a site. With recipes, multiple recipes can be applied after each other.

Install profiles/distributions Recipes Lock-in Not possible to uninstall (until Drupal 10.3) No lock-in Inheritance Cannot extend other profiles or distributions Can be based on other recipes Composability Cannot install multiple profiles or distributions Multiple recipes can be applied on the site and be the basis of another recipe

The recently announced Starshot Initiative will rely heavily on recipes to provide composable features.

The added APIs include Configuration Actions, Configuration Checkpoints and Default Content.

Additionally, it is now possible to install Drupal without an install profile, or to uninstall an install profile after Drupal is already set up.

More flexible access management with the new Access Policy API

The new Access Policy API supports the implementation of access management solutions that go beyond permissions and user roles. Other conditions and contexts may be taken into account, like whether the user used two-factor authentication, or whether they reached a rate limit of an activity. Drupal's existing permission- and role-based access control has been converted to the new API, and custom or contributed projects can add more access policies.

The future of Drupal 10

Drupal 10.3 is the final feature release of Drupal 10. Drupal 11 is scheduled to be released the week of July 29th. With that, Drupal 10 goes into long-term support. While more minor releases will be made available of Drupal 10, they will not contain new features, only functionality backported to support security and a smoother upgrade to Drupal 11. Drupal 10's future minor releases will be supported until mid- to late 2026, when Drupal 12 is released and Drupal 11 enters long-term support.

Core maintainer team updates

Cristina Chumillas (at Lullabot), Sally Young (also at Lullabot) and Théodore Biadala (at Très Bien Tech) were all promoted from provisional to full Drupal Core Frontend Framework Managers.

Alex Pott (at Acro Commerce and Thunder), Adam Globus-Hoenich (at Acquia) and Jim Birch (at Kanopi Studios) are the maintainers of the new Default Content and Recipes subsystems.

Andrei Mateescu (at Tag1 Consulting) is the maintainer of the newly stable Workspaces module.

Ivan Berdinsky (at Skilld) became a co-maintainer of the Umami demo.

Daniel Veza (at PreviousNext) is a new co-maintainer of Layout Builder.

Mateu Aguiló Bosch (at Lullabot) and Pierre Dureau are new co-maintainers of the Theme API, focusing on Single Directory Components.

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, or join us at DrupalCon Barcelona and attend sessions, network, and enjoy mentorship for your first contributions.

Completed Drupal site or project URL: https://www.iowa.gov/

Iowa's state agency websites receive 32 million visitors annually. However, these sites lacked consistent branding, navigation, features, and centralized governance, resulting in stale and redundant content that hindered the user experience.

To address these issues, Lullabot reorganized the agency websites and migrated them to a unified Drupal platform. This new platform enhances the editorial experience, ensures consistent branding, provides agencies with greater flexibility, and resolves major accessibility concerns.
 

Completed Drupal site or project URL: https://www.oise.utoronto.ca/home

Ontario Institute for Studies in Education (OISE), Canada's leading faculty of teaching and learning, known for its research-intensive focus, tasked OPTASY with developing their new website. The primary objective was to enhance the overall user experience by improving website performance, navigation, and responsiveness.

Completed Drupal site or project URL: https://surgery.ucsf.edu/An intuitive user experience that reassures patients and inspires future residents.

The Department of Surgery at the University of California, San Francisco is one of the leading surgical departments in the world with a rich history of scientific, educational, and clinical advancements. Although their care is primarily dedicated to the people of the San Francisco Bay Area (with six major area hospitals), their reputation draws patients nationally and internationally. UCSF surgeons perform a high volume of advanced, complex and technically challenging procedures. This allows them to continually improve their skills, resulting in better outcomes for patients.

The Challenge

The Department of Surgery consisted of over 80+ domains ranging from research-focused, to patient-focused, to those geared towards residents. All were built using a proprietary CMS with no cohesive way to navigate between the various domains. Even worse, many of the domains/departments were creating their own layouts, navigation, and design signals, so there was little consistency between them.

There was also no content strategy whatsoever. Most site users identified as patients and their family members trying to learn more about specific conditions and procedures, which drove organic traffic to pages other than the homepage. But those pages weren’t easy to navigate, and visitors encountered many content dead-ends — with no idea where to go next. Meanwhile, the homepage had become cluttered;, with many competing inline links and no clear content hierarchy.

The CMS didn’t provide an easy way to share content, requiring editors to do extra work recreating content for each domain. The content itself didn't serve any audience needs; it lacked patient-friendly language and didn’t inspire potential residents to apply or take further action.

UCSF needed an inspiring design worthy of their status as a world-class medical school with a growing, innovative and diverse environment. Their new website would need overall consistency, a proper content hierarchy, and a back-end structure that provided both long-term sustainability and flexibility for content editors.

Contact Kanopi about your project

Completed Drupal site or project URL: https://diabetes.org/Overview

The American Diabetes Association (ADA) is a non-profit organization that aims to educate the public about diabetes and provide support to those affected. The ADA contributes to the fight against diabetes by funding research, improving treatment options, and offering care services.

In line with their commitment to staying at the forefront of technology to better serve their users, our clients wanted to improve their online presence by migrating their websites from different versions of Drupal to a unified platform on Drupal 10. This involved consolidating different codebases into one system while meeting diverse database needs through a multi-site architecture.

With the upgrade to Drupal 10 and the development of new components following their original brand guidelines, the ADA can now educate, support, and empower individuals affected by diabetes more efficiently. This allows them to reach a larger audience and have a positive impact on the lives of many people affected by diabetes.

2023 has been an eventful year, full of ideas, discussions and plans regarding innovation, where Drupal is heading, and, in our case, how the Drupal Association can best support. On top of that, you may have already heard, but innovation is a key goal for the Drupal Association.

Drupal is nothing but a big, decentralized, community. And before we can even think of how we can innovate, we need to understand how contribution actually happens and evolves in our ecosystem. And one of the things we agreed early on was that, without numbers, we don’t even know where we are going. 

For that reason in 2024 we want to introduce you to part of the work we’ve been doing during the last part of 2023 to make sure that we know where we are coming from, we understand where we are going and how the changes we are doing are affecting (or not) the whole contribution ecosystem. I want to introduce you to the Contribution Health Dashboards (CHD).

The CH dashboards should help identify what stops or blocks people from contributing, uncover any friction, and if any problems are found, help to investigate and apply adequate remedies while we can as well measure those changes.

One thing to note is that the numbers we are showing next are based on the contribution credit system. The credit system has been very successful in standardizing and measuring contributions to Drupal.  It also provides incentives to contribute to Drupal, and has raised interest from individuals and organizations.

Using the credit system to evaluate the contribution is not 100% perfect, and it could show some flaws and imperfections, but we are committed to review and improve those indicators regularly, and we think it’s the most accurate way to measure the way contribution happens in Drupal.

It must be noted as well that the data is hidden, deep, in the Drupal.org database. Extracting that data has proved a tedious task, and there are numbers and statistics that we would love to extract in the near future to validate further the steps we are taking. Again, future reviews of the work will happen during the next months while we continue helping contributors to continue innovating.

You can find the dashboards here, in the Contribution Health Dashboards, but keep reading next to understand the numbers better.

Unique individuals and organisations

Jumping to what matters here, the numbers, one of the most important metrics to understand in the Drupal ecosystem is the number of contributions of both individuals and organisations.

As you can see, the number of individuals has stayed relatively stable, while their contribution has been more and more significant over the years (except for a slide in the first year of the pandemic). In a way this is telling us that once a user becomes a contributor, they stay for the long run. And, in my opinion, the numbers say that they stay actually very committed.

The number of organisations on the other hand displays a growing healthy trend. This shows that organisations are an important partner for Drupal and the Drupal Association, bringing a lot of value in the form of (but not just) contributors.

It definitely means that we need to continue supporting and listening to them. It’s actually a symbiotic relationship. These companies support and help moving forward, not just Drupal, but the whole concept of the Open Web. And their involvement doesn’t end up there, as their daily role in expanding the reach, the number of instances and customers of every size using Drupal is as well key.

In practical terms in 2023 we have been meeting different companies and organisations, and the plan is to continue listening and finding new ways to help their needs in 2024 and beyond. One of the things we are releasing soon is the list of priorities and strategic initiatives where your contributions, as individuals as well as organisations, are most meaningful. This is something I have been consistently asked for when meeting with those individuals and organisations, and I think it’s going to make a big difference unleashing innovation in Drupal. I recommend you to have a look at the blog post about the bounty program.

First year contributors

The next value we should be tracking is how first time users are interacting with our ecosystem.

While the previous numbers are encouraging, we have a healthy ecosystem of companies and a crowd of loyal individuals contributing to the project, making sure that we onboard and we make it easier and attractive for new generations to contribute to the project is the only possible way to ensure that this continues to be the case for many years to come.

That’s why we are looking at first time contributions, or said differently, how many users make a first contribution in their first 12 months from joining the project. During 2024 I would like to look deeper into this data, reveal contribution data further on time, like after 24 and 36 months. For now this will be a good lighthouse that we can use to improve the contribution process.

Although last year's numbers give us a nice feeling of success, we want to be cautious about them, and try to make sure that the trend of previous years of a slight decline does not continue.

That is the reason why my first priority during the first months of 2024 is to review the registration process and the next step for new users on their contribution journey. From the form they are presented, to the documentation we are facilitating, to the messages we are sending them in the weeks and months after.

The changes we make should be guided as well by the next important graph, which is the Time To First Contribution. In other words, the amount of time a new user has taken to make their first contribution to Drupal.

You’ll see that the Contribution Health Dashboards includes other data that I have not mentioned in this post. It does not mean that it is not equally important, but given the Drupal Association has a finite amount of resources, we consider that this is the data that we need to track closely to get a grasp of the health of our contribution system.

For now, have a look at the Contribution Health Dashboards to get a grasp of the rest of the information that we have collected. If you are curious about the numbers and maybe would like to give us a hand, please do not hesitate to send me a message at alex.moreno@association.drupal.org

As part of my role in the Drupal Association, we are trying to find new ways to unleash innovation. Innovation as it happens is a key goal for the Drupal Association. What surprised me when I started with the Drupal Association was to meet companies that were contributors, (some of them known for being long-time contributors) or that are very interested in contributing, but then not knowing how they could maximize their contributions or even where they should be contributing to.

I don’t think that these are a few isolated cases, as it’s not the first time I've seen this trend. Back when I was working for a 100+ developer consultancy firm there was a big corporate push to increase our contribution to open source. And contribute we did. We started “Pizza Fridays”, which meant we were spending Fridays contributing, doing presentations between us, and having pizza for lunch. We had fun, but we lacked structure, purpose, and higher goals (and a healthy diet on Fridays). Our plan was not aligned with anything other than our own appetite to experiment or learn something.

If we had a structure that aligned us to the project we were contributing to, our contributions would have been more impactful, business would have benefited in a more meaningful way, and the whole team would have probably been allowed to contribute even further and longer in time. We did amazing things, don’t get me wrong, but the impact of those could have been much bigger.

That’s why, today, we are introducing the credit bounty program. The idea is to do an initial experiment, and if it has an impact on Drupal moving forward, we’ll tweak it if needed and continue with new iterations.

I expect that the issues and projects that we are promoting will change over time, so we’ll share soon how you can get updated information.

If you are a maintainer and you would like us to include your issues in this pilot program, that may be a possibility as well, so please send me an email: alex.moreno@association.drupal.org. Depending on how this first phase goes, we may start promoting contributed module issues as well based on the popularity of the modules, usage on sites, complexity, how innovative they are, etc, etc

For now, this is the list of issues where (core for now) maintainers need your help. The reward will be a boost to marketplace rank equivalent to 5 times the normal amount for these issues. Sounds good?

• Cannot save translated nodes after upgrading to 8.8 due to invalid path
  • https://www.drupal.org/project/drupal/issues/3101344
• Composer scaffolding fails when permissions on default.settings.yml or default.settings.php is not writable
  •  https://www.drupal.org/project/drupal/issues/3091285
• Configuration language being overwritten during module install
  • https://www.drupal.org/project/drupal/issues/2905295
• Prevent saving config entities when configuration overrides are applied
  • https://www.drupal.org/project/drupal/issues/2910353

Maintainers will grant credit as normal on these issues, and the contributing organizations that the maintainers credit will receive the full bounty

Make sure to read Drupal Core's Issue Etiquette for core contribution, and the Contributor Guide. 

Have questions or ideas? Please ping me: alex.moreno@association.drupal.org
 

Completed Drupal site or project URL: https://georgia.gov/

The state of Georgia's web infrastructure serves nearly 10 million residents and includes websites and services for more than 80 different programs and agencies. As their network of Drupal 7 websites aged, and the needs of Georgia's diverse state agencies evolved, meeting everyone's requirements had grown increasingly difficult. Without a mandate to centralize web presence, the project required a system that addressed common functional needs while giving each agency its own visual appearance. But this appearance also had to remain identifiable within overall brand guidelines.

Together with Digital Services Georgia (DSGa) and the branding specialists from IDEO, we created GovHub, a next-generation platform that helps state agencies serve residents better, leverages new technologies more effectively, and simplifies the lives of overworked staffers.

New in Drupal 10.2

The second feature release of Drupal 10 improves content modeling, block management, menu and taxonomy organization, and permission administration. New options to sanitize file names make it possible to clean up the names of uploaded files, and media item revisions now have a dedicated user interface.

Easier content management

10.2 improves the user experience for managing several types of content:

• Field types for new fields are visually listed instead of a simple select list. Settings for fields are now all included on one form.
• Menu items and taxonomy terms have a dedicated option to add a child item, which makes item placement easier.
• Media items now have a dedicated user interface to review and manage older revisions.
• CKEditor's language selector can now be configured to only show languages supported on the site.

More flexible block placement

A user interface has been added to show or hide each block based on the HTTP response status, so that specific blocks can be added or removed when the page is not found (404) or access is denied (403).

New built-in file name sanitization options

The functionality of one of the most popular contributed modules is now included in core! Replace whitespace in file names, transliterate text, convert to lowercase, and more.

Faster permission management

The permissions page now comes with a filter on the top to make it easy to find the permission you planned to adjust.

Performance improvements

Drupal 10.2 includes numerous performance improvements for content rendering and HTTP responses, as well as improved caching APIs.

Works on the latest PHP

PHP 8.3 was released three weeks ago, and Drupal 10.2 is already compatible with it.

Modern language feature: PHP attributes

Drupal core has started adopting PHP attributes, a modern PHP language feature, to provide better developer experience for plugin annotations. Contributed and custom code can begin adopting this improved API for their plugins, and Block and Action plugins can all be converted to the new API.

Built-in project news updates

To help keep you up to date with project news, the Announcements Feed module became stable and is now installed by default with the standard profile.

Help topics now in Help module

The experimental Help topics module is now marked as deprecated and all functionality has been integrated into the core Help module.

Developer experience improvements

Drupal 10.2 comes with a number of developer experience improvements:

• A PerformanceTestBase was added to support automated testing of performance metrics with support to send OpenTelemetry traces to an open telemetry endpoint.
• A new DeprecationHelper::backwardsCompatibleCall() method is available that helps write Drupal extensions that are compatible with multiple major versions at once.
• PHP Fibers support was added to BigPipe and the Renderer, which allows Drupal to potentially run different code while it's waiting for an asynchronous operation to return.
• Configuration validation was expanded to better support strict testing and make configuration form validation easier to implement.
• Symfony's autowiring support was adopted for services, based on PHP 8 attributes, making service creation easier.
• The HTML utility classes and filter system was updated to produce HTML5 syntax instead of XHTML.

Core team updates

Drupal is built by an open source community of collaborators across geographies and organizations. Maintainers assess the work of the community and decide when it's ready to commit to Drupal core. After a period as a provisional committer, Dave Long (at Full Fat Things) was promoted to a full release manager. Kristiaan Van den Eynde (at Factorial) and Adam Bramley (at PreviousNext) have also become core subsystem maintainers. Thanks for stepping up!

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, or join us at DrupalCon Portland and attend sessions, network, and enjoy mentorship for your first contributions.

New major release schedule

Beginning with Drupal 10, a new Drupal major version will be released every two years in even years (2022, 2024, etc.). Each major version will receive active support for about two years, followed by maintenance support and security coverage for about two more years. Each is supported until two more major versions have been released.

This is an example. The exact schedule varies, and will be published on the Drupal core release schedule.

Drupal 11 will be released in 2024

Drupal 11 will be released sometime in 2024. Like Drupal 9.0 and 10.0, Drupal 11.0 has three potential release windows, in June, August, and December. The window used will depend on when the beta requirements are complete. For more information, refer to the Drupal core release schedule.

Drupal 11 alpha development opens this week

Following the release of 10.2.0-beta1, changes to 11.x that diverge from Drupal 10 under the continuous upgrade path will begin. Anyone can get involved in completing the requirements for Drupal 11. Join the #d11readiness channel in the Drupal community Slack.

Maintenance minor versions of Drupal 10

Following the release of Drupal 11.0.0 in 2024, a long-term support phase for Drupal 10 begins, and it will include a new maintenance minor every six months. Each maintenance minor will contain a limited set of changes backported from Drupal 11. For more information, refer to the Drupal core release process overview.

Use a supported PHP version for the best ongoing support

Maintenance minor releases for Drupal 10 will keep adding support for newer PHP versions as they are released. The minimum supported PHP version for Drupal core follows the PHP core team's support cycle. (Reference: What does it mean for a PHP version to be supported?)

Site owners wishing to take advantage of Drupal 10's long-term support phase should ensure their platforms always use PHP versions supported by the PHP maintainers.

Announcement written in collaboration by Dave Long, Jess (xjm), Nathaniel Catchpole and Victoria Spagnolo.

Completed Drupal site or project URL: https://www.accelerazero.com/Enabling the clean energy revolution

A recognized global leader as the largest independent engine manufacturer, Cummins Inc. was ready to boldly showcase its leadership in a new domain: zero-emissions technologies.

In support of a strategic commitment towards a net-zero future, Destination Zero, Cummins needed a new digital presence. The Accelera by Cummins brand was conceived to power the world’s hardest-working industries with clean energy and reach net-zero emissions by 2050.

Drupal 9 is end of life as of November 1st, 2023

Drupal 9 relies on several other software projects, including Symfony, CKEditor, and Twig. With Symfony 4's end of life, CKEditor 4's end of life, and Twig 2's end of life all coming up soon, Drupal 9 went end of life on November 1st, 2023. There will be no further releases of Drupal 9.

Two changes for Drupal contributed projects will occur before the end of January 2024. One is that the automated testing platform DrupalCI support for Drupal 9 will stop. The other is that release branches of contributed projects that only support Drupal 9 will be marked unsupported (see the tracking issue for details).

Thanks to everyone who helped create and maintain Drupal 9.

It is time to update to Drupal 10 compatible releases If you are a site owner

Check the documentation on updating a site to Drupal 10.

If you maintain contributed projects

If a contributed project is not yet compatible with Drupal 10, now is a good time to update it. Check for existing Drupal 10 compatibility issues relevant for your projects.

If your project is already compatible with Drupal 10 but does not yet have a stable release, please tag a release, once you are confident in your project's stability. Where possible, tag a minor release supporting both Drupal 9 and 10 to ensure users have a smooth upgrade path.

The Drupal Association is saying goodbye to three board members and welcoming four new members who will join the Drupal Association Board.

First off, the Drupal Association extends a sincere thank you to Mike Herchel, Ryan Szrama, and Board Chair Baddý Sonja Breidert for their service and dedication not only to Drupal but to the Drupal community. Thank you for everything you have done while on the Drupal Association Board! Your time spent on the board made such a difference to the future of the Drupal project, and we thank you all for participating with grace, thoughtfulness, and insightful contributions.

We are also excited to announce that Baddý will continue as a non-voting Immediate Past Chair on the Executive Committee for one year.

The Drupal Association would now like to congratulate our newest board members, officially announced during the recent public board meeting at DrupalCon Lille:

Imre Gmelig Meijling

Lenny Moskalyk

Piyush Poddar

Fei Lauren

An additional congratulations to Fei Lauren for winning the community-elected seat during our 2023 At-Large Board Election! We cannot wait to see what amazing things Fei will accomplish while on the Drupal Association Board. We invite you to get to know Fei and learn more about their background in our ‘Meet Fei Lauren’ blog post. 

I am deeply honoured to have the support of so many brilliant people - and I can’t wait to see what we can accomplish together." - Fei Lauren

We extend our gratitude to all the candidates who participated in the 2023 election. On behalf of all the staff and board of the Drupal Association, a heartfelt Drupal Thanks to all of you who stood for the election this year. It truly is a big commitment to contribution, the Drupal Association, and to the community, and we are so grateful for all of your voices. Thank you for your willingness to serve, and we hope you’ll consider participating again in 2023!

Detailed Voting Results

There were 10 candidates in this year’s At-Large board member election.

477 voters cast their ballots out of a pool of 2,873 eligible voters.

Under Approval Voting, each voter can give a vote to one or more candidates. The final total of votes was as follows:

Candidate

Votes

Fei Lauren

156

Matthew Saunders

144

Mark Dorison

126

Vladimir Roudakov

113

John Doyle

107

Ashraf Abed

104

Carlos Ospina

101

Esaya Jokonya

86

Stephen Mustgrave

85

Brad Jones

77