FAQ

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.

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.

The Content Blocks API does 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.

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.

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.

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.

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.

Yes, the Content Types Team is working on a GUI for Content Blocks. The first steps are already done, and we are looking forward to the first beta phase in 2025.