The Drop Times: DrevOps Releases Vortex 1.38.0 “Prism” with Testing, Mail Controls, and Security Hardening
DrevOps has released Vortex 1.38.0 “Prism”, updating its Drupal project template with JavaScript unit testing, email safeguards, deployment controls, and security hardening. The release focuses on operational reliability for Drupal teams, including changes to CI, configuration import handling, Renovate, and runtime support. It also moves the template baseline to PHP 8.4, Lagoon containers 26.4.0, and Drupal core 11.3.x.
read more
rss
Specbee: How bad tracking affects your data (and what can Google Tag Manager fix)?
Learn how incomplete tracking affects your analytics, why it leads to wrong decisions, and how Google Tag Manager helps create a reliable tracking setup.
read more
rss
amazee.io: Drupal Dev Days Athens 2026: Vibe Coding, Ancient Hospitality, and the Future of Drupal
Master fault-tolerant enterprise hosting with Kubernetes self-healing, multi-zone HA, and canary deployments. Learn how we ensure 24/7/365 reliability.
read more
rss
DDEV Blog: From a Single Chat to a Live Sponsorship Feed: DDEV's Sponsorship Data Story
In January 2025, Anoop John of TheDropTimes sent a LinkedIn message that set things in motion:
"Happy New Year. I was thinking we could put a live sponsorship tracker for DDEV on TDT. We should ask for people for $5 per month and we need 1000 people to hit the target right? What do you think?"
That message led to live, auto-updating DDEV sponsorship displays on multiple web properties, a public data repository, and a reusable web component—all feeding from a single source of truth.
The Challenge
DDEV's financial sustainability depends entirely on sponsorships (we have no other income). Communicating that need—and showing progress toward goals—requires getting accurate, up-to-date data in front of people where they already spend time. We wouldn't really expect to be successful with manual updates across multiple web and CLI properties.
What we needed was a data feed that could be consumed anywhere, updated (mostly) automatically, and displayed consistently.
The sponsorship-data Repository
Anoop's request spurred the creation of ddev/sponsorship-data, a public repository that aggregates sponsorship information from GitHub Sponsors and other sources, updated automatically. The data is published as structured JSON—for example, all-sponsorships.json—that any site or tool can consume.
Mark Conroy's Web Component
Mark Conroy stepped up with a reusable web component that reads from the sponsorship-data feed and renders live sponsorship information. The component lives at web-components.mark.ie and is open source at markconroy/web-components. (DDEV has forked the original in order to maintain it for our particular uses.)
The component makes it trivial to embed a live sponsor list on any site—no backend required, no manual updates.
Integration into DDEV Web Properties
With the data feed and component in place, we integrated the live sponsor display into ddev.com. Since then, it has been added to addons.ddev.com and docs.ddev.com. Source for each:
Now, when sponsors join or leave, the banner updates automatically. No manual edits, no stale lists.
What ddev start Shows
Most dedicated DDEV users aren't spending time on websites—they're in the terminal. ddev start has long provided a tip of the day, so we integrated the sponsorship feed into that output as well:
Some people report watching the numbers change day to day, cheering the project toward its goal.
Why This Matters
The sponsorship situation for DDEV is something we take seriously and we know you do also: the project needs ongoing financial support to continue development and be maintained over the long term. Getting that message in front of people—accurately and consistently—helps. We're all a community working together to make this work.
The path from Anoop's January 2025 LinkedIn message to live sponsor feeds across multiple properties took a few months of work by community members who cared.
Thanks to Anoop, The Drop Times, and Mark Conroy
More than a year later, The Drop Times is still featuring the DDEV sponsorship banner!
Thank you for your support, and thank you for your encouragement to go down this path. It has resulted in better communication with our community and a shared sense of ownership around DDEV's future.
Mark, your packaging of a nice banner made things so much easier!
Join in
If you use DDEV and find it valuable, consider sponsoring at github.com/sponsors/ddev. Every bit that you and your organization can contribute helps all of us. Thank you!
Before the Incident Report: How We Are Collaborative
At DrupalCon Chicago, the Driesnote included a visualization with “community” as one of the three pillars of Drupal, along with “platform” and “agencies.” That framing felt memorable, and worth exploring further.
If you attended DrupalCon Chicago, you might have experienced a slightly differently shaped triangle. I don’t know the attendance numbers, but I saw technical sessions with packed rooms, while community-focused sessions had plenty of empty seats. That’s not new. It’s been true for years. People care about community, but when the schedule forces a choice between a session on AI integration and one on community health, most folks choose the technical session. I understand why. Technical work feels concrete. Community work is generally not why employers send folks to a DrupalCon.
This raises a question: how can all of us work together to close that gap without having to attend community sessions at DrupalCon?
The Conflict Resolution Team handles incidents after they happen. If you file an incident report, they’re the ones who review it.
The Community Health Team works on everything that happens before an incident report, such as workshops, resources, and other preventive work. Our goal is to help the community build the kind of culture where fewer situations reach the reporting stage in the first place.
Both teams matter. And beyond the CWG, the DrupalCon Code of Conduct offers advice for all of us. It includes a section titled “We are collaborative,” which says:
If and when misunderstandings occur, we encourage people to work things out between themselves where this is practical. Where support is beneficial to achieve this, participants agree to ask for help. People are encouraged to take responsibility for their words and actions and listen to constructively-presented criticism with an open mind, courtesy, and respect.
I suspect that many people read the harassment list and the reporting email and stop there. That’s understandable. Those parts exist for a reason. But the passage above describes the wide middle ground where most friction in our community occurs.
The middle ground of community health
If the only two options we envision are “this is fine” and “file a report,” we end up with a lot of buried resentment, a few dramatic blowups, and not much in between. Most day-to-day friction doesn’t rise to the level of a Code of Conduct violation. It’s tone. Assumption. Misread intent. A comment in an issue queue from someone who didn’t scroll up to read what had already been said. A joke that came off differently than it was intended.
The Community Health Team’s work is to strengthen the middle. That means helping people develop the habits and skills to address friction directly, kindly, and early, so it doesn’t compound into something that needs the Conflict Resolution Team. The Code of Conduct invites everyone to do this work. Not just CWG members. Everyone.
Some ways we work things out
Here are four situations I’ve seen in the community, and in some cases been part of. None of these are scripts. They’re illustrations. The point is that the Code of Conduct invites you to try, and that you’re allowed to. You don’t need permission.
Late at night at a DrupalCon, after hours of sprinting and drinks in the hotel lobby, someone says something about another contributor that turns a few heads. That person might realize it the next day. The generous move, the one the Code asks for, is to find that person and say “I said something last night I want to walk back.” Not a grand apology. Just a small, honest correction. Most of the time, that’s the whole fix.
Someone drops a comment in an issue queue without reading the full thread above. Their comment reads as dismissive of work that’s already been done, or repeats a point that was already addressed, and it comes off as rude. They might not know that’s how it came across. A direct message from someone in the thread (“hey, I think you may have missed a few comments, here’s where we landed”) can turn that into nothing. A pile-on in the issue turns it into something else.
You witness an exchange between two people at DrupalCon that makes you wince. Maybe it’s cultural. The Drupal community spans continents, and directness that comes across as rude in one country seems normal in another. Maybe it’s a power dynamic, or a bad day, or both. Checking in with the person on the receiving end, just between the two of you (“I could not help but notice your conversation and I wanted to ask, are you doing okay?”), doesn’t escalate anything. It lets them know they weren’t invisible.
Someone keeps doing something that just doesn’t feel right. Not harmful, but grating. You can do your best to describe how it made you feel before it becomes a grudge you carry into every future interaction. “Hey, can I mention something? The way we’re doing X did not sit well with me, and I want to figure out how to talk about it.”
If you need help figuring out the best way to handle a situation like this, the Community Health Team is available. We can help you talk through a situation, decide whether a direct conversation is possible, or offer a second perspective. You can reach out at any time. We don’t investigate, and we don’t take sides. We think with you.
When it isn’t practical
The Code says “where this is practical.” Sometimes it isn’t.
We live in a world with power differences. If the person on the other side holds significant authority over your ability to contribute, a direct conversation may not be safe for you. Ongoing patterns of behavior are different from single incidents. Safety concerns are different from style concerns. And if the other person has shown they aren’t willing to engage in good faith, you are not obligated to keep trying.
Those are incidents for the Conflict Resolution Team. Those are the situations the people on that team signed up for, and you can reach them through the incident report form. Filing a report is not escalation for its own sake. It’s using the right tool for the situation.
The three-pillar framing
Returning to the Driesnote, if community is one of three pillars holding up Drupal, then the pillar can’t only be carried by the folks who show up to CWG sessions. The math doesn’t work. Community health has to happen in the rooms with the technical sessions, on the Slack channels where the code review happens, or at the dinner table where someone just got interrupted for the third time.
Most of the work the Community Health Team cares about isn’t work you need a whole session to learn. It’s work you’re already in a position to do. The next time something said in an issue queue doesn’t feel right, you catch yourself venting about someone, or you see a newcomer get talked over, you have a chance to support Drupal’s community.
Community is a pillar, which means it doesn't get held up by a small group of people with CWG in their session title. It gets held up, or it doesn't, by how we talk to each other on a Tuesday afternoon when no one's watching.
Drupal’s Code of Conduct doesn’t just give you a way to report harm. It also asks you to do the smaller, harder thing first. That’s where most community health happens.
Community Working Group posts: Before the Incident Report: How We Are Collaborative
At DrupalCon Chicago, the Driesnote included a visualization with “community” as one of the three pillars of Drupal, along with “platform” and “agencies.” That framing felt memorable, and worth exploring further.
If you attended DrupalCon Chicago, you might have experienced a slightly differently shaped triangle. I don’t know the attendance numbers, but I saw technical sessions with packed rooms, while community-focused sessions had plenty of empty seats. That’s not new. It’s been true for years. People care about community, but when the schedule forces a choice between a session on AI integration and one on community health, most folks choose the technical session. I understand why. Technical work feels concrete. Community work is generally not why employers send folks to a DrupalCon.
This raises a question: how can all of us work together to close that gap without having to attend community sessions at DrupalCon?
The Conflict Resolution Team handles incidents after they happen. If you file an incident report, they’re the ones who review it.
The Community Health Team works on everything that happens before an incident report, such as workshops, resources, and other preventive work. Our goal is to help the community build the kind of culture where fewer situations reach the reporting stage in the first place.
Both teams matter. And beyond the CWG, the DrupalCon Code of Conduct offers advice for all of us. It includes a section titled “We are collaborative,” which says:
If and when misunderstandings occur, we encourage people to work things out between themselves where this is practical. Where support is beneficial to achieve this, participants agree to ask for help. People are encouraged to take responsibility for their words and actions and listen to constructively-presented criticism with an open mind, courtesy, and respect.
I suspect that many people read the harassment list and the reporting email and stop there. That’s understandable. Those parts exist for a reason. But the passage above describes the wide middle ground where most friction in our community occurs.
The middle ground of community health
If the only two options we envision are “this is fine” and “file a report,” we end up with a lot of buried resentment, a few dramatic blowups, and not much in between. Most day-to-day friction doesn’t rise to the level of a Code of Conduct violation. It’s tone. Assumption. Misread intent. A comment in an issue queue from someone who didn’t scroll up to read what had already been said. A joke that came off differently than it was intended.
The Community Health Team’s work is to strengthen the middle. That means helping people develop the habits and skills to address friction directly, kindly, and early, so it doesn’t compound into something that needs the Conflict Resolution Team. The Code of Conduct invites everyone to do this work. Not just CWG members. Everyone.
Some ways we work things out
Here are four situations I’ve seen in the community, and in some cases been part of. None of these are scripts. They’re illustrations. The point is that the Code of Conduct invites you to try, and that you’re allowed to. You don’t need permission.
Late at night at a DrupalCon, after hours of sprinting and drinks in the hotel lobby, someone says something about another contributor that turns a few heads. That person might realize it the next day. The generous move, the one the Code asks for, is to find that person and say “I said something last night I want to walk back.” Not a grand apology. Just a small, honest correction. Most of the time, that’s the whole fix.
Someone drops a comment in an issue queue without reading the full thread above. Their comment reads as dismissive of work that’s already been done, or repeats a point that was already addressed, and it comes off as rude. They might not know that’s how it came across. A direct message from someone in the thread (“hey, I think you may have missed a few comments, here’s where we landed”) can turn that into nothing. A pile-on in the issue turns it into something else.
You witness an exchange between two people at DrupalCon that makes you wince. Maybe it’s cultural. The Drupal community spans continents, and directness that comes across as rude in one country seems normal in another. Maybe it’s a power dynamic, or a bad day, or both. Checking in with the person on the receiving end, just between the two of you (“I could not help but notice your conversation and I wanted to ask, are you doing okay?”), doesn’t escalate anything. It lets them know they weren’t invisible.
Someone keeps doing something that just doesn’t feel right. Not harmful, but grating. You can do your best to describe how it made you feel before it becomes a grudge you carry into every future interaction. “Hey, can I mention something? The way we’re doing X did not sit well with me, and I want to figure out how to talk about it.”
If you need help figuring out the best way to handle a situation like this, the Community Health Team is available. We can help you talk through a situation, decide whether a direct conversation is possible, or offer a second perspective. You can reach out at any time. We don’t investigate, and we don’t take sides. We think with you.
When it isn’t practical
The Code says “where this is practical.” Sometimes it isn’t.
We live in a world with power differences. If the person on the other side holds significant authority over your ability to contribute, a direct conversation may not be safe for you. Ongoing patterns of behavior are different from single incidents. Safety concerns are different from style concerns. And if the other person has shown they aren’t willing to engage in good faith, you are not obligated to keep trying.
Those are incidents for the Conflict Resolution Team. Those are the situations the people on that team signed up for, and you can reach them through the incident report form. Filing a report is not escalation for its own sake. It’s using the right tool for the situation.
The three-pillar framing
Returning to the Driesnote, if community is one of three pillars holding up Drupal, then the pillar can’t only be carried by the folks who show up to CWG sessions. The math doesn’t work. Community health has to happen in the rooms with the technical sessions, on the Slack channels where the code review happens, or at the dinner table where someone just got interrupted for the third time.
Most of the work the Community Health Team cares about isn’t work you need a whole session to learn. It’s work you’re already in a position to do. The next time something said in an issue queue doesn’t feel right, you catch yourself venting about someone, or you see a newcomer get talked over, you have a chance to support Drupal’s community.
Community is a pillar, which means it doesn't get held up by a small group of people with CWG in their session title. It gets held up, or it doesn't, by how we talk to each other on a Tuesday afternoon when no one's watching.
Drupal’s Code of Conduct doesn’t just give you a way to report harm. It also asks you to do the smaller, harder thing first. That’s where most community health happens.
Kevin Thull, who leads the Drupal Recording Initiative (DRI), joins us to discuss why DRI started, how it scaled from Kevin recording local camps to supporting many events, the hub-and-mentorship model for maintainers, differences between shipping kits vs onsite support, costs compared with traditional AV vendors, and challenges like aging capture hardware, audio/video troubleshooting, and sustainable funding.
Two Factor Authentication - Two-factor authentication for Drupal sites. Drupal provides authentication via something you know – a username and password while TFA module adds a second step of authentication with a check for something you have – such as a code sent to (or generated by) your mobile phone.
TFA is a base module for providing two-factor authentication for your Drupal site. As a base module, TFA handles the work of integrating with Drupal, providing flexible and well tested interfaces to enable your choice of various two-factor authentication solutions like Time-based One-Time Passwords (TOTP), SMS-delivered codes, pre-generated codes, or integrations with third-party services like Authy, Duo and others.
UI Suite Initiative website: Video series - #03 Display Builder for Drupal: Entity View Display Explained
A walkthrough of how Display Builder (by UI Suite) takes control of your entity displays — and plays nicely with the tools you already use.The Display Builder module continues to mature, and in his latest video, Pierre walks us through one of its most practical features: Entity View Display. If you've been following the series, this third installment builds directly on the foundations laid in the first two videos (component-based layouts and the plugin system). If you haven't seen those yet, this post should still give you a clear picture of what's possible.You can watch the full demo here: Entity View Display — Display Builder Beta
read more
rss
The Drop Times: Who Will Inherit the Code?
Dear readers,
There is a quiet crisis unfolding in the Drupal ecosystem, and the community has yet to fully reckon with it. Beginner training programs, once the pipeline through which new developers discovered and committed to Drupal, are drying up one by one. DrupalEasy has sunset its flagship 15-year-old Drupal Career Online program. Drupalize.me has had to let staff go. DrupalTutor reports his student count has collapsed to roughly a quarter of what it was three years ago. These are not isolated setbacks; they are symptoms of a structural problem that cuts to the heart of Drupal's long-term viability.
What makes this moment especially sobering is that no single villain is to blame. The increasing complexity of post-Drupal 8, the rise of AI-assisted learning that lets developers skip foundational training, and a community that has historically leaned on technical excellence over outreach have all converged at once. Meanwhile, DrupalCon survey data hints at another uncomfortable truth: the community's flagship gathering risks becoming an insider circuit, where veterans feel at home and newcomers feel invisible. A closed loop, no matter how vibrant, eventually runs out of energy.
The path forward demands more than awareness; it demands coordinated will. Nascent initiatives like Drupal Open University, the IXP hiring incentive, and the Promote Drupal campaign are promising, but they cannot succeed as isolated efforts. The Drupal Association, its Certified Partners, and community leaders at every level must align behind a single, urgent mission: making Drupal the place where the next generation of developers begins, not just where the current generation convenes.
On a personal note,as I script my final newsletter as the sub-editor of The DropTimes, I extend my heartfelt gratitude to my teammates at TDT and the whole of Drupal Community for the amazing work they are doing and letting me be a part of it. Thank you!
Let's move on to the story highlights from past week.
Additional developments from across the Drupal ecosystem were published during the week. Readers can follow The Drop Times on LinkedIn, Twitter, Bluesky, and Facebook for ongoing updates. The publication is also active on Drupal Slack in the #thedroptimes channel.
Sitback Solutions: Helping NSW households and businesses unlock energy savings
The NSW Government is focused on helping households and businesses reduce energy costs while accelerating the state’s transition to a more sustainable future. Through targeted rebates, programs and policy initiatives, the Department of Climate Change, Energy, the Environment and Water (DCCEEW) is working to make energy upgrades more accessible and more achievable for everyday people. ...read more
rss
Drupal AI Learners Club Is Here. And You're Invited.
Article by: María Fernanda Silva
If you’ve spent any time around Drupal lately, you’ve probably noticed that AI is everywhere — in the keynotes, in the hallway conversations, in the issue queues. You may also have noticed that everyone else seems to know what they're doing, while you're still trying to figure out where to start.
You are not. Not even close.
Those questions — what is actually going on, and where do I even start? — are exactly what the Drupal AI Learners Club was built for.
Where it started
Angie Byron (webchick) has been part of the Drupal community since 2005: core committer, one of the driving forces behind Drupal 8, and one of those people everyone seems to know. She did not come to DrupalCon Chicago 2026 planning to start anything. She came to celebrate Drupal's 25th anniversary and catch up with old friends.
But somewhere between the hallway conversations and the late-night tables, she started picking up on something: a lot of people were anxious about AI, unsure what it meant for their work, their identity as Drupal developers, their community — and quietly terrified to admit they did not have it figured out.
"I don't know what is going on, and neither do you," she would later describe as the feeling she wanted to create space for. "It's fine. Nobody knows. It's changing too fast."
That feeling stuck with her. And the Drupal AI Learners Club was born. Not as a space to hype AI, and not as a space to condemn it, but as a place to cut through the noise and talk honestly about what these tools actually do, how people are using them, and where they fall short.
Just show up
The club runs on a simple premise: come as you are. Sessions are low-pressure, informal, and require no prepared presentation. Participants share their setups, their workflows, what is working, and what is not.
The first session launched on April 8, 2026, with the topic "Share Your Setup!" and brought together community members to walk through the models, modules, agents, IDEs, and tools they were actually using day-to-day.
Sessions happen whenever someone steps up to talk about something (currently, ~weekly) and are recorded, so anyone who cannot attend live can catch up afterward. And as Angie puts it, there are no stupid questions. Everyone is here to learn, including the people who have been doing this the longest.
Join the conversation
The Drupal AI Learners Club is not here to tell you AI is the future. It’s here to make sure that wherever this is going, the Drupal community goes together — developers, site builders, contributors, and everyone in between.
There are many ways to join the club: attend a session, suggest a topic, volunteer to present, or join the organizing team. Sessions are published to a playlist on the Drupal Association YouTube channel so you can catch up anytime, and the conversation keeps going in the #ai-learners channel on Drupal Slack.
And remember, as the Spanish proverb says: there is no silly question — only silly people who do not ask.
Drupal AI Initiative: Drupal AI Learners Club Is Here. And You're Invited.
Article by: María Fernanda Silva
If you’ve spent any time around Drupal lately, you’ve probably noticed that AI is everywhere — in the keynotes, in the hallway conversations, in the issue queues. You may also have noticed that everyone else seems to know what they're doing, while you're still trying to figure out where to start.
You are not. Not even close.
Those questions — what is actually going on, and where do I even start? — are exactly what the Drupal AI Learners Club was built for.
Where it started
Angie Byron (webchick) has been part of the Drupal community since 2005: core committer, one of the driving forces behind Drupal 8, and one of those people everyone seems to know. She did not come to DrupalCon Chicago 2026 planning to start anything. She came to celebrate Drupal's 25th anniversary and catch up with old friends. But somewhere between the hallway conversations and the late-night tables, she started picking up on something: a lot of people were anxious about AI, unsure what it meant for their work, their identity as Drupal developers, their community — and quietly terrified to admit they did not have it figured out.
"I don't know what is going on, and neither do you," she would later describe as the feeling she wanted to create space for. "It's fine. Nobody knows. It's changing too fast."
That feeling stuck with her. And the Drupal AI Learners Club was born. Not as a space to hype AI, and not as a space to condemn it, but as a place to cut through the noise and talk honestly about what these tools actually do, how people are using them, and where they fall short.
Just show up
The club runs on a simple premise: come as you are. Sessions are low-pressure, informal, and require no prepared presentation. Participants share their setups, their workflows, what is working, and what is not. The first session launched on April 8, 2025, with the topic "Share Your Setup!" and brought together community members to walk through the models, modules, agents, IDEs, and tools they were actually using day-to-day.
Sessions happen whenever someone steps up to talk about something (currently, ~weekly) and are recorded, so anyone who cannot attend live can catch up afterward. And as Angie puts it, there are no stupid questions. Everyone is here to learn, including the people who have been doing this the longest.
Join the conversation
The Drupal AI Learners Club is not here to tell you AI is the future. It’s here to make sure that wherever this is going, the Drupal community goes together — developers, site builders, contributors, and everyone in between.
There are many ways to join the club: attend a session, suggest a topic, volunteer to present, or join the organizing team. Sessions are published to a playlist on the Drupal Association YouTube channel so you can catch up anytime, and the conversation keeps going in the #ai-learners channel on Drupal Slack.
And remember, as the Spanish proverb says: there is no silly question — only silly people who do not ask.
Introducing Entity Webhook: Config-Driven Webhook Integration for DrupalJoel SteidlDrupal
Webhooks are one of the most useful tools in a modern integration toolkit. Instead of your Drupal site repeatedly asking "anything new?" on a schedule, an external system taps your shoulder the moment something changes. The result is faster data, fewer redundant requests, and integrations that actually behave like real-time systems.
At Aten, we build a lot of integrations. A recent project made the need for a more complete webhook solution clear: a client needed a centralized hub that could aggregate order data from Shopify and multiple Drupal Commerce sites, and keep customer addresses synchronized across all of them. Data was flowing in multiple directions, from multiple sources, with different payload formats. The existing options in the Drupal ecosystem either required significant custom code or handled one direction well but not the other. So we built something.
We're excited to introduce Entity Webhook, now available as a contributed module on drupal.org.
What Is Entity Webhook?
Entity Webhook gives Drupal a complete webhook toolkit built around three capabilities:
Inbound (core module): Receive JSON payloads from external services and automatically create or update Drupal entities
Outbound (entity_webhook_broadcast submodule): Notify external systems when Drupal entities are created, updated, or deleted
Polling (entity_webhook_polling submodule): Actively fetch data from external APIs on a schedule, as a fallback for systems that don't push webhooks
The key design decision: all three are driven by the admin UI. No custom module code is required to get a working integration.
Receiving Webhooks and Upserting Entities
The core module handles inbound webhooks through a three-tier configuration structure: endpoints, source types, and field mappings.
An endpoint defines the target entity type — a Commerce Order, a taxonomy term, a user, or any custom entity. A source type represents a particular payload format from a particular service (Shopify, Stripe, another Drupal site), along with its verification method. A field mapping connects a JSON value in the payload to a Drupal entity field.
Once configured, external services POST to:
/webhook/{endpoint_name}/{source_type}
The module responds immediately with a 200, queues the payload, and processes it asynchronously during cron — keeping your endpoint fast and your site stable under load.
Flexible Field Extraction
Field values are extracted from the JSON payload using JSONPath expressions. A mapping like $.order.billing_address.first_name can reach deep into a nested payload structure. You can also combine multiple expressions or use hardcoded static values.
Before a value is written to an entity field, you can optionally run it through a mutation plugin to transform it: convert an ISO date string to a Unix timestamp, map a source status to a Drupal equivalent (paid → completed), convert a cents integer to a decimal price, apply a regex substitution, and more.
Deduplication and Updates
To keep entities in sync rather than creating duplicates, you mark one or more field mappings as identifiers. Before saving, the module performs a lookup — if an entity with those field values already exists, it updates it instead of creating a new one. Multiple identifier fields form a composite key.
Verification Built In
Three verification plugins are included: HMAC-SHA256 signature validation (with configurable header name and encoding), API Key validation from a header or query parameter, and an IP/CIDR whitelist. All verification runs synchronously before any processing begins.
Developer Extensibility
When configuration isn't enough, the module dispatches Symfony events before and after entity saves. A PreSaveEvent subscriber can modify the entity or cancel the save entirely. A PostSaveEvent subscriber can trigger downstream workflows or notifications — without touching core module code.
Broadcasting Outbound Webhooks
The entity_webhook_broadcast submodule monitors entity CRUD events and delivers signed JSON payloads to external endpoints. You configure outbound field mappings to define the payload shape, set a shared secret for HMAC-SHA256 signing, and optionally define conditions that filter which events trigger a broadcast.
Delivery is queue-based and asynchronous. If a delivery fails, the module retries with exponential backoff up to a configurable number of attempts. Every attempt — successful or not — is written to an audit log, which makes debugging integrations considerably less painful.
Polling for APIs That Don't Push
Not every external service supports webhooks. The entity_webhook_polling submodule handles those cases. You configure a schedule using a standard cron expression (e.g., */15****), implement a polling provider plugin for your API, and it feeds results into the same entity upsert pipeline used by inbound webhooks.
To avoid unnecessary processing, each fetched record is hashed with SHA-256. Only records whose hash has changed since the last run are queued for processing.
How It Compares to Other Webhook Modules
There are a few other maintained, Drupal 11-compatible webhook modules worth knowing about. Here's how they differ, based on reviewing each module's source code.
Feature
entity_webhook
webhooks
webhook_receiver
symfony_webhook_receiver
Inbound webhooks
✓
✓
✓
✓
Entity upsert — config-driven, no code
✓
—
—
—
Field mapping UI
✓
—
—
—
Outbound broadcasting
Submodule
✓
—
—
Polling
Submodule
—
—
—
HMAC verification
✓
✓
Token-in-URL only
Symfony-native
API Key / IP whitelist verification
✓
—
—
—
Admin UI
✓
✓
—
—
Custom code required to process inbound
—
✓
✓
✓
Drupal 11 compatible
✓
✓
✓
✓
Webhooks is the most established option and works well for outbound use cases. When it receives a webhook, it fires a webhook.receive Drupal event — your code handles what happens next. That flexibility is useful, but it means every inbound integration requires a custom event subscriber and no entity upsert comes for free.
Webhook Receiver is a code-first plugin framework. Its README is straightforward about this: "This module does not contain any graphical user interface." You extend a plugin base class, implement validatePayload() and processPayload(), and wire everything together in code. It's a solid foundation for developers building bespoke integrations, but every integration is custom work from scratch.
Symfony Webhook Receiver brings Symfony's Webhook component into Drupal. If your team is comfortable with Symfony's ConsumerInterface and service container conventions, it's a clean approach. Like the others, it has no admin UI, and each integration requires custom service definitions and consumer classes.
Entity Webhook is designed for the scenario where you want integrations to live in configuration — deployable, exportable via Drupal's config management, and maintainable without a developer on call every time a payload format changes.
Getting Started
composer require drupal/entity_webhook
drush en entity_webhook
# Enable submodules as needed:
drush en entity_webhook_broadcast entity_webhook_polling
Then navigate to Administration > Configuration > Services > Entity Webhook to create your first endpoint. Full documentation is on the project page.
Let's Build Something
If you're working on a Drupal integration — connecting an e-commerce platform, a CRM, a payment processor, or another Drupal site — we'd love to help. Get in touch with the Aten team.
The Drop Times: LocalGov Drupal Community Advances Committee Management Proposal with Project Quorum
A proposal emerging from the LocalGov Drupal community outlines a shared, open-source approach to committee management in councils. Known as Project Quorum, the initiative focuses on consolidating governance workflows—meetings, agendas, documentation, and public access—into a single Drupal-based platform. While such systems are often overlooked in digital prioritisation due to fragmented usage patterns, community feedback suggests the tool addresses persistent operational gaps across councils.
read more
rss
The Drop Times: For Community, By Community: Stanford WebCamp 2026 Opens Today
Stanford WebCamp 2026 opens its doors today, and as always, it will cost nothing to attend. Free, open, and community-driven for sixteen years, this year's edition arrives at a charged moment for the web: AI is reshaping institutional infrastructure at scale, while the open source values that built the web continue to hold their ground. From a keynote on AI as infrastructure to sessions on accessibility and mentorship, WebCamp 2026 reflects a conversation the web community is having with itself.
read more
rss
DDEV Blog: DDEV April 2026: Talking Drupal, Ubuntu 26.04, coder.ddev.com, Intel Macs fade away, Add-ons as delivery mechanism
What's New
Ubuntu 26.04 and Fedora 44 were released this week. We checked, and we're proud to say that DDEV works great on both. We have one small docs change for the Ubuntu 26.04 native install. The Windows Installer did fail with an Ubuntu 26.04 distro because the wslu package has been removed, but we fixed that in PR, and it has an easy workaround anyway.
coder.ddev.com Updates → More work is ongoing with Coder.ddev.com, we're hoping to make it fulfil even more of your ambitions. drush works again for Drupal's main branch, and there are lots of other updates. Lots of other updates. Visit coder.ddev.com and start.coder.ddev.com for more, and we'd love to hear your suggestions and experiences at coder-ddev repository or in the DDEV Discord. We've deployed a staging server, and have plans for automated testing of changes so we don't just deploy and try them out.
Intel Macs have run their course → We'll be retiring our three macOS AMD64 test runners. There's not much more for them to do, so we're going to turn them off. Only 7.3% of you are still using Intel Macs and it's been a very long time since we saw a regression or problem on the Intel test runners that wasn't also caught by the Apple Silicon runners. See the stats.
Talking Drupal Podcast
Stas and Randy appeared on episode 549 of the Talking Drupal podcast. Get the inside scoop on latest DDEV updates, the DDEV Drupal Contrib add-on, coder.ddev.com, and more. Listen to episode 549↗
DrupalDevDays Athens 2026
Community member bserem presented "From Chaos to Consistency" at DrupalDevDays Athens 2026, a DevOps session covering how DDEV brings order to local development environments. View the presentation slides↗. His correct and well-explained thesis is that DDEV add-ons are just a file/feature delivery mechanism that can be used to systematize your team's projects. Watch here for a blog from him!
Add-on Creation and Maintenance Contributor Training: Watch it↗
TYPO3 Update for DDEV
The TYPO3 community published a post on what's new in DDEV for TYPO3 developers. Read on TYPO3 News↗
Community Tutorials from Around the Web
Getting Started with Search API in Drupal → WebWash covers how to set up and use the Search API module in Drupal — useful alongside a DDEV local environment. Read on WebWash↗
The next DDEV board and advisory group meeting is May 6, 2026 at 8:00 AM US Mountain / 10:00 AM US Eastern / 16:00 CEST.
Add to Google Calendar • See the agenda.
Note: Randy on Vacation May 19–June 9
Randy will be away May 19 through approximately June 9, on a bike trip in Sicily. The community will carry on!
Sponsorship Update
Sponsorship is at 79% of the goal — thank you to everyone who has contributed!
March 2026: ~$9,294/month (77% of goal)
April 2026: ~$9421/month (79% of goal), making progress, thanks!
If DDEV has helped your team, consider sponsoring. Whether you're an individual developer, an agency, or an organization, your contribution makes a difference. → Become a sponsor↗
Contact us to discuss sponsorship options that work for your organization.
Improvements to Drupal.org project maintainers syncing with GitLab project members
As we migrate more projects to GitLab on git.drupalcode.org, we have discovered improvements to make in the mapping of Drupal.org project maintainers to GitLab’s project members, ensuring that it is a 2-way synchronization.
The next time you update maintainers for your project on Drupal.org, this will update all maintainers’ access in GitLab. Please review project members in GitLab, and under Activity, the Team events. Syncing is now more thorough, so there might be more maintainership and member changes than you expect.
In the next few days we plan to bulk update GitLab project members for all projects that have maintainers with “Maintain issues” on Drupal.org, granting them the project planner role in GitLab. This will enable more access for them to manage issues and merge requests in GitLab.
We reviewed all the mappings and have settled on:
“Write to VCS” on Drupal.org grants the GitLab project developer role.
Having both “Administer maintainers” and “Write to VCS” grants the GitLab project maintainer role.
“Maintain issues” grants the GitLab project planner role.
Other Drupal project maintainership roles are not synced.
Syncing is two-way, so that saving maintainers in Drupal will keep choices made in GitLab.
Maintainer in GitLab grants “Write to VCS” and “Administer maintainers,” matching GitLab’s “Administer maintainers” permission on Drupal.org.
Developer grants “Write to VCS” and removes “Administer maintainers.”
Planner grants “Maintain issues” and removes both “Write to VCS” and “Administer maintainers.”
Reporter and Guest remove “Maintain issues,” “Write to VCS,” and “Administer maintainers.”
Reporter is very similar to planner, however it acts the same as guest for maintainership mapping. This preserves access when flipping between setting permissions in GitLab or Drupal. Access to “Maintain issues” in Drupal is mostly irrelevant with issues migrating.
Maintainer in GitLab previously did not grant “Administer maintainers.” It should because in GitLab, it allows the Manage project members permission, so it is a direct mapping.
Removing a maintainer in GitLab will
If they were the project node author on Drupal.org, assign authorship to another person with “Administer maintainers,” or fall back to Unsupported projects.
Remove “Maintain issues,” “Write to VCS,” and “Administer maintainers.”
Not change access to “Edit project” or “Administer releases.”
If they have no remaining Drupal.org project maintainership roles, completely remove them as a maintainer.
In addition to filling the gaps in the mappings, updates to maintainership in GitLab were missed, we hadn’t implemented a listener for the user_update_for_team webhook. So updating maintainers on Drupal.org will catch up all project member roles in GitLab.
Once all issues are migrated, “Maintain issues” will be removed from Drupal, and GitLab itself will be the only way to manage access below developer.
Drupal.org blog: Improvements to Drupal.org project maintainers syncing with GitLab project members
As we migrate more projects to GitLab on git.drupalcode.org, we have discovered improvements to make in the mapping of Drupal.org project maintainers to GitLab’s project members, ensuring that it is a 2-way synchronization.
The next time you update maintainers for your project on Drupal.org, this will update all maintainers’ access in GitLab. Please review project members in GitLab, and under Activity, the Team events. Syncing is now more thorough, so there might be more maintainership and member changes than you expect.
In the next few days we plan to bulk update GitLab project members for all projects that have maintainers with “Maintain issues” on Drupal.org, granting them the project planner role in GitLab. This will enable more access for them to manage issues and merge requests in GitLab.
We reviewed all the mappings and have settled on:
“Write to VCS” on Drupal.org grants the GitLab project developer role.
Having both “Administer maintainers” and “Write to VCS” grants the GitLab project maintainer role.
“Maintain issues” grants the GitLab project planner role.
Other Drupal project maintainership roles are not synced.
Syncing is two-way, so that saving maintainers in Drupal will keep choices made in GitLab.
Maintainer in GitLab grants “Write to VCS” and “Administer maintainers,” matching GitLab’s “Administer maintainers” permission on Drupal.org.
Developer grants “Write to VCS” and removes “Administer maintainers.”
Planner grants “Maintain issues” and removes both “Write to VCS” and “Administer maintainers.”
Reporter and Guest remove “Maintain issues,” “Write to VCS,” and “Administer maintainers.”
Reporter is very similar to planner, however it acts the same as guest for maintainership mapping. This preserves access when flipping between setting permissions in GitLab or Drupal. Access to “Maintain issues” in Drupal is mostly irrelevant with issues migrating.
Maintainer in GitLab previously did not grant “Administer maintainers.” It should because in GitLab, it allows the Manage project members permission, so it is a direct mapping.
Removing a maintainer in GitLab will
If they were the project node author on Drupal.org, assign authorship to another person with “Administer maintainers,” or fall back to Unsupported projects.
Remove “Maintain issues,” “Write to VCS,” and “Administer maintainers.”
Not change access to “Edit project” or “Administer releases.”
If they have no remaining Drupal.org project maintainership roles, completely remove them as a maintainer.
In addition to filling the gaps in the mappings, updates to maintainership in GitLab were missed, we hadn’t implemented a listener for the user_update_for_team webhook. So updating maintainers on Drupal.org will catch up all project member roles in GitLab.
Once all issues are migrated, “Maintain issues” will be removed from Drupal, and GitLab itself will be the only way to manage access below developer.
The Drop Times: DrupalCamp Ottawa 2026 to Highlight Drupal 11, AI Workflows, and Accessibility Practices
DrupalCamp Ottawa 2026 will take place on 1 May 2026 at the Canada Science and Technology Museum, continuing its free, community-driven format. This year’s programme reflects a shift toward practical adoption, with sessions centred on Drupal 11, accessibility, multilingual delivery, and AI integration. Organisers describe the event as designed to balance technical depth with open participation, bringing together local and global contributors across disciplines.
read more
rss
Jacob Rockowitz: Drupal (AI) Playground: Using the AI Schema.org JSON-LD module to "feed the machines"
Preamble
I've been discussing and committed to a Schema.org-first approach to building content models in Drupal for several years. Along the way, someone described Schema.org as "food for machines."
Originally, for Schema.org "machines" meant search engines; now it definitely means AIs and LLMs. Defining and generating accurate, well-structured Schema.org JSON-LD for a website is challenging and often treated as an afterthought. Even if you use my Schema.org Blueprints to create a Schema.org-first content model, it still requires significant work to set up and maintain.
AI can analyze vast amounts of information and provide instant answers to complex questions, or complete challenging tasks within minutes. Last year, I began to see how one could prompt an AI to recommend the ideal Schema.org JSON-LD markup by providing URLs to example content and linking to the appropriate Schema.org types and properties. Keep in mind that the LLMs behind AIs understand every public webpage and actively examine every piece of Schema.org markup on the web.
This realization led me to the notion that in Drupal, we can leverage our existing AI modules and tools to have AIs generate Schema.org JSON-LD markup for content with as little as a well-thought-out prompt.
Before I introduce you to my AI Schema.org JSON-LD module, three things need to be stated immediately and will be addressed in this post and a follow-up.
The remainder of this post is directly copied from the module's project page, with the understanding that additional posts are needed to cover the implications of this module for developers, such as myself, and for site builders and owners.
The Drop Times: Fast Code, Faster Debt: Why Eduardo Telaya Built Drupal AI
Eduardo Telaya spent months reviewing Drupal code where the same AI-generated mistakes kept appearing across projects. Rather than treating them as isolated issues, he identified a structural gap between AI tools and Drupal best practices. That insight led to Drupal AI, a toolkit of skills, rules, and agents designed to guide coding assistants and reduce technical debt in AI-assisted development.
read more
rss
HOOK_DEV_ALTER(): Build a Feature-Rich Frontpage in Drupal: Canvas vs Display Builder (Part 3)
Building a flexible Frontpage has historically been a challenge in Drupal. Often, there is no fixed data model, and editors need the ability to quickly add, remove, or rearrange content. In this article, we compare how Canvas and Display Builder handle this scenario without relying on predefined fields, using only components. After all this will allows us to build all kinds of flexible pages, not just the Frontpage.
Show & Tell: CMS Cultivator — Skills for both Drupal and WordPress sites (Jim Birch)
A walkthrough of the https://github.com/kanopi/cms-cultivator repo that contains several useful agent skills for folks building both Drupal and WordPress sites, along with agents to do QA and site audits.
read more
youtube
Talk: Introduction to Agent Skills (Jim Birch)
In this talk, Jim Birch (Kanopi Studios) shares brief introduction to Agent Skills: What they are, how to use them, best practices in developing and distributing them.
read more
rss
Dries Buytaert: AI rewards strict APIs
Every framework's API surface sits on a spectrum, from strict (typed interfaces, schemas, service containers) to loose (string keys, naming conventions, untyped hooks). Strict APIs cost more upfront: more boilerplate, more to learn before writing code. Loose APIs shift that cost later: more ambiguity, more reliance on naming conventions, and more bugs that are harder to detect and fix.
AI changes who pays. Boilerplate and learning curves don't slow agents down. What slows them down is missing feedback: code that runs but does the wrong thing, errors that don't point to the cause, conventions that have to be guessed. Magic-name binding, untyped hooks, unvalidated configuration, and conventions the code doesn't enforce produce exactly those failure modes.
Magic strings break the loop
For example, both Drupal and WordPress have long used magic-string hooks. In Drupal, you write a function like mymodule_user_login. WordPress uses a related pattern: a string action name passed to add_action(). In both cases, the binding is a string the language can't validate.
Get the name wrong and the system silently skips your code: no error, no warning, nothing in the logs. The function just sits there, unloved.
The signature is a convention, not a contract: the documentation says the user_login hook receives a $user object, but nothing enforces it. To your IDE or a static analyzer like PHPStan, it's just a function. They don't know it's wired into the platform's login flow, so they can't warn you when it's wrong.
A typed alternative makes the binding explicit. With a PHP attribute like #[Hook('user_login')] on a registered service, the class must exist, the method signature is type-checked, and the container wires the dependencies. IDEs, static analyzers, and AI coding agents can follow the chain from the attribute to the implementation.
For AI agents, this keeps the feedback loop tight instead of turning it into trial and error. That means they can move faster, spend less time debugging, and use fewer tokens.
At DrupalCon Chicago this March, AI coding tools migrated a Lovable-generated site into Drupal in hours. The strict APIs kept the agent on track.
A bet made before AI existed
This didn't start with AI. Drupal 8, which we shipped in 2015, introduced Symfony's routing, services, and event dispatcher, replacing large parts of the procedural hook system. Since then, we've kept reducing magic hooks. The attribute-based approach (#[Hook('user_login')]) landed in Drupal 11.1 and helps remove more of the remaining procedural-only paths.
Hooks aren't the only place Drupal has been getting stricter. Drupal stores a lot of configuration in YAML, which was one of the loosest parts of the system. A multi-year validation effort has been tightening that.
When an agent generates a content type definition or editor configuration, validation catches missing keys, invalid values, and broken references before anything is saved. The agent gets a precise error pointing to the exact field, instead of a runtime failure. That tight feedback loop is what makes Drupal a strong CMS for AI-assisted development.
Drupal made this bet early, and it was painful. The Drupal 7 to Drupal 8 transition broke backward compatibility and took years to recover from. But it left the platform much stricter. More than ten years in, we're still making Drupal stricter.
Meanwhile, WordPress made a different bet, prioritizing backward compatibility over stricter APIs. That kept the platform stable for a long time. It also kept the looseness.
Those trade-offs now determine how efficiently AI agents can work with each platform.
What was style is now speed
What used to be a stylistic choice is now a speed and cost problem. Loose APIs mean more debugging and guesswork. Strict APIs mean faster, more precise feedback. This was always true for humans. It's now also true for AI agents. But today that cost shows up in tokens.
Webinar: How Southwark Council is Using AI to Transform PDF Publishing in Drupal
Join us to hear directly from the team behind an award-winning AI solution built for local government. What does genuinely useful AI in public services look like? Not a concept, not a pilot, but a working solution that saves hours of manual work, improves accessibility, and puts better content in front of citizens faster.
We are delighted to invite you to a webinar where you can hear the story first-hand.
About the webinar
Date: Tuesday 16th June | 16:00 BST Guest: Angie Forson, Web and Digital Programme Lead, Southwark Council Host: James Hall, Product Lead, Websites at Everyone TV
This is a rare opportunity to hear directly from a senior stakeholder about how Drupal and AI are delivering real, measurable value in an area that truly matters: public services for the citizens of Southwark.
Angie will walk through the journey, the challenges, the outcomes, and what it means for the wider local government sector.
Manual PDF conversion has long been one of the most time-consuming tasks facing council web teams. Converting a single document can take hours. Multiply that across thousands of PDFs and the burden becomes significant, both in staff time and in the delay it creates before citizens can access accurate, accessible information.
The Southwark team, working with their partners at Chicken, built an AI-powered importer for the LocalGov Drupal Publication Module that reduces that process to minutes, often under one minute.
How it works
Each PDF passes through a three-step pipeline:
Extract - a PDF parser pulls the raw content from the document
Transform - AI converts it to properly structured, accessible HTML with logical pagination
Save - clean HTML pages are ready to review and publish directly in Drupal
The result is an HTML representation of the PDF content, saved into a Drupal Publication and ready for review before going live. Every import is logged, so errors can be identified and resolved efficiently.
The module uses a plugin architecture, meaning each step in the pipeline can be swapped out. Councils can use different extractors, AI models, or output to different Drupal content types, making the solution adaptable to a wide range of content and operational requirements.
Built the right way
The team delivered this project with an agile, user-centred approach, continuously refining requirements to ensure the tool meets real user needs rather than simply ticking a technical specification.
"This project is a great example of AI working alongside and empowering content creators, and Drupal as a platform supports this really well." - Farez Rahman, Drupal Developer
"I'm excited about the impact this product will have, not just for our users, but also in transforming how we design, build, and create content internally. We're shaping a future where services start with HTML-first thinking." - Evelyn Francourt, User Experience Lead
Why this matters beyond Southwark
Local government teams across the country face the same challenge. This solution, built on open source Drupal and the LocalGov Drupal ecosystem, is designed to be shared, not kept in one place.
If your organisation publishes PDFs, manages large volumes of content, or is exploring where AI can deliver practical value without unnecessary complexity, this webinar is for you. Tuesday 16th June | 16:00 BST | Online.
Drupal AI Initiative: Webinar: How Southwark Council is Using AI to Transform PDF Publishing in Drupal
Join us to hear directly from the team behind an award-winning AI solution built for local government. What does genuinely useful AI in public services look like? Not a concept, not a pilot, but a working solution that saves hours of manual work, improves accessibility, and puts better content in front of citizens faster.
We are delighted to invite you to a webinar where you can hear the story first-hand.
About the webinar
Date: Tuesday 16th June | 16:00 BST Guest: Angie Forson, Web and Digital Programme Lead, Southwark Council Host: James Hall, Product Lead, Websites at Everyone TV
This is a rare opportunity to hear directly from a senior stakeholder about how Drupal and AI are delivering real, measurable value in an area that truly matters: public services for the citizens of Southwark.
Angie will walk through the journey, the challenges, the outcomes, and what it means for the wider local government sector.
Manual PDF conversion has long been one of the most time-consuming tasks facing council web teams. Converting a single document can take hours. Multiply that across thousands of PDFs and the burden becomes significant, both in staff time and in the delay it creates before citizens can access accurate, accessible information.
The Southwark team, working with their partners at Chicken, built an AI-powered importer for the LocalGov Drupal Publication Module that reduces that process to minutes, often under one minute.
How it works
Each PDF passes through a three-step pipeline:
Extract - a PDF parser pulls the raw content from the document
Transform - AI converts it to properly structured, accessible HTML with logical pagination
Save - clean HTML pages are ready to review and publish directly in Drupal
The result is an HTML representation of the PDF content, saved into a Drupal Publication and ready for review before going live. Every import is logged, so errors can be identified and resolved efficiently.
The module uses a plugin architecture, meaning each step in the pipeline can be swapped out. Councils can use different extractors, AI models, or output to different Drupal content types, making the solution adaptable to a wide range of content and operational requirements.
Built the right way
The team delivered this project with an agile, user-centred approach, continuously refining requirements to ensure the tool meets real user needs rather than simply ticking a technical specification.
"This project is a great example of AI working alongside and empowering content creators, and Drupal as a platform supports this really well." - Farez Rahman, Drupal Developer
"I'm excited about the impact this product will have, not just for our users, but also in transforming how we design, build, and create content internally. We're shaping a future where services start with HTML-first thinking." - Evelyn Francourt, User Experience Lead
Why this matters beyond Southwark
Local government teams across the country face the same challenge. This solution, built on open source Drupal and the LocalGov Drupal ecosystem, is designed to be shared, not kept in one place.
If your organisation publishes PDFs, manages large volumes of content, or is exploring where AI can deliver practical value without unnecessary complexity, this webinar is for you. Tuesday 16th June | 16:00 BST | Online.
Specbee: Zero-effort Schema Markup: AI Schema Markup generator for Drupal
Schema.org markup can make or break your search visibility, but writing it by hand across hundreds of nodes is unrealistic. What if your CMS just did it for you? Find out in this blog.
read more
rss
Pivale: The SaaS trap: Why the cheapest option often isn't
The SaaS tools you rely on are costing more than you think. We make the case for building software your business actually owns, on a platform built to last.
read more
youtube
Drupal AI Learners Club: Skills in Action
This session is all about Skills... Agent Skills, that is! We start with an introduction to Skills from Jim Birch, followed by a demo of skills in action by Eduardo Telaya. This was definitely a hot topic: expect more skills-related sessions in the future!
read more
rss
DDEV Blog: Contributor Training: Creating and Maintaining DDEV Add-ons
Stas Zhuk and I covered the full add-on lifecycle in this Contributor Training session: bootstrapping from the ddev-addon-template, writing Bats tests, testing locally and against branches or open PRs, and publishing to the registry. The session also covers use cases beyond service providers — custom commands, DDEV hooks, and distributing team workflows across projects.
Most people first encounter add-ons as service providers — Redis, Elasticsearch, Solr, Mailpit — but Bill Seremetis (bserem) put it well in his DrupalDevDays Athens 2026 talk: "an add-on is a set of files: hooks + commands + scripts + config — it's a distribution mechanism." His agency uses a single custom add-on across 100+ Drupal projects to encode institutional knowledge, enforce quality gates, and deliver the team's workflows to the terminal. One update to the add-on propagates improvements to every project. That framing opens up a lot: custom commands that automate your team's processes, DDEV hooks that fire at key checkpoints (sanitize the database on import, install Git hooks on project start), and boilerplate configs or scripts distributed automatically to wherever they're needed.
The heart of every add-on is an install.yaml, which defines what files get placed at the project-level or globally, plus pre_install_actions and post_install_actions that can run shell or PHP scripts during install.
Getting started with a new add-on is straightforward: use the ddev-addon-template, which wires up GitHub Actions CI and a tests/test.bats Bats test suite from the start. You can test locally before publishing with ddev add-on get /path/to/your/addon, against a branch with --version branch-name, or against an open PR with --pr 54. When ready to publish to the world (if you want to), add the ddev-get topic to your GitHub repository and it will appear in addons.ddev.com within about 24 hours.
Your suggestions to improve this blog are welcome. You can do a PR to this blog adding your techniques. Info and a training session on how to do a PR to anything in ddev.com is at DDEV Website For Contributors.
Follow the DDEV Newsletter for information about upcoming user and contributor training sessions.
The Drop Times: Drupal Accessibility Beyond Automation
Accessibility requirements for websites are increasingly being enforced across public and private sectors, affecting Drupal-based systems used by governments, universities, and businesses. Compliance with WCAG standards is no longer treated as a one-time milestone but as an ongoing responsibility that spans both system configuration and everyday content publishing.
In a recent LinkedIn post, John Harris highlights how reliance on automated scans often leaves significant gaps in accessibility compliance, particularly in areas that require manual validation and editorial oversight.
At the same time, accessibility in Drupal environments continues to depend on both technical systems and publishing practices, with emerging risks from AI-generated content further complicating matters. These factors point to accessibility as a continuous, shared responsibility rather than a fixed checkpoint.
Here is a selection of Drupal stories published over the past week.
Additional developments from across the Drupal ecosystem were published during the week. Readers can follow The Drop Times on LinkedIn, Twitter, Bluesky, and Facebook for ongoing updates. The publication is also active on Drupal Slack in the #thedroptimes channel.
Talking Drupal: Talking Drupal #550 - The Future of Site Builders
In episode 550 of Talking Drupal, Rod Martin joins us to discuss how Drupal site builders are defined, how their role has changed across Drupal versions, and what the future may look like with Drupal CMS, Canvas, and Drupal AI. The show's module of the week is Password Policy, presented by Avi Schwab, covering customizable password constraints and password expiration/reset features, along with supporting modules Password Policy Extras and Password Policy Pwned, which checks passwords against the Have I Been Pwned database. The conversation also explores the challenges site builders face around layout, theming, and configuration management, and the need for better templates, workflows, and guardrails as AI-assisted site building evolves.
Password Policy - A password policy can be defined with a set of constraints which must be met before a user password change will be accepted. Each constraint has a parameter allowing for the minimum number of valid conditions which must be met before the constraint is satisfied.
#! code: Drupal 11: Cascading Select Forms With HTMX
Drupal 11: Cascading Select Forms With HTMX
This is part four of a series of articles looking at HTMX in Drupal. In the last two articles we looked at using HTMX with controllers in different ways. This time I'll be venturing into the world of HTMX and forms.
Years ago on this site I wrote an article about Cascading ajax select forms in Drupal, which I often refer back to when I'm trying to figure out something to do with select forms and ajax. In that article I take a year, month, and day select field and tie them together so that they influence each other during the selection process.
I've been writing Drupal sites for quite a number of years and I still need to take a deep breath before attempting to embark on implementing ajax in Drupal forms. I end up with form fields that have wrapper elements or custom attributes in an attempt to get things working. It always seems to be a painful experience.
When I was learning about HTMX and Drupal I sat down to re-implement this cascading select form and had something working in about half an hour. Most of that time was spend adding the form elements to the build form method. A stark difference between the old and the new ways of adding ajax to forms in Drupal.
In this article we will look at creating a form that contains multiple select elements and then use HTMX (and a little bit of the form states API) to tie them together so that selecting one element updates the others.
All of the code contained in this article can be found in the Drupal HTMX examples project on GitHub, but here we will go through what the code does and what actions it performs to generate content.
Just like the other articles on HTMX, I'm going to start with the basics and define the route.
The Drop Times: DevBranch BootCamp Expands as Entry Pathway for Drupal Talent
DevBranch has developed its in-house Drupal BootCamp into a recurring training pathway aimed at preparing new developers for project work. The programme has run eight cohorts since 2021, training more than 30 participants, with about half receiving job offers. Details shared by Functional Manager Nataliia Khomiuk outline how changes in duration, cohort size, and skill focus reflect practical hiring and onboarding needs within distributed Drupal teams.
read more
rss
GitLab issue migration: a contributor's perspective
This is the fourth post in our GitLab issue migration series. The earlier posts focused on what is changing and how maintainers should set up their projects. This one is for the rest of us — the people who file bugs, review code, push fixes, and triage queues without wearing a maintainer hat. If your favorite contrib project has just moved its issues to git.drupalcode.org, here's what you need to know.
What's changed at a glance
When a project's issues are migrated, they move from www.drupal.org/project/{name}/issues to git.drupalcode.org/project/{name}/-/work_items. Old URLs redirect to the new ones, and issue numbers (NIDs) are preserved as GitLab IIDs — so an #3409678: Opt-in GitLab issues you find in a commit message will still resolve to the same issue.
In GitLab, "issues" are technically a subtype of "work items," but the term issue still applies, and you'll see it throughout the UI. If you've worked on any GitHub or GitLab project before, the experience will feel familiar.
What still works the way you're used to
A lot has not changed:
You can still create issues without any special role.
The contribution credit system is unchanged. Every comment you make on a GitLab issue still syncs to its contribution record automatically. The credit UI itself still lives on drupal.org.
Shared issue forks are still the way to collaborate (on code). Drupal still doesn't use personal forks; collaboration on a single fork remains the model. The fork management UI also still lives on drupal.org.
The familiar workflow conventions can still apply — Needs work, Needs review, RTBC, priority levels, and so on. They were migrated as scoped labels (more on this below).
GitLab CI still runs your tests the same way it has for the past few years.
Your Drupal.org login still works. Single sign-on means no extra account to manage.
Cross-references and parent/child relationships still exist, just with slightly different syntax (more on that below).
Some things actually got better
It's worth naming a few real wins for contributors:
A modern issue editor with proper markdown, real code blocks, syntax highlighting, image paste, and a mobile-friendly UI.
Issues and merge requests now live alongside the code, pipelines, and CI logs on git.drupalcode.org — far less context-switching during code review.
Much better filtering, search, and saved queries on issue lists.
Issue boards (Kanban-style) are available for projects that want them.
Who can edit what
A few permission details are worth knowing up front, because they're tighter than what you may be used to on the old issue queue:
Anyone can comment on an issue.
Only the original author or project maintainers can edit the issue description. This is a real change — on drupal.org, any logged-in user could edit an issue summary. If you'd like a description updated and you're not the author, leave a comment with the suggested wording so the author or a maintainer can apply it.
Labels and other metadata (priority, version, category, component, tags) can only be edited by users with a Planner role or higher on the GitLab project.
That last point is real friction for contributors who triage and label issues, and we're addressing it directly. #3559846: Allow changing GitLab issues labels for all contributors is building a label-management UI that will live on drupal.org, alongside the existing contribution credit and issue fork management screens. Once it ships, any contributor will be able to manage labels on any issue without needing a project role on GitLab. This is also an upstream issue, but it doesn't seem to be worked on.
Until then, if metadata needs updating, leave a comment noting what should change. Maintainers and other contributors with the role can apply it.
Old workflow conventions can still apply
Good news for anyone with muscle memory for Drupal's NW / NR / RTBC dance: the conventions weren't dropped in the migration. They were preserved as scoped labels on GitLab issues — state::rtbc, the equivalent state labels for needs-work and needs-review, priority labels, and so on. Each project's setup may vary, but the familiar conventions carried over, and contributors can keep using them.
Convention
Now
Needs work
state::needsWork label (alternative: MR set to Draft)
Needs review
state::needsReview label (alternative: MR set to Ready)
Applying these labels yourself currently requires the Planner+ role on the project, until #3559846 ships the contributor label UI. In the meantime, a comment indicating the status you'd assign is the right move.
Merge request states are a useful parallel signal: an MR's Draft / Ready toggle and approval status reflect the actual code change being reviewed, which often communicates more clearly than a label on the parent issue. Some projects lean heavily on MR state, some on labels, some use both — there's no single right answer.
Day-to-day: how to do common things
Create an issue
Navigate to the project, click Work items in the left sidebar, then New item. The form is just a title and description; labels and metadata are added afterwards by users with the appropriate role. If a project has set up issue templates (markdown files in the repo), you'll see them in a dropdown.
The first auto-generated comment
The first comment on every new issue is posted by DrupalBot. It's the bridge to the things that still live on drupal.org:
A link to the contribution record (where credit is tracked).
A link to the fork management page, where you can create or request access to a shared fork, view existing MRs, and open a new one.
Once #3559846 ships, a link to the contributor label management UI.
Forks and merge requests
The fork management screen on drupal.org works the same way for GitLab issues as it has for Drupal.org issues. From there, you can create a shared issue fork, request access if one already exists, push a branch, and open an MR. Branching and merging happen in GitLab's native UI, where they're already optimized.
Linking issues across systems
During the transition, contributors will be working with both Drupal.org issues and GitLab issues, sometimes in the same comment. The syntax differs by direction:
Drupal.org → Drupal.org issue Brackets around the issue number (without spaces): [ #123456 ] (unchanged)
GitLab → GitLab issue (same project): #123456 (no brackets)
Cross-platform (either direction): paste the full URL
For "related issues" entries on Drupal.org, always use the full URL when pointing at a GitLab issue.
Things you might notice on migrated issues
A few oddities are worth flagging if you're working through historical issues:
DrupalBot is listed as the author on every migrated issue. (Issues created after migration correctly show their actual creator.) The GitLab API forced a tradeoff between preserving the original author and preserving the issue ID. We chose to preserve the ID so that #123456 still maps to the same issue. The original author's name is preserved in the first line of the issue description.
Old drupal.org issue URLs redirect to their GitLab equivalents, so existing links in commit messages, blog posts, and external references continue to work.
Reporting bugs and getting help
Found a bug in the migration itself or in the integration between Drupal.org and GitLab? Please file it in the Drupal.org customizations issue queue.
Have a question, or want to share feedback on the new workflow? Join the #gitlab-issues-feedback channel on the Drupal community Slack.
We're actively iterating on this transition based on what we hear from contributors and maintainers in opted-in projects. The more feedback we get now — while we're still in the opt-in phase — the better the experience will be when the rest of contrib gets batch-migrated.
Reference: GitLab documentation
For more detail on any of the GitLab features mentioned in this post, the official GitLab documentation is the canonical source.
Drupal.org blog: GitLab issue migration: a contributor's perspective
This is the fourth post in our GitLab issue migration series. The earlier posts focused on what is changing and how maintainers should set up their projects. This one is for the rest of us — the people who file bugs, review code, push fixes, and triage queues without wearing a maintainer hat. If your favorite contrib project has just moved its issues to git.drupalcode.org, here's what you need to know.
What's changed at a glance
When a project's issues are migrated, they move from www.drupal.org/project/{name}/issues to git.drupalcode.org/project/{name}/-/work_items. Old URLs redirect to the new ones, and issue numbers (NIDs) are preserved as GitLab IIDs — so an #3409678: Opt-in GitLab issues you find in a commit message will still resolve to the same issue.
In GitLab, "issues" are technically a subtype of "work items," but the term issue still applies, and you'll see it throughout the UI. If you've worked on any GitHub or GitLab project before, the experience will feel familiar.
What still works the way you're used to
A lot has not changed:
You can still create issues without any special role.
The contribution credit system is unchanged. Every comment you make on a GitLab issue still syncs to its contribution record automatically. The credit UI itself still lives on drupal.org.
Shared issue forks are still the way to collaborate (on code). Drupal still doesn't use personal forks; collaboration on a single fork remains the model. The fork management UI also still lives on drupal.org.
The familiar workflow conventions can still apply — Needs work, Needs review, RTBC, priority levels, and so on. They were migrated as scoped labels (more on this below).
GitLab CI still runs your tests the same way it has for the past few years.
Your Drupal.org login still works. Single sign-on means no extra account to manage.
Cross-references and parent/child relationships still exist, just with slightly different syntax (more on that below).
Some things actually got better
It's worth naming a few real wins for contributors:
A modern issue editor with proper markdown, real code blocks, syntax highlighting, image paste, and a mobile-friendly UI.
Issues and merge requests now live alongside the code, pipelines, and CI logs on git.drupalcode.org — far less context-switching during code review.
Much better filtering, search, and saved queries on issue lists.
Issue boards (Kanban-style) are available for projects that want them.
Who can edit what
A few permission details are worth knowing up front, because they're tighter than what you may be used to on the old issue queue:
Anyone can comment on an issue.
Only the original author or project maintainers can edit the issue description. This is a real change — on drupal.org, any logged-in user could edit an issue summary. If you'd like a description updated and you're not the author, leave a comment with the suggested wording so the author or a maintainer can apply it.
Labels and other metadata (priority, version, category, component, tags) can only be edited by users with a Planner role or higher on the GitLab project.
That last point is real friction for contributors who triage and label issues, and we're addressing it directly. #3559846: Allow changing GitLab issues labels for all contributors is building a label-management UI that will live on drupal.org, alongside the existing contribution credit and issue fork management screens. Once it ships, any contributor will be able to manage labels on any issue without needing a project role on GitLab. This is also an upstream issue, but it doesn't seem to be worked on.
Until then, if metadata needs updating, leave a comment noting what should change. Maintainers and other contributors with the role can apply it.
Old workflow conventions can still apply
Good news for anyone with muscle memory for Drupal's NW / NR / RTBC dance: the conventions weren't dropped in the migration. They were preserved as scoped labels on GitLab issues — state::rtbc, the equivalent state labels for needs-work and needs-review, priority labels, and so on. Each project's setup may vary, but the familiar conventions carried over, and contributors can keep using them.
Convention
Now
Needs work
state::needsWork label (alternative: MR set to Draft)
Needs review
state::needsReview label (alternative: MR set to Ready)
Applying these labels yourself currently requires the Planner+ role on the project, until #3559846 ships the contributor label UI. In the meantime, a comment indicating the status you'd assign is the right move.
Merge request states are a useful parallel signal: an MR's Draft / Ready toggle and approval status reflect the actual code change being reviewed, which often communicates more clearly than a label on the parent issue. Some projects lean heavily on MR state, some on labels, some use both — there's no single right answer.
Day-to-day: how to do common things
Create an issue
Navigate to the project, click Issues in the left sidebar, then New issue. The form is just a title and description; labels and metadata are added afterwards by users with the appropriate role. If a project has set up issue templates (markdown files in the repo), you'll see them in a dropdown.
The first auto-generated comment
The first comment on every new issue is posted by DrupalBot. It's the bridge to the things that still live on drupal.org:
A link to the contribution record (where credit is tracked).
A link to the fork management page, where you can create or request access to a shared fork, view existing MRs, and open a new one.
Once #3559846 ships, a link to the contributor label management UI.
Forks and merge requests
The fork management screen on drupal.org works the same way for GitLab issues as it has for Drupal.org issues. From there, you can create a shared issue fork, request access if one already exists, push a branch, and open an MR. Branching and merging happen in GitLab's native UI, where they're already optimized.
Linking issues across systems
During the transition, contributors will be working with both Drupal.org issues and GitLab issues, sometimes in the same comment. The syntax differs by direction:
Drupal.org → Drupal.org issue Brackets around the issue number (without spaces): [ #123456 ] (unchanged)
GitLab → GitLab issue (same project): #123456 (no brackets)
Cross-platform (either direction): paste the full URL
For "related issues" entries on Drupal.org, always use the full URL when pointing at a GitLab issue.
Things you might notice on migrated issues
A few oddities are worth flagging if you're working through historical issues:
DrupalBot is listed as the author on every migrated issue. (Issues created after migration correctly show their actual creator.) The GitLab API forced a tradeoff between preserving the original author and preserving the issue ID. We chose to preserve the ID so that #123456 still maps to the same issue. The original author's name is preserved in the first line of the issue description.
Old drupal.org issue URLs redirect to their GitLab equivalents, so existing links in commit messages, blog posts, and external references continue to work.
Reporting bugs and getting help
Found a bug in the migration itself or in the integration between Drupal.org and GitLab? Please file it in the Drupal.org customizations issue queue.
Have a question, or want to share feedback on the new workflow? Join the #gitlab-issues-feedback channel on the Drupal community Slack.
We're actively iterating on this transition based on what we hear from contributors and maintainers in opted-in projects. The more feedback we get now — while we're still in the opt-in phase — the better the experience will be when the rest of contrib gets batch-migrated.
Reference: GitLab documentation
For more detail on any of the GitLab features mentioned in this post, the official GitLab documentation is the canonical source.
From Leuven to Athens: Celebrating One Year Since the Drupal AI Initiative Took Shape
One year ago, at Drupal Developer Days in Leuven, something special happened.
The Drupal AI Initiative was not officially launched yet. That would happen later, in June. But Leuven was where the spark happened. It was where the first real momentum came together. Where conversations turned into commitment. Where a shared belief became a shared plan.
Five companies stepped up to kickstart the initiative: Dropsolid, Acquia, 1xINTERNET, FreelyGive, and Salsa Digital. Together, they helped turn an ambitious idea into the beginning of a movement.
Now, one year later, as we gather again at Drupal Developer Days in Athens, we celebrate one year since that moment of conception.
Leuven was where the initiative was kickstarted. June was when it officially went live. Athens is where we celebrate how far it has come.
A year of momentum, collaboration, and delivery
The Drupal AI Initiative was created with a bold ambition: to help Drupal become the leading open source CMS for AI-powered digital experiences.
But from the beginning, this was never just about adding AI features.
It was about building AI into Drupal in a way that reflects the values of the Drupal community: open, flexible, responsible, transparent, and collaborative. It was about giving organizations the tools to innovate with AI while keeping control over governance, content, security, editorial workflows, and long-term digital strategy.
Over the past year, the initiative has grown from a spark in Leuven into one of the most ambitious collaborative efforts in Drupal’s history.
What has been delivered?
Since the official launch of the Drupal AI Initiative, the team has made major progress. The amount of installs is growing significantly, 13980 at the time of writing. Adoption is accelerating. According to shared data we’re growing at about 260 sites per week and accelerating.
This is only the sites that share numbers, the real share is much higher.
Growing numbers of Drupal AI Partners
Between Drupal Con Vienna and Chicago, the initiative added 12 new partners, a total of 34, representing a 50% increase in participation. We are on track to match this growth in support between now and DrupalCon Rotterdam, a key goal for this year.
Delivering capabilities at scale
The initiative also successfully established and executed the delivery management RFP process, putting important operational frameworks in place, including:
Partner expectations documentation
Onboarding processes
Development sprint processes
Contribution tracking
Team planning sheets
Weekly status reporting
These may sound like operational details, but they are what make collaboration at scale possible. They help turn enthusiasm into structure, and structure into delivery.
The Drupal AI Initiative has become the largest multi-company collaboration in Drupal community history.
- Dries Buytaert
The initiative is now actively funding critical roles across multiple organizations, including product management, innovation management, technical leadership, and program management. This marks a major milestone: the Drupal AI Initiative has become the largest multi-company collaboration in Drupal community history.
The 2026 roadmap was finalised earlier this year, informed by customer demand and industry insight. Delivery is actively underway.
At the same time, marketing efforts have been elevated to position Drupal as the leading AI-powered open source CMS globally, supported by ongoing storytelling and visibility through the Drupal AI Initiative blog.
Significant rise contribution
Focused effort on strategically important features, combined with a growing number of partners committing resources and strong community participation, has driven a significant increase in momentum and impact.
The tag clouds below visually represent the many Drupal community members who in the past 12 months have contributed to the AI Initiative (sized according to number of fixed issues worked on). Includes code and non code contributions.
The following organizations have also contributed to the Drupal AI Initiative in the past year.
Marketing Drupal AI
From small beginnings with Paul Johnson and Frederik Wouters taking on marketing, we now have a cross disciplinary high performing team with 10 leads across areas of specialization.
Focussing on introducing Drupal to new audiences the emphasis has been on webinars, participating in external events and organising major new customer facing events of our own. These include Drupal AI Summit Paris and New York City (14th May 2026), The AI Summit London (10-11 June 2026) and the latest Enterprise AI Summit Rotterdam (28 September 2026).
Our work has included facilitating Southwark Council, London, winning Digital Leaders AI Impact Award 2026, producing video case studies and highlighting major new AI features announced during the DriesNote with social video content. All these activities have substantially raised Drupal’s profile to a wider audience.
Building toward Rotterdam
The next major milestone is already taking shape.
In Rotterdam, the initiative will launch an exclusive Drupal Enterprise AI event, available only to Drupal AI Initiative partners. The event will bring together European decision-makers aboard the SS Rotterdam for peer networking, customer case studies, and strategic conversations about building AI-powered content management solutions with Drupal.
Participation in this event is limited to partners who join the Drupal AI Initiative by June 30.
That creates a powerful moment for companies that want to be part of Drupal’s AI future. The initiative is scaling, the roadmap is active, the team is growing, and the opportunity to help shape what comes next is open now.
A strong foundation for what comes next
The Drupal AI Initiative is in a strong position.
With $380,000 in cash and $1.5 million in in-kind contributions, more than 50 contributors from partners, the initiative has the resources and commitment needed to continue scaling. The plan is to onboard an additional 12 partners by Rotterdam, further strengthening the team and accelerating delivery.
The message is clear: You counted on Drupal AI, and we delivered. Now we want to create more efficiency and scale.
That is what this next phase is about. More delivery. More visibility. More impact.
Thank you to the people who made this possible
This milestone belongs to many people.
It belongs to everyone who joined those early conversations in Leuven.
It belongs to Frederik Wouters, who brought the right people together at the right moment and helped create the spark that started it all.
It belongs to the five companies that kickstarted the initiative: Dropsolid, Acquia, 1xINTERNET, FreelyGive, and Salsa Digital.
It belongs to every partner, contributor, sponsor, strategist, developer, product thinker, marketer, and community member who has helped move this initiative forward.
And it belongs to the wider Drupal community, whose openness and willingness to collaborate make initiatives like this possible.
You can still join
The Drupal AI Initiative is growing, and companies can still become part of it.
If your organization believes in the future of Drupal, if you want to help shape responsible AI in open source, or if you want to be part of the group building the next generation of AI-powered content management, now is the time to join.
Become part of the 34 makers already helping to build Drupal’s AI future.
To join the Drupal AI Initiative as an organization and become a partner, contact Dominique at dominique@dropsolid.com.
From Leuven to Athens, this has been an incredible first year.
And the best part? We are only just getting started!
Over a decade ago, I co-founded 1xINTERNET on the conviction that Drupal was the best platform for ambitious web applications. That bet paid off. But recently, as AI began disrupting our industry, I found myself facing an unfamiliar feeling: uncertainty. For the first time in my career, the path forward wasn't entirely clear.
If you are a decision-maker navigating this shift, you likely feel the same way. We are all trying to figure out how to leverage AI's huge potential without compromising enterprise security, compliance, or content quality.
The good news is that while the broader AI landscape remains turbulent, the direction for content management systems is becoming clear.
- Christoph Breidert
Christoph Breidert facilitating a Drupal AI workshop at DrupalCon Chicago 2026.
Since the founding, over 30 leading companies have joined the initiative. But a defining moment happened recently at DrupalCon Chicago 2026. During his keynote - the "Driesnote" - Drupal founder Dries Buytaert bluntly asked the community regarding the AI shift: Are you in or are you out?
The undeniable energy from the community and the rapidly intensifying momentum proved one thing: Drupal is all in on AI.
But what does "all in" actually mean? We aren't just talking about adding superficial features like chatbots or simple text generators. We have built a powerful agentic infrastructure natively into Drupal. This provides us with a robust foundation, allowing organizations to build complex AI applications and deploy autonomous agents capable of executing multi-step workflows on their behalf.
What an Agentic CMS actually requires
Let’s be clear: Agentic AI delivers incredible velocity, and every organization from SMEs to global enterprises needs that speed. But deploying autonomous agents without control is a liability. You need AI infrastructure that accelerates your workflows while ensuring that this speed doesn't destroy your content quality or violate your compliance rules.
This requires a robust governance foundation to run the infrastructure safely. The Drupal AI Initiative has spent the past months building exactly that. These are the final pieces we have built to complete the production-ready foundation:
AI Guardrails: Configurable rules that intercept both outgoing requests and incoming AI responses. Whether it's preventing the exposure of personal data (PII), ensuring prompt safety, or mitigating legal liability, guardrails keep the AI agents within defined boundaries.
AI Observability: Complete transparency into what your AI agents are doing. Every prompt, token usage metric, and model response is logged, providing a clear audit trail for compliance and cost optimization.
Context Control Center: AI models are useless without context. This system acts as a router, intelligently feeding the right organizational data (and only the right data) to the LLM based on the user's specific task.
Introducing AI Content Reviews
Let’s separate the hype from reality: The core foundation of Drupal AI is production-ready today. With a secure governance infrastructure now in place, we are shifting from building the engine to delivering the applications. We are shipping out-of-the-box features so organizations can immediately benefit without building complex workflows from scratch.
The first major capability rolling out is AI Content Reviews. This is not a future roadmap concept, it is a real, tangible feature designed to close the quality gap for large websites by acting as a continuous, background quality assurance partner.
It provides scalable, AI-assisted content governance that integrates naturally into how editors already work. The system evaluates content against your organization's specific rules, such as brand voice, legal compliance, SEO, and accessibility. It flags issues, explains them in plain language, and proposes concrete fixes. Crucially, human oversight remains the starting point: an editor simply reviews the flagged issues and can apply the suggested fixes with a single click.
AI Review Management Overview
Upcoming features
AI Content Reviews is just the first application of our agentic infrastructure. Following close behind is AI-powered semantic search with synthesized summaries. This allows visitors to find what they need through meaning rather than keywords, enabling the site to surface direct answers instead of just a list of results.
We are also actively packaging AI assistants embedded natively across editorial workflows, site-building, and end-user interfaces. These capabilities have been thoroughly explored and validated in our innovation workstream and are now being readied for production use.
Want to see the full picture of what we are building? You can explore the complete Drupal AI Roadmap to see exactly where the initiative is heading next.
Overview Drupal AI Roadmap 2026.
Drupal’s architectural advantage
Why build this directly into Drupal instead of relying on external AI services or other CMS platforms? It comes down to a fundamental technological advantage. Many modern CMS platforms, especially closed SaaS products and pure headless systems, force you to rely on disconnected external API wrappers to communicate with AI. This architectural limitation means your developers have to manually rebuild your existing user permissions, workflows, and access rules in a separate middleware layer just to keep the AI secure.
Drupal AI has a distinct head start because of its deep internal architecture:
Co-location with the Content Graph: AI models are only as good as the context they can access. By embedding AI orchestration directly within Drupal, the AI has native, zero-latency access to your entire structured content graph. There is no integration friction.
Native Permissions & Access Control: Because Drupal's entity system and field-level access controls are so deeply integrated, the AI operates entirely within your existing permissions. It cannot expose, analyze, or modify content the user shouldn't see.
Provider-Agnostic Abstraction: Similar to what makes frameworks like LangChain powerful, Drupal AI abstracts the LLM providers (OpenAI, Anthropic, local models, etc.). But unlike external middle-tiers, Drupal enforces strict schema typing before data ever hits your database, ensuring structural integrity.
An Unmatched Ecosystem for AI Agents: Autonomous agents need tools to interact with the outside world. Because Drupal already possesses a massive, deeply established ecosystem of enterprise integrations, your AI agents can directly interact with your CRMs, ERPs, and marketing platforms. You don’t have to build custom API connectors for your AI to take action across your broader tech stack.
Moving forward
The uncertainty of the AI era remains, no one knows exactly what the landscape will look like in three years. I'm being honest about that. But what I do know is that the architecture we are building is solid, the foundation is ready, the community driving it is fully committed and has the resources.
If you are evaluating whether Drupal is the right foundation for AI-powered content management, you don't have to figure that out alone. The Drupal AI Partners network brings together specialized agencies with deep experience deploying exactly these capabilities. If you are ready to move from evaluation to implementation, that is the right place to start.
We are all building in conditions none of us have navigated before.
The difference is what we are building on.
Weekend Hackery: Vibe Coding with Claude from Scratch
In this informal "pair programming" session, webchick and Amber Himes Matz use Claude Code to "vibe code" a plan on automated tool to cross-post announcements about new Drupal AI Learners Club events. We start from a "bare bones" Git repo and use a plan generated from Claude.ai to demonstrate building step by step.
Exploration, learning, and hilarity ensues. :D
00:00: Intros / About the Club
01:48: Challenge we're tackling
03:21: Planning with Claude.ai
04:19: Side-Quest: Drupal.org Permissions
05:33: Back to the plan
06:21: Side-Quest: Additional channel — Luma
07:16: Let's YOLO!
08:45: Git clone an existing project
09:08: Side-Quest: Getting the plan from Claude
10:34: Side-Quest: .claude/ directory
12:30: Starting Claude Code
12:50: Aside about security
15:05: Claude Code first steps
15:30: Side-Quest: Costs between models
17:18: Claude Code first steps FOR REAL :D
18:24: Side-Quest: The many ways to run Claude
20:53: Checking in on Claude Code
...(more to come! :))...
read more
rss
Differentiating Marketplace Site Templates and Community Site Templates
Site templates are available through two distinct pathways, each serving different needs within the community.
The official Drupal.org Marketplace provides a curated collection of site templates that meet certain quality standards, and are built on top of Drupal CMS as a foundation.
Community templates offer an alternative pathway for innovation and experimentation without the constraints of the curation process, by publishing the template as a general project on Drupal.org.
Official Marketplace Site Templates
The Drupal.org Marketplace are built on top of Drupal CMS, and curated to provide new users with confidence that they're starting with a consistent, solid and professionally built foundation that follows established best practices.
Key characteristics
Templates undergo a review processes
Must follow Drupal CMS best practices for security, accessibility (WCAG 2.2 AA), performance, and code quality
In the beginning, focus is solely on growing Drupal CMS adoption; site templates accelerate adoption of Drupal CMS by providing context relevant demo content and Drupal Canvas-compatible theme
Clear documentation, maintenance commitments, and user support expectations
Currently open to Drupal Certified Partners (for organizations) and Ripplemakers (for individuals or very small companies). Apply to become a creator here.
Benefits
Consistency for users who need reliable, production-ready starting points
Quality assurance through professional review processes
Support and maintenance commitments for long-term sustainability
Revenue opportunities for professional template creators
Sustainability for the Drupal Association through revenue sharing
Community Site Templates
Anyone interested in contributing a template can do so now, by publishing it as a general project on Drupal.org. All free site templates, including marketplace templates, are general projects for packaging and distribution purposes. Community site templates will be considered for inclusion in the Drupal.org Marketplace based on their compatibility with the outlined criteria.
Key characteristics
Can be published without formal review or approval
Not bound by the same standards as Marketplace templates
Can be built using Drupal CMS or Drupal Core
Available to all community members
Can take risks and explore directions that might not fit Marketplace criteria
Benefits:
Innovation by removing barriers to experimentation
Diversity of approaches and implementations
Learning opportunities for the community to explore what's possible
Stepping stones that might eventually evolve into Marketplace templates
Lower barriers to entry for community contribution
DrupalCon Chicago 2026 brought together leading experts in digital experience development, open source innovation, and enterprise technology.
The event provided a unique opportunity to connect with decision-makers, technical leaders, and innovators shaping the future of digital experiences. More than 1,300 tech leaders, CEOs, developers, marketing executives, agencies, and enterprise decision-makers gathered to help define the future of the Open Web.
Image: Group photo in Chicago (Photo by Curt Rochon, CC BY-NC 4.0)
A Diverse and Multilingual Global Community
Participants from 26 separate countries brought with them an estimated 15+ languages, reflecting the rich linguistic and cultural diversity of the Drupal ecosystem. The United States (82.4%), Canada (6%), India (2%), Germany (1.2%) and Costa Rica (1.1%) were topping the list in terms of attendee numbers, with Brazil (1%), Colombia (0.8%) and the United Kingdom (0.8%) close behind.
This global span not only highlights Drupal’s widespread adoption, but also underscores the strength of a community shaped by varied perspectives, experiences, and ideas from around the world. Next year we’d love to add more blue!
Event Attendance
A total of 1,316 participants attended in Chicago, an increase from 1,288 for Atlanta 2025. Of these we saw 394 first-time attendees, marking a 10.67% increase from those new to the event in 2025.
539 of 1,316 also chose to extend their learning at the Summits & Trainings, with the AI Summit seeing the largest turnout in its first year, with 104 attendees joining to learn about the latest insights connected to Drupal AI.
Welcoming the Next Generation: Drupal in a Day
Outside of the main conference, and following the successful Drupal in a Day organized ahead of DrupalCon Vienna by Hilmar Kári Hallbjörnsson, DrupalCon Chicago saw the North America inaugural program take place alongside the contribution day.
The training session, organized and staffed by ten volunteers, welcomed 55 learners of high school and college age to interact with Drupal CMS for the first time, helping to expand the reach of the community to new users of all ages. We thank the mentors and supporters who made this event a welcoming place for students, and particularly thank all the individual donors who made this happen, as well as Acquia for sponsoring, and Martin Anderson-Clutz and Jordan Thompson for instructing.
Image: Drupal in a day in Chicago (Photo by Paul Johnson, CC BY-NC 4.0)
Grassroots to Global
Building on the momentum of 2025, the local community ticket-sharing initiative (1 complimentary ticket for every 5th sold through participating organizations) resulted in an increase of 77.5% of ticket purchases which were affiliated with a local group at registration. This initiative continued to grow in both reach and impact, what began as a strong show of grassroots participation has evolved into a more connected and collaborative global network of local camps and meetups celebrating together at DrupalCon.
Participation has expanded beyond the initial groups, with 61 communities engaging through shared resources, cross-promotion, and increased visibility at the 2026 conference. This growth reflects not just higher numbers, but a deeper alignment across the community, where local leaders feel empowered, recognized, and increasingly integrated into the broader Drupal ecosystem.
A Community Spanning All Skill Levels
DrupalCon Chicago 2026 showcased a well-balanced and highly skilled community, with attendees representing every stage of the Drupal journey. Experienced professionals made up the majority, including 348 advanced practitioners (32%) and 301 self-identified Drupal experts (27.7%), creating a strong foundation for in-depth technical exchange and innovation.
Intermediate attendees accounted for 297 participants (27.3%), playing a key role in connecting emerging talent with seasoned leaders. At the same time, the event remained welcoming to newcomers, with 117 beginners (10.8%) and 25 individuals completely new to Drupal (2.3%) joining the community.
Special Luncheons
The Drupal Association formerly required sponsors, who provided programming support for community interest luncheons. These were folded into general programming this year, and we’d like to acknowledge that not all programs had an assigned, designated host. In the next year, our focus is on strengthening local, regional, topical, and community interest groups, so please reach out to us on how to get connected.
Breakfast & Luncheons
Registered
Black in Drupal Luncheon
68
Ripple Makers Breakfast
200
Women in Drupal Luncheon
200
Total
468
See You in Orlando
DrupalCon Orlando will see vision meet execution. Whether you're architecting enterprise platforms, launching your next big project, or scaling what you've already built in Drupal, this is the event that meets you where you are and pushes you further.
Demo: Using AI to solve a Drupal.org issue (Scott Falconer)
Scott demos how he solves a Drupal.org issue using OpenAI Codex, including summarizing the issue, generating a merge request, and asking it questions to verify its response.
This clip is from the Drupal AI Learner's Club "From Autocomplete to Autopilot" meeting: https://www.youtube.com/watch?v=lNnbJQ6l2B4
read more
youtube
Drupal AI Learners Club: From Autocomplete to Autopilot
This session led by Scott Falconer of the Drupal AI Initiative, breaks down the current landscape of AI-assisted coding into clear, practical tiers: inline completions (think autocomplete on steroids), chat-in-your-IDE copilot workflows, and the newer "agentic" coding loops where AI plans and executes multi-step tasks with your oversight. We'll look at what each style is good at, where it falls down, and — critically — how much control you keep at each level.
10:30 Presentation: From Autocomplete to Agent Loops by Scott Falconer
Slides: https://gamma.app/docs/From-Autocomplete-to-Agent-Loops-vb721nb8xh8ojpw
33:47: Demo: Solve a Drupal.org issue with OpenAI Codex
read more
rss
Drupal CMS leadership changes
We're excited to announce updates to the Drupal CMS leadership team, with the addition of Bálint Kléri as our new Frontend Lead.
Bálint Kléri named Drupal CMS Frontend Lead
Bálint Kléri has been named Frontend Lead, a new leadership role created to oversee the frontend architecture for Drupal CMS, Mercury and Mercury-based themes. Bálint is a full-time contributor to Drupal Canvas, leading the development of Code Components for Acquia and a key contributor to Mercury, the Drupal CMS design system.
During development of Mercury, Bálint stepped in to guide the Tailwind CSS implementation and advocate for the use of best practices. We are grateful for his contributions already, and are excited to have him formally join the team. The addition of this frontend role is critical as we refine the Drupal CMS design system, providing users with a modern and adaptable foundation for Drupal sites and site templates.
Pamela Barone promoted to Product Lead
Pamela Barone is now Drupal CMS Product Lead, overseeing product direction, roadmap, prioritization, and delivery. Serving as Product Owner previously, this shift recognizes the product management responsibilities that Pamela has taken on during the evolution of Drupal CMS.
She will continue to work closely with me as I lead the Drupal CMS initiative. I’ll continue to set direction, align teams, and ensure we have the support and momentum to achieve our goals.
We appreciate the ongoing support from Technocrat support in giving Pamela the time to contribute to Drupal CMS.
Tim Plunkett is stepping down as Technical Lead
Tim Plunkett is transitioning out of his role as Drupal CMS Technical Lead to dedicate his full focus to the development of Drupal Canvas. We thank Tim for his leadership and his employer Acquia for all of his contributions.
Adam Hoenich, Lead Architect for Drupal CMS, has been ably overseeing all things technical in the meantime and he will remain in that role. Adam's contribution to Drupal CMS is generously supported by Acquia.
Looking ahead
During DrupalCon Chicago, our leadership team met to discuss the future of Drupal CMS. The first question we asked was 'Do we still think this initiative is important for Drupal's future?' We think it is. We're proud of what we have delivered so far in version 2, with Canvas enablement and site templates as the highlights, but we know there is a lot more to do to meet our objective: To enable marketing teams to launch fully-branded, professional websites in hours, not weeks.
The leadership team is currently working to define the product roadmap for the next 6-12 months, with a strategic focus on launching sites faster with Drupal. We'd love to see new site templates in the marketplace and want to promote easier pathways from installation to going live with a range of hosting options. Other areas we are looking to pursue are: onboarding, better AI tooling, multilingual support for Canvas and site templates, and better support for common third-party integrations.
The inaugural gathering of the Drupal #ai-learners club, where we "show and tell" how we're using Drupal and AI together.
In this edition:
- 11:20 Jürgen Haas shows off the Agent Skills he's using to help LLMs be smarter about Drupal.
- Repo: https://gitlab.lakedrops.com/ai/skills
- 21:11 Mike Herchel demonstrates his use of AI for core development, including visual regression testing for theme-related work.
- Repo: https://github.com/mherchel/ddev-drupal-admin-vrt
- 47:00 Scott Falconer shows some sci-fi AI workflow stuff with Beads and gstack
- Repo #1: https://github.com/gastownhall/beads
- Repo #2: https://github.com/garrytan/gstack
read more
Powered By Combinary
youtube
Demo: Using Agent Skills (Jürgen Haas)
As part of the Drupal AI Learners Club Show Your Setup session, Jürgen Haas shows the Drupal and GitHub Agent Skills he is using for Drupal development.
Repo: https://gitlab.lakedrops.com/ai/skills
read more
youtube
Demo: Using Beads and gstack to supercharge your agentic AI setup (Scott Falconer)
As part of the Drupal AI Learners Club Show Your Setup session, Scott Falconer demonstrates his use of Beads to remind him where he left off, and gstack to guide his engineering in a direction of providing real value to users.
Repos:
- https://github.com/gastownhall/beads
- https://github.com/garrytan/gstack
read more
youtube
Demo: Using AI for Visual Regression Testing (Mike Herchel)
As part of the Drupal Learners Club Show Your Setup session, Mike Herchel demonstrates a visual regression testing tool he's created and how he uses it to contribute to Drupal Core.
Repo: https://github.com/mherchel/ddev-drupal-admin-vrt
read more
youtube
Drupal 25th Anniversary Gala | Chicago 2026
For 25 years, Drupal has been more than software. It's been careers launched, friendships formed, and a global community built around a shared belief in the Open Web.
On March 24, 2026, that community came together at SIX10 in Chicago to celebrate — one night of connection, history, and joy.
The Drupal 25th Anniversary Gala was held during DrupalCon Chicago 2026.
🔗 Learn more about Drupal: https://drupal.org
🔗 Learn more about the Drupal Association: https://www.drupal.org/association
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
youtube
Drupal at 25: What does Drupal mean to you? | Drupal 25th Anniversary Gala
At the Drupal 25th Anniversary Gala in Chicago, we set up a selfie booth and asked the community about their Drupal story — how they got involved, how Drupal has shaped their life, what it means to them, and more.
These are their answers.
Voices from across the global Drupal community — developers, designers, site builders, agency owners, and contributors — sharing what 25 years of Drupal has meant to them.
The Gala was held on March 24, 2026 at SIX10 in Chicago, as part of DrupalCon Chicago 2026. Thanks to Acquia for sponsoring the booth and bringing us these stories.
read more
The second half of the equation is Drupal Canvas AI, the next-generation page builder.
Instead of dragging and dropping components, you can just tell the AI what you want with prompts that describe the page and content you want to produce. Canvas AI, in conjunction with the CCC, will create the page and include the components you need.
As Dries noted, production is becoming a commodity, but judgment and strategy remain human. Drupal AI doesn’t replace your teams, it amplifies their capability to deliver ‘Quality at Scale.’
#MarketingTech #ContentStrategy #DrupalCMS #DXP #AI
read more
youtube
The Context Control Centre (CCC): Institutional ‘Knowledge as a Service’
The most significant hurdle for AI today is a lack of context. Without it, AI simply gives you the "average response." The Context Control Centre changes this by allowing organizations to store their unique "DNA" directly within Drupal.
The CCC organizes institutional knowledge into actionable data:
Brand Guidelines: Specific rules for tone, voice, and formatting.
Personas: Detailed profiles of target audiences (e.g., Controllers vs. IT Ops).
Dynamic Context: A groundbreaking feature where the CCC connects to live data sources like Google Analytics 4 (GA4).
Built into your Drupal CMS, AI tools don't just guess; they work within your specific business reality to ensure their output is always on brand, within guidelines, and relevant to the contextual nuances of the task at hand.
#MarketingTech #ContentStrategy #DrupalCMS #DXP #AI
read more
youtube
Drupal CMS Site Templates - Purpose-Built Templates for Your Industry
Getting started has neveGetting started has never been easier. Drupal CMS introduces purpose-built site templates designed for nonprofits, educators, event organizers, health providers, government agencies, and SaaS companies — all ready to customize out of the box.
Browse free and premium templates at marketplace.drupal.org, or install directly from Drupal CMS. Premium templates like Meridian offer extended visual flexibility and dedicated product support, while every option connects you directly with the makers.
And easy doesn't mean limited. Drupal CMS is built on the same open source foundation powering some of the world's most complex digital experiences — structured content, advanced workflows, airtight security, and access to 10,000+ extensions right from the UI.
Easier than ever to start. Impossible to outgrow.
🔗 Browse templates: https://marketplace.drupal.org been easier.
read more
youtube
#Driesnote | DrupalCon Chicago 2026
Join us live for the #Driesnote at DrupalCon Chicago 2026!
Drupal Founder Dries Buytaert will be presenting on the latest innovations in Drupal, with everything from Drupal CMS and Drupal Canvas improvements, innovation in AI, the Drupal.org site template marketplace and more.
read more
youtube
Helping people tell their cancer stories using AI: Lessons from World Cancer Day
Every year, thousands of people around the world share deeply personal stories about their experiences with cancer through the World Cancer Day campaign.
Behind the scenes, a small communications team reviews these submissions to ensure they are appropriate, relevant, and ready to be shared with the world.
In this Drupal AI Initiative webinar, we explore how the World Cancer Day team introduced artificial intelligence into their Drupal platform to support this process.
Rather than replacing human judgement, AI was used to assist with moderation so that stories could be reviewed faster and contributors could see their experiences published more quickly.
Watch our conversation about:
• The global storytelling effort behind World Cancer Day
• The operational challenges of managing hundreds of story submissions
• How AI can responsibly support human decision-making
• Lessons for organisations exploring AI for the first time
Speakers
• Matthew Saunders — AI Ambassador, amazee.io
• Charles Andrew Revkin — World Cancer Day Programme, UICC
• Diego Costa — COO, 1xInternet
This session was designed for organisational leaders, communications teams, and anyone interested in practical, responsible uses of AI.
#Drupal #OpenSource #AI #Innovation #TechforGood #cancer
read more
youtube
Dries: What's Coming at DrupalCon Chicago 2026 (+ a Special Announcement)
Drupal founder and project lead Dries Buytaert shares a personal preview of what's coming at DrupalCon Chicago 2026 — and why this year's event is something truly special.
Drupal turned 25 in 2026, and the celebration is happening live in Chicago. In this video, Dries gives a sneak peek at his keynote, which will cover the latest Drupal innovations, the impact of AI on the platform, product and ecosystem evolution, and why he's more optimistic about Drupal's future than ever before — including a first look at new innovations he hasn't revealed yet.
And there's more: this year DrupalCon is hosting a special gala in honour of Drupal's 25th birthday. It's a separate ticketed event, and one you won't want to miss.
🎟️ Get your DrupalCon tickets at https://events.drupal.org/chicago2026 and join Dries in Chicago.
Gala tickets available here: https://www.zeffy.com/en-US/ticketing/drupal-25th-anniversary-gala
read more
youtube
KEYNOTE: Neurodiversity: An Underrated Superpower in Business
Vera Herzmann
In tech, some of the most innovative minds think differently – and that difference is often misunderstood. People with ADHD, Autism, or High Sensitivity bring unique strengths like deep focus, pattern recognition, creativity, empathy, and sharp intuition. Yet many workplaces still see neurodivergence as a challenge, rather than recognizing it for the powerful asset it truly is.
This keynote challenges that mindset and reframes neurodiversity as a competitive advantage in business. Drawing from lived experience and years of organizational consulting, you’ll gain a science-backed understanding of neurodiversity, hear real-world stories from the workplace, and explore how recognizing and embracing neurodivergent talent can unlock hidden potential in teams.
Whether you build, design, manage, or lead, this session will shift your perspective, spark meaningful dialogue, and leave you with practical tools to apply in your own professional setting.
read more
youtube
AI Agents in Drupal CMS - Create your own agent
Speaker: https://www.drupal.org/u/vincenzo-gambino
You’ve seen what AI Agents can do in Drupal. What if you could create your own Agents? What if this were so easy that every module across the Drupal ecosystem could have its agents, and they all worked together in harmony? What if, as a result, Drupal became the de facto place to build all AI applications, not just web publishing? If this is you, then this is the talk for you!
This talk will teach you how to create agents from scratch using an existing Drupal module.
We will explore:
- How to code an agent using the framework in the Drupal
ai_agents module.
- Best practices and theory for splitting out functionality into multiple agents.
- How can all those agents be brought together to effectively answer user queries and prove they work with the AI evaluations framework.
read more
youtube
Declarative Shadow DOM and the future of Drupal Theming
Speaker: JohnAlbin
Drupal's old school theming system is server-side rendering. And in the tech world, everything old is new again. In the last two years, modern frontend frameworks have been trying to figure out how to server-side render their client-side JavaScript.
React v19 has figured out how to split its components into client and server parts. As of August 2024, this same "split component" capability is now a part of native Web Components with the introduction of Declarative Shadow DOM. Instead of being written in client-side JavaScript, web components with Declarative Shadow DOM can now be defined using HTML and CSS only.
So if Drupal was server-side rendering before it was cool, can we leverage Declarative Shadow DOM inserted into Single Directory Components to make Drupal cool again?
read more
Powered By Combinary
youtube
Recipes: It's About Time!
Speaker: mandclu
One of the key elements of the Starshot Initiative is the rapidly evolving system for Recipes. Designed to accelerate site-building, recipes will help people new to Drupal to solve for common needs, and for users of all skill levels to quickly build out content architectures using best practices.
This talk will do a deep dive into the Events recipe and its available add-ons, allowing you meet even complex requirements quickly and without custom code. We'll discuss what capabilities are available out-of-the box in Drupal CMS, and the options available to extend them. We'll also talk about how you can add the same capabilities to a site not build with Drupal CMS.
Best of all, during the session we'll do a live demonstration of adding capabilities to your site using Events and other recipes
read more
youtube
"当たり前"を疑いましょ ~ フレームワークからドメインを守るDrupalアーキテクチャ ~
Speaker: umekikazuya
「Taxonomy便利ですよね。」って導入をいつもだったらするんですが、今回はできません。なぜなら私は、TaxonomyをCoreから外してほしいと思っているから。
この冒頭で「何言ってるの？」って感じた方。Taxonomyの強みを言えますか？
本セッションでは、「分類要件といえばTaxonomy！」というDrupalの常識(当たり前)にフォーカスをあてて、その“当たり前”や”習慣”が本当に合理的かを評価し、フレームワークとの向き合い方について、今までのDrupalからすると当たり前ではない提案をさせていただきます。
read more
youtube
大規模Drupalサイトの成功事例：全豪オープンが毎分53万リクエスト以上を処理する仕組み
Speaker: jimmycann
テニスの全豪オープンは3週間の開催期間中に100万人を超える観客が来場し、さらに世界中から数百万人がウェブサイトやモバイルアプリを通じてアクセスする世界的なイベントです。この巨大なデジタル体験を支えているのが大会の情報、選手データ、コンテンツ管理、イベント予約などを統合的に扱う高度なDrupalサイトです。
本セッションでは世界でも有数のアクセス数を誇るDrupalサイトをどのように準備し、安定的に運営しているかをご紹介します。Drupalの強力なキャッシュ機能を最大限に活用し、リスクを適切に管理し、万が一の事態に備える方法について詳しく解説します。
Drupalがどんな規模でも優れたデジタル体験を実現できることを学び、自社サイトで「コストを抑えながら楽にスケールする」実践的なノウハウを得られます。
read more
youtube
Drupal in the Loop: チームで育てる学習データ
Speaker: umekikazuya, sachikonitta
数年前まで、機械学習やファインチューニングは、一部の研究機関やAIスタートアップの専有領域でした。
しかしこの数年、さまざまなツールやプラットフォームの登場によって、それが少しずつ、私たちにとっても身近なものになりつつあります。
学習データは、モデルの「知性」を決める最も重要な基盤です。けれど、そのデータをチームで育てるための仕組みである、バージョン管理、ワークフロー、セキュリティ、アクセス制御、監査ログ出力などの要素を包括的にカバーできるツールは、まだ多くありません。
本セッションでは、Drupalを活用し、研究者やエンジニアだけでなく、コンテンツ制作者や企画担当者も含めたチーム全体で学習データを「育てていく」仕組みを提案します。
read more
youtube
One kilobyte of JS is enough to make a decoupled FE block in Drupal. And no Babels required!
Speaker: murz
To make a Drupal website modern we usually bring there interactive frontend components in JavaScript.
But not only just components!
Together with them, we have to bring a couple of more things:
- A pretty heavy framework: React, Angular, Vue, etc.
- Typescript transpiled to JavaScript.
- Something like Babel to pack all your JS dependencies into one large bundle.
- Rebuild the whole bundle after every change in any TS file!
And, suddenly, to display a simple frontend component, your Drupal webpage should download and execute hundreds of kilobytes, or even megabytes of large JS bundles!
What if I tell you, that you can simply get rid of all these, and just write a kilobyte of a pure and compact JS code? And with no dependency on any JS framework!
So, come and see how it works!
read more
youtube
Smart Search, Safe Search: How Drupal + AI Work Together
Speaker: sachikonitta
AI search is powerful—but without access control, it can leak private content. This beginner-friendly session introduces RAG (Retrieval-Augmented Generation) and shows how Drupal can sit between users and AI to enforce roles and permissions.
The session will include these topics:
- What AI search and RAG really are
- Why just embedding content in a vector database isn’t enough
- Drupal as truth for permissions
- How to connect Drupal with vector DB and AI
- PoC (How a safe AI search looks like)
read more
youtube
デジタル庁が取り組むDrupalを活用した共通CMSの構築
Speaker: Akihiko Sakamoto, Hirokazu Awaji
Drupalを活用して構築した共通CMSの歩み
そのプロトタイプとしてのデジタル庁ウェブサイトの取組
アクセシビリティに対応するためのデジタル庁デザインシステムとの親和性向上の取組等
read more
youtube
I’m Not a Front-End Dev: Building Clean UI in Drupal with SDCs and Shoelace
Speaker: yi_jiang
As a full-stack Drupal developer, I’ve often found front-end frameworks too opinionated or hard to plug into Drupal cleanly. With Single Directory Components (SDCs) and Web Components like Shoelace, we now have a scalable, framework-free way to build modern UI — without needing React or Vue.
This session shows how to use Web Components inside SDCs to create reusable, maintainable elements that integrate easily with Twig, Layout Builder, or Paragraphs. I’ll walk through practical examples and share trade-offs from real projects.
This talk is for developers who live in Drupal, not Figma — and want a sustainable, future-friendly UI approach that doesn’t require becoming a front-end specialist.
read more
youtube
The Future of Workflow Optimization with AI & Drupal Canvas
Speaker: Maggie Schroeder, shumpei
AI is no longer a “nice-to-have” but a necessity for businesses looking to maintain a competitive edge. By identifying inefficiencies and integrating AI solutions from Drupal, organizations can create more collaborative, efficiency, and optimize workflows and the content creation process.
Join us to learn the top 5 ways you can start leveraging AI today with Drupal & Acquia.
read more
Speaker: 晋平 加藤, 俊平 詫間
AI 活用が急速に進む中、Web サイトはこれまで以上に高速性・安定性・セキュリティを求められています。本セッションでは、次世代 CDN/WAF である Fastly を活用し、Drupal サイトのパフォーマンスと拡張性をどのように最大化できるのかを、現場の事例や最新トレンドを交えながらご紹介します。
特に、以下のポイントにフォーカスして解説します：
高速なキャッシュ処理と柔軟なエッジ制御による Drupal 運用の最適化
AI 時代に増加する画像生成・API リクエストなどの新種トラフィックへの対応方法
セキュリティ脅威の高度化に対抗するための最新WAF・Bot対策
開発者が最小限の手間でモダンなインフラを実現するためのアーキテクチャやベストプラクティス
Fastlyを活用することで、Drupalサイト運用は「速く・安全で・管理しやすい」環境へと進化します。
read more
youtube
Epic things you built with Drupal AI
Speaker: schnitzel
Curious about how AI is actually being used in the wild? Join Michael for an in-depth look at the awesome things that have been built with Drupal AI. This session gives an overview of actual running Drupal AI Implementations, how they work, and what we can learn from them. Whether you're a developer, architect, or strategist, you'll walk away with actionable insights and inspiration for your next project.
read more
youtube
Don’t Write Code, Start Prompting! AI Orchestration of Digital Experiences
Speaker: yas
We introduce the architecture of a technology-agnostic workflow engine that defines human-readable decision rules in YAML, ingests them into a RAG datastore, and leverages an LLM to retrieve relevant rules and instantly determine and execute the next approver.
First, we’ll demonstrate the end-to-end flow from rule definition through prompt design to datastore registration. Then, we’ll share production-ready best practices for maximizing retrieval accuracy, using GenAI to extract structured request data from unstructured documents, and keeping workflows current.
Attendees will leave with guidance on expressing approval workflows, practical techniques for structuring decision rules for optimal retrieval, and a roadmap for embedding AI-driven innovation into Drupal or any platform.
read more
youtube
Next steps for Drupal Canvas
Speaker: lauriii
Drupal Canvas initiative aims to revolutionize how content creators and site builders create digital experiences. While there has been significant progress already, the journey is far from over.
This session dives into the exciting next steps for Drupal Canvas, outlining the vision and roadmap on the horizon. You'll leave with concrete understanding of when specific features will be available, how to prepare your projects for Drupal Canvas adoption, and whether it's the right fit for your team's use cases.
read more
youtube
Inside Sharp: How a Global Brand Powers Digital Innovation with Drupal
Speaker: Jason Cort
The Day 2 keynote at DrupalCon Nara 2025 shines a spotlight on how one of the world’s most recognised brands is using Drupal to drive digital success.
On Tuesday 18 November at 9:15am JST, Jason Cort, European Director of Product Management and Marketing at Sharp Europe, will share how this division of the renowned Japanese multinational has embraced Drupal to power its digital ecosystem.
From their flagship website to a vital partner portal, Sharp has built a dynamic and resilient digital presence on Drupal. In this keynote, you’ll hear how open source enables a global corporation to scale with confidence, stay secure, and innovate at speed.
read more
youtube
Migrate APIで移行 (イコー)
Speaker: Matthew Messmer, aniketto
Drupalコアの優れた機能の一つであるMigrate APIは、サイトのバージョンアップはもちろん、さまざまなデータ移行のケースで活用できます。本セッションでは、その具体的な活用例をいくつかご紹介します。
read more
youtube
Brilliant, But Doubting: Imposter Syndrome and the Experience of Women in Tech
Speaker: gargsuchi, JCT321
Despite increasing participation of women in the technology sector, many continue to grapple with imposter syndrome, a psychological pattern marked by persistent self-doubt and a fear of being exposed as a fraud, despite evident competence and achievements.
This session explores the impact of imposter syndrome among women in tech. Drawing on research, lived experiences, and industry data, the session identifies the different factors that contribute to imposter syndrome and explores strategies to foster inclusive environments that support confidence, belonging, and professional growth.
By addressing imposter syndrome not as a personal failure but as a cultural and structural issue, this work aims to contribute to more inclusive and psychologically safe workplaces in the tech industry.
read more
youtube
The future of Drupal core and the ecosystem in the age of Drupal CMS
Speaker: gábor hojtsy
The introduction of Drupal CMS has created a buzz in the Drupal community, redefining how we think about building with Drupal. Its flexible, modern approach to development has opened up new possibilities for innovation. By the time DrupalCon Nara takes place, Drupal CMS 2.0 will have been released with Drupal Canvas and site templates.
But what does this mean for the future of Drupal core and the ecosystem? Especially for those people not using Drupal CMS (yet)? How will Drupal still cater for key use cases, such as headless architectures, social, and e-commerce? What can different personas not in the focus of Drupal CMS (such as developers) expect?
Let's discuss how Drupal CMS may shape the broader ecosystem, and consider the long-term implications for the community.
read more
youtube
Further Empowering Drupal with Single Directory Components using UI Suite
Speaker: drupak
UI Suite is a powerful set of Drupal modules comprising of modules like UI Patterns, UI Patterns Layouts, UI Patterns Block, UI Patterns Field Formatters, UI Patterns Views, UI Styles, UI Skins, UI Icons etc. All these modules empower site builders to use Single Directory Components in a powerful way. These modules add extra metadata to Single Directory Components which can then be used in block, views, field formatters, layouts. This session is about all this.
read more
Global Reach, One Platform: The Journey to Implementing Multilingual in Drupal CMS
Speakers: anjali-rathod, ygoex
After the release of Drupal CMS 1.0, a language selector was introduced but it was later removed due to technical limitations.
Today, multilingual support is more essential than ever.
Organizations need to deliver content in multiple languages to expand their global reach, foster trust, and increase user engagement.
To align Drupal CMS with the multilingual features already built into Drupal Core, a dedicated team of experienced contributors kicked off the multilingual initiative in February 2025.
Join us to explore:
- The approach to move beyond an English-only installation, the technical challenges faced to embed multilingual support.
- Research and design process behind the multilingual UI/UX.
- A glimpse into ongoing work, and how future of multilingual looks like in the Drupal CMS.
read more
Speakers: 晋平 加藤, 俊平 詫間
AI 活用が急速に進む中、Web サイトはこれまで以上に高速性・安定性・セキュリティを求められています。本セッションでは、次世代 CDN/WAF である Fastly を活用し、Drupal サイトのパフォーマンスと拡張性をどのように最大化できるのかを、現場の事例や最新トレンドを交えながらご紹介します。
特に、以下のポイントにフォーカスして解説します：
高速なキャッシュ処理と柔軟なエッジ制御による Drupal 運用の最適化
AI 時代に増加する画像生成・API リクエストなどの新種トラフィックへの対応方法
セキュリティ脅威の高度化に対抗するための最新WAF・Bot対策
開発者が最小限の手間でモダンなインフラを実現するためのアーキテクチャやベストプラクティス
Fastlyを活用することで、Drupalサイト運用は「速く・安全で・管理しやすい」環境へと進化します。
read more
youtube
ネスレグループ日本拠点のDrupal導入の事例： グローバル戦略と現場の運用を繋いでいく
Speakers: taishi, Kozo Takada
前半では日本拠点でのDrupal導入における課題や取り組みを紹介し、後半はグローバルDXPにおけるアジリティ実現をテーマにネスレ日本の担当者の方と対談します。実務担当者の視点からの知見を共有します。
read more
youtube
Kintsugi for the Web: Repairing, Rebuilding, and Reimagining with Drupal
Speaker: dreambubbler
Join Dallas Ramsden on a journey connecting personal resilience with Drupal's transformative power through science, culture, and community. Learn how historical figures like Mo Tzu and the scientific method parallel the "Open Web" and "Open Source" movements, demonstrating how openness drives innovation and freedom.
Having recently relocated to Okinawa, Dallas celebrates DrupalCon Japan by exploring how the island's rich cultural tapestry mirrors Drupal's diverse community. Discover how embracing different perspectives strengthens the Drupal ecosystem and ensures its relevance through forward-thinking solutions.
read more
youtube
CMSに留まらない - AIを操るDrupalの新たな可能性
Speakers: Masami, Akihito.Kimura@ntt.com
Drupalはもはや単なるCMSではありません。AIの一部として機能しながら、同時にAIを操り、対話し、共に進化していく存在へと変わりつつあります。このセッションでは、DrupalがどのようにAIと共に進化し、新たな可能性を切り拓いていくのかを紹介します。
read more
youtube
改めて振り返るDrupalのモジュール/テーマのデバッグ方法
Speaker: otofu
Drupalでモジュールやテーマを開発する際や動作の中で気になる挙動を見つけた際の原因特定を行う為のデバッグ方法について普段私がどのように行っているかをハンズオンを交えて紹介します。
主な内容は以下の通りです。
・デバッグ環境の整え方
・デバッグに便利なコントリビュートモジュールの紹介(Devel, Web Profiler)
・IDE(PhpStorm)とXdebugを組合せたデバッグ方法
read more
Speakers: Miki Yoshida, Misako Fukagawa
Drupalは高機能なCMSとして多くの実績を持つ一方で、日本では「技術者向け」「専門的すぎる」という印象を持たれがちです。しかし実際には、プロジェクトマネージャー（PM）、スクラムマスター（SM）、UXデザイナー、コンテンツプランナーなど、多様な職種が関わり合いながらプロジェクトを成功に導いています。
私たちは「Drupalは特定の人だけのものではない」と感じられるようなMeetupを毎月企画しています。このMeetupでは、これまでにのべ人数100人以上のご参加をいただいており、技術的な知識よりも、「なぜDrupalを使うのか」「それぞれの職種がどう関わるのか」「多様なチームでどんな可能性が生まれるか」といった視点を重視。誰もが自分の立場からDrupalに関われるイメージを持てることを目指しています。
本セッションでは、こうしたMeetupを立ち上げた背景や運営の工夫、これまでに寄せられた参加者の声を交えながら、プロジェクトの現場におけるPM・SM・デザイナーの価値を再発見する機会を提供します。Drupalとの関わりに新しい視点を加えたい方に、ヒントや気づきを持ち帰っていただける内容です。
read more
youtube
Lessons from Integrating AI Into Real Marketing Teams
Speaker: saxenaakansha30
I’ve been working directly with AI to help solve real challenges faced by marketing teams, improving workflows, reducing manual effort, and supporting better decision-making.
In this session, I’ll share lessons learned from trying out different approaches in real marketing use cases. We’ll talk about what worked, what didn’t, and how to introduce AI into a team without disrupting how people already work.
Whether you’re leading a team, building marketing tools, or just curious about how AI fits into day-to-day work, this session will offer real, honest insights from the field.
read more
youtube
That's Not a Theme, It's a Template
Speaker: elliott.mower
The Drupal Canvas design system for Drupal CMS: one system, three site templates, and a streamlined path to low-code site creation—launching together to guide site builders, themers and designers.
read more
youtube
Drupal Commerce's Starshot Roadmap
Speaker: zaporylie
The vision for Drupal CMS (née Starshot) is bold and inspiring, inviting everyone in the Drupal community to consider how they might help end users accomplish even more with Drupal. Hear from the Drupal Commerce maintainers how they revised their roadmap to incorporate Starshot initiatives and to rethink key elements of Commerce Core in line with the Drupal Starshot product strategy. Recent, pending, and future features include:
* Commerce recipes to solve common eCommerce use cases
* AI agents that help merchants with complex configuration tasks
* Experience Builder support for product and order pages
You will leave ready to evaluate the platform afresh yourself, contribute to these and other initiatives, and implement it for your next merchant client.
read more
youtube
Zero-downtime Drupal deployment with Kamal
Speaker: hktang
You've built an amazing Drupal site ready to deploy. You want your deployments zero downtime, error-free, scalable, and future-proof. Yet, you are almost on your own, and Kubernetes is quite a beast to tame!
You don’t want to be overwhelmed by the complexities of container orchestration, nor do you want to gamble with a shaky base system. You need a deployment workflow that’s reliable and stress-free, with a gentle learning curve.
If this resonates with your experience, join this session to explore Kamal — a deployment tool that helps achieve these goals with greater simplicity. I will share my journey of setting up a Kamal-based deployment workflow dedicated for Drupal, and the lessons learned along the way, including on configuration, networking, file system, search API, caching, and more.
The code introduced in the presentation is available at https://github.com/hktang/drupal-kamal
read more
youtube
Beyond Iframes: Modern Embedding in Drupal with Media and oEmbed
Speaker: pcambra
oEmbed is a well established format, however ever evolving content usage policies and security restrictions are preventing site builders from using iFrames to inject external content from sources such as YouTube, Instagram, X, and many social networks and content providers.
By using oEmbed standard practices, external content can be safely embedded to a Drupal website by using core tools such as the Media module and contributed modules such as oEmbed Providers.
In this session we will cover:
- What is oEmbed format and how does it work under the hood.
- What Drupal modules can be leveraged to embed content from third parties.
- CKEditor best practices for embedded objects.
- How to enhance embeds with auth or privacy controls
- How to build your own resources to embed custom content.
read more
First things to keep in mind when building a worldwide multi-site, multilingual site with Drupal
Speaker: ken_taguchi
Drupal is so popular in the enterprise market that there is no single Drupal development project that is easy for developers.
One of the biggest challenges is the global project of deploying multiple sites in multiple languages in so many regions and countries.
In such projects, we have to create a consistent platform while considering the requirements of multiple stakeholders, legal systems, network environments, etc. in each region and country.
As a Drupal agency in Japan, we have helped large Japanese companies build websites around the world with Drupal in many projects.
In this session, we will share some of the key ideas and points to keep in mind when using Drupal to deploy digital marketing in countries and regions around the world.
read more
youtube
Backwards and in High Heels: Early adopter insights on Drupal in Japanese academia
Speaker: shinmaikeru
Fax machines for marketing? Carved ivory seals for bank accounts? These aren't just "WTF Japan" memes; they grew out of the context of the bureaucracy, language, society, and culture. The better you understand this context, the more effective you will be here. Drawing on over 30 years living in Japan and 20 years working in Japanese universities, I will offer a perspective on the technical and administrative challenges facing Japanese educational institutions. I will also offer context on the challenges Japan has faced in using the web. I believe that Drupal is a valuable tool for organizations like mine, and I want to help you understand Japanese organizations better so you can help them benefit from Drupal.
read more
youtube
How to sell Drupal in AI times
Speaker: nielsaers
AI is reshaping buyer expectations faster than any CMS trend we’ve seen. Prospects now ask: “How will your platform harness my data for AI without locking me in?” This session arms agency leads, sales engineers, and product owners with a pitch that lands. We’ll map the AI conversation to Drupal’s core strengths—its open-source DNA, composable architecture, and unrivaled content-model flexibility—showing how those translate into faster model training, lower TCO, and freedom from black-box SaaS traps. You’ll leave with a jargon-free narrative, fresh proof points (from real AI-enabled Drupal builds), and a one-page value-matrix you can drop into your next proposal.
read more
youtube
Drupal CMS now and beyond
Speakers: pameeela, ckrina
With Drupal CMS 2.0 released in September, it's a great opportunity to showcase what we have built so far, what we have planned next on the roadmap, and briefly look back at the process so far.
Some topics we may cover:
* Features and areas we're working on now
* Plans for future versions ongoing
* What we're looking for from contributors
* How we defined the strategy and scope
* Using the strategy to define the roadmap and what it looks like now
* How the community has come together to work toward the same goal
* Highlights from the initial work tracks and what we learned from them
read more
youtube
Welcome Remarks from Nara City Mayor Gen Nakagawa
Welcome remarks from Nara City Mayor Gen Nakagawa
---
Dear DrupalCon Japan participants,
On behalf of the Government and citizens of Nara City, I would like to offer my wholehearted support to the DrupalCon Japan 2025.
Nara is the roots of Japan, where international exchange through the Silk Road flourished and the first capital city was built over 1300 years ago, when people talk about "the real Japan", the landscape of Nara is what comes to mind.
Close to Kyoto and Osaka and quickly accessible by train, Nara is a living history book, full of World Heritage sites and well-preserved temples and shrines. Nara provides a very calm and peaceful environment.
We believe the historical ambience created by Nara's authentic environment will enhance your stay and enrich your mind. It is also good for creative work, drawing inspiration from them.
We look forward to welcoming your delegates and colleagues to Nara.
Yours faithfully,
Gen Nakagawa
Nara City Mayor
read more
youtube
A conversation with Drupal’s founder and project lead, Dries Buytaert
On Monday 17 November at 9:55am JST, Drupal founder and project lead Dries Buytaert took the stage for a special Q&A keynote.
Dries created Drupal in 2001 and has guided its growth into one of the world’s leading open source projects. As project lead, he continues to champion Drupal’s innovation and community-driven spirit.
This keynote is your chance to hear directly from Dries about the future of Drupal, community priorities, and the questions that matter most to you. Look out for a survey link to submit your questions in your inbox the week before the event takes place.
read more
youtube
Forks, Features, and Frustration: Technical Lessons from 100+ Drupal Sites
Benjamin Rasmussen (Ras-ben)
Scaling Drupal across 100+ independent sites brings technical chaos: config overrides, rogue modules, forked repos. In this session, we’ll explore real-world solutions — and the scars — from managing it.
Prerequisite
The talk will be developer-focused, and include code solutions - however, as a use case, it might also be interesting to sitebuilders.
Outline
I work for Reload, a Danish digital agency. We recently built a Drupal platform that is used as the public facing website for 100+ libraries across 3 countries.
Some of these libraries are very small, with very few editorial resources, where things just need to work out of the box.
Others have many editors and technical ambitions, such as having their own modules developed, uploaded and managed, without Reload getting involved.
On-top of all that, the platform is also open-source, meaning that there are some libraries that are completely out of Reload’s control - managed by other digital agencies.
All of this results in a situation where we need to both have a site that can be strictly controlled for some, and very open for others.
A platform, where we need to be able to force through our updates, without overwriting the webmasters work.
Learning Objectives
- Learn practical techniques for managing shared configuration across large numbers of Drupal sites.
- Understand how to structure deployments when allowing different degrees of editorial and technical freedom.
- Identify governance models that reduce platform instability without over-restricting innovation.
- Recognize early warning signs of dangerous forks, rogue modules, or config drift in a platform ecosystem.
Experience level
Intermediate
read more
youtube
Transforming Drupal Agency Ops using Gleicher's Formula for Change
Speaker: Hetal Mistry (Hetalad)
When things are going well, agencies fall into the trap of cognitive ease. There is a false sense of security in the status quo. This sense of security is often disrupted by a change in the business environment. Cognitive ease leaves agencies unprepared for this disruption. Build resilience and adaptability by leveraging Gleicher’s Formula for Change — Dissatisfaction × Vision × First Steps must exceed Resistance.
Prerequisite
Familiar with the Drupal agency ecosystem
Openness to hearing truth bombs about the current uncertainty and volatility in the Drupal agency space
Curiosity about agency growth stages and evolution
Interest in change management and transformation strategies to scale agencies sustainably
Outline
Introduction
In this session, I will share the story of how my team transformed operational and financial decision-making by applying Gleicher’s Formula for Change (D × V × F > R). This framework helped us break free from the trap of “cognitive ease”—a period when things seemed fine on the surface but deeper dysfunction was building underneath.
The Trap of Cognitive Ease
During favourable periods, agencies experience cognitive ease, no significant disruptions, or a need for a heightened focus or mobilised efforts. My team was no different. However, as change began to creep in, we detected warning signs such as longer opportunity cycles and mismatch of capability versus needs.
Gleicher’s Formula for Change: An Agency-Friendly Framework
Once warning signs became significant, the need for change kicked in like a survival mechanism. Unsure what needed to change and how, my research led me to Gleicher’s Formula.
For a change to be successful, the consolidated effect of dissatisfaction, vision, and the initial steps had to be greater than the resistance to change. If any of these are lacking, the transformation may only be theoretical or unsuccessful. I now had the pieces of the puzzle; what remained was to place them together
Leveraging Dissatisfaction
An immediate result of being in a state of cognitive ease amidst an uncertain business environment was dissatisfaction. Factors such as projects running longer than planned, unpredictable opportunities cycle, and inaccurate/no forecasts. We leveraged the dissatisfaction to draw attention to specific and tangible impact areas such as revenue forecasts, project margins, and workforce planning.
Vision Clarity
The current state of the impact areas helped me define what the vision or desired state looks like. The vision was not shared tools, dashboards and metrics, but a shared understanding of what we needed and why. We wanted to equip each team with a shared language of financial intelligence & impact. It started with something as basic as defining essential metrics, designing how to track them consistently and regularly sharing outcomes with the team.
Building Momentum, Not Perfection
A change or transformation is often misunderstood as a big sweeping movement when in reality it is several incremental updates that result in a meaningful impact. We assessed the information available to create building blocks, such as the number of projects, their billing models, actual invoice data and deal pipelines. These became the foundation of our reporting, and we chose to live with accurate data instead of aiming for precision.
Overcoming Resistance
Once the initial reports and models started taking shape, we started soft rollouts with teams. The initial feedback ranged from doubts about overthinking the problem, questioning the impact, and the reliability of data. The combined forces of dissatisfaction with the status quo, a clear vision, and tangible outcomes demonstrated enough evidence that the transformation was much needed, and challenging the status quo was essential for maintaining resilience.
Conclusion
The journey of driving the operational and financial transformation became clearer and easier through the framework of Gleicher’s Formula for Change. If your agency is showing signs of cognitive ease, the Gleicher Formula can guide your shift. Leverage your dissatisfaction, set a clear vision, and let your first steps build momentum. Because when the resistance shows up—and it will—what matters is that the change feels worth it.
Learning Objectives
Identify signs of “cognitive ease” in agency life and understand why it can stall growth.
Apply Gleicher’s Formula for Change to drive meaningful transformation, not performative process shifts.
Learn from my experience of implementing financial visibility through small, iterative, cross-functional steps.
Leave with a tangible framework for mapping dissatisfaction, articulating vision, and reducing resistance inside your agency.
Experience level
Intermediate
read more
youtube
Git into the Groove - Moving from Freelance to Collaborative Workflow
Speaker: AmyJune Hineline (Volkswagenchick)
Git into the groove and git ready to move from freelance to working in an agency. In this session, learn the basics of version control, branches & local environments... all to the tune of our favorite 80s songs!
Prerequisite
Basic Command Line knowledge
Outline
Going from freelance to working in an agency can be overwhelming, but don’t let the fear of a collaborative workflow scare you.
What is Git?? Better question, what is version control? And what the heck is a local environment?
We’ll cover the basics of:
- Local environments, multidevs, and branches
- Version control
- Overview of a git client
Learning Objectives
Target Audience
Freelance Developers Transitioning to Team Environments: Folks used to working solo who want to better understand how to work with teams, version control, and shared environments.
Junior Developers or New Hires at Agencies: Especially those without prior experience using Git, multidevs, or local development environments.
Career Changers or Bootcamp Grads: People coming into tech from other industries who may have limited exposure to collaborative coding workflows.
Designers or Site Builders Dipping into Code: Those who are starting to work with Git and need a low-stress, beginner-friendly introduction.
Experience level
Beginner
read more
twitter
RT @TalkingDrupal: On episode #390, Employee Owned Business with Seth Brown, CEO @lullabot. https://t.co/KiYM6Zwz5C #drupal
read more
twitter
Nonprofit Drupal posts: March Drupal for Nonprofits Chat https://t.co/uJq3iqKikr #drupal
read more
twitter
Community Working Group posts: Call for creators for crafting future Aaron Winborn Awards https://t.co/JqGX6q9W1M #drupal
read more
twitter
Community Working Group posts: Nominations are now open for the 2023 Aaron Winborn Award https://t.co/wrYfMue23T #drupal
read more
twitter
The Drop Times: Just Keep Showing Up, and the Job Is Yours: Chris Wells | DrupalCamp NJ https://t.co/FL1c6MdS9Z #drupal
read more
twitter
RT @ironstar_io: The 2023 Drupal Local Development Survey has now been translated into French, Japanese, and Traditional Chinese. We are ve…
read more
twitter
The 2023 Drupal Local Development Survey has now been translated into French, Japanese, and Traditional Chinese. We are very grateful to @mupsigraphy for her work on this French translation.
If you would like to add a translation, please let us know as there's still time!
read more
twitter
RT @e14t: Mastering Drupal 9 Layout Builder: A Comprehensive Guide to Effortlessly Customize Your Website's Design #drupal https://t.co/veg…
read more
twitter
Mastering Drupal 9 Layout Builder: A Comprehensive Guide to Effortlessly Customize Your Website's Design #drupal https://t.co/vegAGDzSdh
read more
Powered By Combinary
twitter
RT @Drupalcameroun: How #Drupal communities on the #African continent can help their governments in their #digitalization process. @_Africa…
read more
twitter
Chapter Three: where we celebrate National Pi Day with forward-thinking NextJS and Drupal expertise, and National Potato Chip Day with an unparalleled snacking prowess. What is your favorite chip flavor? 🥧 🍟 🤓#PiDay #PotatoChipDay #drupal #nextjs
read more
twitter
Pues me está gustando mucho lo de hacer directos en #twitch sobre desarrollo en #Drupal, le estoy cogiendo el gusto.
read more
twitter
Drupal has offered top-notch no-code/low-code site building functionalities long before these two terms even existed. You can learn more about Drupal as a no-code/low-code tool in this @agiledrop article: https://t.co/TDwJn5DT6r
#Drupal #NoCode #LowCode https://t.co/tGVQhtdtvH
read more
twitter
I spent the last week doing #peformance #optimization of our #drupal 9 application infrastructure. I learned a lot about #PHP #opcache #profiling and Drupal's internal caching systems.
#webprofiler module was a big help, too!
read more
twitter
The Drop Times: A Stitch in Time Saves Nine https://t.co/VMWANTSAUe #drupal
read more
twitter
One of our Back-end Developers, Greg Carlson has officially been with Aten for one year! Greg's favorite project this year was creating a #Drupal module to easily import CSV files to create content for @C4LPreK. In his free time, Greg follows the KU Jayhawks in his hometown. https://t.co/CN5QDULccA
read more
twitter
RT @nmdmatt: .@phpstan's new not-deprecated annotation #drupal
https://t.co/To2MLb1hpw
read more
twitter
RT @nmdmatt: .@phpstan's new not-deprecated annotation #drupal
https://t.co/To2MLb1hpw
read more
twitter
Matt Glaman: PHPStan's new @not-deprecated annotation https://t.co/Idxe5nlpQV #drupal
read more
twitter
Session submission: »The Ten Ways of Trust in Communication« by
@kanadiankicks | @open_strategy
https://t.co/HpYj8309le
#dcruhr23 #Drupal (tf) https://t.co/zkzLT1BNJZ
read more
twitter
#Drupalcamp Colorado has dates! Aug 4 and 5. We want YOU to speak! Your topic doesn't have to be Drupal specifically but should be Drupal adjacent. #drupal #camp #opensource @drupalcolorado
Please share this post liberally!
https://t.co/Yb1x3vxmQ5 https://t.co/jMBQUq2hPu
read more
twitter
Wozu braucht man Drush bei #Drupal 9?
Module lassen sich direkt updaten. Drupal Update mit Drush hat einen Aufkleber "deprecated".
read more
twitter
RT @SamHuskey: Attention #Drupal developers: @scsclassics is hiring! Details at https://t.co/3lTYHaQys3
read more
twitter
Why join the Acquia's Headless Developer Advisory Board? This board is an opportunity to have your say. Provide feedback into our headless products an roadmaps. Check it out! #Drupal #DrupalHeadless #Decoupled #Developers #Technology #Leadership https://t.co/HJVa4aEinQ
read more
twitter
RT @TalkingDrupal: On episode #390, Employee Owned Business with Seth Brown, CEO @lullabot. https://t.co/KiYM6Zwz5C #drupal
read more
twitter
Olivero is the new default theme in #Drupal10 & 9 – and the most accessible one yet. Learn more about this modern theme’s best features, as well as its notable namesake. https://t.co/JHwH3hexgq #Drupal https://t.co/zTEKd7wOMa
read more
twitter
Are you a developer looking to stay ahead of the game? Then mark your calendars for March 19th and join us for the #Drupal Meetup at Zain Zinc! Don't miss out on this opportunity to enhance your skills and connect with fellow professionals! Register Now! https://t.co/0HwzZfdoR6
read more
twitter
What Is a Content Management System (#CMS)? https://t.co/4Pd3JMXeKS #Wordpress 'joomla #Drupal
read more
twitter
Le connecteur officiel #ONLYOFFICE pour #Drupal est est disponible dans le répertoire officiel de Drupal.
En savoir plus : https://t.co/UuUhlOteJn https://t.co/ENue19M7aN
read more
twitter
.@phpstan's new not-deprecated annotation #drupal
https://t.co/To2MLb1hpw
read more
twitter
RT @drupalfr: 🔍 Vous avez peut-être vu passer une enquête sur les environnements de développement locaux avec #Drupal récemment ?
Elle es…
read more
twitter
RT @drupalfr: 🔍 Vous avez peut-être vu passer une enquête sur les environnements de développement locaux avec #Drupal récemment ?
Elle es…
read more
twitter
RT @DrupalCampRuhr: Wir danken unserem Bronze-Sponsor @arocom_GmbH! 🥰
"Sie suchen eine auf das CMS #Drupal spezialisierte Internetagentur…
read more
twitter
RT @drupalasheville: If you have an amazing training idea for #Drupal Camp #Asheville, remember to submit by March 28. That’s in two weeks!…
read more
twitter
If you have an amazing training idea for #Drupal Camp #Asheville, remember to submit by March 28. That’s in two weeks!
If you are an expert in #SEO, #accessibility, #front-end technology, etc. our attendees would love to learn from you.
Learn more at https://t.co/kOg4BLfyXq. https://t.co/IBB17YWptn
read more
twitter
The latest Drupal Review! https://t.co/AWLDaVGtYD Thanks to @laravel_101 #drupal #developer
read more
twitter
RT @DrupalCampRuhr: Wir danken unserem Bronze-Sponsor @arocom_GmbH! 🥰
"Sie suchen eine auf das CMS #Drupal spezialisierte Internetagentur…
read more
Wir danken unserem Bronze-Sponsor @arocom_GmbH! 🥰
"Sie suchen eine auf das CMS #Drupal spezialisierte Internetagentur? Dann sind Sie bei der arocom GmbH genau richtig. Wir entwickeln individuelle Internetauftritte, Portale, Shops und Intranetlösungen." (gs) #dcruhr23 https://t.co/eR7Ql6Tmns
read more
twitter
Join us April 27 for the Drupal Zurich Meeting with talks about Ting, AI-Powered-Search-Indexes as well as @SplashAwards_CH 2023
#Drupal #DrupalZH #DrupalSwitzerland https://t.co/HICNsoGSuv
read more
twitter
I love all my Drupal and Magento projects I developed in the past 😁🙌 especially Shutterstock from the USA liked it #drupal
read more
twitter
RT @drupalfr: 🔍 Vous avez peut-être vu passer une enquête sur les environnements de développement locaux avec #Drupal récemment ?
Elle es…
read more
twitter
🔍 Vous avez peut-être vu passer une enquête sur les environnements de développement locaux avec #Drupal récemment ?
Elle est désormais disponible en français, et vous avez jusqu'au 17 avril pour participer ! 🇫🇷
https://t.co/bvGG2Mh0cI
read more
twitter
On episode #390, Employee Owned Business with Seth Brown, CEO @lullabot. https://t.co/KiYM6Zwz5C #drupal
read more
twitter
Specbee: Mastering Drupal 9 Layout Builder: A Comprehensive Guide to Effortlessly Customize Your Website's Design https://t.co/J3m41Xemep #drupal
read more
twitter
In this blog's category, you’ll learn about useful features of Droopler - our #Drupal distribution for building websites/creating landing pages for #marketing campaigns 👨💻 Check the #SEO and navigation functionalities, and the web pages built on Droopler https://t.co/CeicqTnTad
read more
twitter
RT @ultimike: I am not surprised by these new #drupal modules, and I welcome our new AI-based content overlords with peace and love 😜
http…
read more
twitter
¿Instalar #Drupal con un solo click? Si es posible con nuestros planes de #Hosting (Hospedaje Web), Contrata tu plan ¡Ahora! https://t.co/UyteHPrXCq
read more
twitter
ちょっと時間があったので、https://t.co/Fa5p1pcDT8 Blueprintsを触ってみた。Add https://t.co/Fa5p1pcDT8 content typeでレストランとかパン屋を定義してみて、結構ワクワクした。UIが良く属性定義のベストプラクティスが出てくる感じ。 #Drupal
https://t.co/mkd5ciBgLy
read more
twitter
RT @volkswagenchick: Want to learn how to contribute to #Drupal?
Join me at @FoxValleyDrupal next month to learn the ins and outs of the is…
read more
twitter
RT @volkswagenchick: Want to learn how to contribute to #Drupal?
Join me at @FoxValleyDrupal next month to learn the ins and outs of the is…
read more
twitter
RT @ultimike: I am not surprised by these new #drupal modules, and I welcome our new AI-based content overlords with peace and love 😜
http…
read more
twitter
RT @opensourceway: Want to learn how to contribute to #Drupal?
Join @opensourceway's @volkswagenchick at @FoxValleyDrupal next month to l…
read more
twitter
RT @ultimike: I am not surprised by these new #drupal modules, and I welcome our new AI-based content overlords with peace and love 😜
http…
read more
twitter
With our #webhosting plans, #webdev create your awesome #website with #drupal a #Free content management system (cms) https://t.co/HbNxEroF4h
read more
twitter
RT @volkswagenchick: Want to learn how to contribute to #Drupal?
Join me at @FoxValleyDrupal next month to learn the ins and outs of the is…
read more
twitter
Want to learn how to contribute to #Drupal?
Join @opensourceway's @volkswagenchick at @FoxValleyDrupal next month to learn the ins and outs of the Drupal issue queue.
Spoiler alert: you don't have to be a coder to give back to open source.
… https://t.co/yi56be3YUR
read more
twitter
The latest The drupal Daily! https://t.co/EXg9Mjai8k Thanks to @laravel_101 #drupal #wordpress
read more
twitter
@bretwp I recommend #Drupal for sites that have the need to tie together dynamic content in a plethora of ways. Good for HighEd or government sites.
read more
Powered By Combinary
twitter
opensourceway: Want to learn how to contribute to #Drupal?
Join @opensourceway's @volkswagenchick at @FoxValleyDrupal next month to learn the ins and outs of the Drupal issue queue.
Spoiler alert: you don't have to be a coder to give back to open sour… https://t.co/POww6YqRQP
read more
twitter
Want to learn how to contribute to #Drupal?
Join @opensourceway's @volkswagenchick at @FoxValleyDrupal next month to learn the ins and outs of the Drupal issue queue.
Spoiler alert: you don't have to be a coder to give back to open source.
https://t.co/G3dSaUzV5r
read more
twitter
Want to learn how to contribute to #Drupal?
Join me at @FoxValleyDrupal next month to learn the ins and outs of the issue queue.
Spoiler alert: you don't have to be a coder to give back to open source.
read more
twitter
RT @mikeherchel: #Drupal I wrote a blog post on how I migrated an Olivero component to use Drupal's new Single Directory Components archite…
read more
twitter
RT @boshtian: Drupal 10 upgrade: Custom code upgrades, post by @darthsteven of @computerminds https://t.co/StelwGvv96 #Drupal
read more
twitter
@iansvo @bretwp Not in the recommendation business anymore but here is how it normally goes -
@rootswp for those who love #WordPress + #Laravel.
@drupal for those who love @symfony
I personally prefer #Drupal these days.
read more
twitter
RT @boshtian: Drupal 10 upgrade: Custom code upgrades, post by @darthsteven of @computerminds https://t.co/StelwGvv96 #Drupal
read more
twitter
RT @mikeherchel: #Drupal I wrote a blog post on how I migrated an Olivero component to use Drupal's new Single Directory Components archite…
read more
twitter
#365daysOfCode Day 356
1. Anki
2. Reading: Javascript Security 101
3. #Drupal : Block Views, built my first one!
Still need to push more on drupal it's tough
(anyone know any good resources?)
4. #100Devs Standup
5. PoW Dev Hangout
6. Codewars 6th
read more
twitter
Attention #Drupal developers: @scsclassics is hiring! Details at https://t.co/3lTYHaQys3
read more
twitter
RT @volkswagenchick: Are you ready to be part of the most exciting European #Drupal event of the year? @DrupalConEur Lille's CFPs is now o…
read more
twitter
RT @mikeherchel: #Drupal I wrote a blog post on how I migrated an Olivero component to use Drupal's new Single Directory Components archite…
read more
RT @volkswagenchick: Are you ready to be part of the most exciting European #Drupal event of the year? @DrupalConEur Lille's CFPs is now o…
read more
twitter
RT @DrupalContract: Now #hiring ➡️ We’re looking for a #Drupal Redesign Project Manager who is skilled with managing project development, d…
read more
twitter
RT @DrupalContract: Now #hiring ➡️ We’re looking for a #Drupal Redesign Project Manager who is skilled with managing project development, d…
read more
twitter
Now #hiring ➡️ We’re looking for a #Drupal Redesign Project Manager who is skilled with managing project development, defining project scope, goals, and deliverables, and estimating project resource requirements. Learn more & apply here: https://t.co/TqBE9ftdtR
#techishiring
read more
twitter
Want to learn more about what Contribution Day at #MidCamp 2023 is going to involve?
Have we got a meetup for you on April 19th! Thanks to @FoxValleyDrupal
https://t.co/ROnSakuIlZ
read more
twitter
In the previous versions of #Drupal, you used the #rules module to trigger an action upon an event. In #durpal8
#drupal9 / #drupal10, you subscribe to events and dispatch your own.
read more
twitter
Excited to guest host this webinar and chat with some really great security experts to talk about #security in #Drupal
read more
twitter
Start taking digital security more seriously! Come see our webinar as guests from @ciandt and the @drupalassoc share insights on pressing security concerns for businesses and provide practical tips for protecting against emerging threats. Join us: https://t.co/E6pvqu2mWO https://t.co/TQcrqAxH5u
read more
twitter
Drupal 10 upgrade: Custom code upgrades, post by @darthsteven of @computerminds https://t.co/StelwGvv96 #Drupal
read more
twitter
By not upgrading your #Drupal websites to the latest version of #Drupal, you're making it difficult for yourself in the future.
read more
twitter
I am not surprised by these new #drupal modules, and I welcome our new AI-based content overlords with peace and love 😜
https://t.co/gXLVYFZ19q
Thanks, @kevinquillen, for giving me something new to be distracted by.
read more
twitter
Looking to scale up a Drupal site? Or test its capacity to handle surges in volume? Promet’s Josh Estep reviews four load-testing tools for Drupal.
https://t.co/6mrfGgWghg
#drupal #drupaldeveloper #drupal9 #drugdevelopment #training https://t.co/bKFDuBbrOb
read more
twitter
Sprawdź, który system CMS jest dla Ciebie najlepszy! 🤔👨💻
Czy to WordPress, Joomla, Drupal, Shopify czy Magento, znajdziesz tu informacje, które pomogą Ci podjąć najlepszą decyzję.📝💻
https://t.co/c17hggTOsB
#CMS #WordPress #Joomla #Drupal #Shopify #Magento
read more
twitter
To compete with some of the largest companies on the web, independent bookstores need a platform with all of the e-commerce features people have come to expect.
See how we helped create a full-featured alternative to platforms like Shopify.
https://t.co/A6ApsA1LWP #drupal
read more
twitter
Are you ready to be part of the most exciting European #Drupal event of the year? @DrupalConEur Lille's CFPs is now open
https://t.co/rz4OkhIZhU
read more
twitter
Are you ready to be part of the most exciting European #Drupal event of the year? @DrupalConEur Lille's CFPs is now open
https://t.co/6rFNhpIiwJ
read more
twitter
Are you ready to be part of the most exciting European #Drupal event of the year? @DrupalConEur Lille's CFPs is now open
https://t.co/tVmHJ7JO2a
read more
twitter
This #WomensHistoryMonth, support #womenintech by sponsoring the Women in Drupal event at @drupalcon Pittsburgh!
Grow and diversify talent in your organization by showcasing the #Drupal project and community at its best: https://t.co/j3fGMwOqyy https://t.co/GZUo6uBrlu
read more
twitter
You can write documentation and examples about that documentation. This is also considered a contribution towards the #Drupal project.
read more
twitter
I’ll be speaking at @drupalcampnj this week - who else is going?
read more
twitter
Yesterday we released #GinAdminTheme RC2. Get it while it's hot: https://t.co/O7ItwDngLu #Drupal
read more
twitter
RT @mikeherchel: #Drupal I wrote a blog post on how I migrated an Olivero component to use Drupal's new Single Directory Components archite…
read more
twitter
RT @specbee: Did you know #Drupal offers almost 50,000 modules for you to use in your projects?!
All of these modules are creations of the…
read more
twitter
RT @specbee: Read our detailed blog on the must have Drupal modules for your Drupal project - https://t.co/TJXt8BGS1h
read more
twitter
Attending @DrupalCampNJ in Princeton? Then you won't want to miss @aburke626's session, "Creating a Culture of Documentation,” on Friday, March 17th from 14:30 - 15:15 EST. For more on Alanna's session, check out: https://t.co/1NztgYY9ps
#OpenSource #DrupalCamp #Drupal https://t.co/67kIG6IVcn
read more
twitter
@somnana555 @RMCSportCombat @RMCsport BIG PROMOTION ( Free Trial )
IP TV: 40 € / 12 months
: 30 € / up to 6 months
IP TV is over 18,000 live channels
- 𝐒𝐏𝐎𝐑𝐓
https://t.co/EcsCMBEzEL
#Encodage/ #H264 / #x264 / #x265 / #VOD / #OTT / #IPTV / #HEVC / #av1 / #MotionDesign / #VR / #Drupal / #caméraVR #livestream360
read more
twitter
@steven_reyes_va @CSEmelec BIG PROMOTION ( Free Trial )
IP TV: 40 € / 12 months
: 30 € / up to 6 months
IP TV is over 18,000 live channels
- 𝐒𝐏𝐎𝐑𝐓
https://t.co/EcsCMBEzEL
#Encodage/ #H264 / #x264 / #x265 / #VOD / #OTT / #IPTV / #HEVC / #av1 / #MotionDesign / #VR / #Drupal / #caméraVR #livestream360
read more
twitter
@Transports2K @Panamza BIG PROMOTION ( Free Trial )
IP TV: 40 € / 12 months
: 30 € / up to 6 months
IP TV is over 18,000 live channels
- 𝐒𝐏𝐎𝐑𝐓
https://t.co/EcsCMBEzEL
#Encodage/ #H264 / #x264 / #x265 / #VOD / #OTT / #IPTV / #HEVC / #av1 / #MotionDesign / #VR / #Drupal / #caméraVR #livestream360
read more
