The checklist before shipping a page.
Use these as a fast visual QA pass. They protect the system from drifting back into generic dashboard language.
Ship only what survives the record.
A page belongs in Leadjr when it respects evidence, density, responsive behavior, and the system's editorial restraint.
- 01
Start every route with a scannable reference header, not a marketing hero.
- 02
Use a visible local menu when the page is documentation, inventory, or settings-like.
- 03
Prefer ruled rows and specimens over rounded cards.
- 04
Do not hide component examples below a large decorative intro.
- 05
Every action must point somewhere real or state why it is draft-only.
- 06
Every narrative surface should keep receipts close to the claim.
- 07
Do not let text, controls, tables, or specimens overflow their containers at mobile widths.
- 08
Cabana can supply anatomy and coverage; Leadjr supplies the final language and behavior.