Files
docs/apps/cloud/package.json
T
zeekayandHanzo Dev 5313260909 Every docs site wears the same chrome
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]>
2026-08-29 14:29:19 -07:00

32 lines
796 B
JSON

{
"name": "@hanzo/cloud",
"version": "0.1.0",
"private": true,
"scripts": {
"build": "next build",
"clean": "rimraf .next out",
"dev": "next dev --port 3004",
"start": "next start"
},
"dependencies": {
"@hanzogui/shell": "^7.6.3",
"@hanzo/docs-analytics": "workspace:*",
"@hanzo/brand": "^1.4.1",
"@hanzo/font": "^1.9.2",
"class-variance-authority": "^0.7.1",
"lucide-react": "^0.562.0",
"next": "16.2.12",
"react": "^19.2.8",
"react-dom": "^19.2.8",
"tailwind-merge": "^3.4.0"
},
"devDependencies": {
"@tailwindcss/postcss": "^4.1.18",
"@types/node": "25.0.5",
"@types/react": "^19.2.18",
"@types/react-dom": "^19.2.4",
"postcss": "^8.5.6",
"tailwindcss": "^4.1.18",
"typescript": "^6.0.3"
}
}