Grid_styled_content

TYPO3 Association Community Budget Ideas 2025 Q3
1

Idea Title

grid_styled_content

What is my idea about? What is the problem we are solving?

My Idea for grid_styled_content
As you all may know, the de-facto standard for content element markus is based on fluid_styled_content [FSC],
at least when you do not want to create your content elements from stretch.
The problem is, the markup and styling for theser elements is getting old, very old.
The roots of FSC date back to TYPO3 v7, which is more than 10 years old now.
Meanwhile, there have been significantly improvements to CSS, namely display:flex and display:grid,
which allows to achieve better layouts with less markup and styling.
The plugin extends and alters the “appeareance” Tab of CEs, it adds a “gridclass” select dropdown between layout and frame_class,
and alters the values of theses.
These variables are used to set the necessary classes for efficent grid styling.
My aim for grid_Styled_content is to replace fsc while maintaining backwards compatibility,
to provide future-proof content-element with accessible markup and adaptive styling -
and to educate all of you on the benefits of display:(flex|grid)
In Combination with some containers one can then realize all sorts of state-of-the-art layouts.
To incoropate

The Extension is already working,
but to get this to the core it still needs a polishing and testing -
and an overhauled styleguide.

What we want to achieve by the end of Q3 2025?

A core-ready extension and the according BE touchup.

What is the potential impact of my idea for the overall goal?

We will have state-of-the-art standards-first default content-elements again!

How does my Idea align with the strategic goals for TYPO3 v14.

Provide overall UX improvement and provide a standards first default theme

Which budget do we need for this idea?

5000 Euro

My Name

Markus Timtner

2

Have you made contact with the TYPO3 core developers yet? Unfortunately, experience has shown that it is not easy to incorporate new features into the core if the core developers do not support them. Only then does this budget make sense to me, because as a third-party extension, it will probably amount to nothing.

1 Like
3

Hi Markus,

thank you very much for this idea and the initiative behind it.

I’d like to share some context from my perspective as part of the core team and in my role as URC: We’re already actively working on the topic of themes and improvements to content element rendering, in close coordination with e.g. the Content Blocks team.

As part of this process, we’re moving towards a more component-based approach, with self-contained, reusable content elements that are easier to manage and extend. This includes rethinking how elements are configured, rendered, and integrated into the overall system.

Rather than introducing a direct successor to FSC, the current focus is on evolving the concept into a modern and future-proof solution that fits into this broader vision.

I really appreciate your motivation to improve things, and it would be great to have you involved in the ongoing efforts. Your perspective could be a valuable addition to the shared direction we’re taking. Please feel free to contact me directly anytime.

Best,
Oli