[META] Content templates

hooroomoo → credited phenaproxima → .

hooroomoo → credited tedbow → .

hooroomoo → credited wim leers → .

transferring credits from ✨ Content templates, the boss battle: create a UI for editing templates Active

I am not sure what the difference between the backend items in the map: HTTP endpoint: dynamic props sources and Handle dynamic props is...

I wonder if its the same thing but we just didn't realize when we created this map together. I see only 4 backend tickets got created instead of 5 so maybe it is a duplicate? But I'm not certain.

hooroomoo → credited balintbrews → .

This how issue is about enabling the UI. There has already been a lot of work to make the content template on the back-end. Although there are backend issues they are in support of the UI

Wanted to make a clarification here based on call between myself, @balintbrews, @hooroomoo and fmazeikis.

Current ContentTemplates require at least 1 dynamic prop. This makes sense but this requirement would force use to do issues in certain order and require larger issues. Since all of this work is on 1.x which does not have a release we deemed to ok if in the first few issues Content Templates don't actually require dynamic props and don't have a way to set them.

The requirement will be removed in 📌 Refactor ApiLayoutController into 2 sub-class to support Content Templates Active which is the first major back-end issue. It will be added back near the end in 📌 Require content templates to have at least one dynamic property source Active the actually requirement is 1 schema file change a little test coverage. Details in the related issues

-

📌 Move `PropSourceEndpointTest` into new `XbConfigEntityHttpApiTest::testComponent()` Active is in 🥳 The test coverage for that revealed one bug in shape matching, which isn't a hard blocker, but needs to be fixed at some point. So created a new section.

✨ Move entity type and ID from base path and into routing parameters Active is unblocked because ✨ Allow working with a new (unsaved) entity Active landed! (Which means that one was missing, so added it 😇)

I doubt that we'd be okay with only supporting populating SDC-sourced component instances with structured data — we of course also want to be able to do that for code components. Which means that we have to do #3503038. See #3503038-16: Enable candidate `DynamicPropSource` suggestions for code components: refactor `GeneratedFieldExplicitInputUxComponentSourceBase` and `FieldForComponentSuggester` to need only SDC's ComponentMetadata, not SDC plugin instances → for details.

We've got kind of a meta sprawl going on here 😅🙈 i.e.: what is the difference in intent/scope between:

• this issue
• vs 🌱 [META] 7. Content type templates — aka "default layouts" — clarify the tree+props data model Active
• vs 📌 [PoC] Introduce a `ContentTypeTemplate` config entity Active

So together with @f.mazeikis and @thoward216, clarifying the scope of this meta! 🎉

• Per @lauriii months ago, we won't be building exposed slots until after 1.0.
• Per @lauriii and @effulgentsia, the ContentTemplates scope for 1.0 is limited to only Node entities — since https://git.drupalcode.org/project/experience_builder/-/commit/843e7b0b1....
• no XB-native view mode creation UI

Per @hooroomoo 😊

Moving the Allow linking a component prop of a template to a dynamic field to be higher in the FE list for visibility and higher priority because this could be big one due to it also has to make sure that the component props form can be correctly generated after a dynamic field is set to a prop.

https://git.drupalcode.org/project/experience_builder/-/merge_requests/1...

Added 📌 ContentTemplate status should be used to determine if it should be used. Active to the list

Per 🌱 Milestone 1.0.0: Production Sites Postponed this is a requirement for an XB 1.0.0 stable release, so tagging it as such.

Added 📌 Refactor(or attempt to) all or most ApiLayoutController*Test classes to also test ContentTemplate entities Active

📌 ContentTemplate status should be used to determine if it should be used. Active landed.

Confirmed with product these are out of scope for 1.0 so updating the issue summary

Assigned to: lauriii ✨ Render template data form Active
✨ Allow creating/deleting view mode from UI Active

📌 Refactor ApiLayoutController into 2 sub-class to support Content Templates Active is in.

📌 Create HTTP Endpoint for Content Template Preview Entities Active is in.

Added 📌 `CanvasUiAccessCheck` should grant access if the user has access to content templates or code components Active to the IS.

📌 Create HTTP Endpoint for View modes/content templates Active is in.

And 📌 Create HTTP Endpoint for Content Template Preview Entities Active no longer needs a follow-up! 🥳 Yay more green.

Not every stable blocker needs to block an RC, but this one does.

📌 `CanvasUiAccessCheck` should grant access if the user has access to content templates or code components Active landed.