Skip to content

Layout

Choose page width from the task, then compose the shell and content around it.

Give people enough horizontal space to compare data. Keep editing and configuration within a bounded field of attention. Choose a page archetype before adding component-level spacing.

Page archetypes

ArchetypeTaskStarting width
Resource indexScan records, compare columns, filter, select, and apply bulk actions.w-full max-w-none with 12–16px gutters.
Focused workbenchBuild a rule, edit a template, or work beside a preview.Centered max-w-6xl; give the editor more width than its context.
Settings and detailConfigure a resource or review grouped settings.Centered max-w-5xl.
Focused formComplete a short setup or single-column review.Centered max-w-3xl.
Focused experienceAuthenticate, onboard, or connect an account.A composed focal surface; max-w-4xl is a starting point for a split layout.
Operational overviewReview related metrics, readiness, or active jobs.Moderate overall width with compact, grouped regions.

Choose a starting width for the task, then check it with real content at narrow and wide viewports.

Shell

Keep the global header around 48px. Use compact sidebar rows, a clear current location, and a persistent route to the main workspace. The shell should leave attention available for the task.

Use Akaza AppLayout for the document structure and Sidebar for its responsive navigation. Keep the skip link, meaningful landmarks, and focus behavior.

Data and workbenches

In a resource index, spend width on useful columns and stable alignment. Keep filters, selection counts, and bulk actions close to the records they affect.

In a workbench, group related inputs and keep previews or reference material beside the editor when space allows. Contract the workspace so routine eye movement stays within the task.

Mobile

Choose summary rows, drill-in detail, and drawers when a desktop composition no longer fits. Reduce visible table fields while preserving the same labels and states. Use horizontal scrolling when comparison itself requires those columns.

Respect safe areas for fixed actions. Test keyboard and coarse-pointer interactions alongside narrow layouts.

Documentation profile

Use 15–16px prose and a comfortable reading column, with compact navigation, code controls, and API tables. A 42rem reading column works for this documentation. Keep reading density separate from product table density.