Actions
Task #61836
closedEpic #61834: Create future proof Content Element with strong default
Reorganize Content Element properties within backend Extension
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-02-21
Due date:
2014-08-08
% Done:
100%
Estimated time:
(Total: 0.05 h)
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
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.
Files
Actions