Perhaps the most revealing thing about DrupalCon Rotterdam is that its programme does not tell one tidy story. Drupal is preparing to discuss its transformation into a production-ready Agentic CMS while another session asks, quite directly, why developers still do not choose Drupal. Canvas has become central to Drupal CMS, yet Rotterdam will also put it against Display Builder in a real-world project. Those collisions matter because Drupal’s next phase depends less on any one initiative succeeding than on whether these different bets can reinforce one another without carrying old friction forward.

Connecting Drupal to models and agents is no longer the difficult part of the AI story. Rotterdam moves quickly into hallucination, reviewer trust, orchestration, governed workflows and human control because production use raises harder questions about what an agent may do once it can act rather than merely answer. Permissions, auditability, validation and human approval are becoming part of the product itself. If the Agentic CMS idea is going to mean more than a collection of AI capabilities, those boundaries have to become as deliberate as the capabilities they constrain.

Adoption tests another part of the same argument. Drupal CMS 2.0, Canvas, Recipes and AI-assisted tooling have changed the product presented to builders, but improved technology does not automatically change how Drupal is perceived beyond its existing community. “Why Developers Don’t Choose Drupal” puts that gap unusually plainly. The useful evidence from Rotterdam will not be another inventory of features, but signs that newcomers can enter the system more easily, that organisations are choosing Drupal CMS rather than only inheriting or upgrading Drupal, and that the new experience removes barriers people outside the community can actually feel.

Digital sovereignty makes the question more demanding because Drupal is also being asked to apply its values inward. A Rotterdam discussion on FAIR asks whether sovereignty, governance and cost problems in Drupal’s own software distribution could be addressed differently, starting from Drupal.org’s role as the ecosystem’s central distribution point. That turns openness from something Drupal offers its users into something its own infrastructure may need to demonstrate. Arguments about control become more credible when the project is willing to examine where dependence, responsibility and operational burden sit inside its own systems.

Discovery may be where all of these threads become visible from outside. A Rotterdam discussion on Drupal’s representation in ChatGPT, Gemini and Claude starts from the recognition that developers and decision-makers increasingly encounter technologies through AI-generated answers as well as conventional search. Drupal therefore has to become easier to understand, evaluate and trust not only for people already inside the ecosystem, but also for the systems mediating their choices. Rotterdam will not settle all of that in four days. What it can reveal is whether Drupal’s current direction is beginning to cohere: a product easier to adopt, agents with clearer limits, infrastructure consistent with its sovereignty claims, and a project that can explain its relevance wherever technology choices now begin.

Follow The DropTimes on LinkedIn, X, Bluesky, and Facebook, or join #thedroptimes on Drupal Slack.

Kazima Abbas wrote and curated this issue of Editor’s Pick.

Since September, advertisers in Europe can buy ads inside ChatGPT, and the Ads Manager asks for two things before it can tell you whether they work: a measurement pixel in the browser and, ideally, conversions sent from your server. On a Drupal site that usually means pasting a snippet into the theme, writing the order_created call by hand in a template, and trying to hide the whole thing behind the cookie banner. Then the order paid by bank transfer or payment reference hours later, confirmed by a webhook, never shows up, because no browser was there to see it.

Even when a browser is there, the pixel loses part of the picture. Ad blockers stop it outright, Safari caps cookies written by scripts at seven days, and iOS removes tracking parameters from links shared in Messages and Mail and from links opened in private browsing. OpenAI's own documentation calls the Conversions API "a more reliable tracking source than the pixel alone".

We have released a module for this on drupal.org: ChatGPT Ads, free software under the GPL, for Drupal 10.3 and 11, covered by Drupal's security advisory policy. It plugs into Drupal Commerce, Webform and the Klaro consent manager through sub-modules, and sends events through both OpenAI's Measurement Pixel and the Conversions API. It is a community module, not affiliated with OpenAI.

What you can measure

• With Drupal Commerce, every product added to the cart, including from an AJAX add-to-cart button, with its SKU, quantity and price.
• The start of checkout, and the order itself when it is paid, not merely placed, so an unpaid bank transfer or an expired payment reference never counts as a sale.
• The order paid later and off-site, reported from the server when the payment webhook arrives, with the same event id as the browser, so OpenAI counts it once.
• With Webform, a contact form, a quote request or a newsletter sign-up as a lead: add the ChatGPT Ads handler to any webform and map the email and phone fields.
• Account registrations, from the browser and the server.
• Anything else, with a single call to Drupal.chatgptAds.measure() from your own script.

The pixel goes only on the pages you choose, using the same visibility conditions blocks use: paths, roles, content types, language.

What it refuses to do

Nothing is requested from OpenAI, and no cookie is set, until the visitor has decided. OpenAI's documentation suggests loading the pixel with consent withheld and granting it later, but the script sets cookies as soon as it loads, so the module does not load it at all until there is an answer.

A visitor who has not answered yet is neither a yes nor a no. Their events wait in memory and go out if they accept, so the landing page is not lost; if they refuse, they are dropped. The Klaro integration reads only decisions the visitor has confirmed, because Klaro reports a service's default from the moment the page loads, which would otherwise be read as a refusal while the banner is still on screen.

The same rule applies on the server. Hashed email, phone, IP address and user agent go to the Conversions API only for a visitor whose consent was recorded at the time of the event. For everyone else the conversion still goes, carrying the click identifier and nothing about the person.

The module never saves an order. Saving inside a Commerce transition can fire that transition twice, which on a live store means duplicate receipts and an error at checkout; the click identifiers are stored on the order when the checkout flow saves it anyway.

Pages stay cached

The pixel and the settings that are the same for everyone are cached with the page. What belongs to one visitor, the events collected for that page and, with advanced matching on, their hashed account data, arrives through a placeholder rendered on every request. A page carrying the pixel stays in Drupal's Dynamic Page Cache, instead of turning every page on the site uncacheable to deliver one visitor's identity.

Where it came from

It was built for one of the e-commerce stores we develop in Portugal, where many orders are paid by Multibanco or MB WAY, Portuguese payment methods whose confirmation often arrives hours after checkout. Bank transfers and payment references behave the same way in any country, and that pattern is why the Conversions API is in the first release rather than a later one: without it, those sales are invisible to the ad platform. The pixel, the Klaro gate and the cart events have been running on that store since mid September.

Your consent manager, your choice

Klaro gets a ready-made sub-module: install it and a ChatGPT Ads service appears in the banner, off by default. Any other consent manager reports the decision through a small JavaScript contract, and the README carries a working recipe for EU Cookie Compliance:

Drupal.chatgptAds.consent(true); // granted, now or on a later page Drupal.chatgptAds.consent(false); // refused or withdrawn

To see what else on your site reaches third parties before the visitor decides, Consent Audit records it from real visits.

Get it composer require drupal/chatgpt_ads

You need a ChatGPT Ads Manager account and the pixel id from its Conversions tab. The Conversions API sub-module stores its key through the Key module, so the secret can live in an environment variable instead of your exported configuration. The project page, the documentation and the issue queue are on drupal.org. Bug reports, questions and merge requests are welcome.

The inaugural DrupalCon Talent Show is happening at DrupalCon Orlando on the evening of Tuesday, March 23, 2027 as part of the community party!

We’re planning about two hours of entertainment and looking for roughly 10 acts to take the stage (5–7 minutes for the act, plus up to 3 minutes for stage setup).

This is DrupalCon. The goal is to learn, network, and have fun. Expect jokes, friendly razzing, questionable decisions, and plenty of laughs. You don’t need to be a professional. You just need to be willing to get up there and attempt to entertain your fellow Drupalers (within our Code of Conduct https://events.drupal.org/code-conduct, of course!)

What are we looking for?

Pretty much anything entertaining:

• Musicians
• Bands
• Stand-up comedy (keep it PG-13 please!)
• Magic
• Singing
• Dancing
• Juggling
• Puppet shows
• Ridiculous feats of skill
• Weird talents you didn’t think anyone wanted to see (we do)

Got something that doesn’t fit on the list? Even better. Solo acts, groups, first-timers, seasoned performers, and wonderfully questionable ideas are all welcome.

Think you’ve got something? Sign up here and show us what you’ve got!

FAQs When is the deadline?

The absolute last deadline to sign up is Friday, February 19th. However, submissions are reviewed on a rolling basis as they come in. Once all ~10 spots are filled, sign-ups will close early. We strongly encourage you to submit as soon as possible.

Is there a prize?

Likely, but this hasn’t yet been determined. Suffice it to say that the primary prize will be bragging rights!.

How will performances be chosen?

Performances will be chosen to ensure a wide variety of performance types, geographical regions, companies, diverse performers, etc. You can increase your chances of being selected by submitting earlier rather than later.

How long should the performances be?

5-7 minutes is ideal

Do I have to bring my instrument? Will there be microphones?

We will provide microphones for your band (up to four). If needed by multiple performers, we may be able to supply basic instruments. Details will be provided ahead of the performance if you are accepted to perform. 

Will there be a bar?

A cash (and credit card) bar will be available.

Moving from Drupal to WordPress is not a downgrade when your requirements shrank. When it is right, when it is a mistake, what the migration involves, and what you honestly lose.

Drupal 11: Migrating From Jadu Into LocalGov Drupal: Part 4

This is the fourth article in a series looking at migrating from Jadu into LocalGov Drupal (LGD) for the Central Bedfordshire site. In the first article we looked at the Jadu API itself and setting things up so that we could make calls to the API and parse the XML data using the migration systems available.

In the second article we looked at reproducing Jadu URLs to create redirects for migrated content, even though the Jadu API doesn't contain any URL information.

In the third article we looked at a more complex example of migration, taking documents and pages from Jadu and creating a guide pages from that data.

Now it is time to move onto what became the most complex part of the Central Bedfordshire migration, which was moving directories data from Jadu to LGD. Directories were used on the Jadu site to store all sorts of information, which included schools, the location of car parks, contact information of homecare providers, and even an a-to-z glossary of recycling. This data served different purposes on the site, but it was all hand created and important to bring across during the migration work.

In this article we will look at the Jadu data we needed to fetch to find directory information, and how that data was injected into the LGD structure available.

First, let's look at how we get directory information out of Jadu.

Jadu Directories API

Directories in Jadu can be fetched using the directories index at the following endpoint.

philipnorton42 Sun, 09/27/2026 - 18:45

The prototype works. Taking it to production quality is more than evenings. Whether it should is a question, not a pitch.

One thing before the rest. I am not pushing this. The series is a question to the world: is this work worth more of my time? We are not in the Federation yet, so more time means money, and money means backers. Any answer is fine with me, including no.

Every framework service that holds state is a bug under fibers. The current fix is to switch concurrency off. There is a third option.

Every Druxt site I have built signs people in by sending them somewhere else to do it: out to Drupal's login page, on to a consent screen, and eventually back. With Druxt Auth 0.5.0 the username and password can now be handled entirely in the frontend instead, either through the authorization code grant or through the password grant.

If you have not used it, Druxt Auth wires Nuxt's auth module to Simple OAuth on the Drupal side. It targets Nuxt 2 today, because @nuxtjs/auth-next does.

The first is the authorization code grant, which now takes credentials directly. Druxt Auth signs the visitor in through Drupal's JSON login route first, so the authorize step finds a session waiting and returns a code without rendering anything:

Continue reading →

AI becomes a different infrastructure problem once organisations need to know where data goes, which models are approved, and how spending is controlled. amazee.ai and Tag1 will bring those questions to DrupalCon Rotterdam through a private gateway and Scolta implementation.

A coroutine nobody owns is a leak. Under one process per request you never see it. Persistent servers take that away.

A workflow can report success and still be wrong, while a thriving community can quietly depend on too few people. These Rotterdam speakers look past the demo to the evidence, architecture, feedback, and ownership that determine whether Drupal work holds up.

Drupal CMS 2.2.0 is out, and this release is all about multilingual. Setting up a site to publish in multiple languages has always been possible in Drupal, but it was not easy. With 2.2, we've tackled the biggest pain points from the installer through to translating your Canvas pages.

Finding your language in the installer

The first thing you'll notice is the language selector in the installer. Instead of scrolling through a long select list, you can now start typing and search for your language.

It's a small change, but makes for a much better first impression.

Recipe config is now translated

Previously, if you installed Drupal CMS in another language, any configuration provided by recipes (such as content types, fields, views, even the dashboard) would still show up in English. 

Recipes can include translatable configuration and that is now translated along with the rest of the site.

The multilingual recipe

Adding a second language to a Drupal site involves a lot of steps: installing the right modules, configuring language detection, enabling translation for each content type and field, and making sure you haven't missed anything along the way. Most people figure this out through trial and error (and a fair amount of searching).

The new multilingual recipe takes care of most of this for you:

• Installs the required modules and applies the basic language settings
• Provides a multilingual setup checklist to guide you through the remaining steps
• Modifies the content translation settings page to make it more intuitive, including a 'Recommended setup' option that enables translation for the entities most commonly translated (node types, Canvas pages, menu links and taxonomy terms).

Translating Canvas pages

Canvas now fully supports translation and we're using Canvas Translate to provide the translation management within the canvas editor. You can translate any component on a page, and use the Canvas preview to see how the translated version will look before you publish it.

Using the bundled Canvas Translate AI module, you can also get AI-generated translations with one click: either for all components, or individually.

New multilingual demo

Drupal core has long shipped with the Umami multilingual demo, which has community contributed, cooked and photographed recipes. Umami will not be included in Drupal 12 anymore and it was in need of a design rethink and retooling with our new easy to use page building capabilities. This resulted in the new Dashi demo, which brings the same multilingual content to a customizable setup with Canvas page and content templates.

Try it out

Try it out by installing Drupal CMS 2.2.0!

1. Install DDEV
2. Run the following commands:

mkdir my-drupal-site && cd my-drupal-site ddev config --project-type=drupal11 --docroot=web ddev composer create-project drupal/cms ddev launchFile attachments:  Screenshot 2026-09-23 at 10.38.37 am.png Screenshot 2026-09-23 at 11.38.36 am.png Screenshot 2026-09-23 at 11.38.22 am.png content-translation.gif

DrupalCon Rotterdam 2026 is almost here. The Drupal Association staff and board are heading to the Netherlands next week, and we'd love to see you there!

Photo Credits: Ryan Witcombe

Here's where you'll find us during DrupalCon Rotterdam 2026:

Drupal.org Engineering Panel

Join the DA engineering team for an open and honest look at the current state and future of Drupal.org (the platform the entire community relies on every day). From nearly 10,000 projects migrated to GitLab, plans to support a brand new Drupal.org marketing site, and initiative support for Drupal CMS + Canvas and the AI Initiative, there's a lot to cover. The session closes with an open Q&A, so bring your questions

Day & Date: Wednesday, September 30, 2026

Time: 11:40 to 12:25 CEST

Location: Goudriaan Room I&II

Marketing Panel

Building on the momentum of the Drupal AI initiative, the Drupal Association is growing coordinated advocacy and marketing efforts in new areas, opening the door for more people to get involved and make a visible contribution.

Join the panel to understand how the initiative is taking shape, why they’re gaining traction, and what makes them different. The panelists will discuss how marketing in Drupal is becoming one of the most accessible and high-impact ways to contribute, where individuals and organizations  alike can raise their profile, earn recognition, and help shape Drupal’s future.

Day & Date: Tuesday, September 29, 2026

Time: 16:40 to 17:25 CEST

Location: Goudriaan Room I&II

Drupal Association Public Board Meeting

The DA Public Board Meeting is open to all DrupalCon attendees and is your opportunity to hear directly from the Drupal Association board. Come with your questions, your feedback, and your ideas. This is your chance to engage with the people shaping the future of the Drupal Association.

Day & Date: Tuesday, September 29, 2026

Time: 14:25 – 15:10 CEST

Location: Rotterdam Room I&II

Drupal Association Partner Lunch

An exclusive afternoon gathering for agency leaders and partners to connect with Dries and DA leadership over a seated lunch. A unique opportunity to share strategies, discuss the Drupal business ecosystem, and build meaningful relationships with peers from around the world.

Tickets are required, register here.

Day & Date: Tuesday, September 29, 2026

Time: 12:00 – 13:30 CEST

Location: Postillion Hotel & Convention Centre WTC Rotterdam

Drupal Business Dinner

Cap off Wednesday evening with the Drupal Business Dinner, an intimate gathering of Drupal agency executives for a seated 3-course dinner, a presentation, and meaningful conversations in a beautiful Rotterdam venue.

Tickets are required, register here.

Day & Date: Wednesday, September 30, 2026

Time: 19:00 – 22:30 CEST

Location: De Harmonie, Rotterdam

Photo credits: Matthew Saunders

Whether you're joining us for a session, an exclusive event, or just stopping by our booth to say hello, the Drupal Association team can't wait to connect with you.

The last few days are left to secure your ticket to DrupalCon Rotterdam 2026, if you already haven’t. See You in Rotterdam!

What changes when Drupal becomes something an enterprise AI agent can act on, rather than the place where every user must work? Pantheon plans to show that model running end to end in Rotterdam.

Digital sovereignty does not begin with replacing software. It begins with knowing which services an organisation depends on, who controls them, and what it would cost to leave.

As we see our goals for Drupal AI innovation under responsible human guidance flourishing at such a remarkable pace, we recognize a growing community need for practical, responsible ways to learn it. We’re excited to announce, as part of our efforts to fill that need, AI Inside Drupal Essentials (AIDE,) developed and presented by DrupalEasy, as the official training program of the Drupal AI Initiative. 

We’ve partnered with Drupal expert developer and highly respected trainer Mike Anello (ultimike) to ensure the program supports our mission to drive responsible AI innovation and build on Drupal’s position as the leading open-source content management system for AI integration. Mike and the team at DrupalEasy have the commitment and experience to create, maintain and present the curriculum with our standard for ethical, powerful, and accessible AI in the open-source world.

AIDE

AIDE is designed to help you move forward quickly and confidently with a solid foundation in how to conscientiously take advantage of Drupal AI benefits. The 2-week, 18-hour curriculum is presented on a timetable designed to integrate well into work schedules; meeting live, online for 3 hours every other day. The first session kicks off on November 9, 2026 and runs through November 20th. Additional sessions will be announced in the coming weeks.

In addition to DrupalEasy’s signature lively, online classes; each class session is recorded and becomes part of the video library that participants have lifetime access to. Other resources included as part of the course is a dedicated Slack channel and more than 100 pages of technical guides and implementation tools. The cost to register is $600.

Learn risk mitigation & human oversight

Mike Anello, who has meticulously developed hundreds of hours of Drupal curriculum and trained Drupal developers for more than 20 years, has created another stellar program that leads you, hands-on, through admin-facing responsible AI techniques that prioritize workflows that keep a human in the loop to review AI-generated suggestions before they are saved to the database. From class to class, you'll move from secure foundations to advanced agentic workflows and high-performance retrieval augmented generation (RAG) search, with intensive hands-on examples you can apply to your own Drupal projects right away.

Course content

The course covers four areas:

• AI Foundations: Establish a baseline for secure LLM integration. Configure the AI Automators and Field Widget Actions modules to see how AI output can be reviewed before it's saved.
• AI Agents: Implement agentic workflows and swarm orchestration agents, and deploy tool-calling capabilities that let AI interact directly with Drupal's Tool API.
• RAG Search: Build retrieval augmented generation systems using vector databases, and learn semantic chunking and representation strategies that maximize search accuracy.
• Local AI & Privacy: Deploy local models via Ollama for maximum privacy and cost-efficiency, and use the AI Metering module for automatic local fallback when commercial API quotas are reached.

Our goal, with AIDE and our other learning resources including webinars, workshops, events and the Drupal AI Demo is to make sure everyone who works with Drupal AI can do it safely and effectively.  

Learn more about AI Inside Drupal Essentials training , or ask about the course or AIDE team pricing.

Some Drupal problems begin with too much rather than too little: too much legacy HTML, hundreds of career choices and brand sites, or code generated faster than teams can understand it. These Rotterdam sessions examine the structures that need to exist before speed becomes useful.

For several DrupalCon Rotterdam sessions, the useful question is not simply whether Drupal teams can automate more. It is where automation should stop, where review should begin, and what people still have to judge for themselves.

DDEV v1.25.4 Is Out

DDEV v1.25.4 landed on September 2 with 142 PRs from the community. The theme is doing less by hand:

• Database seeding — a new project can start from a seed snapshot instead of an import step.
• ddev start --reset-database — throw away a project's database and start clean without ddev delete -O.
• Global Dockerfiles and env files — image and environment customizations applied to every project at once, instead of per-project.
• MySQL 9.7 LTS, plus MODX Revolution and Maho project types.
• Linux packages moved to Cloudsmith at packages.ddev.com (Gemfury keeps working).

Read the full release post for details.

Snapshots, Explained (with Screencast)

The snapshot work in v1.25.4 got its own post: DDEV Snapshots: Checkpoints, Restores, and Seeded Databases. It covers basic snapshot use, checkpointing during a migration, uncompressed snapshots, snapshots embedded in the project, and seeding a new project from a snapshot — with a screencast↗ walking through old and new behavior.

The older DDEV Database Management post has been updated to match.

Hobobiker Rides Again: A Three-Part Live Series on Drupal 6 → Drupal 11 with Claude

The Drupal AI Learners Club↗ — the initiative led by Amber Matz and Angie Byron that meets regularly for show-and-tell on AI tools and workflows — has scheduled a three-part live series with Randy Fay joining Amber and Angie as host, migrating hobobiker.com — a Drupal 6 site with years of content — two different ways.

After Jamie Abrahams migrated a site live and checked the result with evals in One Command, One Migration: AI Best Practices in Action↗, Randy tried the approach on his own very old site. The results made one thing clear: Claude does its best work with a guided plan, a clear view of the source and destination, and success criteria it has to prove it has met. So the series takes hobobiker.com on two journeys — one ending in static HTML, the other in Drupal 11 — and checks both against the same test suite.

These are working sessions, not polished demos. Bring your questions, suggestions, and opinions; the peanut gallery is part of the show.

All three are on the club's Luma calendar↗, and recaps of past sessions are collected in the session list on drupal.org↗.

• October 16, 2026 at 9:30 AM US Pacific / 12:30 PM US Eastern / 18:30 CEST — Part 1: Road Test: Having Claude Write the Tests Before the Trip
  Before any migration starts, we need a way to know whether it worked. Randy works with Claude to explore the Drupal 6 site and design automated tests covering content and design: pages, paths, images, menus, and how things look. The goal is a test suite that doesn't depend on any particular destination, so the same tests can run against a static archive and a Drupal 11 rebuild. Along the way: how to push Claude past "looks good to me" toward a complete verification plan, and how a sandboxed environment like coder.ddev.com smooths out the process.
  RSVP↗

• October 23, 2026 at 9:30 AM US Pacific / 12:30 PM US Eastern / 18:30 CEST — Part 2: The Last Ride: Sending a Drupal Site into Retirement
  Not every old Drupal site needs an upgrade; some just need a dignified retirement. Randy has archived plenty of legacy sites as static HTML, and this time Claude does the work — given a proven strategy (Lullabot's "Sending a Drupal Site into Retirement"), clear success criteria, and the tests from Part 1. Can it turn hobobiker.com into a static site that holds up, in an hour, in a way everyone watching can follow? A practical use case for anyone with an aging site that still has content worth keeping.
  RSVP↗

• October 30, 2026 at 9:30 AM US Pacific / 12:30 PM US Eastern / 17:30 CET — Part 3: The Long Haul: Planning and Running a Drupal 6 to Drupal 11 Migration
  This is the hard one. Drupal 6 to Drupal 11 skips many major versions and hits most of the snags that come with them. Instead of turning Claude loose, we prepare it the way you'd onboard a new team member: first it explores the D6 source database and files, then it learns what the D11 destination offers, then it writes a migration plan before touching any code. Randy follows that plan live, with plenty of input from the peanut gallery, stopping at sensible checkpoints and picking up in later sessions if needed. The finish line is the same test suite from Road Test, now running against a working Drupal 11 site.
  RSVP↗

Pressable Ships an Official DDEV Add-On

Pressable↗ released an official, open-source DDEV add-on for syncing WordPress sites between their hosting and a local DDEV environment.

• What it does — ddev pull pressable and ddev push pressable sync the database and uploads over SSH and WP-CLI, with no API tokens or plugins required. --skip-db and --skip-files let you move one or the other, and Pressable limits pushes to non-production staging sites, with confirmation prompts, as a safeguard.
• Install — ddev add-on get pressable/ddev-pressable
• Links: changelog entry↗ • source on GitHub↗

There's also a French write-up from KingLand looking at how Pressable combines the DDEV add-on with MCP-driven AI for agency WordPress maintenance, including the case for keeping humans on the sensitive operations: Pressable : l'hébergement WordPress dopé par DDEV et l'IA↗ (French).

Community Projects

ddev-branchery: a URL, PHP version, and database per branch — Benjamin Kott's add-on gives each Git branch its own worktree beside the main checkout, with its own web address, PHP runtime, and isolated database, while the main project keeps running. Documentation↗

ddev-tailnet-proxy: DDEV projects on your tailnet — Titouan Mathis built a proxy that discovers running DDEV projects on a remote development server, assigns them stable ports, and serves them under the server's Tailscale hostname — no per-project configuration. Read the note↗

TYPO3 Quickstarter 0.7.0 — The CLI that scaffolds local TYPO3 environments on DDEV added support for legacy TYPO3 9 and 10 on PHP 7.4, so older extensions can be worked on before modernizing, plus a built-in phpMyAdmin that auto-logs in. Release notes↗

Knecht Cloud, hands-on — Matthias Andrasch walks through installing Knecht Cloud on a Hetzner VPS: project setup, AI-driven workflows, a browser terminal, and online previews, in a tool built for DDEV projects on TYPO3, Drupal, and Craft CMS. Read part 1↗

Talks and Tutorials from Around the Web

• DDEV & shopware-cli for Shopware 6 → Benny Poensgen's slides from Shopware Open-Stage on September 17, 2026, on pairing DDEV with shopware-cli. View the deck↗ — see also his Shopware on DDEV post, and his October 21 training session below.
• Mailpit with DDEV for Drupal 11 email testing (Spanish) → Jesús Daza covers DDEV's built-in Mailpit integration and an SMTP-based setup, how to reach the UI, and how to confirm mail is being delivered during development. Read on solucionex.com↗
• A DDEV-based local development workflow → Michael K. Laweh on what DDEV gives a consultant working across Laravel, Yii, and WordPress projects: consistency across projects and teams, fast project setup, and framework-agnostic tooling. Read on klytron.com↗

DDEV Live Training

Sessions are open to everybody.

• October 21, 2026 at 8:00 AM US Mountain / 10:00 AM US Eastern / 16:00 CEST — Shopware with DDEV, with Benny Poensgen
  A look at running Shopware on DDEV, from Benny's earlier post on the blog.
  Add to Google Calendar • Download .ics

• November 11, 2026 at 8:00 AM US Mountain / 10:00 AM US Eastern / 16:00 CET — Advanced Coder.ddev.com Techniques
  Using the coder CLI, local and web-based VS Code, and remote-controlling Claude, including the freeform template.
  Add to Google Calendar • Download .ics

Zoom Join Info:
Link: Join Zoom Meeting
Passcode: 12345

Governance

• The next DDEV advisory group meeting, open to everybody, is November 4, 2026 at 8:00 AM US Mountain / 10:00 AM US Eastern / 16:00 CET. Add to Google Calendar • See the agenda. We love to hear from our community!

Sponsorship Update

We so appreciate all of you supporting the project!

August 2026: ~$10,038/month (83.7% of goal)

September 2026: ~$10,099/month (84.2% of goal)

If DDEV has helped your team, consider sponsoring. → Become a sponsor↗

Contact us to discuss sponsorship options that work for your organization.

Stay in the Loop—Follow Us and Join the Conversation

• Blog↗
• LinkedIn↗
• Mastodon↗
• Bluesky↗
• Discord↗

Compiled and edited with assistance from Claude Code.

Today we are talking about GovHub, Drupal in Government, and Why Governments Love Drupal with guest Jasmyne Epps. We'll also cover Convivial Gov Site Template as our module of the week.

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

Topics

• GovHub Origins and Goals
• Feature Requests and Governance
• Why Government Chooses Drupal
• Team Structure and Release Cadence
• Accessibility and Compliance Strategy
• Hosting Model and Multisite
• Structured Content and Microcontent
• Syndication and Emergency Alerts
• Orchard Design System Explained
• Training and Onboarding Editors
• Gov Talks Conference
• Logo Specs and Releases
• Ticket Prioritization PRICE
• QA Workflow with Tugboat
• Handling Traffic Spikes
• Drupal 11 Performance Talk
• Drupal 11 Upgrade Gotchas
• Getting Users Excited
• Translation Strategy Limits
• Why Government Loves Drupal

Resources

• GovHub
• The Bug Stops Here — The State of Georgia Shifts Left (GovCon 2025 presentation with Jasmyne Epps and James Sansbury)
• Accelerating an ambitious migration and development project (GovHub + Tugboat migration story)
• Logo page
• Public facing knowledge base
• Orchard design system
• (P)Rice
  • (P)olitics - (R)each - (I)mpact - (C)onfidence - (E)ffort
• Luma

Guests

Jasmyne Epps - jasmyneepps.com jasmyneepps

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Amber Matz - tugboatqa.com [amber himes matz](https://www.drupal.org/u/amber himes matz)

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to stand up a polished, accessible government website in Drupal (with components, content types, SEO, and cookie consent all wired up) without writing any code? There's a site template for that.
• Module name/project name:
  • Convivial Gov
• Brief history
  • Created in March 2026 by Morpht, the shop behind the Convivial family — with Ivan Zugec leading the maintainer team.
  • Versions available: 1.3.3, which works with Drupal 11
• Maintainership
  • Actively maintained: release just last week, on September 16th
  • Security coverage
  • Test coverage: functional tests for install and validation, plus a kernel requirements test.
  • Documentation there's a full handbook over at docs.morpht.com, and a live demo at gov.convivial.io
  • Open issues: none?
• Site template features and usage
  • Like the Haven site template we talked about a couple of weeks ago, Convivial Gov gives you a curated stack plus demo content, and in this case hands you a robust, ready-to-customize government site.
  • Because it's built on Drupal CMS, you get all the latest Drupal tooling: Canvas for visual page building, Single Directory Components, and Recipes.
  • The front end is Morpht's Morphos theme, built on Tailwind and DaisyUI, so you get dark mode, multiple colour palettes, and a big library of editor-friendly components out of the box. It's worth mentioning that using the Morphos theme on a production site requires a paid license
  • The provided components are sorted into six buckets: container, content, child, element, background, and behavior. They include fun ones like scroll reveal and a colour palette switching behavior
  • The content model is broad. You get seven content types: Page, Section, Article, Publication, Resource, Topic, and Audience. And, they come with a stack of teaser and card view modes to display them.
  • The whole point is no-code: a site builder can compose sophisticated pages in Canvas without ever touching a template.
  • One thing to watch: the default timezone is Australia/Sydney out of the box
  • It's also worth comparing Convivial Gov to another site template called Local. Both dropped in March 2026, both are Canvas-based Drupal CMS site templates for the public sector, and both lean on ECA for automation — so there's real common ground. The difference is scope and mechanism. Local, from Annertech, is narrowly purpose-built for local councils and community-service directories: it ships a specific service information architecture — Service and Service Landing content types — with ECA wired so section pages stay in sync when service pages get published or updated, taking its cues from the gov.uk design system. Convivial Gov goes the other way — it's design-system-led and general-purpose, a broad component library and content model meant for any government, agency, or marketing site rather than one particular workflow.