Backend Layouts

TYPO3

Beschreibung

Backend layouts define the content areas shown in the TYPO3 Page module and control frontend rendering at the same time. 

They are configured in Page TSconfig as part of a site package, which is the recommended approach; alternatively they can be created directly in the TYPO3 backend and stored as database records, though this is no longer considered best practice. 

Each layout consists of a grid of rows and columns; each column represents a named content area with a unique colPos value. Using the page-content DataProcessor and the identifier property, backend layout columns map directly to Fluid template variables. Since TYPO3 14, columns can additionally restrict which content element types are allowed or disallowed within them.

Ziele

• I know that backend layouts are defined in Page TSconfig.
• I know the required and optional properties for a column: name (label in the Page module), colPos (integer used to store and retrieve content elements), identifier (readable string used by the page-content DataProcessor), colspan, and rowspan.
• I know that the identifier value of a column becomes the variable name in Fluid, making content from that area available as e.g. {myContent.main} when using the page-content DataProcessor.
• I know the three slideMode values for a column: slide (use content from the nearest parent page if the column is empty), collect (merge content from this page and all parent pages), and collectReverse (same as collect but in reverse order); an empty value means no inheritance.
• I know that since TYPO3 14, allowedContentTypes and disallowedContentTypes can be set per column to restrict which tt_content.CType values editors may add.
• I know it is best practice to define backend layouts in Page TSconfig files (*.tsconfig), because they can be put under version control.

Maintainer

Oliver Thiele Web Development Oliver Thiele