Backend Layouts in TYPO3: Page Structure for Editors

Backend Layout

The definition of which content areas a page has and how they are presented to editors in the backend.

What a backend layout does

In TYPO3 a page does not simply have one content area but as many as the backend layout provides. A main area and one or two secondary areas are typical, sometimes with an additional area above or below the main content.

For editors, the backend layout is therefore the answer to the question of where a piece of content can go. It makes the structure of the page visible in the backend without anyone having to switch to the frontend.

Defined in the sitepackage

Backend layouts can be created as a record in the backend or as a file in the sitepackage. The file route is preferable, because it can be versioned and travels with the rest of the project.

The definition itself is built along TypoScript lines and describes a grid of rows and columns with a number and a label for each area.

Take the labels seriously

A detail that often gets skipped: the areas need names that mean something to editors. Area 1 and Area 2 are technically correct and worthless in daily work.

Names such as main content, side column or teaser area under the title cost a minute to write and save questions for good.

Common questions

How does a backend layout relate to the frontend?

The backend layout defines areas and gives them numbers. The Fluid template in the frontend pulls the content of those areas using exactly those numbers.

So the connection is the number, not the name. Change an area number in the backend layout and the template has to change with it, otherwise the output stays empty without any error appearing.

How many backend layouts make sense?

As few as possible. Every additional layout is a decision editors have to make when creating a page, and one more variant that wants maintaining.

In many projects three or four are enough: home page, standard page, a variant with a side column, and possibly a special page for landing purposes. If the number grows well beyond that, it is worth asking whether variants can be merged.