Allow developers to customize how components behave in XB

Created on 11 December 2024, 11 days ago

Overview

The goal for Experience Builder is to provide developers an easy way to expose their components to content creators, so that they can build content using the developer created components. Because of this, we are using the existing SDC from Drupal core.

The current schema definitions may not provide sufficient information to build an optimal editorial experience. While we may want to introduce some additional for Experience Builder since not all of these settings make sense for core, we want to make sure that we meet the following principles when we design a solution for this:

  1. Components built for Experience Builder should work with Drupal Core without Experience Builder installed.
  2. Components built for Drupal Core should work with Experience Builder without additional changes.

Known use cases that may fall under this:

  1. Hiding properties from the UI: ✨ How to pass content_attributes to SDC without it being shown in the XB UI Active
  2. Grouping fields in the UI: ✨ Allow component properties to be categorized Active
  3. Per-slot tag/category-based restrictions: 📌 [SPIKE] Comprehensive plan for integrating with SDC Active
  4. Default values for slot: 📌 [SPIKE] Comprehensive plan for integrating with SDC Active

Proposed resolution

User interface changes

✨ Feature request
Status

Active

Version

0.0

Component

Page builder

Created by

🇫🇮Finland lauriii Finland

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

Comments & Activities

  • Issue created by @lauriii
  • 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

    I think this means we'll need to modify the ADR introduced in 📌 Document the current component discovery + SDC criteria, and describe in an ADR Active as well as the product requirements.

    But…

    1. Components built for Drupal Core should work with Experience Builder without additional changes.

    👆 this is pretty much the original product requirement you stated.

    Which implies that if this must be upheld, that is the inevitable consequence?

  • 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
  • 🇫🇮Finland lauriii Finland

    @wim leers Is there a specific change that you think is needed to that ADR? I read it again and to me, it doesn't seem to be in conflict with what's being stated here. We want to keep the experience where SDCs compatible with core could be consumed by XB without requiring changes to the components. This doesn't mean that XB couldn't allow SDC authors to use XB specific settings to enhance how components are displayed in XB, so long as the way that XB provides these settings, allows the SDCs to be still consumed by Drupal Core.

Production build 0.71.5 2024