mirror of
https://github.com/hanzo-docs/docs.git
synced 2026-10-25 04:20:02 +00:00
zeekay
7218bcd39c
Thirteen shipped apps and every scaffold in packages/create-app pulled their face from Google at request time — Inter through next/font/google in the examples and the four Next templates, Geist and Geist_Mono in the apps, and in the seven react-router roots a bare <link> to fonts.googleapis.com. That last one never even applied what it fetched: nothing in those trees set a family, so the browser downloaded Inter, spent two preconnects on it, and rendered system-ui. So `create-app` handed a customer a new docs site whose first act was a third-party font request for a face that is not ours. The apps read the family back through --font-sans and --font-mono, which are next/font's handles rather than names of anything, so those follow the binding over to --font-zen-sans and --font-zen-mono. Eight of them had only ever bound the mono and were leaning on Tailwind's default for the text face; they now name both, or swapping the binding would have dropped the body copy to system-ui without a word. Zen and ZenMono are built faces, not constructors — subsetting, display: swap and fallback metrics are already in them — so the call and its options go away.
10 lines
261 B
CSS
10 lines
261 B
CSS
@import 'tailwindcss';
|
|
@import '@hanzo/font/css';
|
|
@import '@hanzo/docs-base-ui/css/neutral.css';
|
|
@import '@hanzo/docs-base-ui/css/preset.css';
|
|
|
|
@theme inline {
|
|
--default-font-family: var(--font-zen-sans);
|
|
--default-mono-font-family: var(--font-zen-mono);
|
|
}
|