PageLayout

The rhythm of a page's content — the gap between blocks, a reading width, and an optional side index. What every screen used to assemble by hand.

When to use it

Every admin screen. The block order is binding: header → metrics → toolbar → content; the gaps between them are held by this primitive, not by classes written in place.
A screen that is read — a long settings flow, legal text, a detail with no tables: width="reading". A line across a whole monitor is skimmed, not read.
A screen with its own index (aside + IngotSideNav): the index stands still, the content scrolls.

When not to use it

The application's outer frame — the 1440 px width and the edge padding are held by the shell under the top bar, not by the page.
A card grid or a two-column block inside the content. That is the inside of a block (a grid written in place), not the page frame — the frame must not know what is in it.
Application-level side navigation. The admin has none; aside is the index of one page's content.

Properties

width: "full" | "reading" — full (default) for tables and lists · reading for screens that are read.
aside: ReactNode — The side index on the left, typically IngotSideNav. The column is sticky.
children: ReactNode — The page's blocks in the binding order. The gaps between them are drawn by the layout.
testId: string — An anchor for tests. It does not affect the appearance.