Display
Use display for heroes and major editorial moments only. Weight stays 400.
Typography
Calm display type, practical body copy.
Use Satoshi for compact editorial display, General Sans for practical body and UI text, and IBM Plex Mono only where technical evidence needs it.
Primary visual route
Yellow lab
System first
Proof-led
Useful blocks
Warm control
Guidance
Display hierarchy
Satoshi display: compact, technical and editorial.
Display mega / 80 / 400 / 1.0
Technical delivery with proof.
Display xl / 64 / 400 / 1.0
Systems, crew and control.
Display lg / 52 / 400 / 1.0
Production that holds together.
Display md / 44 / 400 / 1.09
A calmer technical voice.
Display sm / 36 / 400 / 1.11
Proof before conversion.
Text hierarchy
General Sans roles for titles, body, labels and actions.
Title lg / 32 / 400 / 1.13
Connected division family
H3 / title md / 18 / 600 / 1.33
Technical scope and delivery responsibility
Title sm / 16 / 600 / 1.25
Commissioning and handoff
Body md / 16 / 400 / 1.5
Soundfangled brings planning, systems, crew and technical delivery together across Production, AV systems and Acoustics.
Body strong / 16 / 700 / 1.5
Use strong body weight for emphasis inside proof, not as a substitute for hierarchy.
Body sm / 14 / 400 / 1.5
Useful for card summaries, metadata explanation and compact supporting copy.
Caption / 13 / 400 / 1.5
Media proof, updated after internal review.
Caption strong / 12 / 600 / 1.5
Primary proof format
Button / 16 / 600 / 1.15
Discuss an AV system
Nav link / 14 / 500 / 1.4
Commercial hierarchy
Technical evidence
Mono appears only when the content is genuinely technical.
Mono number / 18 / 500 / 1.4
budget.control = six-figure
Mono evidence / 14 / 400 / 1.5
signal.path = stagebox / control / playback / handoff
Usage rules
Keep hierarchy calm, clear and sentence case.
Titles
Use title roles for cards, panels and section support where display would feel too loud.
Body
Use body roles for explanation, proof and commercial clarity. Keep line length readable.
Captions
Use captions for metadata, proof labels, workflow status and source context.
Buttons
Use sentence-case action language that reflects intent, not generic contact pressure.
Mono
Use mono for specs, signal paths, system status, budgets and technical evidence.