AppShell
The outermost frame of a signed-in app: chrome, an optional rail, a measured content column, and the mounts every app needs exactly once.
Boards
Tick a row to raise the bottom bar.
| Board | Objects | |
|---|---|---|
| Q3 roadmap | 240 | |
| Onboarding flow | 180 | |
| Pricing tests | 120 |
import { AppShell, Navbar, NavbarBrand, ListPage } from '@objectifthunes/whiteboard'
<AppShell
navbar={<Navbar brand={<NavbarBrand mark="◈" name="My Whiteboard" />} items={NAV} />}
sidebar={<VerticalToolbar position="static">…</VerticalToolbar>} {/* optional */}
maxWidth="72rem" {/* or "none" for a canvas */}
stickyBar={selected.length ? <SelectionSummary /> : null}
toasts="bottom-right" {/* false when mounted higher up */}
>
<ListPage … />
</AppShell>Owns layout and nothing else. No data, no routing, no state.
Every screen was otherwise re-deciding the same three things by hand: where the navbar goes, how wide the content column is, and where to mount the toast stack. Mount the stack once here rather than per page.
stickyBar is a slot rather than a boolean because what belongs in it is always specific to the screen, but that it hangs off the bottom and that the content clears it are not. Pass null and nothing renders.
contained drops the viewport height so the shell fills its parent, which is how the example screens embed inside these docs pages.