---
title: "Feature: Content element rendering"
manual: "Frontend Theme for Extension Development"
version: "main"
source: "Changelog/2.0/Feature-ContentElementRendering.rst"
modified: "2026-09-17T04:52:50+00:00"
---

# Feature: Content element rendering

## Description

The theme renders content elements itself, without depending on
`fluid_styled_content`.

Two content elements are rendered:

| Content element | Rendered |
| --- | --- |
| **Header** | The heading, at the level chosen in **Type**. The **Hidden** option of that field is honoured. |
| **Text** | The heading and the rich text of the element. |

Both are wrapped in an element frame carrying the familiar `c<uid>` anchor, so
links to a content element keep working.

> [!WARNING]
> **Text & Media**, **Bullet List**, **Table**,
> **File Links** and the menu elements can be created in the backend -
> their TCA comes from EXT:frontend, not from `fluid_styled_content` \- but
> they have no rendering definition here yet and therefore render the TYPO3
> notice saying so.
>
> **Images** is rendered, see
> [Feature: Rendering of the Images element](Feature-ImageContentElementRendering.html#feature-image-content-element-rendering).

## Overriding the templates

The element templates live below `Resources/Private/Templates/ContentElements/`
and use the same Fluid paths as the page templates, so the constants under
`theme.` redirect them together - see [Configuration](../../Configuration/Index.html#configuration).

The rendering definition itself is the TypoScript object `lib.contentElement`,
which fills the role the object of the same name has in
`fluid_styled_content`.