Files
market/docs/mintlify.md
zeekay 661a6a28d5 rebrand: Bot Hub → Hanzo Market, white-label via @luxfi/brand schema
- Repo transferred hanzobot/hub → hanzoai/market (matches owned hanzo.market domain)
- npm package: bothub → @hanzoai/market, packages/bothub → packages/market
- bothub-schema → @hanzoai/market-schema
- CLI binary: bothub → market
- Brand: Bot Hub → Hanzo Market across ~95 user-facing surfaces (README, docs, k8s,
  Dockerfile, public/manifest.json, OG image, CLI banner, site config, theme)
- Brand-neutral white-label: src/brand/ owns BrandConfig + BrandTheme + loader,
  public/brands/<id>.json presets for hanzo, zoo, lux, pars, liquidity, generic
- BRAND_ID env at build picks default; ConfigMap-mounted brand.json overrides at runtime
- Legacy paths retained for compat: ~/.bothub, .bothubignore, /.well-known/bothub.json,
  bothub-theme localStorage key, LEGACY_HOSTS for hub.hanzo.bot/clawhub.ai
- Fixed broken sed-replace artifacts in packages/market/src/cli/botConfig.test.ts
- Drops Clawd/OpenClaw dead brand surface, keeps Clawdis* schema types and
  clawd skill directory paths (backward compat for installed bot products)
2026-05-29 13:46:09 -07:00

1.1 KiB

summary, read_when
summary read_when
Mintlify setup notes for publishing docs/.
Setting up docs site

Mintlify

Goal: publish docs/ as a browsable docs site (nice UX for OSS users).

This repo does not include Mintlify config yet (mint.json missing).

Minimal setup

  1. Install Mintlify CLI (per Mintlify docs).

  2. Add a mint.json at repo root that points to docs/ pages.

Example (starter):

{
  "name": "Hanzo Market",
  "logo": "public/logo.svg",
  "navigation": [
    { "group": "Start", "pages": ["docs/README", "docs/quickstart"] },
    { "group": "Concepts", "pages": ["docs/architecture", "docs/skill-format", "docs/telemetry"] },
    { "group": "Reference", "pages": ["docs/cli", "docs/http-api", "docs/auth", "docs/deploy"] }
  ]
}

Notes:

  • Mintlify usually wants page paths without extension; keep files as .md.
  • If you prefer Mintlify conventions, rename to .mdx later (optional).
  • Add an “Overview” page (use docs/README.md).
  • Keep “Quickstart” copy/paste friendly.
  • Provide CLI + HTTP API reference pages (done here).
  • Add a Troubleshooting page for common setup failures.