Examples
Whole screens built from the components, with realistic data. For seeing the parts work together, and for testing changes against something real.
An experiment, after Notion: no line under the sidebar top, a lighter grey, and the page one white plane. The customer side of the app: projects, their tabs, and a mission.
Account and organization settings, with a navigation list, forms and members.
Mockups for dashboards and data views: stats, freshness, a status timeline, coverage, quality flags and a segmented meter.
A programme on one screen: stations by missions, compact or full scale, with status, dots or method symbols in the cells.
Device controls together: a vessel’s systems and its water sampler, with commands that wait on the vessel.
The chat parts on a made-up figure assistant: status while it works, streamed answers, tool calls, approval before changes.
People talking on a plan, the crew and the office: bubbles, acknowledgements, pins, edits, and a message that fails to send.
A data table of CTD casts: one toolbar for waypoint, cast and quality, bins, columns, and flagging rows. The header stays as you scroll.
One profile form in eight layouts, from cards and rows to a save bar.
A top bar says which organization and project you are in. The sidebar is that scope’s navigation.
No top bar. The project switcher heads the sidebar, and the content has one header.
After Linear and Attio. The sidebar sits on the ground and the content is a panel set into it.
After Vercel and GitHub. No sidebar: switchers and sections run across the top, content gets the width.
After Plane. Projects are listed in the sidebar and the open one unfolds into its sections.
One sidebar everywhere. A project is a page with tabs, and a mission opens as a sheet, then a page.