App shell
The whole-page frame: sidebar + topbar + content area. Every product surface lives inside it. Five compositions, one per role the chrome adapts to.
Operator default
The standing layout — 252 px sidebar, breadcrumb topbar, content column. The chrome the typical operator uses all day.
Park Centre · today
Three tills open, one cashier on lunch.
Owner · multi-site
Topbar carries a site picker; the sidebar groups by site. The owner can hop between Park Centre, Avondale, Glen Lorne without losing context.
$ 5,212 group revenue
Compact · sidebar collapsed
Sidebar reduces to an icon rail when the operator needs maximum content space. Persisted per user.
2,418 products
Settings shell · nested
When the active surface is settings or master-data, the content column itself splits into a section rail + content (the SHL-02 shell).
Members & roles
Focus mode · workflow
When the operator starts a multi-step workflow (close shift, post payroll, import students), the chrome collapses to just brand + a step header — sidebar hidden until cancel.
Count the drawer
Enter the cash in the till by denomination.
Shared rules
What every composition obeys.
Persist sidebar collapsed / expanded state per user. Operators stay in their preferred config.
Hide the org switcher even when only one workspace exists. Position consistency matters.
Adapt the topbar to the role — site pickers for owners, breadcrumbs for operators.
Use the shell to host marketing or onboarding. Strip it for those flows.