Feed aggregator

Centarro: Webinar: Your Drupal Commerce Website Doesn't Have to Be Slow

Drupal Planet -

Drupal Commerce powers live auctions involving thousands of concurrent users, serves catalogues with millions of products, and presents rich product pages with hundreds of attributes and variations. And it does so with speed and reliability. In fact, it was architected to manage high volume and high complexity.

So why does your Drupal Commerce site feel so slow? Why does it feel like you’re constantly fighting bottlenecks and performance problems?

It’s not the platform. It’s something else.

In this webinar, Ryan Szrama and Tom Ashe will cover the most common culprits behind slow Drupal Commerce sites and how you can start fixing them.

Whether you're troubleshooting a slow site yourself or managing a team that is, you'll walk away with a practical checklist to investigate and a process for diagnosing your performance issues.

Join us on Tuesday, June 9th, at 10:30 AM ET.

Register for the webinar.
 

Read more

Drupal AI Initiative: Call for Papers: Enterprise AI Summit Europe 2026

Drupal Planet -

The Enterprise Drupal Summit Europe 2026 will take place on 28 September 2026 in the SS Rotterdam.

We are now accepting session proposals.

Focus of the summit

The program focuses on Drupal in enterprise contexts, with emphasis on:

  • Large-scale Drupal architectures
  • Digital experience platforms built on Drupal
  • AI use in enterprise content and delivery workflows
  • Composable and API-driven architectures
  • Governance, security, and compliance in regulated environments
  • Operating Drupal at scale in complex organizations

The event is aimed at practitioners and decision-makers working on enterprise digital platforms.

What we are looking for

We are prioritizing submissions that are based on real implementations.

Relevant topics include:

  • Case studies from enterprise or public sector deployments
  • Architecture decisions in complex Drupal systems
  • AI integration in content management or delivery
  • Multi-site and multi-brand Drupal setups
  • Sessions should be grounded in practical experience rather than product positioning.
Format

Accepted formats include:

  • 20 minute talks (MAX)
  • Case study presentations (focus on the business side)
  • Architecture or strategy sessions
Selection criteria

Proposals will be evaluated on:

  • Relevance to enterprise Drupal use cases
  • Clarity of problem and solution
  • Evidence of real-world implementation
  • Transferable lessons for other enterprise organizations
  • Technical or organizational depth
Submit a proposal

Submissions are open via Pretalx.

Looking forward to seeing you there!
 

Gábor Hojtsy: Stability & Innovation: Web Acceleration with Drupal Core and Drupal CMS - session recording

Drupal Planet -

Stability & Innovation: Web Acceleration with Drupal Core and Drupal CMS - session recording

I recently stood before a room of fellow builders at Drupal Developer Days Athens 2026 and asked a question: "How many of you use Drupal distributions?" Lots of hands shot up across the room. But when I followed up with, "And how many of you are actually happy with them?" the room went quiet, only a couple hands remained in the air. Distributions were our solution for long to make starting easier with Drupal, so this was sad.

Gábor Hojtsy Thu, 05/07/2026 - 13:35

Drupal AI Initiative: The skills that matter for leaders, builders and doers in the age of AI

Drupal Planet -

Article by: Aidan Foster, Foster Interactive

The three human skills that turn AI into a multiplier.

Creativity, strategic thinking, and articulation are the three skills that decide whether AI makes you better or just faster.

  • Strategic thinking comes from experience. There's no shortcut.
  • Creativity can be learned, but it's more like going to the gym than reading a book. You build it through reps.
  • Articulation lets you craft quality prompts and specs for AI, and it's the most trainable of the three. But it only matters when there's something worth articulating. The value lives in the other two.
What Everyone Is Getting Wrong

The AI discourse has one dominant message: automate faster, cut the grunt work, reduce headcount, ship more.

Most leaders are responding by getting better at execution. Better prompts. Faster workflows. More output per person.

Execution still matters. It's just not where the constraint is anymore. The leaders who pull ahead in the next three years won't be the ones who automated the most; they'll be the ones who understood where the real constraint moved.

The Bottleneck Moved

Think back to five years ago. A new landing page meant a brief, a copywriter, a designer, a developer, a round of revisions, and three weeks of calendar time. A campaign asset required coordinating four people across two time zones for something that might run for six days before you killed it.

That friction was real. Teams were sized around it. Agencies were built on it. Budgets accounted for it. That friction is gone.

A capable team can now produce a landing page in hours. Drafts, variants, and structured content at a pace that would have required six people two years ago. The execution ceiling collapsed.

The bottleneck didn't disappear. It moved upstream, to the quality of thinking that goes in before AI touches anything.

Strategic clarity. Creative direction. Precise articulation of what you actually want.

That's where the value lives now. That's where most teams are dangerously underprepared.

Strategic Thinking

A CMO walks into a strategy review and knows something is wrong. They've seen this pattern fail before, in a different market with a different product. They remember exactly how it ended.

That's not intuition in the mystical sense. It's pattern recognition built through immersion. You watch your confident calls go wrong, you figure out why, you adjust.

Strategic thinking requires experiencing consequences. You have to have been wrong, and had something depend on you being right.

Researchers studying scientists at the frontier of human knowledge found the same principle. The best of them use cultivated judgment to ask better questions, to know where to go next. AI needs to be pointed. It executes brilliantly within a defined frame. The frame has to come from somewhere.

Our sense for aesthetics, meaning and embodiment give us a vital advantage over our technological creations.

Why Human Intuition Is Still Science's Greatest Tool In The Age Of AI - Noema Magazine, 2026

Creativity

Most people believe creativity is an innate trait. Either you have it or you don't. That's wrong.


86% more ideas after 3 months of training. The untrained control group barely changed.

Creativity is a muscle. It responds to reps, to practice, to deliberate exposure to new inputs. A controlled study at Radboud University found that students who went through structured creativity training nearly doubled their ideation output in under a year. The untrained group stayed completely flat. (PLOS ONE, 2020)

You cannot read your way to it. You have to do the reps.

Research across Nobel laureates and major creative contributors identified two distinct types of creativity with two distinct peak ages. Conceptual innovators - the ones who execute one brilliant overarching idea - tend to peak young. Experimental innovators - the ones who synthesize across years of accumulated experience and observation - peak in their 50s. (Galenson and Weinberg, via Big Think)

The kind of creativity that matters most in marketing is the experimental kind. The kind that gets better the more you've seen.

The senior strategist who's been in the game 15 years isn't past their creative peak. The research says they may not have hit it yet.

Articulation

Articulation gets your thinking and creativity out of your head and into a form AI can use.

A VP with sharp strategic instincts and genuine creative range can still get generic output from AI if they can't extract what's in their head and structure it precisely.

Imprecise input produces generic output. Always.

The model doesn't know what your brand sounds like. It doesn't know who your buyers are, what language they use, or what keeps them up at night. It doesn't know what you've learned over three years about what actually converts.

All of that has to come from you, structured in a way AI can use. Articulation responds to deliberate practice faster than the other two. Most people never treat it as something worth developing. (Canadian Marketing Association AI Playbook, 2025)

Experience Is the Advantage If You Use It Correctly

The skills AI cannot replicate are the ones that take years to build. But knowing that doesn't help unless you act on it. Three things worth doing now:

Audit your process assumptions, not your expertise. The judgment you've built is the asset. The habits formed around the old production bottleneck are what need to change.

Treat articulation as a skill to develop deliberately. Document what you know about your buyers, your brand, your market. Structure it. That structured knowledge is what separates useful AI output from generic noise.

Do the creative reps. Consistent exposure to new inputs and new problems. New disciplines.

Give yourself and your team time to be creative. Whiteboard ideas as a group. Collect interesting work and express what specifically about it grabbed your attention.

Skip the reps and your creative edge fades.

Leaders who invest in all three first will pull ahead. The advantage compounds.

Where does your team sit?

Most teams I talk to are strong on execution. The upstream work - the strategic clarity, the creative direction, the structured articulation of what makes them different - is where the gap is.

That gap is also where the opportunity is.

Drop a comment. I'd like to hear how others are thinking through this.

Sources: Noema Magazine (2026), Radboud University / PLOS ONE (2020), Galenson and Weinberg / De Economist (via Big Think), Canadian Marketing Association AI Playbook (2025)
 

Dries Buytaert: AI-generated Rector rules for Drupal

Drupal Planet -

Keeping up with major Drupal Core releases takes real effort. Each release deprecates APIs and introduces new coding patterns, forcing module developers to update their code.

That is how most software evolves: old patterns are gradually replaced by better ones.

Tools like Drupal Rector help automate parts of that work, but still rely on hand-written rules. Historically, that hasn't scaled well. Writing Rector rules is often more tedious than difficult: reading change records, understanding edge cases, finding real-world usage patterns, and testing rules.

So I asked a different question: what if we didn't have to write Rector rules at all?

If AI can generate Rector rules automatically, Drupal Core can keep evolving without every API change turning into manual migration work.

That idea led me to extend Drupal Digests, the tool I built to follow key Drupal developments. In addition to generating summaries, it now also analyzes Drupal Core commits and generates Rector rules automatically.

When a Drupal Core commit deprecates an API or introduces a new pattern, the tool reads the related issue, analyzes the discussion around it, reviews the code changes, and generates a corresponding Rector rule.

The system has only been running for a few weeks, yet it has already generated over 175 Rector rules, with new rules continuously added as the pipeline processes more Drupal Core issues.

AI-generated code is far from perfect. Some rules will have bugs, and others will miss edge cases. But that is exactly why I wanted to publish them now: the more people test them on real projects, the faster they will improve.

Special thanks to Björn Brala, co-maintainer of Drupal Rector, who discovered I was working on this and quickly jumped in to help test and validate some of the generated rules. That kind of feedback is incredibly valuable.

You can try them as follows:

git clone https://github.com/dbuytaert/drupal-digests.git composer require --dev rector/rector vendor/bin/rector process web/modules/custom \ --config drupal-digests/rector/all.php --dry-run Example

Take Drupal's modernization of the $entity->original property, which exposed the unchanged copy of an entity. Drupal 11.2 deprecated the property in favor of explicit $entity->getOriginal() and $entity->setOriginal() methods. The old property will be removed in Drupal 12 so various module maintainers have to update their code.

Drupal Digests generated a Rector rule that rewrites read access to getOriginal() and write assignment to setOriginal().

Before:

$entity->original->field->value; $entity->original = $unchanged;

After:

$entity->getOriginal()->field->value; $entity->setOriginal($unchanged);

AI-generated upgrade rules will not eliminate all upgrade work anytime soon. But even partial automation can reduce a surprising amount of repetitive work while helping Drupal evolve faster.

Synthetic Personas Have Never Been More Real

Phase II Technology -

Synthetic Personas Have Never Been More Real kdavis Wed, 05/06/2026 - 14:14 Topic Artificial Intelligence Summary Ever wonder why your customer personas feel outdated the moment they're finished? Static personas can't keep up with audiences that shift constantly, so the fix is pairing two AI-powered approaches: synthetic personas that act as interactive thought partners for early ideation, and research-bounded tools that surface trustworthy insights from your existing research. The takeaway? Empathy and evidence aren't opponents, they're partners, and the smartest teams use both. Promo Image Synthetic Personas Whitepaper gif.jpg

The Drop Times: DrevOps Releases Vortex 1.38.0 “Prism” with Testing, Mail Controls, and Security Hardening

Drupal Planet -

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.

DDEV Blog: From a Single Chat to a Live Sponsorship Feed: DDEV's Sponsorship Data Story

Drupal Planet -

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!

Community Working Group posts: Before the Incident Report: How We Are Collaborative

Drupal Planet -

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?

Consulting our Code of Conduct

I serve on the Community Working Group (CWG), specifically on the Community Health Team. A lot of people don’t know there are two teams inside the CWG, so here’s the short version:

  • 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.

File attachments:  pillars-of-drupal.png

Talking Drupal: Talking Drupal #551 - Drupal Recording Initiative

Drupal Planet -

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.

For show notes visit: https://www.talkingDrupal.com/551

Topics
  • Module of the Week TFA
  • Why Recording Matters
  • Early Events and Growing Pains
  • Post Production and Gear Limits
  • Recording DrupalCon vs Camps
  • Costs and Value Breakdown
  • Pittsburgh Turning Point
  • Hubs and Mentoring New Recordists
  • Beyond Drupal Events
  • Hands Off Goals
  • Impact and Adoption
  • Workflow Pain Points
  • Content First Recording
  • Maintainers and Volunteers
  • Volunteer Stress Factors
  • Funding and Platforms
  • Drupal TV Origins
  • Roadmap and Growth
  • Wrap Up and Contacts
Resources

MOTW - Two-factor Authentication (TFA) - https://www.drupal.org/project/tfa TFA Email OTP Plugin - https://www.drupal.org/project/tfa_email_otp National Institute for Standards and Technology's Special Publication 800-63B section 3.1.1.2 "Password Verifiers" - https://pages.nist.gov/800-63-4/sp800-63b.html#passwordver Drupal Recording Initiative - https://www.drupal.org/project/dri DrupalCon Chicago Playlist - https://www.youtube.com/playlist?list=PLpeDXSh4nHjQpb2cHv9rgQv4lvq1-ZkC3

Guests

Kevin Thull - Drupal Recording Initiative kthull

Guest Host

Bernardo Martinez - bernardm28

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan

Avi Schwab - froboy.org froboy

Module of the Week

with Avi Schwab- froboy.org froboy

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

Drupal Planet -

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

The Drop Times: Who Will Inherit the Code?

Drupal Planet -

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. 
 

DISCOVER DRUPALORGANIZATION NEWSEVENTTRAINING


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.

Alka Elizabeth
Sub-editor
The Drop Times

Sitback Solutions: Helping NSW households and businesses unlock energy savings

Drupal Planet -

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

Drupal AI Initiative: Drupal AI Learners Club Is Here. And You're Invited.

Drupal Planet -

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.
 

Pages

Subscribe to www.hazelbecker.com aggregator