[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

-