Workspace
A bounded application frame with an optional 48px rail, 240px navigation channel, and main surface.
Interactive example
Browse files, reorder tabs, and leave a note. Use the navigation and inspector toggles to change the layout without losing your work.
Shell.tsx
Give the inspector room without losing the work underneath it.
@@ -18,10 +18,13 @@ Workspace layout export function Workspace() { const [inspecting, setInspecting] = useState(false);+ const compact = useCompactLayout(); return (- <div className="workspace">- {!inspecting && <Document />}- {inspecting && <Inspector />}+ <div className="workspace" data-compact={compact}>+ <main hidden={compact && inspecting}>+ <Document />+ </main>+ <Inspector hidden={!inspecting} /> </div> ); }@@ -40,7 +43,13 @@ Returning to the document function closeInspector() { setInspecting(false);+ requestAnimationFrame(() => {+ returnFocus.current?.focus({+ preventScroll: true,+ });+ }); } function openInspector() {+ returnFocus.current = document.activeElement; setInspecting(true); }layout.css
Two independent working areas. One continuous, quiet surface.
@@ -1,9 +1,15 @@ Workspace columns .workspace { display: grid; min-height: 0;- grid-template-columns: 1fr;+ grid-template-columns: minmax(0, 1fr) 320px; } +.workspace[data-compact='true'] {+ grid-template-columns: minmax(0, 1fr);+}+ .document, .inspector {+ min-width: 0; overflow-y: auto;+ overscroll-behavior: contain; }@@ -24,3 +30,9 @@ Motion preferences .inspector { border-inline-start: 1px solid var(--divider); }+ +@media (prefers-reduced-motion: reduce) {+ .workspace {+ transition: none;+ }+}Keyboard accessibility
Make the workspace equally useful without a pointer. Focus should follow intent, not the animation.
Decisions
Start with the work, then make room for the tools around it.
- Keep a predictable tab order across the application.
- Return focus to the trigger when a temporary panel closes.
- Preserve the same controls when a panel docks or takes over.
Acceptance checklist
What stays in place
A wide window should support moving between files without losing the current task. A narrow window should give that task the room it needs, without removing access to navigation.
Changing the layout is not starting a new session.
The reading position, open files, review decisions, and unfinished notes belong to the work—not the arrangement of the panels.
Review in context
Open Shell.tsx and compare the implementation with these decisions. Use the inspector for questions and keep the document open as a reference.
Before we ship
Check light and dark themes, a keyboard-only review, and a phone-sized window. Keep the scope small: layout and interaction first, shared component APIs after review.
Release checklist
Ship a small, coherent update. Keep the things that work and make each change easy to evaluate.
Decisions
Start with the work, then make room for the tools around it.
- Review the same populated screen in light and dark mode.
- Try a narrow window, keyboard navigation, and reduced motion.
- Separate layout experiments from changes to shared component defaults.
Acceptance checklist
What stays in place
A wide window should support moving between files without losing the current task. A narrow window should give that task the room it needs, without removing access to navigation.
Changing the layout is not starting a new session.
The reading position, open files, review decisions, and unfinished notes belong to the work—not the arrangement of the panels.
Review in context
Open Shell.tsx and compare the implementation with these decisions. Use the inspector for questions and keep the document open as a reference.
Before we ship
Check light and dark themes, a keyboard-only review, and a phone-sized window. Keep the scope small: layout and interaction first, shared component APIs after review.
Composition
<Workspace
navigationTitle="Atlas"
rail={({ showNavigation }) => (
<TabBar
variant="rail"
tabs={views.map((view) => ({
...view,
onClick: () => {
selectView(view.id);
showNavigation();
},
}))}
/>
)}
navigation={({ dismissNavigation }) => (
<Pane padding="medium">
<FileList
onSelect={(file) => {
selectFile(file);
dismissNavigation();
}}
/>
</Pane>
)}
>
<AdaptiveSplitView panelTitle="Inspector" panel={inspector}>
<Pane header={<Toolbar variant="pane" headline="Document" />}>
{document}
</Pane>
</AdaptiveSplitView>
</Workspace>
- Give the workspace a bounded height. It fills the available space.
- The channel docks when at least 820px is available, plus 48px when a rail is present.
- One toggle shows or hides the channel without removing the rail. It docks on wide layouts and floats on narrow ones; there is no separate pinning mode.
- The document card extends beneath the raised channel while keeping its content clear. Tabs and headers remain flush with the document surface.
- Floating navigation stays within the viewport, including inside a scrolling page.
- Floating navigation uses a native modal dialog containing both the rail and channel, so the same toggle remains usable. Outside interaction and Escape dismiss it, focus returns to the opener, and nested Aidos popovers remain usable.
- A focused channel stays open when the window narrows. Otherwise the document takes priority. Explicitly closing the channel is remembered across resizing.
- Channel and main content stay mounted through layout changes. The application owns navigation selection, drafts, and persistence.
- Use navigationOpen with onNavigationOpenChange to own channel visibility. Controlled visibility survives resizing; the shell still switches between docked and floating layouts. Omit navigationOpen for automatic responsive visibility.
- rail, navigation, and children accept nodes or functions receiving showNavigation and dismissNavigation. Dismiss only closes floating navigation; file selection does not hide a docked channel.
- Omit either navigation level when it is not needed. Without a rail, Toolbar variant="pane" reserves room for the floating channel toggle.
- navigationTitle defaults to “Navigation”. jss and ordinary view attributes customize the frame.
NavigationSplitView remains available for page layouts with compact/bottom navigation.
Documentation layout
The documentation site uses the same shell without a rail, document tabs, or an inspector. It removes the outer frame decoration so the reading card is not framed twice. Workspace owns navigation; its content can be any view.
<Workspace
navigationTitle="Aidos UI"
navigation={navigation}
jss={{
border: 0,
borderRadius: 0,
backgroundColor: "transparent",
overflow: "visible",
}}
>
<Pane
header={
<Toolbar variant="pane" headline="Documentation" actions={actions} />
}
>
{article}
</Pane>
</Workspace>
Routing, search, anchor links, and reading-position restoration remain application concerns.