Milestone 0.2.0: Experience Builder-rendered nodes

Open on Drupal.org →

Created on 19 June 2024, 3 months ago

Updated 18 September 2024, 10 days ago

Purpose:

Save content created using the Experience Builder

Not included:

Backwards compatibility, migration

Requirements:
Building on top of 🌱 Milestone 0.1.0: Experience Builder Demo Active , this would add:

14. Configuration management — Not ALL config management, only config entities that are necessary to support the other requirements.
⚠️ What config entities that would be is unclear at this point. See #3444424-7: [META] Configuration management: define needed config entity types → questioning the sole config entity that exists at the time of writing (2024-06-19), 🌱 [later phase] [META] 7. Content type templates — aka "default layouts" — affects the tree+props data model Active signaling we couldn't work on XB's third party settings for EntityViewDisplay, and config entities needed for design system/styleguide/design token are all still undefined.
6. Save (draft) content
9. Revisionable pages
7.1. Tokens — Only support for structured data in local context, e.g. current node. Not design tokens (details TBD)
⚠️ Not to be confused with Drupal's existing Token API, which cannot do what this needs.

Expected result:

Everything that 🌱 Milestone 0.1.0: Experience Builder Demo Active allows you to do, can now be saved (and viewed).
It's possible to look at the current live revision, past revisions and future revisions.
On top of what 🌱 Milestone 0.1.0: Experience Builder Demo Active allows you to do, you'll now be able to also assign not only static values, but also use "tokens" to dynamically place a value that exists in the host entity (i.e. local context)'s structured data (one of the fields of the article content type) to an SDC prop.
NOT: 7. Content type templates — see 🌱 [later phase] [META] 7. Content type templates — aka "default layouts" — affects the tree+props data model Active for that.

So, in a nutshell: a working new field type that is used by the demo UI of 🌱 Milestone 0.1.0: Experience Builder Demo Active .

🌱 Plan

Status

Active

Component

Page builder

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.

Needs issue summary update
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Issue created by @wim leers
Status changed to Postponed 3 months ago4:27pm 19 June 2024
Comment 3 months ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
This builds on top of 🌱 Milestone 0.1.0: Experience Builder Demo Active , so marking this . That doesn't mean we're not working on this already: work is already happening and being coordinated in 🌱 [META] Early phase back-end work coordination Active — with some of the issues in there being necessary for 🌱 Milestone 0.1.0: Experience Builder Demo Active .

(If there wasn't a hard DrupalCon Barcelona deadline, 🌱 Milestone 0.1.0: Experience Builder Demo Active and this milestone/issue would probably be one and the same.)
Comment 3 months ago →
🇫🇮Finland lauriii Finland
Assigned to lauriii
Status changed to Active 10 days ago11:12am 18 September 2024
Comment 10 days ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
🌱 Milestone 0.1.0: Experience Builder Demo Active is nearly done. DrupalCon Barcelona 2024 is in a few days.

Time to get this fleshed out!
Comment 10 days ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Also: do we want to keep using 🌱 [META] Early phase front-end work coordination Active + 🌱 [META] Early phase back-end work coordination Active ?
Comment 5 days ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024