Epic #61834: Create future proof Content Element with strong default
Reorganize Content Element properties within backend Extension
To be prepared for the future of new Content Elements many properties of tt_content should be refactored.
Main problems are: Unused/antiquated fields, unclear naming, un-deterministic spelling.
As discussed at the T3UXW14 the best technical approach is to move fields to EXT: css_styled_content.
Allow extensions for alternative Content Elements with Rendering.
As a first step for a clean up and refactored tt_content properties - specific properties should be moved to EXT: css_styled_content.
New approaches for Content Elements are born with EXT: content_elements and EXT: fluid_contentelements or futuristic Content Element Types.
#1 Updated by Felix Kopp about 5 years ago
Keep only the necessary basic properties for Content Elements:
+ Authoring (user, tstamp, time)
+ Hierarchy (position, sorting, parent page)
+ Visibility (frontend user access, access time, )
+ Channel (language, workspace)
Move everything else to CSS-Styled-Content.
#2 Updated by Felix Kopp about 5 years ago
- Subject changed from Move Content Element fields to CSS-Styled-Content to Strip down Content Element
Move additional properties of Content Elements to CSS-Styled-Content.
TYPO3 core will deliver CSS-Styled-Content and a modern version of CSS-Styled-Content with modern Content Elements plus migration wizard.