UI Suite Monthly #36 — Beta 5, Recipes, and AI That Builds Your Pages

Our 36th monthly UI Suite meeting (June 18, 2026) was a packed one. Despite the early-summer heat in Paris and a few people already on holiday, the team walked through a string of releases, demoed a brand-new starter kit, and gave a first live look at AI agents building Drupal pages on their own. Here's everything that happened.

Overall Summary

This month was about momentum. Display Builder Beta 5 is right around the corner — and remarkably, it ships with less code than Beta 4 while adding new features. Jean introduced Recipes, a ready-to-use website starter kit that gives you a real, content-filled Drupal site out of the box. And Rajab demonstrated the new Display Builder AI module, where an orchestrator agent coordinates sub-agents to generate landing pages from a single prompt.

Alongside the headline acts, there were solid maintenance updates across the suite (UI Patterns 2.0.16, UI Styles, UI Skins, UI Suite DSFR), a proposal to revamp the component platform's UX, and a frank discussion about the real-world cost of AI-driven page building.

A few quick highlights before we dive in:

• Display Builder Beta 5 is imminent, with a clean upgrade path from Beta 4.
• Recipes is stable for Bootstrap and DSFR, with Daisy UI and possibly USWDS on the way.
• AI agents can now build pages from prompts, images, or Figma links — and the cost is starting to look genuinely marketable.
• The next monthly meeting is set for July 23 (we're skipping August, as always).

Key Topics Discussed

Display Builder Beta 5

Beta 5 is "around the corner" — just two small tickets away. The big surprise is that it contains less code than Beta 4 while still adding review labels, translatable instance paths, and configuration imports in the logs.

Pierre ran a live Beta 4 → Beta 5 upgrade to show what to expect: after a quick drush updb, you keep everything you published, but non-published revisions and drafts are lost. So the rule of thumb is simple — publish what you want to keep before upgrading.

With Beta 5, the architecture is now complete. A few things worth knowing about how it works under the hood:

• The display is a revisionable and translatable content entity acting as a single source of truth.
• It uses HTMX to trigger server-side state changes, with island plugins returning small, light renderable fragments.
• Unlike Drupal core's locality-of-behavior approach, Display Builder swaps multiple fragments in a single HTTP response with event-driven updates — which is exactly what makes it so fast and so light.

This is an innovation the team genuinely hopes to bring back into Drupal core.

Recipes — a real starter kit, not just a profile

Jean introduced Recipes, built on Drupal Recipes. The goal: a Display-Builder-ready website you can spin up in seconds, complete with real, editable content — not a fake demo, and not something painful to set up.

The standout idea is zero footprint. You start Drupal with the recipe, and then you can forget about it and go back to your regular Drupal configuration workflow. No lock-in.

In the demo, Jean showed the Bootstrap version handling things that are usually a headache:

• Resolving all dependencies (UI Patterns, UI Icons, the theme) automatically.
• A fast install from a minimal profile — the recipe step took about 26 seconds.
• Containers and container-fluid living happily together, with full-width and contained sections side by side.
• Page layouts with different headers per page — no Drupal blocks involved, just clean page layouts.

Recipes is stable for Bootstrap and the French Design System (DSFR) today. Daisy UI is next in line (it needs more opinionated meta-components like a hero), and USWDS may follow, with Stephen Mgra interested in starting it. Jean offered to help anyone who wants to set up a recipe for another theme.

AI meets Display Builder

This was the show-stopper. Rajab walked us through the new Display Builder AI module, now published on drupal.org. The architecture centers on a "super agent" orchestrator that coordinates specialized sub-agents:

• A UI Patterns agent and component agent that gather and manage the available components.
• A UI Icons agent.
• UI Skins and UI Styles awareness, so the AI can manage colors and styling without ever touching files or the database directly.

The live demo built a landing page — hero, three feature cards, and a call-to-action — from a single prompt, with the orchestrator calling the template builder and component agents to do the work. The same approach can take an uploaded image or a Figma link and turn it into a design. Rajab also showed a terminal-driven flow using Claude Code and the Playwright MCP, where the agent opened a browser and built the page entirely on its own.

The kicker, as Pierre noted: because design tokens and style utilities stay inside the system, the agent stays smart and the whole thing stays maintainable. These are exactly the two APIs the team wants to push into Drupal core.

Maintenance updates across the suite

• UI Patterns 2.06 shipped just before the meeting, including a decorator feature for better Canvas compatibility. The roadmap: drop Drupal 10 support in early December and ship a simpler "next" release that reorganizes features without breaking anything — which will also unlock new capabilities for Display Builder.
• UI Styles & UI Skins are in maintenance mode: moving config storage into third-party settings and preparing for Drupal 12. Bootstrap support is waiting on new core APIs.
• DSFR is stable, with recent upstream updates from Jean, and a 2.x version planned for the future — always with a commitment not to break existing implementations.

Drupal core, GitLab, and a UX revamp

The team missed the 11.4 target but is now aiming for 11.5 and Drupal 11, with roughly six months to push the needed APIs. The new GitLab issue tracker is rolling out gradually; early feedback from Sharique was positive ("better than what we have already").

Pierre also proposed a UX revamp of the component platform this summer, taking inspiration from ECA's accessible, on-demand lazy-loading model — mainly to speed up the source selector. Interested contributors are invited to PM Pierre to organize workshops.

What does AI page building actually cost?

A practical question from shibin das led to some useful numbers from Rajab:

• About $30 covered three weeks of his testing and development.
• A single page typically needs ~4 iterations to come out right.
• The Sonnet model was recommended as the most cost-effective choice for this content-creation use case (not the most imaginative model — that's not what's needed here).
• Projected out, a 1,000-page migration lands around $400 — a figure the team considers genuinely marketable to clients.

Rajab also noted that, with a GitLab token, the AI can manage the full issue lifecycle (create, fork, merge requests), provided it follows the Drupal community's AI policy on reviews and checkpoints.

Key Action Points

Plenty came out of this session. The headline item: next month, the team wants to bring the Display Builder AI work to a more concrete, presentable state. Here's who's doing what:

• The group — Revamp the component platform UX (workshops this summer) and implement lazy loading for the source selector. Also: submit improvement ideas for Recipes by opening issues in the project queue.
• Jean — Publish the Daisy UI project code to the public repository.
• Pierre — Test the current Recipes implementation, and present Distributor and HTMX at Beijian camp, plus the API work at Drupal Rotterdam.
• Stephen Mgra — Start the USWDS project, based on Bootstrap.
• Marin & Andreas — Run the page builder test match at Drupal Rotterdam.

Want to get involved? The deeper we get into beta, the easier it is to jump in — and as Pierre put it, this is where the fun stuff is happening.

Upcoming Deadlines / Releases

See you on July 23. In the meantime, install the modules, try out Recipes, and play with the new AI module — and let us know what you think in the issue queues.