Accepted sessions

Learn how volunteers from the Drupal community built a platform that provides instant demos of Drupal site templates and how you can use Drupal Forge to market amazing Drupal services.

Almost a year ago, we launched the IXP Program to solve a challenge every Drupal community member knows: talented newcomers can't get hired without experience, but can't gain experience without someone taking a chance on them. This program embodies Drupal's values of "Better together" and "Prioritize impact."

This session shares real outcomes from putting community values into action: 5 new developers connected with 3 companies, delivering over 1500 contribution credits. IXP participants mastered content management, created custom modules, implemented DevOps practices, and contributed meaningfully to Drupal.org modules.

Rather than theoretical frameworks, you'll learn from both our victories and challenges—the practical reality of building sustainable talent development that works for newcomers, organizations, and the entire Drupal ecosystem.

Choosing the right content management system (CMS) can truly shape the success of your digital experience strategy. In this session, we’ll take a closer look at how Drupal stacks up against other well-known platforms like WordPress, Craft CMS, and Adobe Experience Manager (AEM) in terms of architecture, scalability, and customization. Here’s what we’ll cover: 

1. How each CMS approaches content modeling and flexibility
2. Key performance and scalability factors for large-scale projects
3. Insights on security, community support, and extensibility
4. When Drupal shines and when it might be wise to consider other options 

By the end of this session, attendees will walk away with a solid grasp of the strengths and weaknesses of each CMS, empowering them to make well-informed choices for their upcoming projects.

Have you used CiviCRM and wished it were truly native to Drupal? Or struggled to integrate an external CRM with your favorite CMS?

Join us to explore Drupal CRM, a modern Drupal-first contact relationship management system.

Created to match the site building spirit of Drupal CMS, it’s designed to serve organizations of all sizes, with a special emphasis on those with limited technical or financial resources.
Just as Drupal CMS reimagines content management, Drupal CRM empowers site builders with structured contact data, right inside Drupal.

Avoid costly and complex integration with a proprietary CRM by consolidating data and business logic in a single powerful Drupal-based platform!
 

With so many new features added to CSS in the past couple years, is Sass still needed in your projects? Is it time to remove Sass from your build process? What can native CSS and PostCSS do that can replace Sass functionality and how do you implement PostCSS in a Drupal 11 theme?

In this session, I will discuss an overview of current CSS features that replace functionality in Sass, and bleeding edge features that will replace Sass functionality in the future including:

• CSS custom properties
• Nesting
• New color functions
• if() and @function
• And more!

I will also give an overview of PostCSS, what functionality it can add to your project, and how to set up PostCSS in your Drupal 11 theme.

Lastly, I will discuss when you might not want to replace Sass *just yet* and how you can use Sass AND native CSS together to take advantage of your existing build process.

It’s an exciting time to be a CSS developer and the perfect time to learn more about what CSS can do natively without using Sass.

Join us to hear the latest news on Drupal Canvas from the Product Lead of the initiative.

Drupal Canvas has shipped its 1.0.0 release, revolutionizing how websites are built with Drupal and positioning Drupal to compete in an AI-driven development landscape.

Drupal Canvas enables marketing teams without Drupal experience to easily build their entire website without the need to write code beyond basic HTML, CSS, and templating markup. It enables content creators to create and compose content on any part of the page without relying on developers. And it provides the foundation for AI-powered site building that will define the next era of web development.

As AI reshapes how websites are created, Drupal Canvas ensures Drupal remains competitive, combining visual simplicity with the power and flexibility Drupal is known for.

In this session you'll:

• Understand what shipped in Drupal Canvas 1.0.0 and how it delivers on the original vision
• Gain practical knowledge on using Canvas and learn its key features and capabilities
• Identify how Canvas positions Drupal for AI-powered site building
• Explore the roadmap and upcoming opportunities for involvement
   

At Evolving Web, we built a new visualization tool for GRID (Global Repository of Income Dynamics), an application that serves 300+ economic statistics through a fully dynamic react interface powered by shadcn and Highcharts. This talk breaks down the architecture behind it: how a config-driven system combined with a small hierarchy of variable classes lets the app generate its UI, controls, chart logic, and constraints automatically, without hardcoding a single dropdown or visualization rule.

I’ll show how we structured the app so new datasets, view modes, and visual behaviors can be added by editing configuration instead of touching components. You’ll see how polymorphism handles different data types, how the factory pattern keeps everything consistent, and how this approach eliminates repetitive code while making future data growth trivial.

With git worktree it's easy to have multiple versions of your Drupal project checked out into different directories.

And DDEV has a special feature to let you have the name of the project be determined by the directory it's in.

So you can have the same git repository checked out 5 places and all 5 of them (with different features or bugs or whatever) running at the same time.

This is surprisingly easy and pretty mature stuff. Take a moment with it and we'll have fun!

Components break when the content model underneath is rigid. This featured session reveals how content strategy decisions made months before Drupal implementation—field structure, required versus optional, granularity, relationships—directly determine whether your component system enables speed or becomes a bottleneck.

Drawing on platforms serving 50+ Iowa state agencies, 80+ Georgia government websites, and Georgia Public Broadcasting's multi-brand system, you'll see the complete content modeling process: from workshops with authors using paper prototypes, through data dictionary work (cardinality, character limits, display variations), to embedding simplified specs into Figma files so designers can stress-test with real content constraints. You'll discover common pitfalls that hurt component flexibility and learn field structures that enable the same components to serve wildly different organizational needs—without custom code for every use case.

The session concludes with an audience-driven demo: suggest an agency and page type, and we'll build it together in real time—proving the model's flexibility on the spot.

This session is for content strategists, developers, site builders, and UX designers working with component-based systems at scale; anyone tired of hearing "but we're different" from their stakeholders is welcome.

You'll leave knowing:
 - Where to put guardrails versus where to allow flexibility
 - How to validate content models before AND during building
 - Field-level decisions that make or break component reusability

Structure doesn't restrict flexibility—it enables flexibility at scale. But you need to know where the guardrails belong, because components are only as flexible as the content model underneath them.
 

Hat tip to Talking Drupal for clueing me in to the Custom Field module right at the time I was exploring rolling my own custom entities to solve a longstanding client issue: feeds imports containing paragraph fields.

The problem: 

Updating a 4000ish node data set with a few dozen fields—only four of which were paragraphs—via xml feeds import would take around 27 hours to complete. Deleting and reimporting from scratch "only" took about an hour, with the obvious disruptions and caveats.

Enter Custom Field:

Nothing slows down a project—or a contribution—like pushing your code only to have GitLabCI reject it. Missed coding standards, preventable errors, and style issues waste review cycles and delay releases. Not anymore.

You’ll learn how to bring those same checks into your local environment so you can catch problems before they hit Drupal.org’s pipelines. By running the exact tools GitLabCI uses—ESLint, Stylelint, PHPCS, and PHPStan—you’ll cut down on frustrating back-and-forth, write more consistent code, and keep your contributions moving smoothly.

You don’t need deep expertise: I’ll provide ready-to-use configuration so you can get started right away.

I’ll cover:

• Installing and configuring each linter for Drupal
• Matching GitLabCI behavior locally
• Automating checks for faster feedback
• Catching issues early to speed up reviews and QA
• Extending checks beyond what GitLabCI enforces

Whether you’re submitting your first merge request or keeping client projects clean, these practices will improve your workflow, reduce wasted time, and help the whole Drupal ecosystem move faster.

At the end of this session, attendees will be able to:

1. Set up local code-quality tools (ESLint, Stylelint, PHPCS, PHPStan) in a Drupal project with provided configuration.
2. Run and automate the same checks used on Drupal.org’s GitLabCI to catch errors early and reduce failed builds.
3. Extend these checks to raise internal quality standards and deliver more consistent, maintainable Drupal code.

Single Directory Components have changed the way some Drupal sites are themed. Drupal Canvas (formerly Experience Builder) has the potential to change how some Drupal sites are built. What happens when both are available widely?

In this session, we'll take a look at how to create forward-looking Single Directory Components that will integrate nicely with Drupal Canvas. We'll cover the basics of SDCs (especially their component.yml files) as well as demonstrate SDC usage inside of Drupal Canvas.

Merlin of Chaos created Drupal Views back in 2003 and it remains a Drupal super-power to this day. Ironically, it creates order from chaos. It is the ultimate list maker and report generator with access to nearly everything that is contained in Drupal.  This is an introduction to Views that will benefit site builders, designers, content managers, and developers of all sorts. Learn to leverage the power of Views to make your Drupal site more useful. Content for this session was graciously contributed to by DrupalEasy. 

Drupal CMS launched  to much fanfare... to existing Drupal developers and customers.  Now, Drupal comes with AI agents, visual page builders, one-click Recipes. It's genuinely impressive tech. So why don't students or developers care?

Here's the uncomfortable part: we already fixed the technical problems. Drupal CMS isn't hard to use anymore. The learning curve is way better. We have actual innovation happening.

But new developers still aren't showing up. They're on YouTube, Discord, and Twitch learning JavaScript frameworks or the new hotness language.  The "Drupal is legacy tech" perception hasn't budged.

I'm a Drupal developer who streams game development on Twitch to an audience that mostly doesn't know what Drupal is. I've built unconventional projects like using Drupal as a game backend, and I spend time in gaming and indie dev communities where Drupal isn't even on the radar. I've learned what makes someone outside the Drupal bubble actually get curious about a technology. And what makes them scroll past.

This session is a frank conversation about the gap between having good tech and getting people to notice. We'll talk about:

• Where developers actually discover new frameworks (spoiler: not drupal.org)
• Why technical excellence doesn't equal excitement
• What we can do as individuals, not just "the community"
• Real examples of what's working vs. what we think should work

What you'll get: 3-5 concrete actions you can take this week, not someday. Plus a clearer picture of why the usual "let's market Drupal better" approach keeps missing the mark.

We have a very short window before Drupal CMS becomes "that cool thing that launched that nobody noticed." Let's actually do something about it.

A demo deep dive on CSS variables, and how they can be leveraged to make your components more configurable and reusable. We'll explore inheritance, typing, composability, the JavaScript API, and other scary-sounding but actually not too bad concepts that reduce development effort and increase component utility. Supercharge your components with CSS custom properties!

Ever feel like requirements gathering produces documents nobody reads, leaving developers guessing what stakeholders actually want? Or ship a feature only to hear "that's not what I meant"? 

There's a better approach: collaborative workshops where stakeholders, developers, and testers work through concrete examples together—defining requirements in plain language that become your automated tests. No more translation gaps between what's requested and what's built.

In this session, you'll learn a workshop technique called Example Mapping that transforms vague feature requests into clear, testable requirements. We'll walk through how these examples written in plain language flow directly into automated tests using Behat and Behavior Driven Development (BDD), turning those examples into tests that automatically confirm you built the right thing.

What you'll learn:

• Learning how to facilitate a collaborative requirements workshop with your team
• Using the four-color card system (stories, rules, examples, questions)
• Writing examples in plain language that everyone can understand
• Translating examples into automated test scenarios for Behat
• Integrating this testing approach into your Drupal development workflow
• Real-world examples from Drupal projects

Who should attend:

This session is for developers, project managers, business analysts, and anyone involved in defining or building Drupal features. No prior testing experience required.

I began my career as a developer, where building websites for clients and learning development best practices were my primary responsibilities. As I became a team leader and manager, I quickly learned that my job now had a very different set of objectives, priorities, and keys to success. Instead of solving technical problems with code, the most important parts of my days became addressing more ambiguous "people problems" and coaching my team members toward growth.

This session will cover how I shifted from a front-end development role into management, and the lessons I've learned that can help other developers thinking of making a similar move. I'll detail how delegation was my biggest struggle and greatest help, the importance of clear communication and expectations, and how to support my team while building their skills, not just my own. I'll also touch on the differences in feedback loops between development and management problem-solving, along with how to stay technical while spending less time directly working on code.

The Event Platform module is a useful tool for Drupal camp event-organizers to schedule featured speakers, customized sessions, and event job listings to the various sponsors. 

What is the best way to begin creating an automated test script for a contributed module? How do you go about making a standardized and enterprise standard test for you to contribute, apply, and share with your own organization? 

There are many steps in the process of making a useful automation test for your contributed module, so you can save time in testing and improve your test driven workflow toward a site feature you consistently work with.  

This session will go over the common practices that are used from: developing a test with targeting the right elements in your script, to refactoring your test script to code-standards, as well as ensuring generic application and test reliance as well. 

Discover how you can improve your existing testing workflow, contribute your own test to the Drupal work space, and use automated testing for your existing modules within your team.

Drupal Canvas introduced Code Components in early 2025, opening a new avenue for Drupal frontend engineering by shipping a zero-setup, in-browser code editor, and out-of-the-box support for React and Tailwind CSS. A lot has happened since then. As the technical lead for Code Components, I've watched the possibilities steadily grow as Drupal Canvas has matured and become stable.

New features have been introduced to support data fetching and Next.js-style image optimization. Experiments are underway to support server-side rendering and third-party imports. Editing Code Components is no longer bound to the browser: A CLI tool makes it possible to work with them in any development environment. This opens up interesting opportunities, such as building decoupled frontends.

This session will discuss different approaches and techniques for working with Code Components in Drupal Canvas, as well as the current state of all features, experiments, and plans for the future.

This session will provide step-by-step guidance on how to edit and add text formats, to customize the behavior of Drupal's formatted text entry fields. You'll learn about the problems they can help you solve, the pitfalls to avoid, and how to troubleshoot problems you might encounter.

We'll also cover some ways that Drupal modules can extend the capabilities to make life easier for your content editors.

Accessibility is often treated like a quest with an ending. We audit, we fix, we ship, and we move on. But in real projects, the story does not stop at launch. Standards evolve, technologies shift, content changes, and new contributors join, sometimes undoing accessibility work without realizing it. Progress can fade quietly if no one is watching.

This session frames accessibility as a never-ending story. Not because the work is impossible, but because it lives inside systems that are constantly changing. Like any long-running narrative, accessibility depends on care, shared responsibility, and the willingness to keep moving forward, even when progress feels slow and familiar challenges resurface.

We’ll explore how accessibility holds up across the full lifecycle of open source projects, from early design and development through ongoing maintenance and content updates. Along the way, we’ll look at what WCAG 2.2 tells us about the barriers users still face, what the move toward WCAG 3 signals about the future of accessibility, and how the European Accessibility Act is reshaping expectations for digital products.

Rather than chasing a perfect ending, this session focuses on building practices that prevent accessibility from quietly sinking back into the Swamps of Sadness after launch. Attendees will leave with practical ways to recognize where accessibility slips, how to keep momentum without burnout, and how to design workflows that allow the story to continue.

Drupal CMS is a great starting point! It gives us a lot of flexibility right out of the box, but you still need to understand how Drupal works and the philosophy behind Drupal CMS.

In this session we'll cover all of the tips and tricks you need to know about building sites specifically with Drupal CMS, including enabling modules, designing with Drupal Canvas (at whatever usability level we have at the time of the Camp), turning on Drupal AI and other cool tools.

This session is for people looking at Drupal CMS as an option.  It is not a deep-dive into the code.

Security and privacy compliance certifications—like SOC 2 (a leading audit standard for security, availability, and confidentiality) and HITRUST (a healthcare-focused security framework) — are becoming requirements for healthcare, finance, and other high-trust industries. Waiting until audit season to start to prepare can be overwhelming.

This session shares engineering-side lessons from Encore Healthcare’s journey to SOC 2 and HITRUST readiness. Instead of a checklist of requirements, we’ll focus on designing systems, processes, and documentation so you’re always ready to provide evidence to an auditor. We’ll walk through how we integrated compliance into our SDLC, infrastructure, access control, logging, and team processes—what worked, what didn’t, and the pitfalls we wish we’d avoided.

You’ll leave with a blueprint for making security compliance part of your natural engineering workflow, not a stressful scramble.

Learning Objectives

By the end of this session, attendees will be able to:

1. Apply engineering practices (SDLC, logging, IaC, access control) that generate audit-ready evidence automatically.
2. Perform internal reviews (onboarding checklists, policy adherence, vendor management) that reduce last-minute compliance gaps.
3. Develop a practical plan for working with consultants, clarifying ambiguous audit requests, and avoiding common pitfalls in SOC 2/HITRUST readiness.

Target Audience

• Engineering leaders and senior developers responsible for compliance-sensitive Drupal applications
• DevOps and infrastructure teams preparing for SOC 2 or HITRUST
• Technical managers balancing product delivery with compliance requirements

Prerequisites

• Familiarity with modern software development practices (version control, CI/CD, IaC)
• Experience operating Drupal or other SaaS/web applications in production
• No prior compliance experience required — this is about engineering preparation, not legal fine print

Accessibility issues don’t have to surprise you — or your users. Continuous AI for Accessibility is an approach to building accessible products by embedding tools, AI, and best practices directly into the development process. In this session, we’ll share how we built our open-source prototype and show features like automated accessibility scans and alerts with GitHub Actions, AI-driven fixes from Copilot, and collaborative pull requests that keep humans in the loop. The result: developers tackle issues seamlessly, accessibility best practices become second nature, and teams are ready to build inclusive products from day one.

Curious about what AI can do in Drupal—but not sure where to start? This beginner-friendly session will introduce you to DrupalAI using a series of short, live demos powered by amazee.ai. You’ll see how to use the amazee Provider Framework and key AI modules to streamline content creation, enhance UX, and even automate tedious site tasks, all without writing a line of code.

We’ll break down what makes a good AI prompt for different Drupal use cases, show how to generate content and categorize it intelligently, and walk through launching your own ready-to-play-with DrupalAI site using amazee’s Advanced User Demo. We’ll also cover how makers, trainers, and maintainers can get unlimited AI credits to power their development efforts.

Bring your laptop if you want to follow along—we’ll get hands-on and leave plenty of room for questions, play, and ideas.

Matthew is a Drupal AI trainer who has open-sourced materials for other trainers. He is deeply involved with the Drupal AI Strategic Initiative. 

How do you learn how CI/CD pipelines work when your workplace systems feel too complex or risky to experiment with? When I pivoted from creating Drupal tutorials into the DevOps and QA space, I needed a safe, low-stakes environment to understand how automated workflows really function. So I built a small personal playground: a Hugo-powered blog, stored in a GitHub repository and published through GitHub Pages. From there, I began adding the QA tools I was used to using at work to see how they could run automatically in my personal deployment pipeline. That hands-on exploration helped me understand more complex DevOps workflows and gave me ownership of quality checks for my own site.

In this session, we’ll place CI/CD pipelines within the broader QA landscape. I’ll share an overview of the types of quality checks people rely on, including content linting, accessibility checks, link validation, code style tools, and how different roles use them to check their own work and review others’ code. Then we’ll walk through how to transition from an in-editor check to a local command-line tool, to an automated step inside a CI/CD workflow.

I’ll show you how I built my first CI/CD pipeline and how I iteratively added simple QA checks that now run automatically on every commit. We’ll examine the GitHub Action that powers my pipeline, and I’ll also share small, parallel examples of how the same workflow would appear in GitLab CI/CD and Bitbucket Pipelines.

Attendees will leave with:

• A clear, beginner-friendly mental model of CI/CD
• Practical QA tools that they can run manually, locally, or in automation
• A personal deployment workflow that they can recreate immediately
• Confidence to continue exploring DevOps through small, safe, meaningful steps

Git by yourself is easy: commit, push, done. But the moment a team joins the party, suddenly there are branches, pull requests, merge conflicts, and a complex workflow (that may or may not be documented). 

In this beginner-friendly session, we’ll demystify how teams actually use Git. You’ll learn common branching strategies, follow an example workflow from task to deployment, and walk away ready to collaborate with confidence.

Building a site template and not sure where to begin? In this session, we’ll share lessons learned from developing our own recipe-based site templates. You’ll hear what worked, what didn’t, and how you can avoid common pitfalls.

We’ll explore the Drupal Recipes ecosystem, starting with basic usage and moving into advanced strategies for creating scalable, reusable recipes that can be assembled to meet the needs of different site templates. 

You’ll learn how to:

• Get a high-level overview of using recipes to build site templates
• Organize recipes so they remain flexible and extendable
• Empower site administrators to pick and choose the recipes that fit their needs
• Use tools to automate and test recipe building for scalable, reliable site template delivery
• Handle dependencies cleanly to avoid brittle stacks
• Apply real-world examples to your own projects

Through real-world examples and a live demo of our recipe stack, you’ll leave with practical knowledge and the confidence to structure recipes that meet your organization’s needs today while remaining adaptable for the future.

Drupal 10.3 quietly introduced a powerful new tool for handling complex access control: the Access Policy API. And if you missed it, you’re not alone.

Roles have always been Drupal’s primary tool for granting permissions. But as projects grow more complex, teams often end up battling role explosion — creating more and more narrowly-defined roles just to capture specific business rules. And when roles aren’t enough, access logic gets scattered across hooks, services, and conditionals.

The Access Policy API gives developers a flexible alternative: a clean, centralized way to grant permissions based on real-world conditions — without overloading  or multiplying roles, or scattering access logic throughout a codebase.

In this session, you’ll learn:

• What changed in Drupal core with the introduction of the Access Policy API
• The anatomy of an access policy — how policies are structured, how they work, and how to write your own
• How to decide when to use roles, policies, or both
• How access policies can save time for site administrators by reducing role clutter and simplifying permission management
• What documentation and community resources exist for understanding the API 

If you’ve ever struggled to model complex access rules cleanly in Drupal, this talk will give you new tools — and a new way to think about permissions.

Drupal sites rarely stay simple for long. New content types, fields, roles, and menus are added over the years, often by different teams. When it is time for a redesign, a migration, or a new feature, one of the most complex parts is answering basic questions like “what is actually on this site,” “what is still in use,” and “where is this configured.”

This session will examine common discovery challenges and demonstrate how the Audit Export module can provide a clear, repeatable view of a Drupal site. We will focus on how Audit Export helps you prepare for redesigns and migrations, understand inherited projects, and keep ongoing work grounded in the actual structure of the site.

You will see how to run the built-in reports from the admin UI to review content types, fields, roles, menus, taxonomy vocabularies, and views. From there, we will examine scheduling those audits to run regularly, exporting results to CSV for your team, and utilizing Drush commands to integrate audits into technical discovery, deployment, and maintenance workflows. Along the way, we will briefly note that Audit Export is also available as a plugin for WordPress, allowing the same approach to be used across mixed Drupal and WordPress portfolios.

To conclude, we will explore how the Audit Export Tool submodule exposes audits through Drupal’s Tool API, enabling other systems to interact with them in a structured manner. This opens the door to automation and deeper analysis, including integration with modern tools like ChatGPT and Claude when you are ready to explore AI-assisted workflows.

You will leave with a clear understanding of:

• How to use the default Audit Export reports to understand site structure quickly
• How to add custom reports for site-specific entities and business rules
• How to schedule and automate audits with cron and Drush
• How the Audit Export Tool submodule and Tool API prepare your site for integration with external tools

No prior experience with automation or AI tools is required. Basic familiarity with Drupal administration or development is recommended.