Move default content elements to EXT:fluid_styled_content

Open discussion topic here - looking for a solution. Not saying the below is the solution.. But it’s let’s talk about it.

I find myself doing this resetting of content elements task for each project / site set in page.tsconfig

TCEFORM.tt_content.CType.removeItems = header, text, textpic, image, textmedia, bullets, table, uploads, div, html, menu_abstract, menu_categorized_content, menu_categorized_pages, menu_pages, menu_subpages, menu_recently_updated, menu_related_pages, menu_section, menu_section_pages, menu_sitemap, menu_sitemap_pages

The reason for this is the defualt content elements are living inside EXT:frontend - a required package.
So this makes the resetting of content elements a required part each time.

The elements are following the rendering of EXT:fluid_styled_content - but fluid_styled_content is not required in a minimal setup. So we leave every new project with either a hard dependency on fluid_styled_content (for quick output) or a not-working-rendering-of-elements-presents

Idea

lib.parseFunc* is a important part of rendering - that lives inside EXT:frontend - that’s great.

What about we aim for a clean core in terms of rendering and elements.

Move content elements and corresponding database fields (TCA and all) to EXT:fluid_styled_content

Aim for projects requiring a “content elements rendering package” (such as fluid_styled_content or content blocks) either get elements out of the box or know what they will build the blocks themself.

And yes - I will take charge of such operation, I will do changes and follow it to the finish line :chequered_flag:

All in the name of simplifying workflows

A first take on it

https://review.typo3.org/c/Packages/TYPO3.CMS/+/92249