mirror of
https://github.com/hanzo-docs/docs.git
synced 2026-10-29 07:01:44 +00:00
zeekayandHanzo Dev
5313260909
One app carried the Hanzo shell and twenty did not, so a reader crossing from base.hanzo.ai to zen.hanzo.ai left the ecosystem and landed somewhere that only resembled it. Five of those twenty had hand-rolled a footer of their own — sixteen lines of copyright and a repo link, written five separate times. Each app now loads the brand tokens before its own sheet, reports through docs-analytics under its own product name, and renders HanzoFooter from @hanzogui/shell — the same 6-column ecosystem footer, defined once, that apps/docs already used. A footer written inside a layout was chrome pretending to be content, and it is gone. A footer written inside a page is content pretending to be chrome: those keep their words and become sections, so each page has one contentinfo landmark instead of two. Three manifests listed @hanzo/font twice in the same object. Builds verified across the four shapes this repo has: a static export, a next.config.mjs app, a single-page app with no route groups, and one that already reported analytics. Every one renders exactly one footer. Co-authored-by: Hanzo Dev <[email protected]>
22 lines
511 B
TypeScript
22 lines
511 B
TypeScript
import { HomeLayout } from '@hanzo/docs-base-ui/layouts/home';
|
|
import type { ReactNode } from 'react';
|
|
import { Footer } from '@/components/footer';
|
|
|
|
export default function Layout({ children }: { children: ReactNode }) {
|
|
return (
|
|
<HomeLayout
|
|
nav={{
|
|
title: 'Pulsar',
|
|
url: '/',
|
|
}}
|
|
links={[
|
|
{ text: 'Docs', url: '/docs' },
|
|
{ text: 'GitHub', url: 'https://github.com/luxfi/pulsar' },
|
|
]}
|
|
>
|
|
{children}
|
|
<Footer />
|
|
</HomeLayout>
|
|
);
|
|
}
|