zeekayandHanzo Dev
4389e82bf6
The purpose-prefixed labels (hanzo-build-*, hanzo-deploy-*, hanzo-docs-build-*) are retired in favour of the bare <os>-<arch> every runner already advertises. They were not a capability, only a habit, and the habit cost builds: papers asked for hanzo-build-linux-amd64, no online runner offered it, and two idle linux-amd64 runners sat beside the queue while the build simply never ran. The lux tree lost three days to lux-linux-amd64 the same way. What a job is FOR is the workflow's name. runs-on is the machine it needs. Co-authored-by: Hanzo Dev <[email protected]>
Hanzo Team Docs
Product documentation for Hanzo Team — the all-in-one workspace for project tracking, documents, chat, planning, and drive. Published at docs.hanzo.team.
Built on the house docs stack: Fumadocs + Next.js
(static export) + Tailwind, the same toolchain as the rest of the hanzo-docs
org. Served on the Hanzo native stack — the export is baked into
ghcr.io/hanzoai/team-docs (Dockerfile: build stage + ghcr.io/hanzoai/static),
built by in-cluster BuildKit (ci/buildkit-job.yaml, .github/workflows/build.yml),
run by the operator (universe crs/team-docs-site.yaml), and routed by
hanzoai/ingress' file provider. No Cloudflare Pages.
Develop
pnpm install
pnpm dev # http://localhost:3007
Build
pnpm build # static export to ./out
Structure
content/docs/ # MDX docs (one folder per section, meta.json = sidebar order)
app/ # Next.js app router + Fumadocs layouts
lib/ # source loader, shared layout options, metadata
source.config.ts # Fumadocs MDX collections
Add a page: drop an .mdx file under content/docs/<section>/ and list its slug
in that folder's meta.json. Push to main and native CI rebuilds
ghcr.io/hanzoai/team-docs and rolls docs.hanzo.team forward.
Attribution
Adapted from the upstream Huly documentation under the Eclipse Public License
2.0. See NOTICE and LICENSE.