Milestone 0.2.0: Early preview

This builds on top of #3454094: Milestone 0.1.0: Experience Builder Demo, so marking this Postponed. That doesn't mean we're not working on this already: work is already happening and being coordinated in #3450586: [META] Back-end Kanban issue tracker — with some of the issues in there being necessary for #3454094: Milestone 0.1.0: Experience Builder Demo.

(If there wasn't a hard DrupalCon Barcelona deadline, #3454094: Milestone 0.1.0: Experience Builder Demo and this milestone/issue would probably be one and the same.)

#3454094: Milestone 0.1.0: Experience Builder Demo is nearly done. DrupalCon Barcelona 2024 is in a few days.

Time to get this fleshed out!

Also: do we want to keep using #3450592: [META] Front-end Kanban issue tracker + #3450586: [META] Back-end Kanban issue tracker?

Some markup changes to improve clarity/scannability.

Initial issue for product requirement 19. Modify the page template created: #3478537: Introduce an XB `PageTemplate` config entity.

Overhaul of the meta to reflect which of the 10 requirements are actionable, and to what extent. 9 of the 10 cannot begin UI+UX (aka client side) work due to designs not being ready.

Updated the status for 19. Modify the page template (i.e. global sections) and 29. Layout patterns (i.e. sections).

#3479982: HTTP API to read+write PageTemplate and Pattern config entities landed!

For 2.1. Content editing of meta fields, a new issue was identified as blocking the 0.2 milestone: #3463991: [RESEARCH] How to identify all meta fields for an arbitrary content entity?.

Finished adding 🟢, 🟡 or 🔴 to every ⮑.

Also clarified why the two stretch goals are pretty firmly out of reach already at this stage.

Updated the 19. Modify the page template (i.e. global sections) requirement. It's working, but there's 3 currently known rough edges:

1. #3497747: Global regions containing only "dynamically missing blocks" (due to emptiness or access) cause malformed pages
2. #3497744: If an autosave entry exists before enabling global regions for a theme, theme regions cannot be seen
3. #3497648: Focus mode for global regions, blocked on #3489106: Show page information in top bar

4th rough edge for #32.

@effulgentsia Did you intentionally delete

• Finish Media Library integration for 1. Adding components (built for 0.1):
  ⮑ #3471978: Make the Media Library dialog look like the admin theme without materially affecting anything outside of the dialog (possibly use an iframe for CSS isolation)

in #37?

Updated the 29. Layout patterns (i.e. sections) requirement.

(And also updated 19. Modify the page template's issue list — lots of activity over there this week.)

One more for 19. Modify the page template, that was created a few hours ago!

Add anchors to facilitate deeplinking.

I wonder if we should turn each of the top-level requirements, such as "Place Blocks as Components", into their own Plan issue, so that we can make those the parent of the above issues and similar individual issues for the other top-level requirements.

-1 — too much overhead and issue queue noise. I'd rather have a single issue with >200 updates than having to monitor half a dozen issues, each of which causes actual MR issues to be somewhat obscured.

Updated 5. Place blocks as components — included everything @effulgentsia listed in #44 and expanded.

#3486203: Integrate saving sections with the backend: (de)normalize Pattern config entities using the client-side data model just landed, which means 29. Layout patterns is AFAICT the first requirement to be completely done! 🥳

Thanks, @tedbow! Updated that 6. Save (draft) section section to follow the same structure as the others (BE/FE/E2E/Polish). Some were miscategorized. Some icons were off. But I kept the same set of issues.

Thanks, that really helped!

And now adding + removing issues to that same section.

Added:

• #3488368: Also convert metadata (page data) fields in ClientDataToEntityConverter
• #3489994: Create an endpoint to publish all auto-saved entities
• #3489743: Create AutoSave service and HTTP API to retrieve all entities with pending changes
• #3487484: Save page data form values in application state with support for undo/redo

Removed (given my understanding of Lauri's original product requirements, but I was not in every meeting while working at limited capacity during paternity leave, so correct me if I'm wrong 🙏):

• #3467870: Support `{type: array, …}` prop shapes — we should absolutely do this and it is a stable blocker, but this was never intended to be solved as part of this
• #3462235: [PP-1] Add typed value-objects for the component tree structure — definitely never intended to be solved as part of this

Moved #3495598: [PP-1] Don't store page template model data in auto-save for an entity to Polish for "Save (draft) content", and added a placeholder for the missing validation error support.

Also marked both "Save (draft) content" and "Modify the page template (i.e. global regions)" as 🟢 — but not yet ✅: I have high confidence we'll be able to wrap those up given the current status + pace + outlook, but they're not yet done.

Fixed formatting and added jumplinks.

Introducing an explicit 🔵 Polish for later phase. to allow identifying which things are known to be needed in the future, but explicitly omitted from the 0.3 scope.

Discussing this with @effulgentsia and @lauriii. To enable @lauriii to specify which polish he considers necessary for meeting the product requirements, I need to:

1. clearly distinguish between must-have (all the "foundations" bits), should-have (the "polish for long-term API stability" aka avoid technical debt) and nice-to-have ("polish for later phase")
2. I should first order the should-have lists by what I perceive to be priority order; this enables @lauriii to either confirm or ask for changes

This update to the issue summary only does the first bit.

#59.2 — pass 1 of N.

#59.2 — pass 2 of N.

#59.2 — pass 3 of 3.

Still outstanding:

1. Reconciling the should-haves for 6. Save (draft) content with those of 5. Place blocks as components — both are impacted by/need changes to the data model. I still need to dig deeper to be able to articulate which falls in which bucket.
2. 23. Component creation via code editor: actual implementation work has only truly begun last week. See the plan at #3499919: [Meta] Plan for in-browser code components, which @balintbrews crafted. Pinged him to ask about must-have/should-have/nice-to-have breakdown, because that meta doesn't currently specify.
3. 2.1. Content editing of meta fields needs clarification from @effulgentsia on whether it's essentially done by virtue of having the Page content entity type plus a working 6. Save (draft) content. (I was on paternity leave and working limited capacity, I was in none of the meetings.)

At this time, there's nothing more I can do. Hopefully updates on the remaining pieces in the next 24 hours.

Ready for @lauriii:

• 19. Modify the page template (i.e. global regions)
• 5. Place blocks as components
• 29. Layout patterns

Increasing the priority for following issues:

You didn't actually — you only added those new issues. Made it so!

I'm surprised #3500390: The pending changes API endpoint should list individual regions for global template changes isn't on here (for 6. Save (draft) content).

But AFAICT #3501600: Split 1 PageTemplate config entity into N PageRegion config entities is now likely to be the successor to that, but it'd fall under 19. Modify the page template (i.e. global regions). Tentatively adding it to "should-have", but I have a hunch that even though unplanned, @lauriii would now in hindsight mark this as "must-have" — so added it there.

Adding #3491978: Implement saving block settings forms.

Per meeting with @lauriii, @effulgentsia, Prafful and @jessebaker: some must-haves have been shifted to should-haves. Those are marked with a ⭐️.

Lots has happened. Update some status emojis.

All #3499919: [Meta] Plan for in-browser code components must-haves are done! 🤯🥳

Plus, the long-standing #3498419: Assign each Component to a logical "UI library" during normalization finally landed too, which empowers a much nicer UX for landing

All must-haves listed in this meta are done now, so marked each of the 7 requirements as ✅.

It's live: https://www.drupal.org/project/experience_builder/releases/0.2.0-alpha1