Block layout
The screen that decides which blocks appear in each region of a Drupal theme and in what order; every change is saved as configuration.
Block layout is the Drupal admin page, at Structure › Block layout, where you place blocks into a theme's regions, drag them into order, disable them or remove them. It has one tab per theme, because block placement is stored per theme. The page requires the administer blocks permission.
How the block layout page works in Drupal 11
The route block.admin_display lives at /admin/structure/block and has the title Block layout. Each theme that has a UI gets a tab, created by the ThemeLocalTask deriver; the default theme's tab comes first. Other tabs point to /admin/structure/block/list/{theme}.
Under each visible region heading, the table lists its blocks in columns named Block, Category, Region, Weight and Operations. An empty region shows the text No blocks in this region. The Place block button next to a region opens the block library in a modal dialog. Operations include Configure and Remove, plus Disable or Enable.
Rows can be dragged to change order and region. The Drupal User Guide adds that Show row weights swaps the handles for numeric weights, where lower values appear first.
The page changes configuration. Each placement is a block configuration entity, so it follows your normal configuration workflow. When a theme that brings no placements of its own is installed, Drupal copies the default theme's placements to it.
Example
To put a newsletter box in the sidebar, go to Structure › Block layout and open the tab of the theme your visitors see. Click Place block beside the sidebar region, then choose the block from the library. In the configuration dialog, check the region, optionally limit the pages, and click Save block. Drag it to the right spot and click Save blocks.
Common mistakes
- Working in the wrong theme's tab. The Drupal User Guide stresses that block placement is defined per theme. Check the tab before you edit.
- Forgetting Save blocks. Dragging only changes the form. Leave the page without saving and the old order stays.
- Looking for hidden regions. The page lists only visible regions, so
page_topandpage_bottomnever appear. - Expecting page-by-page layouts. This page arranges blocks per theme. For a layout that differs between pages, use a tool built for that, such as Layout Builder or DXPR Builder.
For marketing and content teams
Requests such as "move the banner" or "hide the signup box on the pricing page" are handled here. Ask for the administer blocks permission, or ask a site builder to do it. Each change applies to every page that prints that region in that theme, within the block's visibility rules, so test visibility rules on a staging copy first. The theme decides which regions exist.
With DXPR
Some blocks do not need a region. DXPR Builder can place a Drupal block as an element inside a page, so a block can sit in the page body, next to the text it supports. See DXPR Builder.
Sources
- Drupal User Guide: Placing a block in a region
- Drupal User Guide: Concept: Regions
- Block module routing, Drupal 11.4.0 source
- Block module local tasks, Drupal 11.4.0 source
- ThemeLocalTask deriver, Drupal 11.4.0 source
- BlockListBuilder, Drupal 11.4.0 source
- BlockAccessControlHandler, Drupal 11.4.0 source
- BlockDeleteForm, Drupal 11.4.0 source
- ConfigEntityListBuilder, Drupal 11.4.0 source
- Block entity, Drupal 11.4.0 source
- BlockHooks, Drupal 11.4.0 source
- Layout Builder module info file, Drupal 11.4.0 source