FirstWho Brand Style Guide · v1.0

Form follows data.

FirstWho is a functionalist brand. The interface is an instrument for cognition, not a canvas for expression. This guide defines how the brand looks, reads, and behaves so that every surface stays consistent, legible, and honest to the data it carries.

Discipline
Functionalist / Swiss
Prime Directive
Maximize the data-ink ratio
Audience
External · public web
Status
Approved for use
01

Foundation

What the brand believes, stated once so every later decision can point back to it.

The Prime Directive
Every pixel and every word must justify its existence by contributing to understanding or task completion.

Structure over decoration

Order comes from the grid and the hierarchy, not from ornament. If an element can be removed without losing meaning, it is removed.

Color carries meaning

A color is a signal, never a mood. Each hue is tied to a category or a state, so people can navigate by seeing.

Plain language wins

We write like a precise, calm technical manual with a human voice. No hyperbole, no filler, no corporate happy-talk.

03

Color

Color is information encoding. Before using any hue, name the meaning it carries. If it carries none, use neutral gray.

Roles

Deep Indigo — Brand

Identity and primary action. Navigation, primary buttons, the logo, and top-level headings.

Teal — Interactive

Anything the user can act on: links, controls, and in-context prompts. Teal always means "clickable."

Amber — Wayfinding

Numbering, step indicators, and structural markers that orient the reader. Used sparingly, never as fill.

Green / Yellow / Red — Status

Reserved strictly for state: success, warning, error. Never decorative.

Gray ramp — Structure

Text, borders, dividers, and surfaces. Carries the layout so color can carry meaning.

Brand — Deep Indigo
312c86
brand-700#312c86Dark bars, headers
4132a9
brand-600#4132a9Primary — nav, buttons, H1
5346c0
brand-500#5346c0Hover state
edeafc
brand-100#edeafcTint / highlight
f5f4fe
brand-50#f5f4feLightest wash
Interactive — Teal · Wayfinding — Amber
007596
teal-600#007596Links, controls
0090b8
teal-500#0090b8Hover
d6f0f8
teal-100#d6f0f8Tint background
d97706
amber-600#d97706Numbering, markers
fef3c7
amber-100#fef3c7Tint
Status
16a34a
success-600#16a34aAvailable / done
ca8a04
warning-600#ca8a04Caution
dc2626
error-600#dc2626Error / stop
Neutrals
101727
gray-900#101727Primary text
3d4248
gray-700#3d4248Body text
6b7280
gray-500#6b7280Muted text
d1d5db
gray-300#d1d5dbBorders
f3f4f6
gray-100#f3f4f6Subtle fills
f9fafc
gray-50#f9fafcPage background

Contrast: body and UI text must meet WCAG AA against its background; primary text pairs aim for AAA. Never rely on color alone to signal state — pair it with text or an icon.

04

Typography

Two families, strictly divided. Inter carries the interface; Merriweather is reserved for page titles and posed questions, where a human voice matters.

Aa

Inter — interface & body

Neo-grotesque, neutral, built for legibility at every size. The default for all UI, labels, and running text.

Regular 400 · Medium 500 · SemiBold 600 · Bold 700
Aa

Merriweather — titles & questions

A serif with warmth, used only for H1 page titles and question text. Never for body copy or UI.

Regular 400 · Italic · Bold 700
Scale — Major Third (1.250)
Display / 36px
Bold / 1.05
Create your first job
H1 / 30px
Serif Bold
Page heading
H2 / 24px
SemiBold
Section heading
H3 / 20px
SemiBold
Subsection heading
Body / 16px
Regular / 1.5
Body copy sets at sixteen pixels with generous line height. Measure stays under about seventy characters so the eye returns cleanly to the next line.
Caption / 14px
Regular
Metadata, captions, and helper text
Label / 12px
SemiBold · tracked
Uppercase label

Do

  • Keep a strict hierarchy — one H1 per page.
  • Set body measure at 60–75 characters.
  • Reserve Merriweather for titles and questions.
  • Use tracking only on uppercase labels.

Don't

  • Set body text in a serif or display face.
  • Track lowercase text — it breaks word shapes.
  • Skip heading levels for visual effect.
  • Introduce a third typeface.
05

Voice & Tone

Write to be understood, then to be finished with. Precise, calm, direct — a technical manual with a human pulse.

Principles
01Omit needless words. "To start," not "In order to start the process."
02Front-load. Lead with the conclusion; put the keyword first.
03Active voice. "The system saves the file," not "The file is saved."
04No marketing fluff. Cut "revolutionary," "cutting-edge," "seamless."
05Plain language. Write for the reader's level, not the company's ego.
06Name things by control. "Save changes," not "Submit."
Before & after
Instead of
We are currently experiencing a high volume of calls.
Write
Call volume is high.
Instead of
Welcome to our state-of-the-art, game-changing solution.
Write
Screen candidates with structured, scorable interviews.
Instead of
The file is saved by the system automatically.
Write
FirstWho saves your work automatically.
Errors & empty states

Failure and emptiness are moments for direction, not mood. An error says what went wrong and how to fix it, in the interface's voice — it never apologizes and is never vague. An empty screen is an invitation to act, not a dead end.

06

Layout & Grid

A rigorous grid creates order the reader feels without noticing. Whitespace is a structural element, not leftover space.

12-column Swiss grid

Align every element to the grid. A 7 + 3 split (content + sidebar) is the default reading layout. Break the grid only for a stated functional reason.

Small multiples
Q1
Q2
Q3
Q4
Q5
Q6

Repeat one format to let the reader spot patterns across many values. Consistency of frame is what makes comparison fast.

Content width

720px main column; 320px sidebar. Text measure stays comfortable.

Spacing

4px base unit. All gaps are multiples of it — no arbitrary values.

Corners

4/6/8/12px only. Sharp and structural. Pills for tags alone.

Elevation

One light card shadow. No heavy drops, no glows, no glass.

07

Data & Imagery

Above all else, show the data. Strip everything that isn't the signal — grid noise, bevels, shadows, and decoration around numbers.

Do — high data-ink ratio
Don't — chartjunk

Do

  • Erase non-data ink until only the signal remains.
  • Use functional, geometric icons (Otl Aicher).
  • Encode categories with the palette's meaning.
  • Label directly; skip legends where you can.

Don't

  • Add drop shadows, bevels, or 3D to charts.
  • Use "ducks" — shapes that mimic the metaphor.
  • Fill space with mesh gradients or blobs.
  • Draw heavy gridlines that fight the data.
08

In Practice

Before any page ships, run the cruft scan. If it fails a line, the page isn't ready.

Is the grid obvious?Alignment is visible without turning on guides.
Is the data-ink ratio high?Nothing can be erased without losing meaning.
Is the color functional?Every hue signals a category or a state.
Is the text skimmable?Headers, short paragraphs, front-loaded points.
Did you delete the adjectives?Language is plain, direct, and active.
Is it accessible?Contrast passes; markup is semantic; focus is visible.