Skip to content

docs: add brand guide capturing the current site styles - #17

Merged
Babissimo merged 1 commit into
mainfrom
docs/brand-guide
Jul 29, 2026
Merged

docs: add brand guide capturing the current site styles#17
Babissimo merged 1 commit into
mainfrom
docs/brand-guide

Conversation

@Babissimo

Copy link
Copy Markdown
Contributor

What

Adds docs/brand/ to the org reference docs: a descriptive brand guide for the Offworld Labs / RETINA web surfaces, plus a tokens.css starter and a preview page.

Why

We have four hand-authored web surfaces that share a family resemblance but no stylesheet:

  • offworldlabs.com — the lab (editorial, warm paper, Source Serif 4)
  • retina.fm — the product (commercial, warm paper, Fraunces)
  • dash.retina.fm — the admin console (utilitarian, cool slate, system fonts)
  • map.retina.fm — the live radar map (dark FR24-style navy console, Inter)

A new page currently has to reverse-engineer the colours and fonts by eye, which invites drift. This captures what already exists so future pages can match it.

What's in it

  • brand-guide.md — the "one family, four voices" model, then foundations, colour, typography, shape/space/motion, components, the radar-diagram motif, voice, how to use the tokens, and an advisory improvements/gaps/discrepancies section.
  • tokens.css — the same values as CSS custom properties: a shared :root spine plus four surface classes (.owl / .retina / .dash / .map). A page adds one class to <body> and reads var(--ink), var(--canvas), var(--accent), etc. The .map class is dark, so components written against the tokens invert automatically.
  • preview.html — renders identical component markup under each surface class, as a proof the starter reproduces the four looks.

Deliberately descriptive, not prescriptive

It's a snapshot of the current state, not a target. Where the surfaces disagree (four type systems, four distinct blues, semantic colours that drift by a shade, the marketing-diagram green/amber vs the live-map teal/Doppler scheme, accessibility gaps) it records the disagreement rather than resolving it.

🤖 Generated with Claude Code

We have four hand-authored web surfaces (offworldlabs.com, retina.fm,
dash.retina.fm, and the dark map.retina.fm) that share a family
resemblance but no stylesheet, so a new page has to reverse-engineer the
colours and fonts by eye and tends to drift. This adds a descriptive
brand guide plus a tokens.css starter so future pages can match what
already exists instead of guessing.

The guide is deliberately a snapshot of what we have, not a target: it
records the shared foundations, the per-surface differences, and the
places the surfaces disagree (four type systems, four blues, semantic
colours that drift by a shade, the marketing-diagram vs live-map colour
schemes) rather than trying to resolve them. tokens.css unifies the
token naming across the four surfaces (owl/retina/dash/map body classes)
and preview.html renders identical markup under each class as a proof
the starter reproduces the looks.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Babissimo
Babissimo merged commit 0e1cd0b into main Jul 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant