Persona
Section
Page Layout
Updated
Sep 29, 2026

Split column

The page body under PageHeader. An 8:4 main and aside for a task with persistent supplementary context.

The page body under PageHeader. main is the task. aside is supplementary context that stays on the page. Do not wrap this template in Container or Section.

import Header from '@persona/design-system/components/PageHeader';
import { SplitColumnLayout } from '@persona/design-system/patterns/PageLayout';
<Header title="Home" />
<SplitColumnLayout main={<MainContent />} aside={<AsideContent />} />

Use it for a detail page with a metadata sidebar, a form with help beside it, or a master-detail page. main and aside need stable, different jobs.

Do not use it for temporary context. Use Modal or Popover. Do not put the primary task in aside.

Two cards side by side are not a split page. Use Single column when the cards have equal weight, belong to one collection, continue onto more rows, can be reordered or removed, or should reflow with the width. Charts, metrics, and dashboard tiles are that case.

main is 8 columns. aside is 4. There is no other ratio and no span prop. Below 768px the regions stack full width, main then aside. Content stays in the region it was given. Each region stacks its own children with Spacing[4].

width="standard" (the default) uses the fixed grid, centered at 1408px. width="wide" fills the available width.

Top and bottom padding match the grid’s horizontal padding: Spacing[6] (32px) at the medium breakpoint and up, Spacing[5] (24px) below that. When tabs is present, top padding is a fixed Spacing[5]. Spacing[5] separates tabs, pageNotice, and the body. An omitted region leaves no gap. tabs scrolls with the page.

tabs switches between a small set of peer views in the same product area or object. The tab group spans both columns. Omit it when the page has one view.

pageNotice is information about this page or task: a limitation, an incomplete setup, delayed data, a required next step, or context for reading the results. It sits under the tabs, spans both columns, and scrolls with the body.

Product-wide incidents belong in the application shell, not in pageNotice.

Was this page helpful?