feat(website): unify all fonts onto the next/font variables - #876
Merged
Conversation
Findings audit §10, executed as its own decision per the polish arc. layout.tsx loads Inter, JetBrains Mono, and EB Garamond via next/font, which registers each family under a hashed name and exposes it only through --font-inter/--font-mono/--font-garamond on <html>. Raw stacks like 'Inter, system-ui, sans-serif' therefore only matched a locally installed Inter and silently fell back to system fonts — the site was a mix of real webfonts and system lookalikes (measured ~2.5px width shifts between the two). This replaces all 94 literal font-family sites across the six scope stylesheets with the vars, normalizes 12 var-with-fallback spellings, and retires the migration-era 'fonts are verbatim literals' exception comment in ui.css with the new rule. Deliberate sitewide visual change: real self-hosted webfonts with size-adjusted fallbacks everywhere. Verified in-browser: every element under main on the homepage and docs resolves to a next/font stack (zero stragglers). nx test green, lint 0 errors, production build green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
enabled auto-merge (squash)
August 30, 2026 20:05
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
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
1 participant
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.
Summary
Findings audit §10, executed as its own decision.
layout.tsxloads Inter / JetBrains Mono / EB Garamond via next/font, which registers each family under a hashed name — reachable only through--font-inter/--font-mono/--font-garamondon<html>. Raw stacks likeInter, system-ui, sans-serifonly matched a locally-installed Inter, so they silently fell back to system fonts; the site was a mix of real webfonts and system lookalikes (~2.5px measured width differences).font-familysites across the six scope stylesheets with the vars.var(--font-*, fallback)spellings to the bare var (theme.css still defines the same names underneath, so the var always resolves).ui.csswith the new rule: everyfont-familyin website CSS is one of the three vars.Deliberate sitewide visual change: real self-hosted webfonts with size-adjusted fallbacks everywhere, no more mixed stacks. Design tokens (
libs/design-tokens) untouched — Angular consumers keep the raw stacks.Verification
mainresolves to a next/font stack ("Inter Fallback"/"JetBrains Mono Fallback"/"EB Garamond Fallback"), zero stragglers.nx test websitegreen, lint 0 errors, production build green (exit codes verified).🤖 Generated with Claude Code