City Website Design: What the 100 Biggest US Cities Put One Click Away
How a Drupal chatbot can answer product questions and guide customers
Help customers find suitable products, compare specifications, and locate manuals with a Drupal chatbot fed by your content. Here’s what to build, connect, and test. Webhooks and event-driven Drupal integrations
Price, stock, and lead-time changes need to reach connected systems quickly. Learn how to choose and operate a Drupal webhooks module with reliable delivery, secure requests, and a clear recovery path. Tickets for Mountain Camp 2027 Are on Sale
Tickets for Mountain Camp 2027 are now available. Our 6th edition, 10 years since the first Mountain Camp, takes place from 2 to 4 March 2027 at the Davos Congress Centre in Switzerland, and we would love to see you there.
At a Glance- Dates: 2 to 4 March 2027
- Place: Davos Congress Centre, Davos, Switzerland
- Tickets: early bird CHF 90, regular CHF 120
These are the first confirmed speakers. More featured speakers will be announced soon.
Keynote: Lena Fuhrimann
A Practical Guide to Fast and Private LLMs
Most AI tools send your text to someone else's servers. Lena's keynote shows how to run language models yourself, at home or at work, so your data stays with you and your costs stay clear.
She will cover the choices that actually matter: which model size fits the job, how to make it run faster and more efficiently, what hardware you need, and which software to run it on. Everything she shares comes from real setups.
Fireside Chat: Dries Buytaert
Dries Buytaert, founder and project lead of Drupal and Academy Member of the European Open Source Academy (EOSA), joins us in Davos for a fireside chat.
Talking Drupal #578 - Rosetta
Today we are talking about Better traceability, better debugging, and Rosetta with guest Jürgen Haas. We'll also cover Maestro as our module of the week.
For show notes visit: https://www.talkingDrupal.com/578
How Drupal's Context Control Center Feeds Brand Voice and Site Rules to AI Agents
Drupal to WordPress migration: when it makes sense and how to do it
Migrar de Drupal a WordPress: cuándo tiene sentido y cómo hacerlo
Salsa at DrupalSouth Community Day 2026
How to Personalize the Post-Login Experience in Drupal Based on User Roles
A user has logged in to your Drupal website. What happens next? Does their journey follow the same path as everyone else’s, or can your website tailor the experience to their roles and tasks?
Upgrading tmgmt_deepl from 2.2.x to 2.4.x with the DeepL setup wizard
The new tmgmt_deepl Upgrade Wizard assists with the upgrade from version 2.2.x to 2.4.x: key migration, new default values, custom code validation, and configuration validation. Here's how the upgrade works, step by step.
Drupal and the Missing Photographer
Consumer Node Preview 1.0.0-rc1; preview for Fully Decoupled Drupal sites

Press Preview on a Fully Decoupled Drupal site, and Consumer Node Preview 1.0.0-rc1 shows the unsaved page in the frontend your readers will see: the title you just changed and the text you just rewrote, rendered by the site that will publish them.
Drupal's own Preview renders the node in Drupal's theme, not your frontend, so editors save a draft to check it. Next.js draft mode smooths that workaround, but still needs a saved revision. Consumer Node Preview works on what's still in the edit form, for the person writing it, before anything is saved.
Anything that reads JSON:API can be on the other end. Druxt Node Preview 0.1.0 is the Nuxt one, already running druxtjs.org's previews.
Migration support for Drupal 6 and 7 sites will not be in Drupal 12
The Migrate Drupal module, which is required for migrating Drupal 6 and 7 sites, will be removed from Drupal core in the next major release, Drupal 12. Also removed is the Migrate Drupal UI module, which provides a basic user interface for running a migration. Both of these modules will not be moved to a contributed project, as is often done for removed extensions.
This means that legacy Drupal sites will not be able to migrate directly to Drupal 12 and later. Legacy sites should migrate to Drupal 11 and then upgrade to Drupal 12.
This was decided in [Policy] Migrate Drupal and Migrate Drupal UI after Drupal 7 EOL and also discussed in Future of migrate in core in a post Drupal 7 world.
Decreasing need for Migrate Drupal
The decision to remove the Migrate Drupal module is driven by several factors:
-
A strategic track for Drupal is modernization and we want all Drupal sites to enjoy the benefits of Drupal 11 and beyond.
-
Setting a clear deadline for sites to use Migrate Drupal in core may help some sites schedule the work without delay.
-
The percentage of Drupal sites using Drupal 6 or 7 continues to decline.
-
Sites can migrate to a supported release of Drupal up to 3 years after the end of life for Drupal 7 and 12 years after the end of life for Drupal 6. This is because Drupal 11 will be supported until mid to late 2028.
-
After 2028, it will still be possible to migrate to Drupal 11 in a development environment, then update to Drupal 12 (or beyond) prior to launching a site.
Migrate Drupal will not become a contributed project
Following from the above, Migrate Drupal will not become a contributed project
Does Drupal need cheap and easy hosting? Let's see!
The work that just happens: the DA Insider for October 2026
In Rotterdam, Dries asked the community to talk louder about Drupal. The response so far: 264 pieces of advocacy from nearly 150 people, in at least seven languages, on everything from Reddit threads to a major Italian daily. I spent the past week reviewing all of it, and I'm feeling incredibly optimistic about what this program can unlock.
This month's Insider leads with the full wrap-up: the numbers, the credit matrix we built along the way, and fifteen people whose work shows what the program is for. If you've been waiting to see whether the Advocacy Program is real before joining in, consider this your evidence.
Thanks for reading, and for telling Drupal's story.
Ryan Witcombe, Director, Product Marketing
The Advocacy Program by the numbersAt DrupalCon Rotterdam, Dries asked the community to talk louder about Drupal, and the Drupal Association launched the Advocacy Program to back it. The idea is simple: tell Drupal's story in your own voice, and earn contribution credits through the same system that recognizes code.
One month in, 264 pieces of advocacy have gone through review from nearly 150 contributors: blog posts, videos, conference talks, podcast episodes, Reddit replies, and press coverage, in at least seven languages. Around 2,400 contribution credits are now going out through Drupal.org.
The pattern we hoped for showed up in the data. Social posts made up more than half the volume but under a fifth of the credits, and the biggest scores went to work that travels furthest:
Why our Drupal sites now wait a day for updates
Composer 2.11 can hold back new releases for a cooldown period, counted from when the registry first saw them. LakeDrops now applies a one-day cooldown to its Drupal projects without changing a single composer.json or lock file: one central policy file, merged in memory by a plugin every project already has. Jürgen walks through why the policy couldn't live in composer.json, a Docker image or an environment variable, why drupal/* packages wait too, and why one week was too long. Three LakeDrops additions fill the gaps: lock trust prevents downgrades, a guard stops moves from stable to dev, and a fast lane lets fixes for Drupal Security Team advisories through early. Side stories: a release that was three years old on day one, a spell checker that reordered the rollout, and a composer outdated edge case reported upstream.