Milestone 0.2.0: Experience Builder-rendered nodes

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.)

🌱 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!

Also: do we want to keep using 🌱 [META] Early phase front-end work coordination Active + 🌱 [META] Early phase back-end work coordination Active ?

Some markup changes to improve clarity/scannability.

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

Let me know if you want/need anything in SDDS for this next milestone as well as for DrupalCon Singapore.

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 and .

📌 HTTP API to read+write PageTemplate and Pattern config entities Active landed!

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

Finished adding 🟢, 🟡 or 🔴 to every ⮑.

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

Removed the stretch goals from the list. We're not currently working on them so there's no realistic plan of them getting done by early January.

Also descoped (with confirmation from @lauriii) revisions and Workspaces from 0.2.0.

The Purpose and Expected result sections are incomplete. They don't capture the entirety of the remaining items that are in the Requirements section. When I find a bit of time, I'll fill in those sections so that they add clarity as to what the overarching goal of the 0.2.0 milestone is.

Updated the proof-of-concept issue for the component code editor from 📌 [exploratory] StackBlitz PoC Active to ✨ [exploratory] PoC of Preact+Tailwind components editable via CodeMirror or Monaco Active .

I updated the "Content editing of meta fields" section with 0.2.0 scope vs 0.3.0 scope.