In a constantly evolving digital world, being strategic about where to focus our social media efforts is essential for effective community building and outreach. At the same time, it is also important to choose the platforms that align with the values of the community being represented. This has been a growing conversation within the Drupal community, especially around the ethical use of platforms.
After reviewing the engagement metrics and audience reach across platforms, we're implementing a tiered approach that balances our commitment to Drupal's values of openness, inclusiveness, and digital freedom with our responsibility to grow the Drupal ecosystem and serve our global community effectively.
We are choosing to focus our resources where we can create the most meaningful engagement and build genuine community connections. This approach allows us to be more responsive, create better content, and foster stronger relationships with our community.
The Platform Choices Explained
Here’s how we are approaching each platform going forward:
Preferred Platform: LinkedIn
LinkedIn is going to be the primary platform for community communication. After analyzing our performance data, LinkedIn consistently delivers our strongest engagement rates and reaches our core professional audience most effectively.
As a professional platform, LinkedIn allows us to share updates, highlight community achievements, showcase member contributions, and connect with developers, decision-makers, and organizations across the Drupal ecosystem.
Emerging Preferred Platforms: Mastodon & Bluesky
As open source advocates, we are enthusiastic about the platforms Mastodon and Bluesky. These are decentralized, community driven and privacy conscious platforms that align with the Drupal community values.
We will be doing focused growth efforts on these platforms for the upcoming six months. If either platform reaches 5,000 followers during this period, we'll promote it to preferred platform status alongside LinkedIn. We're optimistic about their potential to become key channels for our community.
Instagram & Facebook
While Instagram and Facebook will be a conscious choice for selective updates, we recognize their strengths in visual storytelling and broad audience reach. They serve better as amplifiers rather than primary communication channels.
We'll maintain selective engagement on these platforms for:
Event promotions and DrupalCon marketing
Product announcements and major initiative updates
Reaching audiences who may not be active on our preferred platforms
Transitioning from X/Twitter
After reviewing engagement data and platform dynamics, we're transitioning away from regular posting on X (formerly Twitter).
Our existing presence will be maintained to direct our followers to our preferred platforms, helping facilitate community migration while preserving connections with our established audience.
Channels We Manage
The Drupal Association manages social media accounts for multiple brands within its ecosystem:
Drupal: Our primary project accounts focusing on product news, project updates, community news, and developer resources
Drupal Association: Organizational updates, partnership announcements, and community support initiatives
DrupalCon: Event-specific marketing, speaker highlights, and attendee engagement
Moving Forward
This strategic approach ensures we can maintain effective community communication and product marketing while being thoughtful about where we invest our time and resources. By focusing our efforts on platforms where we can create the most value, we're better positioned to serve our global community and promote Drupal's mission of building the open web.
Follow us on
Preferred Platforms
LinkedIn
Drupal
https://www.linkedin.com/company/drupal-project
Drupal Association
https://www.linkedin.com/company/drupal-association
DrupalCon North America
https://www.linkedin.com/company/drupalcon-north-america
YouTube
Drupal Association
https://www.youtube.com/@DrupalAssociation
Emerging Preferred Platforms
Mastodon
Drupal
https://mastodon.social/@drupal
Drupal Association
https://mastodon.social/@drupalassoc
DrupalCon North America
https://mastodon.social/@drupalcon
Bluesky
Drupal (brand new)
https://bsky.app/profile/drupalofficial.bsky.social
Drupal Association
https://bsky.app/profile/drupalassociation.bsky.social
DrupalCon North America
https://bsky.app/profile/drupalcon.bsky.social
Other Platforms
Instagram
Drupal Association
https://www.instagram.com/drupalassociation/
DrupalCon North America
https://www.instagram.com/drupalcon/
Facebook
Drupal
https://www.facebook.com/DrupalOpenSource/
DrupalCon North America
https://www.facebook.com/DrupalCon
Marketplace Share Out #8: FAQ and What’s Changing Post-Feedback
Thanks to everyone who’s participated in the proposal feedback! Based on your input, here’s a transparent summary of what’s changing, what’s under consideration, and what questions we heard most.
Recommendations Based on Your Feedback
No Listing Fees During the Pilot
To keep the pilot accessible and grounded in contribution, we’re recommending no listing fees during the initial pilot for DCPs. This will allow us to gather real cost data on quality reviews and operations before deciding on any post-pilot fees.
Revisiting DCP Accessibility
Several of you shared that the current DCP model may be out of reach for small but impactful contributors. The DA is encouraged to explore whether the DCP program can:
Support solo contributor/very small teams (up to 3 people)
Accept in-kind contribution in lieu of some financial sponsorship
Standalone Telemetry Module
Usage data is critical—but many of you don’t use the Site Update module consistently. We’re exploring the idea of a small standalone module focused solely on telemetry to better understand real-world adoption without requiring full updater usage.
Strong Preference for On-Site Purchasing
Feedback was clear: many of you want on-site purchasing with a seamless Drupal.org experience. While MVP will still use off-site sales (for financial viability), the DA will investigate what on-site options might be possible with comparable investment.
Frequently Asked Questions
Why is the pilot limited to DCPs?
To keep the pilot focused and feedback structured, we’re starting with partners already contributing both financially and technically. Future expansion is possible, but perhaps the best approach is to make sure that the DCP program is accessible to .
Why off-site sales?
It’s currently the only financially feasible model that allows template makers to set their own pricing and manage licensing. On-site sales would require significant investment and admin overhead—but it’s being actively explored if not for MVP, then for future phases.
Why was a $395 listing fee proposed?
That fee reflects ~50% of estimated QA costs per template. However, it’s not being recommended for the pilot based on your feedback. We’ll revisit this once we have real usage and cost data.
Why would the DA receive fees if they’re not handling sales?
Because quality review, governance, platform updates, and Marketplace operations all require staff time and infrastructure. The proposal aims to break even in Year 2 with listing fees and a 10% referral share from upsells—without those, it may run a small deficit.
How are referrals and upsells handled?
A 10% referral fee applies to any upsell tied to a Marketplace listing. The length of this referral window (no more than 12 months) will be finalized with initial partners.
What about updates and support for templates?
This came through strongly in feedback: people want reassurance that templates will be supported and updated. That can be finalized through participation agreements—maintenance is required, and templates that go stale will be delisted.
How do templates get deployed?
While one-click hosting is not part of the MVP, the DrupalCMS Leadership Team is exploring this for the future. It’s not a must-have for the pilot, but definitely on the roadmap.
Next Steps
Board review: The DA Board will vote on the pilot and MVP investment on July 24.
If approved, DA staff will begin outreach to DCPs to confirm participation and finalize the initial 10+ templates and will explore technical delivery options—including on-site purchasing possibilities.
Thank you for helping shape a Marketplace that’s community-centered, contributor-aware, and designed to build trust from day one. If you haven’t already, head to #drupal-cms-marketplace to continue the conversation or drop in with questions.
Recommendations Based on Your Feedback
No Listing Fees During the Pilot
To keep the pilot accessible and grounded in contribution, we’re recommending no listing fees during the initial pilot for DCPs. This will allow us to gather real cost data on quality reviews and operations before deciding on any post-pilot fees.
Revisiting DCP Accessibility
Several of you shared that the current DCP model may be out of reach for small but impactful contributors. The DA is encouraged to explore whether the DCP program can:
Support solo contributor/very small teams (up to 3 people)
Accept in-kind contribution in lieu of some financial sponsorship
Standalone Telemetry Module
Usage data is critical—but many of you don’t use the Site Update module consistently. We’re exploring the idea of a small standalone module focused solely on telemetry to better understand real-world adoption without requiring full updater usage.
Strong Preference for On-Site Purchasing
Feedback was clear: many of you want on-site purchasing with a seamless Drupal.org experience. While MVP will still use off-site sales (for financial viability), the DA will investigate what on-site options might be possible with comparable investment.
Frequently Asked Questions
Why is the pilot limited to DCPs?
To keep the pilot focused and feedback structured, we’re starting with partners already contributing both financially and technically. Future expansion is possible, but perhaps the best approach is to make sure that the DCP program is accessible to .
Why off-site sales?
It’s currently the only financially feasible model that allows template makers to set their own pricing and manage licensing. On-site sales would require significant investment and admin overhead—but it’s being actively explored if not for MVP, then for future phases.
Why was a $395 listing fee proposed?
That fee reflects ~50% of estimated QA costs per template. However, it’s not being recommended for the pilot based on your feedback. We’ll revisit this once we have real usage and cost data.
Why would the DA receive fees if they’re not handling sales?
Because quality review, governance, platform updates, and Marketplace operations all require staff time and infrastructure. The proposal aims to break even in Year 2 with listing fees and a 10% referral share from upsells—without those, it may run a small deficit.
How are referrals and upsells handled?
A 10% referral fee applies to any upsell tied to a Marketplace listing. The length of this referral window (no more than 12 months) will be finalized with initial partners.
What about updates and support for templates?
This came through strongly in feedback: people want reassurance that templates will be supported and updated. That can be finalized through participation agreements—maintenance is required, and templates that go stale will be delisted.
How do templates get deployed?
While one-click hosting is not part of the MVP, the DrupalCMS Leadership Team is exploring this for the future. It’s not a must-have for the pilot, but definitely on the roadmap.
Next Steps
Board review: The DA Board will vote on the pilot and MVP investment on July 24.
If approved, DA staff will begin outreach to DCPs to confirm participation and finalize the initial 10+ templates and will explore technical delivery options—including on-site purchasing possibilities.
Thank you for helping shape a Marketplace that’s community-centered, contributor-aware, and designed to build trust from day one. If you haven’t already, head to #drupal-cms-marketplace to continue the conversation or drop in with questions.
Webinar: Choosing the right AI tools for content and marketing: Making informed choices for your business
The current AI marketplace is crowded with startups and established technology providers, each vying for attention offering a bewildering array of features.
For business leaders, the real challenge lies not in the availability of options, but in choosing a solution that genuinely supports strategic goals and day-to-day operational needs.
It is all too easy to be influenced by hype or surface-level features, rather than focusing on long-term value and alignment with business priorities.
In this webinar, we explore:
A practical methodology: for identifying AI tools that support your business requirements
The value of open source: in enabling flexibility and control when working with different AI and LLM technologies
How to approach AI governance: and responsibly delegate tasks to automated systems
Evidence-based insights: and actionable guidance to support confident decision-making
Register here: https://drupalassoc.zoom.us/webinar/register/WN_z3lrNnwjQdeaAcO6w9ifXQ
Speakers
Alan Botwright
With over 20 years of experience at the crossroads of technology and digital innovation, Alan is well positioned to guide organizations through the selection and implementation of AI solutions. As Director of Product and Solution Marketing and former Principal Solutions Architect at Acquia, he has worked closely with clients to define and deliver AI-driven digital strategies that create real business value.
Alan’s background as the founder of a Drupal application development agency and his leadership roles in both London agencies and enterprise tech have given him hands-on expertise in integrating emerging technologies; from initial assessment, strategy to full-scale deployment.
Experience with brands, architecture, product marketing, and digital transformation allows him to translate complex AI concepts into actionable guidance for clients embarking on their AI journey.
Matthew Saunders
A digital strategy leader, AI advocate, and neurodiversity champion with deep experience in accessibility, inclusive design, and enterprise transformation. He has led AI-powered innovation at Pfizer, where he helped scale global platforms and streamline digital operations.
Today, he serves as an AI Ambassador for amazee.io and contributes to the Marketing Track Team for the Drupal AI Strategic Initiative, helping shape the future of open-source AI. His work focuses on using technology—especially AI—to create more accessible, equitable experiences for everyone.
Jamie Abrahams
Jamie is a co-founder of FreelyGive, a Drupal agency specialising in native Drupal CRM. With the release of ChatGPT 3.5 he became obsessed with AI and dedicated all his time to pushing AI and particularly Drupal AI forwarded.
He's been involved in maintaining the AI module, the Drupal CMS AI Track and involved as a founding member of the Drupal AI Strategic Initiative. He's not a developer but has been keenly involved in shaping the direction of AI in Drupal until now.
Paul Johnson (Chair)
Agency leader for over a decade possessing a wealth of experience advising a diverse range of clients on digital marketing strategy from both private and public sectors.
Now business development manager at 1xINTERNET, a leading European Drupal specialist, where the focus is on digital experience platforms for multinational enterprises, government, education and nonprofits.
Always at the forefront of innovation, he is part of the Drupal AI Initiative leadership team, helping to ensure those favouring open source solutions have access to leading AI technology.
Drupal AI 1.2.0-alpha1 is out and ready to be tested
Drupal AI 1.2.0-alpha1 was just released and it comes as a feature preview of what is coming with the AI 1.2.0 release.
Watch a highlights video about the release.
Note that since this is an alpha, we will not provide upgrade paths from this alpha and more features will still be added before the beta releases.
Article by Marcus Johansson.
Field Widget Actions - invoke AI from anywhere
The new Field Widget Actions module makes it possible to add interactive buttons on any entity form, to make it easy for editors to interact and fill out fields with AI from anywhere. With a push of a button you can have suggestions or picks - if you are not happy, you can push and ask again. This ensures that we can use AI to help the editor, but the editor has the final decision.
This works together with the AI Content Suggestions, AI Automators and AI Agents module, to have anything from simple preset configurations to custom logic business or even agents taking autonomous decisions on how to help fill out a field.
Possible solutions that come out of the box, but are not limited too, are picking categories, creating tags, helping with writing summaries, coming up with titles, extracting e-mails from sources.
Example of adding a button for rewriting a filename based on the image.
Example of adding a button for rewriting a filename based on the image.
In conjunction with the AI Automators, there are at least 100+ different use cases for these buttons. With agents, you can have the agent go out and research things on the Internet for you, to give you suggestions on improved Meta tags for instance.
And for advanced site builders, you can invoke this via ECA, which already has an integration. That together with the option to create your own processor makes the possibilities endless for this.
View documentation here.
Prompt Library
With the release of 1.2.0, we make it possible to ship prompts as configurations. This will also make it easier for third party modules to give suggested prompts to use for their products.
Example of prompt library
Since context engineering is an important part of a well working AI ecosystem, and since these can be hard to understand, we now have the possibility to ship them together with any module.
Gone will be the times when you would have to guess or ask a maintainer for best practice prompts, we make them possible to ship.
This also means that you can make your own business stand out, by using well-crafted prompts, that you can share over projects via recipes.
AI Content Suggestions on Block and Taxonomy Terms
For the longest time the content suggestions were only allowed on Nodes, we have now also added the possibility to add them to Block and Taxonomy Terms entities.
Mocking library for testing or replaying requests
One of the big issues with developing AI, is that you spend a lot of time waiting for AI providers to process the result. It can also be expensive, if you need to run your query over and over.
Another issue is when you write automated testing, that you need to replicate how an AI provider responds, without necessarily needing to send requests to an AI provider for similar reasons.
We have now added the possibility to mock any request done to a real provider and replay it while developing or while testing.
View documentation here.
Allow more file types for AI models
The LLM models are evolving, and the vision models are not the only files that can be ingested anymore. There are models that can read PDF files or even look at videos. We have changed the foundation of the AI core module to make it possible for providers to feed them with any type of files.
New Automator Types
The AI Automators make it possible to set up AI in a simple manner, how a field should be automatically filled using AI. With the addition of the Field Widget Actions, these will also be available with a user interface for the editors. It already has 60+ features, the following is added as of 1.2.0-alpha1:
Image Alt Text - this can look at any image, and use different context fields, like the article, the filename of the image and more to generate a proper alt text for the image. This will work magic for accessibility.
Image Filename Rewrite - in a similar manner for SEO, it is important that your image files are named expressively, however when you load them directly from a digital camera, they might be named DSC_0034.jpg. The AI can now look at them after you uploaded them, and rename them to something that actually describes what is in the image.
Summary Generation for Text with Summary - if you use Text with Summary field, this automator can look at the text and generate a summary for it, in the summary field.
Vector databases are abstracted for recipes
All vector databases have some base functionality that all of them share. This means that from a feature point of view it doesn’t really matter if you use Milvus, Postgres or Pinecone.
However in recipes you would need to specify exactly that, meaning that a recipe that adds a “chat-with-your-documents” feature, would only work with one service.
We had already abstracted this away for AI Providers, and with 1.2.0-alpha1 it will be possible to ship a whole AI and vector database solution that doesn’t care about what AI providers or vector databases you have, it just works.
Versioned Documentation
With the speed of how fast AI is moving and the AI module in its turn is moving, versioned documentation is something that is needed to make sure that you can locate the latest documentation for the version you are working with.
Our documentation is now not only versioned, but does actually version based on the major or minor version you push changes to the documentation for.
View documentation here.
Helper abstraction for providers
If you are a provider contributor or are developing a provider in-house for private reasons and that provider is based on the OpenAI standard that many providers support - Mistral, Anthropic, Ollama and more - we now have an abstracted base class that you can use, making it a lot easier to get started with a contributed or custom provider.
This will also make it easier for us to do incremental updates and improvements on these providers, without the person developing providers needing to change their provider.
Thank you to the following contributors for helping out:
scott_euser, gxleano, marcus_johansson, breidert, kevinquillen, mrdalesmith, prashant.c, annmarysruthy, arthur_lorenz, dan2k3k4, matthews, svendecabooter, sarvjeetsingh, anjaliprasannan, valthebald, apmsooner, leo pitt, davidlfg, michaellander, andrewbelcher, narendrar, arisha, emacoti, efpapado, a.dmitriiev, akhil babu, bisonbleu, kristen pol, prabha1997, sundflux, arkener, rajab natshah, jan kellermann, emma horrell, rszrama, g.rocchini, doxigo, adwivedi008, ankitsingh0188, shalini_jha, sayyedhali, lukasfischer, yautja_cetanu, jurgenhaas, lussoluca, sijumpk, arwillame
Thank you to the following organizations for helping out:
Factorial GmbH, FreelyGive, 1xINTERNET, Velir, QED42, Drupal India Association, Soapbox, Acquia, drunomics, Amazee Labs, amazee.io, Sven Decabooter, EntityOne, Make It Fly, Dropsolid, SystemSeed, Globant, Elevated Third, Zoocha, Common Sense Media, utdanning.no, Salsa Digital, INDICIA, Vardot, werk21, The University of Edinburgh, Centarro, Ramsalt Lab, Cognizant Technology Solutions, LakeDrops, SparkFabrik, Calibrate
Watch a highlights video about the release.
Note that since this is an alpha, we will not provide upgrade paths from this alpha and more features will still be added before the beta releases.
Article by Marcus Johansson.
Field Widget Actions - invoke AI from anywhere
The new Field Widget Actions module makes it possible to add interactive buttons on any entity form, to make it easy for editors to interact and fill out fields with AI from anywhere. With a push of a button you can have suggestions or picks - if you are not happy, you can push and ask again. This ensures that we can use AI to help the editor, but the editor has the final decision.
This works together with the AI Content Suggestions, AI Automators and AI Agents module, to have anything from simple preset configurations to custom logic business or even agents taking autonomous decisions on how to help fill out a field.
Possible solutions that come out of the box, but are not limited too, are picking categories, creating tags, helping with writing summaries, coming up with titles, extracting e-mails from sources.
Example of adding a button for rewriting a filename based on the image.
Example of adding a button for rewriting a filename based on the image.
In conjunction with the AI Automators, there are at least 100+ different use cases for these buttons. With agents, you can have the agent go out and research things on the Internet for you, to give you suggestions on improved Meta tags for instance.
And for advanced site builders, you can invoke this via ECA, which already has an integration. That together with the option to create your own processor makes the possibilities endless for this.
View documentation here.
Prompt Library
With the release of 1.2.0, we make it possible to ship prompts as configurations. This will also make it easier for third party modules to give suggested prompts to use for their products.
Example of prompt library
Since context engineering is an important part of a well working AI ecosystem, and since these can be hard to understand, we now have the possibility to ship them together with any module.
Gone will be the times when you would have to guess or ask a maintainer for best practice prompts, we make them possible to ship.
This also means that you can make your own business stand out, by using well-crafted prompts, that you can share over projects via recipes.
AI Content Suggestions on Block and Taxonomy Terms
For the longest time the content suggestions were only allowed on Nodes, we have now also added the possibility to add them to Block and Taxonomy Terms entities.
Mocking library for testing or replaying requests
One of the big issues with developing AI, is that you spend a lot of time waiting for AI providers to process the result. It can also be expensive, if you need to run your query over and over.
Another issue is when you write automated testing, that you need to replicate how an AI provider responds, without necessarily needing to send requests to an AI provider for similar reasons.
We have now added the possibility to mock any request done to a real provider and replay it while developing or while testing.
View documentation here.
Allow more file types for AI models
The LLM models are evolving, and the vision models are not the only files that can be ingested anymore. There are models that can read PDF files or even look at videos. We have changed the foundation of the AI core module to make it possible for providers to feed them with any type of files.
New Automator Types
The AI Automators make it possible to set up AI in a simple manner, how a field should be automatically filled using AI. With the addition of the Field Widget Actions, these will also be available with a user interface for the editors. It already has 60+ features, the following is added as of 1.2.0-alpha1:
Image Alt Text - this can look at any image, and use different context fields, like the article, the filename of the image and more to generate a proper alt text for the image. This will work magic for accessibility.
Image Filename Rewrite - in a similar manner for SEO, it is important that your image files are named expressively, however when you load them directly from a digital camera, they might be named DSC_0034.jpg. The AI can now look at them after you uploaded them, and rename them to something that actually describes what is in the image.
Summary Generation for Text with Summary - if you use Text with Summary field, this automator can look at the text and generate a summary for it, in the summary field.
Vector databases are abstracted for recipes
All vector databases have some base functionality that all of them share. This means that from a feature point of view it doesn’t really matter if you use Milvus, Postgres or Pinecone.
However in recipes you would need to specify exactly that, meaning that a recipe that adds a “chat-with-your-documents” feature, would only work with one service.
We had already abstracted this away for AI Providers, and with 1.2.0-alpha1 it will be possible to ship a whole AI and vector database solution that doesn’t care about what AI providers or vector databases you have, it just works.
Versioned Documentation
With the speed of how fast AI is moving and the AI module in its turn is moving, versioned documentation is something that is needed to make sure that you can locate the latest documentation for the version you are working with.
Our documentation is now not only versioned, but does actually version based on the major or minor version you push changes to the documentation for.
View documentation here.
Helper abstraction for providers
If you are a provider contributor or are developing a provider in-house for private reasons and that provider is based on the OpenAI standard that many providers support - Mistral, Anthropic, Ollama and more - we now have an abstracted base class that you can use, making it a lot easier to get started with a contributed or custom provider.
This will also make it easier for us to do incremental updates and improvements on these providers, without the person developing providers needing to change their provider.
Thank you to the following contributors for helping out:
scott_euser, gxleano, marcus_johansson, breidert, kevinquillen, mrdalesmith, prashant.c, annmarysruthy, arthur_lorenz, dan2k3k4, matthews, svendecabooter, sarvjeetsingh, anjaliprasannan, valthebald, apmsooner, leo pitt, davidlfg, michaellander, andrewbelcher, narendrar, arisha, emacoti, efpapado, a.dmitriiev, akhil babu, bisonbleu, kristen pol, prabha1997, sundflux, arkener, rajab natshah, jan kellermann, emma horrell, rszrama, g.rocchini, doxigo, adwivedi008, ankitsingh0188, shalini_jha, sayyedhali, lukasfischer, yautja_cetanu, jurgenhaas, lussoluca, sijumpk, arwillame
Thank you to the following organizations for helping out:
Factorial GmbH, FreelyGive, 1xINTERNET, Velir, QED42, Drupal India Association, Soapbox, Acquia, drunomics, Amazee Labs, amazee.io, Sven Decabooter, EntityOne, Make It Fly, Dropsolid, SystemSeed, Globant, Elevated Third, Zoocha, Common Sense Media, utdanning.no, Salsa Digital, INDICIA, Vardot, werk21, The University of Edinburgh, Centarro, Ramsalt Lab, Cognizant Technology Solutions, LakeDrops, SparkFabrik, Calibrate
July Drupal for Nonprofits Chat
Join us THURSDAY, July 17 at 1pm ET / 10am PT, for our regularly scheduled call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)
We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google doc: https://nten.org/drupal/notes!
All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.
This free call is sponsored by NTEN.org and open to everyone.
Join the call: https://us02web.zoom.us/j/81817469653
Meeting ID: 818 1746 9653
Passcode: 551681
One tap mobile:
+16699006833,,81817469653# US (San Jose)
+13462487799,,81817469653# US (Houston)
Dial by your location:
+1 669 900 6833 US (San Jose)
+1 346 248 7799 US (Houston)
+1 253 215 8782 US (Tacoma)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
Find your local number: https://us02web.zoom.us/u/kpV1o65N
Follow along on Google Docs: https://nten.org/drupal/notes
View notes of previous months' calls.
We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google doc: https://nten.org/drupal/notes!
All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.
This free call is sponsored by NTEN.org and open to everyone.
Join the call: https://us02web.zoom.us/j/81817469653
Meeting ID: 818 1746 9653
Passcode: 551681
One tap mobile:
+16699006833,,81817469653# US (San Jose)
+13462487799,,81817469653# US (Houston)
Dial by your location:
+1 669 900 6833 US (San Jose)
+1 346 248 7799 US (Houston)
+1 253 215 8782 US (Tacoma)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
Find your local number: https://us02web.zoom.us/u/kpV1o65N
Follow along on Google Docs: https://nten.org/drupal/notes
View notes of previous months' calls.
Call for Training Proposals for DrupalCon Chicago 2026
We’re excited to invite training partners to submit proposals for DrupalCon Chicago 2026, taking place 23-26 March at the Hyatt Regency Chicago.
DrupalCon is the premier gathering for the global Drupal community, bringing together developers, designers, strategists, and business leaders for a week of collaboration and knowledge sharing. This year, DrupalCon will highlight major innovations in Drupal CMS, including the rollout of Drupal CMS 2.0, and growing momentum around Drupal-powered AI tools and integrations. It’s a pivotal time in the Drupal ecosystem—and your training can help prepare attendees to thrive in this next era.
Training Day Details
Date: Monday, 23 March 2026
Format: Full-day trainings, split into two 3-hour sessions with a break for lunch
Time: 09:00 – 16:00
Model: Profit-sharing. If selected, you’ll be asked to provide a W9, electronic fund disbursement form, and signed agreement.
How to Submit:
To be considered, please submit a proposal via email to Meghan Harrell, Director of Community Programs at the Drupal Association, at meghan@association.drupal.org. Your proposal should include:
Title and description of your training
Level of experience required (beginner, intermediate, advanced)
Key takeaways: What participants will learn and be able to do after the training
Deadline & Next Steps
Proposal Deadline: Friday, 1 August 2025 (EOD)
Review & Notification: Proposals will be reviewed the following week, with all applicants notified of their status by Monday, 11 August 2025.
Our goal is to finalize the training lineup in time for our Early Bird ticket launch on 15 September.
If you have any questions, please don’t hesitate to reach out to meghan@association.drupal.org. We look forward to reviewing your proposal and potentially partnering with you at DrupalCon Chicago 2026!
DrupalCon is the premier gathering for the global Drupal community, bringing together developers, designers, strategists, and business leaders for a week of collaboration and knowledge sharing. This year, DrupalCon will highlight major innovations in Drupal CMS, including the rollout of Drupal CMS 2.0, and growing momentum around Drupal-powered AI tools and integrations. It’s a pivotal time in the Drupal ecosystem—and your training can help prepare attendees to thrive in this next era.
Training Day Details
Date: Monday, 23 March 2026
Format: Full-day trainings, split into two 3-hour sessions with a break for lunch
Time: 09:00 – 16:00
Model: Profit-sharing. If selected, you’ll be asked to provide a W9, electronic fund disbursement form, and signed agreement.
How to Submit:
To be considered, please submit a proposal via email to Meghan Harrell, Director of Community Programs at the Drupal Association, at meghan@association.drupal.org. Your proposal should include:
Title and description of your training
Level of experience required (beginner, intermediate, advanced)
Key takeaways: What participants will learn and be able to do after the training
Deadline & Next Steps
Proposal Deadline: Friday, 1 August 2025 (EOD)
Review & Notification: Proposals will be reviewed the following week, with all applicants notified of their status by Monday, 11 August 2025.
Our goal is to finalize the training lineup in time for our Early Bird ticket launch on 15 September.
If you have any questions, please don’t hesitate to reach out to meghan@association.drupal.org. We look forward to reviewing your proposal and potentially partnering with you at DrupalCon Chicago 2026!
Disruptive deprecations should now be scheduled for removal in Drupal 13.0.0
Drupal 10 will be supported until December 2026
From Drupal 10 on, Drupal core has a new major release schedule with a long-term support phase, so that two major versions are supported at a time. We previously announced that Drupal 10 would be supported until mid- to late 2026, depending on when Drupal 12 was released.
We are updating the release schedule and have agreed that Drupal 10 will officially be supported until December 2026, regardless of whether Drupal 12 is released in June, August, or December. This fixed end-of-life date should provide more certainty for the ecosystem and make planning site upgrades easier.
Disruptive deprecations should now be scheduled for removal in Drupal 13.0.0
Drupal core uses a deprecation process to provide backwards compatibility and a continuous upgrade path between major versions. When new APIs are added, the old code is deprecated and scheduled for removal in a later major version. Under the continuous upgrade path, the new major version has the same API as the final minor version of the previous major, but with deprecated code removed.
Drupal 12 is scheduled for release in 2026, and its first possible release window is June 2026. This means that the next major version of core may have a stable version in less than a year, with its beta versions released as early as March. At the same time, the current maintenance minor version of Drupal 10 (10.5.x) will receive security coverage until June 2026.
As a result, contributed projects may add Drupal 12 support while Drupal 10.5 is still supported during early 2026, which means those core versions need to share the same important APIs. Therefore, disruptive deprecations in Drupal 11.3.x and higher should be scheduled for removal in 13.0.0 (rather than 12.0.0). This allows contributed modules to support both the next major release and the currently supported minors. This way, we will not break backwards compatibility with 10.5.x for important APIs.
Help us get ready for Drupal 12!
Core modules are actually not disruptive to deprecate, because we can create an equivalent package in contrib and provide sites a smooth upgrade path for these modules from Drupal 11 core to Drupal 12 contrib. Take a look at the list of modules and other dependencies planned for removal from Drupal 12, and consider helping move these issues forward.
From Drupal 10 on, Drupal core has a new major release schedule with a long-term support phase, so that two major versions are supported at a time. We previously announced that Drupal 10 would be supported until mid- to late 2026, depending on when Drupal 12 was released.
We are updating the release schedule and have agreed that Drupal 10 will officially be supported until December 2026, regardless of whether Drupal 12 is released in June, August, or December. This fixed end-of-life date should provide more certainty for the ecosystem and make planning site upgrades easier.
Disruptive deprecations should now be scheduled for removal in Drupal 13.0.0
Drupal core uses a deprecation process to provide backwards compatibility and a continuous upgrade path between major versions. When new APIs are added, the old code is deprecated and scheduled for removal in a later major version. Under the continuous upgrade path, the new major version has the same API as the final minor version of the previous major, but with deprecated code removed.
Drupal 12 is scheduled for release in 2026, and its first possible release window is June 2026. This means that the next major version of core may have a stable version in less than a year, with its beta versions released as early as March. At the same time, the current maintenance minor version of Drupal 10 (10.5.x) will receive security coverage until June 2026.
As a result, contributed projects may add Drupal 12 support while Drupal 10.5 is still supported during early 2026, which means those core versions need to share the same important APIs. Therefore, disruptive deprecations in Drupal 11.3.x and higher should be scheduled for removal in 13.0.0 (rather than 12.0.0). This allows contributed modules to support both the next major release and the currently supported minors. This way, we will not break backwards compatibility with 10.5.x for important APIs.
Help us get ready for Drupal 12!
Core modules are actually not disruptive to deprecate, because we can create an equivalent package in contrib and provide sites a smooth upgrade path for these modules from Drupal 11 core to Drupal 12 contrib. Take a look at the list of modules and other dependencies planned for removal from Drupal 12, and consider helping move these issues forward.
Event Report: Drupal Contribution Japan – July 2025
On July 11, 2025, the Japanese Drupal community reached a significant milestone with the first-ever Drupal Contribution Day held in Tokyo. This groundbreaking event brought together developers, translators, and Drupal enthusiasts from across Japan for a full day of collaborative contribution to the Drupal project and the broader open web ecosystem.
Setting the Stage for DrupalCon Nara
This contribution day was strategically designed as part of our efforts to strengthen Japan's Drupal contributor base ahead of DrupalCon Nara in November 2025. With DrupalCon Nara featuring a dedicated contribution space for all three event days, we recognised the importance of preparing our rapidly growing Japanese Drupal community to actively participate in global Drupal development.
The event welcomed a diverse range of participants, from experienced developers looking to contribute bug fixes and patches to newcomers interested in translation work and community building. The inclusive atmosphere fostered collaboration between seasoned contributors and first-time participants, creating an ideal environment for knowledge sharing and skill development.
Empowering First-Time Contributors
A highlight of the day was the First Time Contributors Workshop, delivered in Japanese by Jimmy Cann from Ironstar. This workshop proved invaluable in breaking down barriers for new contributors, providing hands-on guidance on navigating Drupal's contribution processes, understanding issue queues, and making meaningful contributions to the project.
The workshop's success was evident in the enthusiastic participation throughout the day, with several attendees making their first contributions to Drupal core and contributed modules. Special thanks go to mradcliffe, ninelivesblackcat, and larowlan for their support.
Tackling Real-World Issues
After Jim's contribution workshop, participants broke off into three groups focused on contribution relevant to the local community and users:
Internationalisation and Localisation: The team worked on critical issues affecting Japanese users, including problems with content transliteration where Japanese text was incorrectly being transliterated as Chinese. This work directly impacts the user experience for Japanese Drupal sites and demonstrates the importance of having diverse, international contributors.
Metatag Module Improvements: Contributors focused on resolving canonical link issues in the Metatag module, particularly problems affecting multilingual sites where canonical links weren't properly referencing the current language page. This work has direct implications for SEO and site architecture in multilingual Drupal installations.
Core JavaScript Enhancements: Advanced contributors worked on updating core JavaScript functionality, including the removal of deprecated UIEvent.which usage, ensuring Drupal stays current with evolving web standards.
CKEditor Integration: The team addressed issues with CKEditor 5 integration, working on problems related to image handling and element spacing that affect content editor experiences.
Community Spirit and Collaboration
Japan is already home to a collection of experienced contributors and we were grateful to have some of them attend and help in the mentoring experience. As with other Drupal communities spread across the world, this was another contribution event where there was a natural emphasis on sharing, collaboration, and inclusiveness.
Acknowledgments
The success of this inaugural event would not have been possible without the generous support of our sponsors and the dedication of our speakers and participants.
Special thanks to our speakers:
Kensuke Naoe from Ironstar Japan
Jimmy Cann from Ironstar Australia
Heartfelt gratitude to our sponsors:
Genero
Ironstar Japan
Previous Next
Pixel Onion
Stirling Marketing
Most importantly, very special thanks to all attendees who volunteered their time and energy to make meaningful contributions to Drupal and the open web. Your dedication and enthusiasm made this event a resounding success.
Looking Forward
The inaugural Drupal Contribution Day Tokyo 2025 represents more than just a single successful event—it marks the beginning of a new chapter for Drupal contribution in Japan. As we approach DrupalCon Nara in November, we're excited about the momentum building within the Japanese Drupal community.
One of our central goals for planning DrupalCon Nara has been to ensure that local Japanese-speaking community members had an opportunity to engage in the conference in their own language, even though English is the primary language of the conference. We're excited to have nearly a third of all accepted sessions for Nara be in Japanese, and now to have an experience group of Drupal contributors who can act as Mentors for their local community in their own language.
The Future of Open Source in Japan
The inaugural Drupal Contribution Day Tokyo 2025 proved that when diverse minds come together with a shared commitment to the open web, great things happen. Here's to many more successful contribution days and a thriving Japanese Drupal community!
See you at DrupalCon Nara!
Mike Richardson, Chair, Drupal Asia Steering CommitteeFile attachments: IMG_3178.jpg IMG_3187.jpg
Setting the Stage for DrupalCon Nara
This contribution day was strategically designed as part of our efforts to strengthen Japan's Drupal contributor base ahead of DrupalCon Nara in November 2025. With DrupalCon Nara featuring a dedicated contribution space for all three event days, we recognised the importance of preparing our rapidly growing Japanese Drupal community to actively participate in global Drupal development.
The event welcomed a diverse range of participants, from experienced developers looking to contribute bug fixes and patches to newcomers interested in translation work and community building. The inclusive atmosphere fostered collaboration between seasoned contributors and first-time participants, creating an ideal environment for knowledge sharing and skill development.
Empowering First-Time Contributors
A highlight of the day was the First Time Contributors Workshop, delivered in Japanese by Jimmy Cann from Ironstar. This workshop proved invaluable in breaking down barriers for new contributors, providing hands-on guidance on navigating Drupal's contribution processes, understanding issue queues, and making meaningful contributions to the project.
The workshop's success was evident in the enthusiastic participation throughout the day, with several attendees making their first contributions to Drupal core and contributed modules. Special thanks go to mradcliffe, ninelivesblackcat, and larowlan for their support.
Tackling Real-World Issues
After Jim's contribution workshop, participants broke off into three groups focused on contribution relevant to the local community and users:
Internationalisation and Localisation: The team worked on critical issues affecting Japanese users, including problems with content transliteration where Japanese text was incorrectly being transliterated as Chinese. This work directly impacts the user experience for Japanese Drupal sites and demonstrates the importance of having diverse, international contributors.
Metatag Module Improvements: Contributors focused on resolving canonical link issues in the Metatag module, particularly problems affecting multilingual sites where canonical links weren't properly referencing the current language page. This work has direct implications for SEO and site architecture in multilingual Drupal installations.
Core JavaScript Enhancements: Advanced contributors worked on updating core JavaScript functionality, including the removal of deprecated UIEvent.which usage, ensuring Drupal stays current with evolving web standards.
CKEditor Integration: The team addressed issues with CKEditor 5 integration, working on problems related to image handling and element spacing that affect content editor experiences.
Community Spirit and Collaboration
Japan is already home to a collection of experienced contributors and we were grateful to have some of them attend and help in the mentoring experience. As with other Drupal communities spread across the world, this was another contribution event where there was a natural emphasis on sharing, collaboration, and inclusiveness.
Acknowledgments
The success of this inaugural event would not have been possible without the generous support of our sponsors and the dedication of our speakers and participants.
Special thanks to our speakers:
Kensuke Naoe from Ironstar Japan
Jimmy Cann from Ironstar Australia
Heartfelt gratitude to our sponsors:
Genero
Ironstar Japan
Previous Next
Pixel Onion
Stirling Marketing
Most importantly, very special thanks to all attendees who volunteered their time and energy to make meaningful contributions to Drupal and the open web. Your dedication and enthusiasm made this event a resounding success.
Looking Forward
The inaugural Drupal Contribution Day Tokyo 2025 represents more than just a single successful event—it marks the beginning of a new chapter for Drupal contribution in Japan. As we approach DrupalCon Nara in November, we're excited about the momentum building within the Japanese Drupal community.
One of our central goals for planning DrupalCon Nara has been to ensure that local Japanese-speaking community members had an opportunity to engage in the conference in their own language, even though English is the primary language of the conference. We're excited to have nearly a third of all accepted sessions for Nara be in Japanese, and now to have an experience group of Drupal contributors who can act as Mentors for their local community in their own language.
The Future of Open Source in Japan
The inaugural Drupal Contribution Day Tokyo 2025 proved that when diverse minds come together with a shared commitment to the open web, great things happen. Here's to many more successful contribution days and a thriving Japanese Drupal community!
See you at DrupalCon Nara!
Mike Richardson, Chair, Drupal Asia Steering CommitteeFile attachments: IMG_3178.jpg IMG_3187.jpg
