UI Suite Monthly #35 Highlights Translation Support, Core APIs, and AI-Assisted Display Building

Translation workflows, Drupal core proposals, and AI-assisted display generation were among the major topics discussed during UI Suite Monthly #35, which featured technical demonstrations and roadmap updates tied to upcoming Drupal 11.4 and Drupal 12 development cycles.

The session covered progress across the UI Suite ecosystem, including updates to Display Builder, UI Patterns, schema migration work, Drupal core integration, and experimental AI-assisted display workflows. Organisers also issued an urgent call for community review of several Drupal core proposals ahead of the 15 May freeze for Drupal 11.4 and Drupal 12.

A significant portion of the discussion focused on Display Builder, which contributors described as reaching the midpoint of its beta phase. Foundational work involving Drupal display integration, storage systems, business logic, and user interface functionality has now been completed, while current development priorities include translation handling, accessibility improvements, interface refinement, and bug fixing.

Christian Wiedemann demonstrated new support for symmetric and asymmetric translations integrated with Drupal’s Translation API. The implementation allows administrators to determine whether structural changes should remain synchronised across languages while preserving language-specific text customisation. According to the demonstration, configuration translation remains synchronised by design, while Display Builder reconstructs multilingual content trees during publishing workflows through integration-specific plugins.

The session also outlined plans to migrate UI Patterns toward Drupal core’s unified schema namespace. Migration tooling already allows projects using older UI Patterns implementations to transition through the UI Patterns Legacy module and associated Drush commands, while additional work continues around compatibility between Drupal Canvas and UI Patterns through changes to the SDC plugin manager.

Another major demonstration focused on new functionality introduced in Drupal 11.3 allowing SDC components to function directly as Form API elements. Florent Torregrosa showed how form controls such as text fields, checkboxes, and radio buttons can now operate as reusable design-system components within Drupal forms. Contributors also demonstrated how UI Patterns Field Widgets could extend the same approach into Drupal entity form displays.

The session additionally highlighted two proposed Drupal core initiatives targeting Drupal 11.4 and Drupal 12: the Design Token API and the Style API. The Design Token API aims to establish a platform-agnostic framework for managing design tokens within Drupal themes, while the Style API proposes a structured plugin-based system for applying and tracking CSS styles through Drupal configuration workflows.

Community reviewers were encouraged to help move the proposals toward RTBC status before the upcoming freeze deadline. Organisers noted that additional review activity over the coming days could determine whether the proposals advance within the current Drupal release cycle.

The meeting concluded with early discussion of AI-assisted display-building workflows. Contributors outlined two experimental approaches under evaluation: one using Playwright-based browser automation and another interacting directly with Display Builder APIs through a limited set of public methods capable of generating complete displays programmatically. A live demonstration of the Playwright-based workflow is planned for next month’s session.

The updates reflect broader momentum across Drupal’s frontend ecosystem around design systems, component-driven architecture, multilingual content workflows, and AI-assisted tooling as preparations continue for Drupal 11.4 and Drupal 12.