design(landing): identity-first reskin — token SSOT, serif voice, monogram avatars - #107
Merged
Merged
Conversation
…ogram avatars Botsmann had no identity of its own: a generic 2021-era AI-SaaS skin with the brand fragmented across three disagreeing sources (config OpenAI-green, globals.css black/white, page blue/purple/cyan gradients). Derive Botsmann's OWN voice — serious, credible counsel: warm editorial ink + a single authoritative ochre accent, carried by a serif display face, not gradient tricks. - globals.css is now the single SSOT for design tokens (semantic colors for brand/action/surface/text + radii + shadows, two-tier primitive→semantic). - tailwind.config wired to the CSS vars; literal colors removed. Ripped out the OpenAI-borrowed tokens (openai-green #10a37f / openai-gray) and migrated every consumer to the semantic `action` / `brand` tokens. - Killed the generic "AI gradient" skin: removed the blue→purple→cyan gradient wordmark, the blurred gradient hero blobs, gradient buttons, and glassmorphism. Replaced with one confident ochre accent + ink, hairline editorial surfaces. - Real typeface via next/font: Fraunces (serif display, headings + wordmark) + Inter (UI/body), bound to --font-serif / --font-sans. Retires system-ui. - Replaced emoji professional avatars (⚖️🩺🔬🇨🇭🎨♛) with a ProfessionalAvatar monogram badge built on the existing accentColor SSOT. - One headline value prop: tab title, hero H1 and footer now all agree on "Your Private AI Professionals" (was a split tagline vs H1). Design only — all content and functionality preserved. Lint clean; no new tsc errors (the pre-existing embeddings.test.ts error is unchanged from main); production CSS resolves the full token chain. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A design assessment found the Botsmann landing looked like a generic 2021-era AI-SaaS template with no identity of its own. The brand was fragmented across three disagreeing sources:
tailwind.config→ OpenAI-borrowedopenai-green #10a37f/openai-grayglobals.css→ plain black/whitepage.tsx→ scattered blue→purple→cyan gradientsThis PR derives Botsmann's own voice — serious, credible counsel (real domain professionals, not a toy chatbot): warm editorial ink + a single authoritative ochre accent, carried by a serif display typeface rather than gradient tricks. No reasoning-by-analogy — this does not try to look like ChatGPT/OpenAI/x.ai.
What changed
globals.css— two-tier (primitive → semantic) CSS custom properties for brand / action / surface / text + radii + shadows.tailwind.config.jsis wired to those vars (no literal values). Ripped outopenai-green/openai-grayand migrated every consumer to the semanticaction/brandtokens.next/font— Fraunces (serif display, headings + wordmark) + Inter (UI/body), bound to--font-serif/--font-sans. Retiressystem-ui.ProfessionalAvatarmonogram badge built on the existingaccentColorSSOT.Scope & safety
bg-[#hex], tailwind maps to CSS vars, tokens live only inglobals.css.Verification
npm run lint(next lint --max-warnings 0) → cleannpx tsc --noEmit→ no new errors (the one error intests/__tests__/lib/embeddings.test.tsis pre-existing onmain, unrelated to this PR)next build→ compiled successfully; production CSS resolves the full token chain (--color-action: var(--primitive-ochre-600)→.bg-action{background-color:var(--color-action)})🤖 Generated with Claude Code