The core must provide structured content elements which are configurable similar to backend layouts out of the box
The final goal should be to provide at least the must haves and ideally some of the should haves within the next two versions of TYPO3 CMS.We started with a first try in 2015 already, but this has been postponed on request by several members of the core team due to different reasons.
- The first reasons was, that we should avoid to rush things in, just because we want to have them, since this has lead to some pitfalls with other features in the past.
- The second reason is, that we need a well implemented technology to deal with tree structures, since nested content is basically nothing else but a tree
- Last but not least to make sure that the concept we are going to implement fits the needs of our userbase, we need properly written stories first
So before we get lost in discussions about details of the implemetation like configuration syntax or data management, we need to make sure we all know WHY we are going to do it and WHAT we actually want to get.
The blue print was a first step into that direction. Now everbody is invited to join the interest group on slack https://typo3.slack.com/messages/C8Z2UM50Q/ so we can build a team there to come up with the user stories, which we will then put up for discussion on https://decisions.typo3.org/
Keep in mind, that in the first place this is about WHY, then about WHAT and after the decisions have been made, we will start to think about the HOW.