Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Apr 02 2021
Apr 02


The goal of this survey was to better understand the preferences of organisations and individuals who are already building decoupled applications in order to help inform the decisions we make going forward. The survey was executed using Survey Monkey and was promoted primarily via existing Drupal developer channels. The survey ran for 2 weeks, and received a total of 133 responses.

This analysis and post where created by Baddý Breidert, Liam Hockley, and Joe Shindelar with support from others in the community.

Below are some of our initial findings from looking at the results. And we anticipate coming back to this data later to help better understand the needs of existing decoupled application developers.

You can learn more about the Decoupled Menus Initiative, and come say hi on Slack in #decoupled-menus-initiative.


Q1: How many years have you been building decoupled applications?

Question 1 - Graph showing count of Responses
Caption: Question 1 - Graph showing count of Responses
Question 1 - Table showing count of responses
Caption: Question 1 - Table showing count of responses

These results show a significant amount of users in the 1-3 year range, this is somewhat expected given how the growth of frameworks like Vue, React, has accelerated in the past few years. A notable amount of users have been building decoupled sites for longer than 3 years, perhaps a sign that we have almost 30% of our responses being early adopters?

Q2: Which CMSs do you use?

Question 2 - Graph showing CMS usage
Caption: Question 2 - Graph showing CMS usage
Question 2 - Table showing CMS usage responses
Caption: Question 2 - Table showing CMS usage responses

The overwhelming number of responses are Drupal users. This was a multiple choice question, and there were only 9 respondents who did not list Drupal. Given how the survey was marketed largely to our existing networks this isn’t surprising. It is worth remembering, however, that these results are going to be heavily skewed towards the thoughts of existing Drupal users.

In the future we need to find more ways to engage with users outside the Drupal bubble if we want to learn what is required to make Drupal an attractive platform for them.

Q3: Which JS frameworks do you use?

Question 3 - Graph showing which JS frameworks are being used
Caption: Question 3 - Graph showing which JS frameworks are being used
Question 3 - Table showing which JS frameworks are being used
Caption: Question 3 - Table showing which JS frameworks are being used

It is clear that React is certainly favored among out participants, with Vue being a fairly close second. Other frameworks do not have a lot of representation. These results indicate that we should make efforts to ensure that we cater to both React and Vue users, with other frameworks being secondary concerns in terms of support?

According to the 2020 State of JS survey 80% of JavaScript developers use React, and 49% use Vue. That’s a much larger difference than what we see in our data. And maybe indicates that there’s a stronger attraction to Vue amongst Drupal users than in the general JS world. Which may be worth noting when making decisions using these numbers. Also, Angular has 56% usage, higher than Vue, in the State of JS survey but only 17% amongst Drupal users.

The Next/Nuxt frameworks are used by ~30% of React/Vue developers. This is something we should be aware of. And at least ensure that our solutions are compatible with these tools with minimal fuss.

Q4: Which JS (nodejs) tooling do you use?

Question 4 - Graph showing which JS (nodejs) tooling are used
Caption: Question 4 - Graph showing which JS (nodejs) tooling are being used
Question 4 - Table showing which JS (nodejs) tooling are being used
Caption: Question 4 - Table showing which JS (nodejs) tooling are being used

NPM is the most widely used nodejs tool which isn’t too shocking. We didn’t have an option for Yarn, but it was written in the other response 10 times. It is probably safe to say that a majority of our user base still prefer to use NPM as their package manager. Webpack and Gulp use should not be ignored as it looks like these are the two most prevalent node build tools.

This lines up with the broader JavaScript ecosystem where the State of JS data indicates that both NPM and Webpack are nearly ubiquitous among JavaScript developers.

One thing this data doesn’t tell us is what tooling people *want* to use. And it may be worth trying to dig into that more. Especially if the goal is to be an attractive platform for developers. We should be aware of both what tools are most common, but also what tools people prefer.

Q5: Which API technologies do you use?

 Graph showing which API technologies are being used
Caption: Question 5: Graph showing which API technologies are being used
 Table showing which API technologies are being used
Caption: Question 5: Table showing which API technologies are being used

A healthy mix of API technologies are being used here, but again it may be worth noting that a lot of our Drupal users are using JSON:API by necessity as it is the primary way Drupal is used as a REST API. We shouldn’t ignore that over 50% of respondents are using GraphQL, this may or may not be in the context of Drupal, but it does signify that there may be a desire to use this for retrieving decoupled data?

Q6: Which data fields or properties do you believe are essential to render a menu component?

Question 6 - Table showing responses of which data fields or properties are essential to render a menu component
Caption: Question 6 - Table showing responses of which data fields or properties are essential to render a menu component

A surprising result here is that the Active Trail is not a priority to our users. Menu Hierarchy and Multilingual being the most important means that we need to ensure that we are able to cleanly deliver the menu tree data, along with appropriate translation data.

Q7: What is the best experience you have had when working with menu responses?

This was an open-ended question and received 42 write in answers.

There was some interest in Gatsby. Some narratives included:

A recent menu integration with Gatsby worked well - we accessed menu data via gatsby-source-Drupal and then exported these components using webpack along with their data. This allowed us to use the exact same React footer in pages rendered by Drupal and Pages rendered by Gatsby.

Gatsby, with the `activeMenuClass` and `partiallyActive` features, makes it soooo easy to have an active menu and active trail.

We saw some interest in GraphQL, with responses like: 

On the backend we used the GraphQL Drupal module and declared a schema, following the documentation (https://drupal- graphql .gitbook.io/graphql/queries/menus) On the frontend, using Apollo we would just query the menu and then render that into a custom component.

Using the graphql Drupal module with Next.js. The only thing that we had to do was made a query by menu name to Drupal, the response was an array of items of type { link, label, children: [] }

Writing a custom GraphQL resolver for Drupal 9 that returns exactly what I need.

Which highlights that a handful of respondents have been reaching for GraphQL in order to provide a simple data -> frontend flow.

The answers to this question highlight that right now, in order to manage menus using Drupal in a decoupled scenario, people are invariably crafting their own solutions. That people have been able to make things work. And that at best the experience has been fine, and at worst it’s frustrating. People have used a range of approaches including; Using data available in the existing JSON:API output, custom GraphQL resolvers, putting the content of a menu into a custom block and consuming that block, using the jsonapi_menu_items module in contrib, and hard-coding menus into the front-end, and more.

This indicates that there is definite potential for standardization and providing a built-in solution so that people don’t have to reinvent the wheel with every new project. And, some people mentioned having already started work on their own reusable solutions to this problem.

Another common thread in these answers is that most people’s custom solutions involved creating the data in Drupal in some way (custom block entity, GraphQL resolver, jsonapi_menu_links) so that the front-end application could consume the entire menu in a single response that contained titles, links, and hierarchy. This desire to be able to construct a single menu object in the UI was also mentioned in answers where people talked about non-Drupal menu building experiences.

Netlify Menus, set a collection of type Menu, and edit the links. That's the easiest way. For Drupal is not a big deal but separated fragments have to be done in order to pull just those entities.

Q8: How do you use API data to build a Menu Component?

Question 8 - Table showing responses of how do you use API data to build a Menu Component
Caption: Question 8 - Table showing responses of how do you use API data to build a Menu Component

Early analysis of the results, we found this to be a trend which has held. This is quite surprising, given the bounty of available frameworks out there. But it perhaps illustrates either the challenging nature of adapting drupal menu data to a framework, or the demands of clients that need more flexibility than frameworks are able to provide?

Q9: What expectations do you have for Documentation, when working with a headless CMS?

Question 9 - Table showing responses of expectations for Documentation, when working with a headless CMS
Caption: Question 9 - Table showing responses of expectations for Documentation, when working with a headless CMS

We think that quality documentation will be an important part of improving the experience for JavaScript developers consuming data from Drupal APIs. And are already planning on making that a focal point of the work we do in this initiative. Based on the results we clearly need to make sure that code snippets and a getting started guide are part of whatever we create.

Based on the result of question 3, it seems that we should also attempt to provide these code snippets in both React and Vue variations.

Q10: Describe the biggest challenges you encounter when building a project with Decoupled/Headless CMS

This was an open ended question and received 63 responses.
What appears to stand out here are the words Drupal, data, menu, and routing. This probably indicates that the data and routing are challenges that we will want to make sure we address. Drupal and menu are terms that are probably used in a majority of responses without negative or positive context, per se. We could dive into some of the direct response texts in order to attain a better idea of the context in which these terms are being used.


The survey results indicate that people view code snippets, and a getting started guide, as a critical part of the documentation we produce. We should try and further define what awesome examples of these look like so we know what to aim for.

We’re aware that the results of this survey for the most part only reflect people who are already engaged with the Drupal community. Since part of this initiative’s goals are to help make Drupal a more attractive platform for JavaScript developers who are not already part of the Drupal community we’ll have to make sure and do the work of connecting with those people. It’s important that their voices are heard and that we don’t build solutions in an echo chamber.

Mar 16 2021
Mar 16

Last week, we posted about the new starterkit custom theme creation process and base theme with the goal of replacing Classy in Drupal 10. Yesterday Lauri Eskola demonstrated the current status of the starterkit at the Drupal 10 meeting. Check out the recording and post your feedback in the issue.

Discuss in the #frontend channel on Drupal Slack too. Drupal 10 readiness meetings are every other Monday at 19:00 UTC in the #d10readiness.

Participate in the Drupal 10 readiness day at DrupalCon North America 2021 to learn even more and get mentored contributing to starterkit.

Mar 11 2021
Mar 11

Peter Weber leads CKEditor 5 integration development for Drupal 9.

While Drupal 9 already comes with CKEditor 4, that will go end of life in 2023, so we need to upgrade to CKEditor 5 to provide this replacement for Drupal 10. The target release date for Drupal 10 in June 2022 (in 15 months!). We plan to add CKEditor 5 integration to Drupal 9 even sooner though, to help the Drupal contributed ecosystem catch up and prepare in time.

There are various moving parts and several items left on the roadmap for beta level core inclusion. Peter presented a demo today to showcase where the current state stands primarily to get more feedback about the developer interface. A simple infobox CKEditor 5 plugin was also showcased to asses the integration developer experience. Check out the video recording here:

Discuss in the #ckeditor5 channel on Drupal Slack. CKEditor 5 integration meetings are every other Thursday at 15:30 UTC in the same channel.

Participate in the Drupal 10 readiness day at DrupalCon North America 2021 to learn even more and get mentored contributing to the CKEditor 5 integration.

Mar 11 2021
Mar 11

Drupal has been providing subtheming capabilities for over a decade. When you create a theme for Drupal 8 or 9, a best practice is to subtheme the core Classy theme, so you get common CSS classes and usual markup for a Drupal site. This means the Classy theme is used in the runtime as part of your theme. As a consequence, Classy has not been receiving updates since Drupal 8.0.0, because most changes are not possible while retaining backwards compatibility. We need to retain backwards compatibility because design requirements of themes depending on Classy could depend on markup and/or CSS provided by Classy.

To solve this problem, we are working on a new custom theme creation process and base theme with the goal of replacing Classy in Drupal 10. 

The new starterkit theme we are working on is not going to serve as a base theme to be subthemed, but rather a theme to be copied on a new theme's creation. It will allow front-end developers to get a copy as a starting point for their theme. Tooling is provided as part of the included Drupal command line interface for automating this:

php core/scripts/drupal generate-theme mytheme

We believe that this new process will serve front-end developers better because it will allow us to provide more frequent updates to the default markup and CSS shipped as part of Drupal core.

Subtheming as a concept will continue to exist even after this change. This is valuable in particular in cases where themes are inheriting design and ideas from the base theme. For example, a university could have a base theme that provides design concepts and basic layout to all of their departments. That base theme could be generated using the starterkit theme:

Starterkit theme means forking the base theme instead of extending it runtime

We believe starterkit theme will serve majority of our use case better, because most custom themes are based on bespoke designs that aren’t a good fit for subtheming an opinionated theme. Since fully custom themes customize many aspects of the theme, it is difficult for the base theme to ship improvements to the subtheme without risking regressions in the subthemes.

We would like to hear your thoughts on the new starterkit theme on this Drupal core issue to add a new starterkit theme. If you have questions about the new starterkit theme, feel free to get in touch with us in Drupal Slack (https://www.drupal.org/slack) #d10readiness and #frontend channels.

We are doing a live demo of the starterkit on the next Drupal 10 readiness meeting which is taking place on #d10readiness channel in Slack on 16th March, 19:00 UTC. 

Thank you to @Gábor Hojtsy for help writing and reviewing this blog post.

Feb 24 2021
Feb 24

We plan to release Drupal 10 in 2022, ideally in June. That means there are 15 months left before the new major release is expected to be available. I provided an update about the initiative last time in December at DrupalCon Europe. I wanted to give a quick update on some of the highlight areas we are working on. Join the discussions and help shape Drupal 10's direction every other Monday at 19:00 UTC in the #d10readiness channel on Drupal Slack.

All work is done in Drupal 9 for now

The same way we built most of Drupal 9 in Drupal 8, we are building Drupal 10 in Drupal 9 as much as possible. There is one key exception, the CKEditor 5 project is being built as a contributed module to help test it and make it easier to collaborate on.

PHP 8 and Composer 2 support shipped

Both shipped in Drupal 9. Composer 2 support was even backported to Drupal 8, but that was not possible for PHP 8 compatibility. We plan to require PHP 8 for Drupal 10 given the end of life of PHP 7 in November 2022.

Symfony 5 support is good, Symfony 6 support in the works

One of two main drivers of the Drupal 10 timeline is Symfony 4's end of life in November 2022. We plan to update to at least Symfony 5. We did resolve all known Symfony 5 compatibility issues to date, so that looks promising.

While in Drupal 10's time, Symfony 5 will be on the long term supported 5.4 branch, that would "only" be security supported until November 2025, giving Drupal 10 a 2.5 year lifetime. To possibly expand this, we are exploring to update to Symfony 6 and resolving incompatibilities identified in Drupal 9 already. Symfony 6 development is not itself open yet, so we are only able to work on things that are already deprecated.

CKEditor 4 to 5 update needs more hands

The other big motivation behind the Drupal 10 timeline is CKEditor 4 support lasting until 2023 only. CKEditor 5 support is being worked in a dedicated contributed module for now. We are collaborating heavily with the CKSource team on runtime plugin support (Webpack DLLs), general HTML support (to avoid data loss when using CKEditor 5 on legacy content), etc. There are various great benefits of CKEditor 5 including optional collaborative editing functionality (using a paid server component).

We need more people involved in this. Dedicated CKEditor 5 meetings happen every other Thursday in #ckeditor5 on Drupal Slack at 15:30 UTC.

Starterkit theme prototype needs feedback

This is a Drupal theming paradigm shift! While inheriting from runtime base themes have served us well to avoid duplication, it causes serious problems for innovation and makes us supporting old bugs to not break live sites. So instead we aim to provide built-in support for generating a theme in core that is based off of a prepared starterkit: php core/scripts/drupal generate-theme . Lauri prototyped an initial solution, needs more feedback.

jQuery UI components have replacements prototyped, need reviews

Practically all of the jQuery UI components as well as various uses of Backbone.JS have replacements prototyped: dialog, toolbar, tabbing manager, autocomplete, tours, etc. All of them are in need of serious feedback though and testing.

Internet Explorer 11 support will be dropped

An agreement has been made to drop support for IE11 from Drupal 10. The official announcement is forthcoming.

Some one-off feature modules will likely be removed

We already agreed to deprecate aggregator module in Drupal 9 and remove in Drupal 10. There will possibly be other single-use core modules removed that lack maintainers and momentum. Work is underway to indicate individual module lifecycle states, although this needs more help soon for us to be able to use it to deprecate modules in time.

Drupal 10 readiness day at DrupalCon North America

The above were just some of the highlights we are working on. DrupalCon North America 2021 is online and will focus one of the days on Drupal 10 readiness. We submitted various in-depth talks to illuminate further details of the above areas and more. Join us there and use the opportunity to be at the forefront of the new version.

Dec 07 2020
Dec 07

As part of the Drupal Association’s ongoing mission to foster contribution in the Drupal project, we're bringing you the first edition of a new Initiative Update blog series. The vision is a series with regular updates on initiatives across the Drupal ecosystem, as well as calls to action highlighting where contributors are most needed.

In gathering feedback from the community, we understand it can be difficult to identify the priorities of the Drupal community, the state of current initiatives, and how to contribute. Our goal is to provide a useful overview of current priorities in Drupal and connect you to the individual mentors, initiative leads, and other community organizers who can help you get involved. 

The plan is to provide updates on a regular basis throughout the year. We thank the Wordpress community for their example of a concise initiative update. Based on your feedback on this first edition, this format may evolve. 

If we missed reaching out to you, but you'd like to provide an update on an initiative you are involved in, please feel free to submit your update to this form.


In this release, we have reports from the following initiatives and community groups. This is not a comprehensive list of all initiatives and community groups, just those who were able to provide an update in time for this post:

Active Drupal Core Initiatives

Mike Herchel updates us about Olivero - the new front-end theme

About this Initiative: The New Front End Theme initiative seeks to create a new default front-end theme for Drupal with a modern look and feel.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Getting into core! We're finally in 9.1 as a beta experimental theme. Check it out!

What has been your greatest challenge in the last three months?

Getting it into core was a mad dash at the very end, but we pulled it off thanks to a lot of help from Drupal's core contributors. Those folks are amazing! 

And what has been your greatest success in the last three months?

Getting into a beta status for core

Do you have a "call to action" you want to make to the Drupal Community?

Use it. Find and file bugs!

xjm updates us about Drupal 10 Readiness

About this Initiative: The goal of the Drupal 10 Readiness initiative is to release Drupal 10 in 2022, providing adequate time to update sites while keeping Drupal secure and up to date.

Where can we read more about your initiative?


What have been your priorities in the last three months?

  1. Ensuring that Drupal core is internally compatible with Symfony 5.0 and 5.1 (without using deprecated APIs), so that we can easily release Drupal 10 with a dependency on Symfony 6. (Done!) 
  2. Ensuring Drupal core and its upstream dependencies are fully compatible with PHP 8 as soon as possible so that Drupal 10 can set its minimum dependencies accordingly. (Done!) 
  3. Initial discovery on CKEditor 5 integration for Drupal 10 (Ongoing, challenging) 
  4. Replacing remaining forked jQuery UI code with modern alternatives (Ongoing) 
  5. Reducing jQuery use for an easier upgrade to future versions

What has been your greatest challenge in the last three months?

We have lots of JavaScript work needed, both for integrating CKEditor 5 and for reducing legacy jQuery and jQuery UI use, and few working on it these difficult problems.

And what has been your greatest success in the last three months?

Really great collaboration and problem-solving for upstream blockers to PHP 8 compatibility, and all compatibility issues with Symfony 5 are resolved, We’re now working on Symfony 6 compatibility (that is, addressing deprecations introduced in Symfony 5.1 and 5.2), which is the real goal for us for Drupal 10’s release.

Do you have a “call to action” you want to make to the Drupal Community?

Frontend contributors! We love you and we need your help!

We need help with several big changes related to core’s JavaScript: 

Furthermore, we need help from theme developers and contributors to join a new initiative to build a Starterkit Theme for Drupal core. https://www.drupal.org/project/drupal/issues/3050384 This theme starterkit will replace Classy as the best way to start building a theme for a Drupal site.

Tim Lehnen provides the latest info about Automatic Updates

About this Initiative: The goal of the Automated Updates Initiative is to provide a system to easily and securely update Drupal sites, reducing total cost of ownership for site owners. 

Where can we read more about your initiative?

The best place to stay up to date is in the Automatic Updates issue queue, or by joining us in the #Auto-Updates channel in Drupal Slack.

What have been your priorities in the last three months?

Current Priority: Finishing our implementation of the php-tuf client and server code, so that we can move from our secure signing implementation into our actual updater code. 

Previous Priority: Over the course of the last quarter, the Drupal Association hosted three contribution weeks with Drupal initiative contributors as well as representatives from Joomla and Typo3. We used these contribution sessions to scaffold out the php-tuf library and to align our architectural decisions in ways that will work across the php ecosystem. 

What has been your greatest challenge in the last three months?

Our update process must run the appropriate Composer updates as well, so we are currently attempting to architect a solution to account for the fact that Packagist itself does not yet have a signing solution for third party libraries. 

And what has been your greatest success in the last three months?

The Drupal Automatic Updates initiative has joined forces with both the Typo3 and Joomla communities to share certain foundational components, like our secure signing schema. And speaking of secure signing, we are working closely with the Cloud Native Computing Foudnation's TUF initiative for a robust and standards based signing solution. 

Do you have a "call to action" you want to make to the Drupal Community?

If you're interested in the problem-space of securely signing software, consider contributing to the php-tuf project. If you're more interested in understanding the update process itself, please join us in the Drupal Slack channel!

About this Initiative: The goal of the Decoupled Menus Initiative is to provide the best way for JavaScript front ends to consume configurable menus managed in Drupal.

Where can we read more about your initiative?

The Decoupled Menus Initiative is in the process of organizing the official initiative team. Regular meetings are happening in the #decoupled-menus-initiative in Drupal Slack.

What have been your priorities in the last three months?

The main priority for the initiative has been gathering the initial group of contributors and getting organized. There is a clear path for understanding what a javascript menu component looks like, but there are much more challenging questions to be resolved about how to integrate non-php components into the Drupal core process. 

What has been your greatest challenge in the last three months?

This initiative is in the first stages of getting organized and up to speed. In addition, understanding how to work on non-php for Drupal core is a major challenge. Once official initiative coordinators have been selected they can help to provide the next update.

And what has been your greatest success in the last three months?

Just launching this initiative as an official goal is greatly important. There has been very active conversation between initiative team members, core maintainers, and the drupal association as the organization kicks off. 

Do you have a "call to action" you want to make to the Drupal Community?

If you are an expert in using a javascript front-end for a Decoupled Drupal solution, if you are familiar with open source contribution in the javascript ecosystem, or if you are a competent project manager your insight would be valuable. Please join the initiative's slack channel and regular meetings.

Additional Core Initiatives, Community Initiatives, and Community Group Updates

Jennifer Hodgdon updates us about Documentation and Help

About this Initiative: The goal of the Documentation and Help initiative is to improve the Drupal evaluator, developer, and site builder experiences through improved documentation on Drupal.org, and improve in-application help via a new topic-based help system.

Where can we read more about your initiative?

User Guide: https://www.drupal.org/project/user_guide; Contributor Guide: https://www.drupal.org/community/about/getting-involved-guide-becoming-contributor-guide; Help Topics: https://www.drupal.org/project/drupal/issues/3027054

What have been your priorities in the last three months?

User guide: minor updates and supporting groups making translations. There has been a lot of progress lately on German and French! Help topics: mostly writing new topics, and some progress on other Roadmap issues. 

Contributor Guide: Migrating content from the old Getting Involved Guide.

What has been your greatest challenge in the last three months?

Getting other contributors to review and commit patches, and to provide feedback on plans.

And what has been your greatest success in the last three months?

Migrating most of the content in the Getting Involved Guide to make several new and better-organized areas, such as the Issues documentation at https://www.drupal.org/docs/develop/issues and the Git documentation at https://www.drupal.org/docs/develop/git

Do you have a “call to action” you want to make to the Drupal Community?

You can help with curating and migrating older documentation into the newer documentation content types, or into the new Contributor Guide. Join the #documentation channel in Drupal Slack and another contributor can help you find a place to get involved. 

Elli Ludwigson updates us about Contribution Mentoring

About this Community Group: The Contribution Mentoring Group works to inspire, enable, and encourage new contributors. They also work on the core tools, process, and community to make it easier for new contributors to get involved.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Getting ready for DrupalCon Europe, updating documentation and materials

What has been your greatest challenge in the last three months?

Engagement. It's been difficult to demonstrate value and a clear path to success for contributors and mentors. Also, everyone seems a little low on energy lately and we could use more fresh folks coming into leadership roles.

And what has been your greatest success in the last three months?

Updating the contributor guide! http://drupal.org/community/contributor-guide  

Jennifer Hodgdon and others have reorganized and made everything much more logical. AmyJune continues to do an amazing amount of work at many many virtual events, giving contributors a place to get started with Drupal.

Prior to the last three months Rachel Lawson did a lot to rethink the contribution and mentoring process with the portal we used at DrupalCon Global. Matthew Radcliffe and Gábor Hojtsy did a lot of work on that as well. And Randy Fay is often on hand to help with any and all local development environments and general Drupal troubleshooting.

Do you have a "call to action" you want to make to the Drupal Community?

Without creating any new projects, I'd say we could use an enthusiastic and experienced person to help clean up old issues and polish the documentation work. We could also use more mentors on hand in general for virtual events across various time zones, especially outside the Americas.

Kaleem Clarkson updates us about Event Organizers Working Group

About this Community Group: The Event Organizers Working Group (EOWG) is concerned with supporting community-led events within the Drupal community. These include camps, summits, training days, contribution days, and meetups.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Over the last three months we have mostly focused on finalizing what initiatives we should start with in 2021. 

What has been your greatest challenge in the last three months?

Our greatest challenge has been attracting more global representation at our monthly community meetings. At the beginning of this year, our group made an intentional effort in attracting more global participation. Through our efforts, we were able to recruit two new board members representing India and Ukraine. Another strategy was to change our meeting times to UTC format and alternate between 12pm and 12 am UTC. We are hoping that in 2021 we can increase the number of global camps represented in our open meetings. 

And what has been your greatest success in the last three months?

I think our biggest accomplishment has been confirming our four major initiatives that our group will focus on in 2021. These initiatives will be:

  • Onboarding At DrupalCon Community at Events, 
  • Event Organizers Website Starter Kit
  • Marketing the Events Organizer Group
  • Events Database Website on Drupal.org. 

Each initiative will have committees made up of one Event Organizer’s Working Group board member and volunteers from the Drupal community. For so many reasons, we are all looking forward to working in concert with event organizer volunteers from around the world.

Do you have a “call to action” you want to make to the Drupal Community?

We need all Drupal event volunteers to help spread the word about the Drupal Events Working Group. 

We will be looking for volunteers to serve on the committees of each of our four major initiatives and we can’t do it without you. 

Jess Snyder updates us about Nonprofits

About this Community Group: The Nonprofits Community Group provides a gathering point for all Nonprofit organizations using Drupal, and leads monthly community meetings.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Our top priority continues to be to provide a welcoming place for nonprofit Drupalists to get advice, share knowledge, and discuss the issues we’re all facing in this challenging time.

What has been your greatest challenge in the last three months?

Aside from dealing with the curveballs the past several months have thrown at all of us, nonprofits continue to struggle with the changes in Drupal requirements that have increased the expertise and costs required to build and maintain Drupal sites.

And what has been your greatest success in the last three months?

Aside from seeing new faces on our monthly calls, which we’re always thrilled about, we’re also proud of how our community is encouraging nonprofit orgs to try new features, like Layout Builder, while also discussing the challenges that come with trying new features that are still in flux.

Do you have a “call to action” you want to make to the Drupal Community?

Come and join our monthly call! Held on the third Thursday of the month at 1pm ET/10am PT, it’s free of charge, beginner-friendly, and open to anybody working for or with nonprofits and Drupal. 

Call-in info can be found on our community page (https://www.drupal.org/community/nonprofit-drupal) or in our collaborative notes document (https://nten.org/drupal/notes).

Nico Grienauer updates us about Drupical

About this Initiative: Drupical is a beautified overview of Drupal Events that provides a bird’s-eye view of Drupal community events happening all over the World. 

Where can we read more about your initiative?


What have been your priorities in the last three months?

Getting the new drupical 2.0 ready for launch

What has been your greatest challenge in the last three months?

Finding time beside the global covid problems 

And what has been your greatest success in the last three months?

  • Getting finally access to drupal.org/community/events
  • Finalising the first version of the new drupical fronten now in vue.
  • Getting work done on the new drupal 8/9 drupical backend – found a possible solution, to also display online events on a map :)
  • Getting a link from the drupal main menu to drupical. 

Hopefully it will all be released in time for DrupalCon Europe!

Do you have a “call to action” you want to make to the Drupal Community?

stay healthy, stay at home and see you at one of the next virtual Drupal events!

Chris Teitzel updates us about the Privacy Initiative

About this Initiative: The Privacy Initiative focuses on addressing the increasing importance of managing user privacy in a world with increasing regulation. While the Drupal ecosystem has previously relied on solutions in contributed modules, this initiative proposes Privacy changes in Drupal Core. 

Where can we read more about your initiative?


What have been your priorities in the last three months?

We are continuing to work with the community and project stakeholders to come to a plan for a privacy initiative and/or team that can be involved in core conversations to ensure privacy is taken into account with core features and initiatives. 

What has been your greatest challenge in the last three months?

Funding of the initiative is the next hurdle to jump after receiving confirmation from Dries that he still desires it to be an initiative.

And what has been your greatest success in the last three months?

Receiving confirmation from Dries that he still desires it to be an initiative!

Do you have a "call to action" you want to make to the Drupal Community?

Continued support and talking to maintainers about the need for a formal privacy team/initiative within the community, as well as sponsorships; any individual or organization can be involved.

Tara King updates us about Drupal Diversity & Inclusion

About this Community Group: The Drupal Diversity & Inclusion group seeks to continue the conversation about diversity and inclusion within Drupal. The group organizes regular meetings and curates a resource library.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Drupal Diversity & Inclusion has been working on: 

  • Defining our roles & responsibilities: https://www.drupaldiversity.com/docs/roles-and-responsibilities
  • Recruiting new leaders to our leadership team
  • Holding space for our community to discuss diversity & justice
  • Planning social events for marginalized individuals
  • Developing talks & booth activities for Drupal events (most recently BADCamp)

What has been your greatest challenge in the last three months?

2020 has been our greatest challenge. :)

We have struggled with volunteer burnout, due to both COVID-19 and the US election cycle. Many folks have very limited time to give and even less energy, so we have focused on activities that support folks rather than new programming. 

And what has been your greatest success in the last three months?

We are thrilled to have three new individuals on our leadership team: Tearyne Almendariz as Careers Lead (https://www.drupal.org/u/ninelivesblackcat), Monica Flores as Resources Contributor (https://www.drupal.org/u/monicadear) and Esaya Jokonya as Booth Contributor (https://www.drupal.org/u/esayaj). 

Do you have a “call to action” you want to make to the Drupal Community?

Please join our meetings! We are making 2021 plans, and focusing on careers & job hunting for marginalized folks. We’d love to have more hiring managers and HR professionals involved in that work. Bring your ideas and we can work together to make the Drupal community more diverse & inclusive.

Alex Moreno-Lopez updates us about Drupal Swag Shop working group

About this Community Group: The Drupal Swag Shop working group is an initiative to offer sustainably sourced Drupal branded merchandise that both promotes Drupal and generates revenue for the Drupal Association.

Where can we read more about your initiative?

https://www.drupal.org/project/swagshop and, of course, visit the Swag Shop itself, at https://www.drupal.org/swag

What have been your priorities in the last three months?

On one hand, helping local DrupalCamps and DrupalCon to collaborate with the shop. On the other hand we’ve been trying to make sure the products available were event specific.

What has been your greatest challenge in the last three months?

Coordinating information and people, and particularly everything related to vouchers, discount codes has been particularly challenging

And what has been your greatest success in the last three months?

Watching other Drupal camps getting interested in using the swag shop and discovering that it gives them a good value as well. For example, NedCamp: https://nedcamp.org/

Do you have a “call to action” you want to make to the Drupal Community?

We need more people to talk about the initiative, and if you know a local camp, encourage the organisers to join the initiative.

Rain Breaw Michaels updates us about Accessibility

About this Community Group: Drupal's official Accessibility maintainers, as well as a number of community experts in accessibility issues focus on ensuring that all other features and initiatives within Drupal maintain our commitment to accessibility for all.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Our main priority has been helping the Claro and Olivero themes reach a high enough accessibility standard to make it into core. We believe that these two projects will have a significant impact on enhancing Drupal’s position as an accessible authoring platform out of the box. 

A secondary priority has been increasing community involvement, and this is where we will focus our principal efforts over the next three months.

What has been your greatest challenge in the last three months?

Our greatest challenge is limited time and resources, largely due to the additional strain that COVID lockdowns and distance learning/remote working has put on our maintainers. 

An additional challenge is that our documentation is woefully out of date. This makes it more difficult for us to easily onboard potential contributors.

And what has been your greatest success in the last three months?

We held a public review of Olivero with the National Federation of the Blind (NFB). This is the start of what we hope may be a long standing relationship, as well as a new process for evaluating the accessibility of core contributions. We also added a new provisional topic maintainer, Ben Mullins!

Do you have a “call to action” you want to make to the Drupal Community?

Yes! Please review issues tagged with #accessibility, and find ones to fix, or that you would like to bring to our monthly office hours! You don’t have to be an expert. 

Become accessibility champions for initiatives that interest you and start conversations with us early so that we can help you find the right resources for evaluation and feedback. 

Finally, our documentation needs to be brought up to date, and your help would be welcome. 

Kay VanValkenburgh updates us about DrupalLadder

About this Initiative: DrupalLadder is a community initiative to create an onramp for new Drupal users as well as new contributors to the Drupal project, or for those looking to level up their skills.

Where can we read more about your initiative?

https://www.drupal.org/project/drupalladder and https://drupalladder.org

What have been your priorities in the last three months?

Feature development focused on

  1. usability for learners and
  2. connecting Ladder info to corresponding official docs

What has been your greatest challenge in the last three months?

User experience design of the website

And what has been your greatest success in the last three months?

Seeing the value of the broad concepts and fitting together some of the major features

Do you have a “call to action” you want to make to the Drupal Community?

Help us by sharing information about how you work effectively - reach back to the people following in your footsteps and give them clear, adaptable paths to success

Drupal participation in Google Summer of Code

About this Initiative: Google Summer of Code is an annual program to promote technology education while supporting Open Source projects. Drupal has been a participant in Google Summer of Code for more than a decade.

Where can we read more about your initiative?

https://groups.drupal.org/google-summer-code – our community collaboration location  https://summerofcode.withgoogle.com/ – Google’s official program website  https://www.drupal.org/node/2415225 – where to get started for students (good read for potential mentors too). Read the 12 steps to help any student can get started on their own @ https://groups.drupal.org/node/535795

What have been your priorities in the last three months?

Google Summer of Code? an annual program for university students organized by Google with projects managed by open source organization mentors such as us (Drupal!). GSoC takes place during “summertime in North America” and wrapped up October with a very successful project. 

As a community, our initiative’s team of volunteers and mentors priority was supporting our student Vishal contributing to Drupal for several months. It was our responsibility to help the student learn more than writing code for a module. As mentors, we helped the student learn project management tools with professionally managed issue queues and techniques such as SCRUM. e reviewed code and tested modules with feedback helping a student who didn’t have a background in Drupal. As a community of volunteers, we made it a priority to ensure that our selected student would be as successful as possible.

What has been your greatest challenge in the last three months?

Finding mentors and project ideas. If you’re interested in mentoring, please realize that we pair each student with on average 3-5 mentors per project. Mentoring is not a full-time gig and can be accomplished with a few hours per week. Even if you simply have an idea for a project without becoming a mentor, please contact us at @ https://groups.drupal.org/node/536212

And what has been your greatest success in the last three months?

Vishal Chaudhary ( https://www.drupal.org/u/vishalghyv ) was Drupal’s Google Summer of Code 2020 student and obviously our greatest success in the last year. The fact that Drupal continues to find at least one student every year who becomes a truly amazing member of our community provides evidence GSoC was a success in 2020. 

Find Vishal’s code below and read about his journey through his @vishal38785">weekly GSoC blog and review his work on the Commerce Fraud project page

We also conducted an interview with Vishal, one of his mentors, and the creator of Drupal Commerce:

[embedded content]

Do you have a “call to action” you want to make to the Drupal Community?

Do you have a project idea and/or want to be a mentor? Please edit our 2021 project idea page @ https://groups.drupal.org/node/536212 with your idea. Even a few sentences or a link to an existing module page that can be ported to D8/9 works.

About this Community Group: The mission of the Community Working Group (CWG) is to foster a friendly and welcoming community for the Drupal project and to uphold the Drupal Code of Conduct.

Where can we read more about your initiative?


What have been your priorities in the last three months?

  1. The Community Health Team has been developing “nudge” templates to be used in issue queues to encourage all participants to engage in positive discourse: https://www.drupal.org/project/drupal_cwg/issues/3129687
  2. Offering discounted Code of Conduct enforcement training for Encouraging representatives from DrupalCamps and other events: https://www.drupal.org/community/cwg/blog/a-different-kind-of-contribution-become-a-trained-drupal-event-code-of-conduct
  3. Offering discounted Mental Health First Aid training for Drupal community members: https://www.drupal.org/community/cwg/blog/online-mental-health-first-aid-workshop-october-27-2020

Do you have a “call to action” you want to make to the Drupal Community?

Come to our session at DrupalCon Europe to learn more about what we’re doing and how you can get involved! https://events.drupal.org/europe2020/sessions/how-community-working-group-helping-make-healthier-community-panel

Local and Regional Updates

Andrii Podanenko and Alla Petrovska update us about Drupal Virtual Cafe Ukraine and the Drupal Ukraine Community

About this Community Group: The Drupal Ukraine Community represents the interests of the Drupal developers, users, and site owners in Ukraine.

Where can we read more about your initiative?




What have been your priorities in the last three months?

Supporting the Ukraine Drupal community during the pandemic.

What has been your greatest challenge in the last three months?

Finding the available speakers for Drupal Virtual Cafes.

And what has been your greatest success in the last three months?

We have organized three Drupal Virtual Cafes with 2 speakers per each event and 60+attendees from Europe and North America.

Do you have a "call to action" you want to make to the Drupal Community?

Connect with the Ukraine Drupal Community. We have the capacity to organize, but need support to find available speakers.

We need to have more information about bottlenecks for organizing virtual DrupalCamps. We have planned DrupalCamp Kyiv 2021, but unsure about the details.

We want your feedback!

We hope that this first edition of our quarterly update has been useful. Because this first edition is an experiment, we’d very much like your feedback as a contributor or potential contributor to Drupal. 

  • What do you think about the length? 
  • Would it be more helpful to organize by code and non-code initiatives, or by some other method? 
  • Does quarterly seem like the right cadence? 
  • What would make the calls to action more clear for how to get involved?

Please let us know any ideas you have to help keep the community more informed and able to understand how to get involved.

Dec 02 2020
Dec 02

What’s new in Drupal 9.1.0?

The first feature release of Drupal 9 includes the new experimental Olivero frontend theme and various additions to the Claro administration theme. Installer performance is improved 20% and full Composer 2 and PHP 8 support is available. Images with known dimensions are set to lazy-load by default to improve frontend performance.

Download Drupal 9.1.0

New experimental Olivero theme

A new beta experimental frontend theme has been added to Drupal core called Olivero. This is a new modern and clear theme that is planned to become the new default Drupal theme later (replacing Bartik). Subtheming Olivero is currently not supported, but formal support may be included in the future.

The theme is named after Rachel Olivero (1982-2019). She was the head of the organizational technology group at the National Federation of the Blind, a well-known accessibility expert, a Drupal community contributor, and a friend to many.

Key additions to the Claro theme

The experimental Claro administration theme introduces designs for various key pages: the extensions administration page, views administration, status report and media library received Claro styled designs.

Composer 2 and PHP 8 support

Drupal 9.1 is fully compatible with Composer 2. If you are using Composer 1, now would be a great time to update. Most plugins used on Drupal sites are compatible and/or obsolete with the new version. The memory and performance requirements reduced dramatically, which should improve your experience.

PHP 8 is also supported in Drupal 9.1, including all of Drupal's dependencies. There may be contributed projects that are not fully compatible though. Drupal 9 is still compatible with PHP 7.3 and newer. There are various exciting new features in PHP 8, but the JIT compiler and performance improvements are not likely to affect Drupal. Drupal 10 is planned to require PHP 8 in 2022. It is worth examining the support timelines of PHP versions to schedule your platform updates.

Other improvements

Installer performance is improved 20%, so getting a new Drupal site set up will be faster.

Images rendered by Drupal with known dimensions will be set to lazy-load automatically. This means browsers will only load them when they should appear in the viewport of the user, improving the user experience by making content appear faster.

Drupal 10 is planned for mid-2022. While Drupal 9 keeps requiring Symfony 4, Drupal 9.1 includes adjustments required to support Symfony 5 already.

What does this mean for me?

Drupal 8 site owners

Update at least to 8.9.x to continue receiving bug fixes until the end of life of Drupal 8 in November 2021. The next bug-fix release (8.9.11) is scheduled for January 6, 2021. (See the release schedule overview for more information.) As of this release, sites on Drupal 8.8 will no longer receive security coverage.

We suggest that you update from Drupal 8 to Drupal 9 though. Updating is supported directly from 8.8.x and 8.9.x. Of the top 1000 most used drupal.org projects, 85% are updated for Drupal 9, so there is a high likeliness that most of the modules and themes you rely on are compatible.

Drupal 7 site owners

Drupal 7 support was extended to November 28, 2022, and will continue to receive bug and security fixes throughout this time. From November 2022 until at least November 2025, the Drupal 7 Vendor Extended Support program will be offered by vendors.

On the other hand, the migration path for Drupal 7 sites to Drupal 9 is stable. Read more about the migration to Drupal 9.

Translation, module, and theme contributors

Minor releases like Drupal 9.1.0 include backwards-compatible API additions for developers as well as new features.

Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 9.0.x and earlier will be compatible with 9.1.x as well. However, the new version does include some changes to strings, user interfaces, internal APIs and API deprecations. This means that some small updates may be required for your translations, modules, and themes. Read the 9.1.0 release notes for a full list of changes that may affect your modules and themes.

This release has advanced the Drupal project significantly and represents the efforts of hundreds of volunteers and contributors from various organizations. Thank you to everyone who contributed to Drupal 9.1.0!

Nov 30 2020
Nov 30

We are currently planning for Drupal core to drop support for Internet Explorer 11 in Drupal 10 (scheduled to be released in June 2022). Drupal 9 will be supported until late 2023, which means that sites that want to support Internet Explorer 11 can continue using Drupal 9 until then.

Feedback needed from assistive technology stakeholders

WebAIM's survey of screen reader users shows Internet Explorer 11 usage dropping from 23.3% in October 2017 to 10.9% in September 2019. The next edition of their survey is likely to be released at the end of 2021, but we need to finalize our browser support within the next month in order to develop and release Drupal 10 on schedule.

We need feedback from assistive technology users and accessibility stakeholders. Do you or your users still use Internet Explorer 11 with screen readers? Do their screen readers support browsers other than Internet Explorer 11? How feasible is it to upgrade to a different browser for use with your screen reader? We are requesting feedback until December 18th, 2020 January 31st, 2021. 

Why would we drop support for Internet Explorer 11?

  • Microsoft stopped developing Internet Explorer 11 in 2015. For that reason it is significantly behind modern browsers that have continued development. Because more and more libraries are adopting the use of those features, there is a significant cost associated with maintaining Internet Explorer 11. For example, the latest major release of CKEditor has dropped support for Internet Explorer 11, which means that Drupal 10 cannot securely support both CKEditor5 and Internet Explorer 11.

  • Microsoft itself has dropped support for Internet Explorer 11 in many of its services, and the rest will drop support in mid-2021.

  • Usage of Internet Explorer 11 has decreased significantly. Drupal doesn’t collect analytics on browser usage from its end users, so we rely on data provided by other projects such as Wikimedia, WebAIM, and Statcounter. For example, in October 2019, Wikimedia had 4.4% of its traffic using Internet Explorer 11. At the same time this year the number had dropped to 1.4%. We assume that the number of Internet Explorer 11 users will continue decreasing before the release of Drupal 10.

  • Supporting Internet Explorer 11 degrades the experience for everyone. We currently supply all users extra code to make Internet Explorer 11 work. This increases the request size and makes page load time slower for everyone.

  • The additional requirements of Internet Explorer 11 demand additional development time that far exceeds the browser's market share. These efforts come at the expense of new features and bug fixes.

What if I need to support Internet Explorer 11?

Even if Drupal 10 drops support for Internet Explorer 11, you can continue using Drupal 9 until late 2023. We recommend advising your users to move to another browser before that. If you believe your users have specific requirements as to why they cannot move from Internet Explorer 11, post them on the Internet Explorer 11 policy discussion.

Would this affect Drupal 7?

No. Drupal 7 remains compatible with Internet Explorer 11. A separate announcement will be issued if that changes.

Edit December 17th, 2020: feedback window extended until the end of January 2021.

Oct 06 2020
Oct 06

Reposted from the Core group on groups.drupal.org

In preparation for the minor release, Drupal 9.1.x will enter the alpha phase the week of October 19th, 2020. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. The 9.1.0-alpha1 deadline for most core patches is October 16. (More information on alpha and beta releases.)

  • Developers and site owners can begin testing the alpha after its release.

  • The 9.2.x branch of core will be created, and future feature and API additions will be targeted against that branch instead of 9.1.x. All outstanding issues filed against 9.1.x will be automatically migrated to 9.2.x.

  • Once 9.2.x is branched, alpha experimental modules will be removed from the 9.1.x codebase (so their development will continue in 9.2.x only). The Config Environment module is an alpha stability module in 9.1.x.

  • All issues filed against 9.0.x will then be migrated to 9.1.x, and subsequent bug reports should be targeted against the 9.1.x branch.

  • During the alpha phase, core issues will be committed according to the following policy:

    1. Most issues that are allowed for patch releases will be committed to 9.1.x and 9.2.x.
    2. Most issues that are only allowed in minor releases will be committed to 9.2.x only. A few strategic issues may be backported to 9.1.x, but only at committer discretion after the issue is fixed in 9.2.x (so leave them set to 9.2.x unless you are a committer), and only up until the beta deadline.

Drupal 9.1.0-beta1 will be released the week of November 2nd

Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.

The release candidate phase will begin the week of November 16th. See the summarized key dates in the release cycle, allowed changes during the Drupal 8 and Drupal 9 release cycles, and Drupal 8 and 9 backwards compatibility and internal API policy for more information.

The scheduled release date of Drupal 9.1.0 is December 2nd, 2020.

Bugfix and security support of Drupal 9.0.x, 8.8.x and 8.9.x.

Security coverage for Drupal 8 and 9 is generally provided for the previous minor release as well as the newest minor release. However, Drupal 8.9.x is a Long-Term Support release where support is provided until November 2021. Based on these the following changes are upcoming:

Drupal 8.8.x Security releases will be provided until December 2nd, 2020. Drupal 8.9.x Security releases will be provided until November 2021. Bugfix support will continue into early 2021. Drupal 9.0.x Normal bugfix support ends on December 2nd, 2020. However, security releases are provided until the release of Drupal 9.2.0 on June 2, 2021.

2021 Support Timeline

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web