Issue Task Closed

#61836Reorganize Content Element properties within backend Extension

Felix Kopp 09/24/14, 11:17 updated 10/26/17, 11:10

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.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Subtasks 1