---
title: "FAQ"
manual: "Content Blocks"
version: "main"
permalink: "https://docs.typo3.org/permalink/friendsoftypo3/content-blocks:faq@main"
source: "FAQ/Index.rst"
rendered: "2026-09-22T14:15:39+00:00"
---

# FAQ {#faq}

Answers to frequently asked questions.

## Which parts of Content Blocks are in TYPO3 v13 Core? {#integration-v13}

-   [Feature: #104002 - Schema API](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.2/Feature-104002-SchemaAPI.html#feature-104002-1718273913)
-   [Feature: #103581 - Automatically transform TCA field values for record objects](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.3/Feature-103581-AutomaticallyTransformTCAFieldValuesForRecordObjects.html#feature-103581-1723209131)
-   [Feature: #103783 - RecordTransformation Data Processor](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.2/Feature-103783-RecordTransformationDataProcessor.html#feature-103783-1715113274)

Content Blocks is partly integrated into TYPO3 v13. Since version 1.0 it
is based on the new, underlying API from the Core. Most importantly the
new Record Transformation API, which was previously implemented in
Content Blocks for v12.

## Why YAML and not PHP? {#yaml}

Content Blocks is supposed to be the intersection where frontend and
backend developers meet. YAML is currently the best suited format for
both parties. It allows comments and auto-completion for IDEs with JSON
schemas.

## How can I extend an existing Content Block? {#extending-types}

This is not possible. The philosophy behind Content Blocks are reusable
components, not extendable components. If there is an existing Content
Block you want to adapt to your custom needs, simply copy it as a whole.
There is no drawback to it. Normally, you don't even want future changes
to a Content Block from external parties. By owning the Content Block
your code can't break with an update.

If you really need to override a Content Block, you can always fall back
to traditional methods like [TCA Overrides](https://docs.typo3.org/permalink/friendsoftypo3/content-blocks:cb-extendtca@main).

## Can I add PHP code to my Content Blocks? {#add-php-code}

The Content Blocks API does not support PHP files at all. If you want to add
some PHP logic to your Content Blocks, you have to use the old common
ways.

## Can I use twig templating engine with Content Blocks? {#twig-in-content-blocks}

No, it's not possible. The main rendering engine for TYPO3 is Fluid.
If you want to use something else, you are on your own.

## Can I use headless with Content Blocks? {#headless-with-content-blocks}

Content Blocks generates TYPO3 core code under the hood (TCA, TypoScript
and so on), so you have to prepare your headless setup like you have to
do with core content elements.

## Are the Content Blocks assets (JS and CSS) compressed by core? {#assets-compression}

Content Blocks uses core's asset collector, so the assets are not merged
together. Since they get registered only if the Content Block is used on
the page, each file is included separately.

## Can I add Content Blocks assets (JS and CSS) to my build process? {#assets-build-process}

This is not a specific Content Blocks question. You can add your assets
to the build process like you do with any other assets. For example you
can add your Content Block CSS to your main CSS file, and remove the CSS
registration in the Content Block.

## Will there be a GUI (Graphical User Interface) for Content Blocks? {#content-blocks-gui}

Yes, the Content Types Team is working on a GUI for Content Blocks. You can
find the currently ongoing work on [GitHub](https://github.com/friendsOfTYPO3/content-blocks-gui/)
or in [Extension Repository](https://extensions.typo3.org/extension/content_blocks_gui).