Skip to content

Design direction: noise audit + refinement plan#233

Draft
jackhenderson12 wants to merge 1 commit into
mainfrom
design/direction-audit
Draft

Design direction: noise audit + refinement plan#233
jackhenderson12 wants to merge 1 commit into
mainfrom
design/direction-audit

Conversation

@jackhenderson12

Copy link
Copy Markdown
Contributor

What this is

Step 1 of the refinement workflow — a planning PR, not a code change. It adds a single file,
DESIGN_DIRECTION.md, auditing where the
site's execution gets noisy and proposing a tightened direction within the existing brand
(black / white / #EDFF38, Messer + Suisse Int'l). No templates, tokens, or styles change here.

Opened as a draft for review — please react to the direction and the open questions at the
bottom before I start the visual PRs.

How I audited

Local npm run build (passes) served and reviewed: homepage, Updates listing, Projects, Tools,
and a blog article — desktop + mobile, light and dark mode.

Headline findings

  1. Yellow is wallpaper, not punctuation — whole screens are bg-golden-fizz (homepage, Tools,
    the shared introduction macro). When everything is yellow, yellow can't mark anything. Root cause.
  2. Flat hierarchy — five near-identical bold-uppercase kicker labels stacked down the homepage;
    no section rules, no scale contrast.
  3. Display font underused — the homepage hero is Suisse Bold sentence case (the brand book's
    own "incorrect" example); Messer is reduced to the logo + one stat.
  4. Link-stuffed paragraphs and min-h-screen + content-between dead space.
  5. Dark-mode black-on-black<body> sets no background/color, so prefers-color-scheme: dark
    visitors get black text on a dark canvas across all unpainted pages. ADA failure; one-line fix.
  6. Palette drift (gray/red/light-gold in config) and ~13 ad-hoc type sizes.
  7. One-off components — four card idioms, a hand-rolled accordion in <table><tbody><ol> with
    multiple <h1>s, no shared section-header/"see all" rhythm.

Proposed direction (detailed in the doc)

  • Reclaim white as the default surface; yellow returns to accents + one deliberate "moment" per page.
  • ~6 documented type roles (one Messer weight → hierarchy by size).
  • A small reusable component library: section header, content card (promote the good Updates card),
    primary/secondary buttons, motif utilities (underline, icon-circle, highlight, number-circle, stat).
  • Spacing & grid discipline; fix the dark-mode/background foundation and heading semantics.
  • Before/after sketches for the homepage and a listing page; a small-PR sequence to get there.

Constraints respected

Stays in 11ty + Nunjucks + Tailwind. Preserves content, routes, redirects, i18n (portuguese/),
Fathom, newsletter. npm run build passes.

Please weigh in on

  1. Homepage hero: oversized Messer ALL CAPS vs. Suisse Bold sentence case (I lean Messer).
  2. White-surface default with yellow reserved for accents + one moment per page — OK? Any page that
    should stay fully yellow on purpose?
  3. Should the first implementation PR fold in the palette cleanup, or keep that separate?

🤖 Generated with Claude Code

Audits the live site (homepage, Updates, Projects, Tools, an article;
desktop + mobile, light + dark) and names the concrete sources of
clutter, then proposes a tightened, within-brand direction.

Key findings:
- Yellow used as full-page wallpaper instead of punctuation (root cause)
- Flat hierarchy: identical uppercase kicker labels, no section rhythm
- Messer display underused; homepage hero is Suisse Bold sentence case
  (the brand book's "incorrect" example)
- Link-stuffed paragraphs; min-h-screen+content-between dead space
- Dark-mode black-on-black (no body bg set) — ADA failure
- Off-brand palette drift (gray/red/light-gold); ~13 ad-hoc type sizes
- One-off cards/accordions instead of a small reusable component set

Proposes: reclaim yellow as accent on white surface; ~6 type roles
(one Messer weight); a small component library (section header, content
card, button pair, motifs); spacing/grid discipline; foundation fixes.
Includes before/after for the homepage and a listing page, plus a
small-PR sequence. No template changes in this PR.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
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