PNW Drupal Summit Speakers Take on Live Chat, Accessibility and HTMX

Speakers preparing for the Pacific Northwest Drupal Summit have outlined plans to demonstrate two-way communication between Drupal and Matrix, share accessible web components across publishing platforms and simplify development workflows. Scheduled for 17–18 October 2026 at the British Columbia Institute of Technology (BCIT) Downtown Campus in Vancouver, the regional conference will bring together Drupal developers, designers, site builders and technology professionals. Several presenters have shared insights with The DropTimes ahead of their sessions, explaining the technical approaches and practical questions they intend to examine.

The 2026 summit carries the theme “Make websites that make a difference,” with sessions covering accessibility, artificial intelligence, frontend and backend development, DevOps, content strategy and community collaboration. The speaker contributions offer a closer look at work already underway, including Western Washington University's cross-platform design system and an evolving Matrix integration for the Drupal Groups Initiative. Other presentations will address changes to Drupal's AJAX architecture and ways to catch coding errors before they reach continuous integration pipelines.

Making Accessible Design Systems Work Across Platforms

Maintaining a consistent user experience across hundreds of websites becomes more complicated when organisations depend on different content management systems. Max Bronsema, Director of Web Communication Technologies at Western Washington University, and Carly Gerard, the university's Web Accessibility Engineer, are listed among the presenters alongside David Engebretson. Their session will explore this challenge during “One Design System, Many Platforms: Scaling Accessible Web Components Across Drupal, WordPress, and Beyond.” Their session is scheduled for Saturday, 17 October, from 09:30 to 10:15 PDT in Room 381.

The university has developed a design system using reusable web components that can operate across Drupal, WordPress and custom applications. Drupal is the primary development environment, while the university distributes the components through a content delivery network for other systems to consume. This arrangement allows the university's web team to manage components centrally while supporting different publishing platforms and website requirements.

Max explained the architecture in comments to The DropTimes:

The presentation will examine how the team approached design system governance, accessibility requirements, testing and deployment. The team uses Cypress for automated accessibility and regression testing, while Azure Front Door provides the CDN distribution layer. According to the session description, the team will discuss versioning and rollout strategies without presenting its CDN configuration as an advanced implementation.

Maintaining the components also involves repeated decisions about how much flexibility to provide individual websites and users. Max and Carly will discuss their exploration of light and dark themes, font selection and alternative menu presentations. These options must be evaluated against usability, accessibility and the need for a consistent design system.

Max emphasised that automated testing is only one part of maintaining accessible interfaces. His advice to attendees is to continue gathering feedback, automate testing wherever practical and conduct manual testing frequently. The presentation will also cover accessibility regressions identified through testing and the adjustments made during component development.

The event has a personal connection for Max, who previously spoke at the regional summit during the early years of Git adoption. He also helped recruit sponsors for the previous year's conference and said he was looking forward to returning as a presenter alongside a colleague.

Connecting Drupal Groups With Matrix Conversations

Communication between content management systems and chat applications frequently stops after a notification is sent. John Locke, president and founder of Freelock Computing, is developing a different approach through the Drupal Groups Initiative's Matrix integration effort. His presentation, “Building the Chat Layer for Drupal Groups (and Beyond),” will take place on Saturday, 17 October, from 09:30 to 10:15 PDT in Room 472.

The project explores how Drupal content and conversations on Matrix, an open communication protocol, can remain connected in both directions. John plans to demonstrate a Drupal node appearing as a message in a Matrix room, followed by a reply in Matrix being reflected as a threaded comment on the Drupal website. The objective is to connect published content and ongoing discussion rather than maintain two separate conversations.

The integration also raises questions about identity and permissions. John's planned demonstration includes connecting Matrix accounts with Drupal users, attributing replies to linked Drupal identities and managing access to Matrix rooms. Application-server configuration and entity mapping will be discussed as mechanisms for relating Drupal groups, nodes and comments to Matrix spaces, rooms, messages and threads without requiring additional fields on individual Drupal entity types.

Some of the underlying capabilities are already being developed. A Matrix.org update published on 4 September 2026 described bidirectional messaging support in the Drupal Matrix API module and recipes using ECA to send published articles to Matrix rooms and return threaded replies as Drupal comments. More extensive identity mapping, entity relationships and application-server management were identified as areas for further development.

John told The DropTimes that the Vancouver presentation will be highly interactive, with attendees participating in a live demonstration to assess how the integration performs under load.

Attendees who want to participate directly are encouraged to create a Matrix account before the session. The demonstration will allow participants to exchange messages between a Matrix room and Drupal comment pages while contributing feedback about the integration's behaviour.

The technical challenges extend beyond moving messages between systems. Matrix identities are effectively immutable, its threading model differs from Drupal's comment structure, and some messages may exist only within Matrix. John also intends to discuss whether older conversations remain discoverable, how to represent different relationships between nodes and rooms, and how to prevent automated notifications from overwhelming useful discussions.

The work is being developed with the Drupal Groups Initiative in mind, but John considers the underlying integration pattern potentially useful beyond the initiative and Drupal itself. The session will use his team's internal Matrix environment as a case study, including decisions that remain unresolved. Audience feedback is expected to inform further development.

Understanding HTMX and Drupal's Changing AJAX Architecture

Drupal's move towards server-rendered interactivity will be another technical subject at the summit. Andrew Morton, a Drupal developer, mentor and community organiser, will present “HTMX: Get this, and put it there” on Sunday, 18 October, from 09:00 to 09:45 PDT in Room 381. The intermediate-level session is intended for developers who are unfamiliar with HTMX or have not yet used it within Drupal.

HTMX allows HTML elements to initiate server requests and update selected parts of a page through attributes rather than extensive custom JavaScript. Instead of returning JSON that frontend code must interpret and render, applications can return HTML fragments for insertion into the existing page. This approach can make use of Drupal's server-side rendering, theme templates and caching capabilities.

That transition is gradual rather than complete. HTMX became a dependency of Drupal core in version 11.2, while Drupal 11.3 introduced fuller integration through APIs for HTML attributes, response headers and dynamic form interactions. Drupal's existing AJAX functionality remains relevant as core features and contributed projects adopt the newer approach.

The transition also has implications for future Drupal versions. Drupal 12.0.0-beta1 upgrades HTMX from version 2.0 to 4.0, introducing compatibility considerations for developers using custom HTMX functionality. The release remains a beta intended for testing, not production deployment.

A Drupal.org technical article published on 17 December 2025 reported reductions of up to 71% in loaded JavaScript for certain browser-server interactions, including HTML streaming with BigPipe. The figure is specific to the documented implementation and should not be interpreted as a guaranteed reduction across all Drupal websites.

Andrew's session will cover the underlying HTMX concepts, practical examples, development tips and the implementation work taking place in Drupal core. He also plans to discuss opportunities for contributed modules. Andrew attended his first Drupal conference at the Pacific Northwest summit in Portland in 2011 and has since participated in the community as a presenter and organiser.

Running Drupal Code Quality Checks Before Deployment

Repeated failures in continuous integration pipelines can delay development when preventable coding-standard or static-analysis issues are discovered only after changes are pushed. Bob McDonald, Drupal Practice Lead at Kalamuna, will demonstrate an approach to identifying these problems locally. His session, “Pre-Flight Checklist: Local Code Quality for Drupal Developers,” is scheduled for Sunday, 18 October, from 10:00 to 10:45 PDT in Room 472.

Bob developed ddev-drupal-code-quality, an add-on for the DDEV local development environment. It provides configurations and commands for tools including PHPCS, PHPStan, ESLint, Stylelint, Prettier, CSpell and Composer validation. The add-on is designed to reduce the configuration work required to run Drupal-oriented quality checks before code reaches a GitLab CI pipeline.

The presentation will follow an example Drupal project through installing the add-on, running checks, interpreting the results and correcting violations. Bob will demonstrate automated formatting corrections, PHPStan baselines for managing existing analysis findings and integrations that make diagnostic messages available within an editor. The session will also distinguish the add-on's use in full Drupal website projects from ddev-drupal-contrib, which targets contributed module and theme development.

Bob's comments about the tool were previously provided to The DropTimes in connection with his DrupalGovCon presentation and have been reused for this session. Explaining the configuration barrier he wanted to address, he said, 

The beginner-level session is intended to help developers bring routine checks into their local workflow without requiring previous experience with the individual tools. Participants will see how automated fixes and editor feedback can reduce avoidable pipeline failures while allowing existing codebase issues to be addressed incrementally.

Community Activities and the Wider Programme

The Pacific Northwest Drupal Summit will also feature sessions on AI, business strategy, search, security, content strategy and neurodiversity. The published programme groups sessions loosely into AI Strategy, Accessibility and Design, and Case Studies and Coding tracks. Saturday's keynote, “AI for All Minds,” will be presented by Josh Penzell and will examine cognitive diversity through audience participation and AI-assisted analysis.

Community activities form another part of the two-day schedule. Saturday includes an unconference beginning at 13:30 PDT and a Community Groups Fair at 16:00 PDT, giving participants opportunities to exchange ideas and learn about Drupal initiatives, regional meetups and other open-source projects. Sunday will include lightning talks beginning at 13:00 PDT, followed by the conference's closing session.

The programme brings together established technical practices and approaches still under development. The speaker contributions highlight recurring challenges for Drupal teams, including managing interfaces across platforms, connecting content with community discussion, adapting to changing frontend APIs and making quality checks part of everyday development.

The summit programme remains subject to change. Further information about the conference, complete session schedule, registration and participation opportunities is available on the official Pacific Northwest Drupal Summit website.