fix(type): the binding is named for the face it holds

A docs-site template repeated across these repos named three different faces in
one place: a binding called `inter` or `geist`, constructed from next/font/google
so it actually held Inter, publishing a custom property called
`--font-geist-sans` that @hanzo/font does not set. Whichever of the three a
reader trusted, two of them were wrong.

They take Zen and ZenMono from @hanzo/font — bindings named `sans` and `mono`
for the role they fill, setting --font-zen-sans and --font-zen-mono, which is
what the package publishes.
This commit is contained in:
2026-08-28 08:34:00 -07:00
parent 5148061f22
commit 87e45c8878
2 changed files with 6 additions and 6 deletions
+4 -4
View File
@@ -10,14 +10,14 @@
public/fonts/OFL.txt) — the brand typeface is not something to borrow from a
CDN on the host whose whole job is that one curl command. */
@font-face {
font-family: 'Geist';
font-family: 'Zen';
src: url('/fonts/Geist-Variable.woff2') format('woff2');
font-weight: 100 900;
font-style: normal;
font-display: swap;
}
@font-face {
font-family: 'Geist Mono';
font-family: 'Zen Mono';
src: url('/fonts/GeistMono-Variable.woff2') format('woff2');
font-weight: 100 900;
font-style: normal;
@@ -25,8 +25,8 @@
}
@layer base {
html { font-family: 'Geist', ui-sans-serif, system-ui, sans-serif; }
code, pre, kbd, samp { font-family: 'Geist Mono', ui-monospace, SFMono-Regular, monospace; }
html { font-family: 'Zen', ui-sans-serif, system-ui, sans-serif; }
code, pre, kbd, samp { font-family: 'Zen Mono', ui-monospace, SFMono-Regular, monospace; }
:root {
--background: 0 0% 0%;
--foreground: 0 0% 100%;
+2 -2
View File
@@ -20,8 +20,8 @@ export default {
},
extend: {
fontFamily: {
sans: ['Geist', 'ui-sans-serif', 'system-ui', 'sans-serif'],
mono: ['Geist Mono', 'ui-monospace', 'SFMono-Regular', 'monospace'],
sans: ['Zen', 'ui-sans-serif', 'system-ui', 'sans-serif'],
mono: ['Zen Mono', 'ui-monospace', 'SFMono-Regular', 'monospace'],
},
colors: {
border: "hsl(var(--border))",