Zigbook is a Nuxt-powered documentation site that republishes the Zig 0.15.1 standard library with curated navigation and LLM-friendly exports. The goal is to provide a production-grade reference for Zig developers until the upstream docs stabilize.

• Node.js 22.9.0 (or newer 22.x release) with the built-in node:sqlite module
• npm 10.x (ships with Node 22)
• macOS, Linux, or WSL2 environment with git

Use nvm use (or install via Volta/ASDF) to align with the pinned runtime:

nvm use

The repo enforces engines via .npmrc, so older Node versions will be rejected at install time.

# Install dependencies (lockfile driven)
npm install

# Launch the development server
npm run dev

# Run linting and type analysis
npm run lint
npm run typecheck

Visit http://localhost:3000 after npm run dev boots.

• Category ordering on the home page is controlled by the optional weight field in data/std-navigation.json. Higher values surface first; ties fall back to alphabetical ordering.
• The landing page uses a client-side Fuse.js index for fuzzy search. The index hydrates after mount, so the UI exposes a loading state and a deterministic fallback filter until Fuse finishes building. If you add new categories or modules, no extra wiring is required—just ensure the metadata lives in the JSON file so the index rebuilds automatically.

├── app.config.ts          # Docus theming, header/footer, UI overrides
├── assets/                # Tailwind entrypoint and shared styles
├── components/            # Vue components for reference navigation and tools
├── content/               # Hand-authored and generated Markdown via Nuxt Content
├── data/std-categories.json
│                          # Category metadata for Zig stdlib syncing
├── scripts/sync-std-docs.mjs
│                          # Generates /content/docs/std/* from /std sources
├── std/                   # Vendored Zig 0.15.1 Markdown from upstream
├── nuxt.config.ts         # Nuxt configuration (modules, content, tailwind)
├── tailwind.config.ts     # Tailwind 4 theme extensions
├── docs/                  # Engineering docs, including active to-do list
└── public/                # Static assets (favicons, logos, OG images)

1. Update Markdown in std/ or category metadata in data/std-categories.json.
2. Run npm run sync:std to regenerate the Nuxt Content entries under content/docs/std/.
3. Commit both the source Markdown and generated files to keep history in sync.

The sync-std-docs.mjs script maintains front matter, SEO metadata, badges, and callouts automatically. It will throw when category assignments are missing to avoid silent omissions.

• Linting: npm run lint uses the Nuxt flat ESLint configuration.
• Type safety: npm run typecheck calls nuxt typecheck for full app analysis.
• Build: npm run build performs the production compile and Nitro output generation.
• CI: GitHub Actions run install → lint → typecheck → build on every push and pull request (see .github/workflows/ci.yml).

1. Create a feature branch from main.
2. Make changes with tests/docs as needed.
3. Run npm run lint, npm run typecheck, and npm run build locally.
4. Submit a pull request; the CI workflow must pass before review.

For larger enhancements, coordinate using the roadmap and to-do list in docs/ so we can stage work across milestones.

MIT.