Sessions

We'll explore the dynamics of the TYPO3 community and uncover the key factors behind its popularity in Germany, where Drupal has yet to make a similar impact.

Discover what each system can learn from the other. Ingo Schmitt, a seasoned TYPO3 expert (https://my.typo3.org/u/ischmittis), and Peter Majmesku (https://www.drupal.org/u/jepster_), a veteran Drupal specialist, will come together to present the unique approaches and strengths of both systems. Don't miss this opportunity to gain a deeper understanding of these powerful CMS platforms and their communities.

We we'll talk about the following topics:

• Community: Explore how each community fosters connections and collaboration. Examine the methods for sharing knowledge and code within each community.
• Configuration management: Compare how both systems handle configuration settings. Strategies for versioning configurations and deploying them across systems.
• User permissions: Analyze how permissions are managed and assigned in both systems.
• Theming and frontend: Approaches to setting up the frontend technology stack
• Extension development: Investigate how backend development is approached for implementing custom functionality through modules or extensions.
• Caching: Delve into the caching strategies employed by both systems to maintain website performance
• Deployment and application management: How are updates communicated and managed? The processes for deploying updates and managing applications effectively.

Drupal Core still provides a very rudimentary API for sending transactional emails. Most projects, including Drupal CMS rely on several contrib modules in order to provide an acceptable UX for both site builders and site users.
 

Work is underway to modernize the APIs around transactional email in Drupal Core. The first step was to introduce the Symfony Mailer component as a core dependency. Since then, people have been busy hashing out the transport layer by introducing the necessary components into the dependency injection container. The work on the transport layer is done and may ship with Drupal 11.3. It is now time to focus on how transactional mails should be built and rendered in future versions of Drupal.
 

This session will be a very brief overview of the state of core and contrib mail APIs, followed by a (hopefully) long Q&A where the audience is encouraged to bring in their PoV regarding the future of transactional email. The results of this session will ideally lead to a clear and widely accepted plan for how Drupal core transactional email will be modernized in future releases.

Who pays for AI? What's the point? And who decides?

With Drupal CMS 1.0 released in January and Drupal CMS 2.0 about to land, we're now well into development and refinement of the next features.
So it's a great opportunity to discuss what we have planned next on the roadmap, provide updates on how we are tracking 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
• Contribution pathways for the next features and getting involved

How deeply any given topic will be discussed very much depends on the attendees, but topics could be:

• Forward revisions
• Revisioning Translations
• Computed Fields
• Query Access
• Validation Constraints

The complex path to get to an amazing, full-fledged, all-encompassing automated test suite often stands in the way of having any form of CI at all.

Using Gitlab CI and the infrastructure around it it is possible to get you up and running with something as your automated testing story really quickly and without much hassle or prior knowledge. That's why this session really is for everyone! Will it be everything you ever wanted? Nope, but it will be better than nothing and you can always go from there to improve.

Having a country-specific Drupal information page is a key element in increasing the visibility of Drupal on a nationwide level. For a long time, however, the German website had fallen behind – outdated content and a lack of attention left it trailing other official Drupal sites across Europe.

At the start of 2025, the site was finally relaunched — but a new look alone doesn’t tell the full story. In this session, I’ll take you behind the scenes to explore the collaborative community efforts that made this relaunch possible. You'll learn how volunteers came together, what challenges we faced, and how we’re continuing to build momentum.

Beyond the relaunch, I’ll also share insights into ongoing community-driven initiatives in Germany aimed at strengthening Drupal’s presence and visibility — online and beyond.

Imagine a button that renames your uploaded image file based on what’s actually visible in the image. Or a way to trigger an ECA action using the context of the field you just filled out.

Meet the Field Widget Actions module, a new submodule introduced in AI Core 1.2.0. It’s a simple yet flexible framework that lets you attach custom functionality to any field in your Drupal site. Using a clean UI, you can link multiple actions to a single field widget. Each action shows up as a button next to the form element, right where editors need it.

In this session, I’ll show how the module works, walk through real-world examples, and explain how you can create and attach your own custom plugins to bring useful tools closer to your content editors.

Implementing designs in Drupal has often been a challenge due to outdated workflows, leading to inefficiencies and inconsistent results. With tools like Single-Directory Components, Storybook, Vite, and the new Display Builder, developers now have the power to streamline their workflow and deliver faster, higher-quality themes.

This session will introduce a modern, component-based approach to theming that bridges the gap between design and development. By sharing best practices and practical techniques, I will help developers to improve their frontend stack, enhance maintainability and boost efficiency.

Create better Drupal themes with less effort!

This will be an updated version of the session I gave at Drupal Dev Days this year in Leuven.

By now we all know how to implement the basic needs for accessibility: use semantic HTML, have alt-texts for images, add styles for focus states, test with keyboard, etc. That might be enough for a small website.

Bigger sites have more complicated components like: sliders; info cards that turn 180 degrees; navigation elements with more content; and lightboxes. We will have a look at some of those elements for the website of the Jewish Museum Berlin.

At the end of last year, we had an external accessibility expert check the site. He had a lot to say about those components and made a few suggestions to improve the accessibility. In this session, we will have a detailed look at the problems he found and the steps we took to improve the components.

I will add some smaller problems in surprising places, and some problems that Drupal or screenreaders add to the mix. Like that one incredibly annoying “feature” in CKEditor.