Support for Experience Builder

Created on 7 January 2025, 4 months ago

Goals

There's no detailed plan at the moment. The repository for this issue holds some code; when and how this will find its way to the main module is unknown.

Status

A tree of XB components (as edited in the XB UI) can produce... some kind of (JSON) output.

See details and installation instructions in modules/custom_elements_xb/README.md.

Next steps

  • test more complicated Single Directory Components (only simple ones have been seen to work so far)
  • support for blocks
  • talk to front end people and see how the output should change, to be useful
📌 Task
Status

Active

Version

3.0

Component

Code

Created by

🇳🇱Netherlands roderik Amsterdam,NL / Budapest,HU

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @roderik
  • 🇳🇱Netherlands roderik Amsterdam,NL / Budapest,HU
  • 🇳🇱Netherlands roderik Amsterdam,NL / Budapest,HU
  • Merge request !116Draft: First version, renders basic SDCs. → (Open) created by fago
  • 🇦🇹Austria fago Vienna

    I had the opportunity to dive into this a bit at DrupalDevDays. XB already does a great job rendering into components, so we should be able to re-use that and build upon it perfectly fine. There is the "hydated-component-tree" which we could use, see ComponentTreeHydrated. Or, we simply use the generated render-array consisting of nested components and blocks, and process into the tree of custom elements. (Similar to what we do with layout builder). Code-components are rendered as astro-islands, so could be output as astro-island component also.

    I clarified with balint brews that we do not need to handle auto-saving storage or something, preview is going to work differently anyway. Then we should be able to do all this as simple CE-field formatter.

    Created 📌 First-class experience builder support Active for the overall plan.

Production build 0.71.5 2024