Expressions · Components
Built to repeat.
A component is a brand decision made reusable: one implementation carries its hierarchy, states, semantics, and motion constraints across every page that uses it.
New components are designed for three pages, not one.
- 01ActionButtonMake priority visible.
- 02SurfaceCardGive content a repeatable shape.
- 03ArgumentSectionHeaderSet the reading order.
- 04MotionRevealAssemble once, then settle.
Stage 01 · Action
Priority before proximity.
A component does not become primary because it sits first. Variant, semantics, and state make the next move legible before the label is read.
Stage 01
Action
Choose the next move
One view. One priority.
The primary action starts a conversation. Supporting actions explain the model without competing for attention.
Primary opens tetrifox.com in a new tab. Tab through the actions to inspect the shared focus outline.
The rules
- Must
Reuse
Button,Card,SectionHeaderand theRevealfamily before creating a component. New components are designed for three pages, not one. - Must
Lead each view with at most one primary button; use secondary and link buttons for everything else.
--color-brand-700 - Must not
Hand-style an arrow next to text. Use
<Button variant="link">.
Stage 02 · Surface
Give the action a shape.
A Card holds a repeatable content decision without forcing every service, process step, or metric into the same anatomy.
Stage 02
Surface
01
Service
Software Development Teams
Consultancy, technical leadership, and engineering delivered as one accountable unit—from blueprint to production.
Homepage · Software Development Teams
The rules
- Prefer
Use
Cardas a composable content cell on thesurfacetoken with the canonical Cell inset, not as a rigid title-and-description schema.--surfaceExtension - Must not
Give a card its own outer border, lift it without a real interaction, or hand-style its actions.
Extension
Stage 03 · Argument
Structure before style.
The header turns a reusable surface into a section with a subject, a claim, and enough context to understand what follows.
Stage 03
Argument
Software development teams
One accountable Mino.
Consultancy, technical leadership, and engineering delivered as one accountable unit—from blueprint to production.
01
Service
Software Development Teams
Consultancy, technical leadership, and engineering delivered as one accountable unit—from blueprint to production.
Homepage · Software Development Teams
The rules
- Must
Shape every section as
Section>Cell>SectionHeader> content > optional call to action. - Must
Open with
SectionHeader: an eyebrow (label-sm text-accent), a realh1–h3whose level is independent of its size, and abody-lgsubtitle on a capped measure. PassanchorIdso the heading owns the deep link.label-smbody-lg--text-accent - Must
Use semantic elements —
nav,main,section,article,aside,header,footer— and a skip link on every page. Neverdivsoup. - Must
Render images with
next/image, never a raw<img>, with explicit dimensions orfillin a sized parent. Meaningful images carry realalttext; decorative ones usealt=""andaria-hidden.
Stage 04 · Motion
Assemble. Reveal. Settle.
The complete section arrives once, in reading order. Its borders never move, its information never waits, and its reduced-motion state is already complete.
Software development teams
One accountable Mino.
Consultancy, technical leadership, and engineering delivered as one accountable unit—from blueprint to production.
01
Service
Software Development Teams
Consultancy, technical leadership, and engineering delivered as one accountable unit—from blueprint to production.
- Anatomy
- Header · content surface · action
- Semantics
- h2 · article · links
- States
- Rest · focus · disabled
- Source
- Real content · extended Card
- Reduced
- Visible and settled immediately
gridStagger · fadeUp
The component system is visible in its settled state.
The component system is visible in its settled state.
The rules
- Must
Wrap entrances in
Reveal,RevealStagger/RevealItem, or — above the fold —HeroReveal/HeroStagger. Do not hand-wiremotion.divin sections.transitions.revealvariants.fadeUpvariants.gridStagger - Must
Use CSS transitions (about 200ms) for hover, never Motion components, and honour
html[data-motion]as well asmotion-reduce.durations.fast
Resolved
One decision. Every use.
New components are designed for three pages, not one. Build the contract once, then let every composition inherit the same priority, semantics, state, and restraint.