Skip to content
Tetrifox

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.

Inside-out assemblyDecision → interface
  1. 01ActionButtonMake priority visible.
  2. 02SurfaceCardGive content a repeatable shape.
  3. 03ArgumentSectionHeaderSet the reading order.
  4. 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.

Realbrand-bundle/components.md

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, SectionHeader and the Reveal family before creating a component. New components are designed for three pages, not one.

  • Must

    Use the three button variants only: primary (solid orange pill) and secondary (bordered pill that never fills with a surface colour), both labelled body-sm weight-medium; and link (accent-sm accent text with an arrow).

    --color-brand-700--border-strongbody-smweight-mediumaccent-sm

  • Must

    Lead each view with at most one primary button; use secondary and link buttons for everything else.

    --color-brand-700

  • Must

    Links navigate; buttons perform an action. Use next/link for internal routes, and give external links target="_blank" with rel="noopener noreferrer".

  • Must not

    Hand-style an arrow next to text. Use <Button variant="link">.

  • Must

    Share one visible focus outline across variants (outline-2 outline-offset-2 outline-brand-600). Disabled buttons use the native disabled attribute, keep their shape at 50% opacity, and lose hover and active movement.

    --color-brand-600

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.

ExtensionThe live source repeats service, process, and metric content shapes, but it does not define a shared visual Card component. The primitive shown here is a brand-book extension derived from those shapes, the semantic surface tokens, and the closed-grid rule.

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 Card as a composable content cell on the surface token 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.

Real

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 real h1–h3 whose level is independent of its size, and a body-lg subtitle on a capped measure. Pass anchorId so 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. Never div soup.

  • Must

    Render images with next/image, never a raw <img>, with explicit dimensions or fill in a sized parent. Meaningful images carry real alt text; decorative ones use alt="" and aria-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.

RealRuntime presets · @/lib/motionExtensionReplayable teaching specimen

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-wire motion.div in sections.

    transitions.revealvariants.fadeUpvariants.gridStagger

  • Must

    Use CSS transitions (about 200ms) for hover, never Motion components, and honour html[data-motion] as well as motion-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.