Files
zeekay 498ba0715b 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.
2026-08-28 08:40:15 -07:00

40 lines
1.0 KiB
TypeScript

import "./global.css"
import { RootProvider } from "@hanzo/docs-ui/provider/next"
import { ZenMono } from "@hanzo/font/mono"
import { Zen } from "@hanzo/font/sans"
import type { ReactNode } from "react"
export const metadata = {
title: {
default: "Lux Consensus Documentation",
template: "%s | Lux Consensus",
},
description: "Quasar consensus engine with post-quantum finality for Lux blockchain",
}
export default function Layout({ children }: { children: ReactNode }) {
return (
<html
lang="en"
className={`${Zen.variable} ${ZenMono.variable}`}
suppressHydrationWarning
>
<body className="min-h-svh bg-background font-sans antialiased">
<RootProvider
search={{
enabled: true,
}}
theme={{
enabled: true,
defaultTheme: "dark",
}}
>
<div className="relative flex min-h-svh flex-col bg-background">
{children}
</div>
</RootProvider>
</body>
</html>
)
}