Cabana anatomy, Leadjr judgment.
This page explains how to use the system while converting template components into Leadjr-native components.
The design system is the override layer.
Cabana can tell us what component coverage should exist. It does not decide how Leadjr should sound, look, or behave.
When Cabana, Base UI defaults, or a local prototype conflicts with Leadjr, Leadjr wins.
Use Base UI for accessibility and behavior, then style the result into Leadjr's square, editorial language.
Treat Cabana as a coverage checklist: variants, states, parts, and examples. Do not import its visual personality.
Any surface that implies a professional claim must keep evidence, status, or provenance close enough to inspect.
How new components enter the system.
Every imported idea has to become native to the evidence newspaper: useful, restrained, responsive, and source-aware.
- 01
Start from Base UI behavior and accessibility, then apply Leadjr surface language.
- 02
Use Cabana to understand parts, variants, states, and expected coverage.
- 03
Replace Cabana's visual personality with hard borders, editorial type, warm paper, and restrained state language.
- 04
Do not add a component until its responsive behavior is clear at mobile, tablet, and desktop widths.
- 05
Do not let example content imply a professional claim unless it is visibly sample-only or backed by evidence.