Authored interface standard
The Basel Standard.
A disciplined interface standard for dense, product-facing software. Designed and authored by Byron Wall.
Tables, overlays, forms, and navigation resolved together.
Density, focus, validation, and dark mode handled as one system.
Registry items remain practical to adopt inside shadcn workflows.
Dense records, metadata rails, and review drawers without visual drift.
The proof starts with alignment. Copy, labels, and controls sit on a consistent structural rhythm.
Dense surfaces keep focus explicit. Accessibility remains visible instead of being left to default browser behavior.
Long labels, compressed rows, and overlay states hold together without visual drift or improvised fixes.
state: "focused" overflow: "wrap" density: "maximum"
Interactive demo
See the system under load.
The point is not more controls. The point is whether the interface keeps its reading order when density, language length, overlays, and keyboard states are all in play.
Structure under pressure.
Switch the scenario, density, and proof state. The specimen should stay legible when hierarchy is put under pressure.
Collection intake
Structured records, acquisition notes, and review states in one reading surface.
Requires caption hierarchy pass and long-label overflow review.
Rows compress without losing hierarchy, border rhythm, or keyboard focus visibility.
German-length labels and drawer headings wrap without breaking the grid.
Command, drawer, and validation states inherit the same spacing and rule system.
Why it works
A calmer, more exact interface language.
Typography creates reading order before color does.
Alignment and rhythm carry composition instead of effects.
Accent remains sparse and functional, not atmospheric.
Borders and dividers define the system without softening it.
Use cases
Breadth, shown in context.
Show the system where it earns trust: control planes, dense data surfaces, and research views where structure matters more than decoration.
Navigation, dense tables, command flows, and review drawers act as one system instead of separate decisions.
Cards, metadata, totals, and status language remain readable without resorting to decorative emphasis.
Detail views, notes, and editorial content inherit the same logic as product-facing surfaces.
Package
A complete edition, not a starter scaffold.
The value is the work that has already been resolved: hierarchy, density, navigation, overlays, state treatment, and documentation that explains how the parts belong together.
Proof
Credibility, made visible.
Focus, overflow, validation, and resize handling are shown directly instead of being left as claims.
The standard reads as one authored system across surfaces instead of one more styled demo.
Registry items, docs, and package framing stay close to practical adoption.
FAQ
What buyers usually need to know.
You still need product-specific content and wiring. The difficult baseline work is already resolved: hierarchy, dense states, overlays, focus visibility, and structural spacing.
No. The core value is product-facing UI: tables, forms, navigation, command surfaces, drawers, and documentation that explain how those pieces behave in practice.
That is the point of the demo. The page shows long labels, compressed density, keyboard states, and dark-mode parity so the system is judged under load instead of at rest.
The standard includes installable components, composed blocks, documentation, and the authored decisions that usually consume weeks of internal design and frontend iteration.
Closing
Give the product a sharper standard.
For teams that want software to feel edited, composed, and ready to be trusted.