UI Suite Pushes Core APIs and Display Builder Toward RC1 Ahead of Drupal Freeze

Recent discussions within the UI Suite initiative indicate a coordinated effort to advance design system APIs into Drupal core while stabilising Display Builder ahead of its first release candidate. The work is framed by the approaching Drupal code freeze in mid-May 2026, which limits the window for proposals such as Style API, Design Tokens, and Icon API to be reviewed and accepted.

The meeting summary, published by contributor Michael Fanini, focused on aligning technical readiness with Drupal’s release timeline. Style API is currently under review following earlier feedback cycles, while work on Design Token variable access remains incomplete. A planned migration of Single Directory Components schema references to Drupal 11.3 is expected to simplify component definitions and improve interoperability across UI Pattern systems.

These efforts reflect a broader objective of defining structured YAML formats and plugin systems that allow design systems to integrate directly with Drupal APIs. If accepted into core, these proposals would formalise how tokens, styles, and icons are defined and rendered across Drupal projects, reducing reliance on fragmented implementations.

UI Patterns 2 has reached a stable release and is reporting approximately 100 new site adoptions per week. However, migration from UI Patterns 1 remains uneven. While upgrade tools and documentation are available, a significant portion of existing users has not transitioned. The summary does not identify specific technical barriers, indicating a gap between availability and adoption.

Compatibility challenges remain unresolved. The Canvas module conflicts with UI Patterns at the component plugin manager level, and both teams have identified this as a priority area. No implementation approach or resolution timeline is detailed in the report.

Display Builder continues to follow a rapid release cycle, with Beta 2 through Beta 4 completed and Beta 5 scheduled for April 2026. Recent updates include support for Layout Builder migrations, initialisation of layouts from Block Layout configurations, and improved logging during display creation. The roadmap toward RC1 prioritises API stability, expanded test coverage, and the introduction of symmetric translation.

The planned translation system will be implemented in stages, including a transition to SQL-based storage and integration with Drupal’s revision log interface. These changes will introduce breaking modifications to draft-level instance entities in upcoming beta releases, while published content and configuration are expected to remain unaffected.

Adoption metrics show stronger traction for UI Icons, which has gained approximately 2,000 new installs since the previous meeting. Around 60% of tracked Drupal CMS 2 installations include the module as a dependency. The initiative aims to move the Icon API into Drupal core for version 11.4, aligning with the W3C Design Token Community Group format to support automated workflows from design tools such as Figma through to Drupal rendering.

The meeting also introduced early-stage discussions on AI-assisted workflows. Contributor Rajab Natshah outlined how structured UI schemas could enable AI agents to interpret and manipulate Drupal design systems. A proposal to include an agent.md context file in repositories was discussed as a preliminary step. No implementation details or working prototypes are included in the summary.

Display Builder’s relationship with the Paragraphs module remains unresolved. Current approaches include using Paragraphs for content entry while delegating layout control to Display Builder, or replacing Paragraphs once locking features are complete. A third option, embedding Paragraphs within Display Builder layouts, has been identified but not yet implemented due to architectural complexity.

The session concluded with operational next steps, including a dedicated AI discussion scheduled for April 2026 and preparation of a starter template for agent-based workflows. A follow-up meeting on 7 May 2026 is expected to include demonstrations and further technical validation.

The source summary lacks detailed implementation examples for several proposals, particularly in AI integration and Design Token handling. The full meeting notes are available at the original post here.