mycomyco-sh-docs-pipelinelisted
Install: claude install-skill goondocks-co/myco
# myco.sh Docs Site — Dual-Surface Build Pipeline, Pages Deployment, and Content Safety
The myco.sh docs site serves **two distinct audiences from one content base**: raw `.md` files for AI crawlers and LLM contexts (indexed via `llms.txt`, `sitemap.xml`, and `robots.txt`), and statically-rendered HTML pages for human readers. The build step (`npm run build` inside `docs/`) compiles everything into `docs/_site/` — both surfaces live there: copied raw `.md` files and generated `.html` files. That `_site/` directory is what gets deployed to GitHub Pages.
Changes to any of these areas are coupled — a new guide needs an entry in `docs/lib/nav.mjs` (the sidebar manifest), and a link in `llms.txt`. The `sitemap.xml` is auto-generated from the nav manifest. Understand the full picture before editing any one part.
---
## Prerequisites
- Node.js available; build runs as `npm run build` from inside the `docs/` directory (executes `docs/build.mjs`).
- Familiarity with `docs/` directory structure:
- `docs/*.md` — source markdown guides (do not move or rename without updating `llms.txt` and the nav manifest)
- `docs/lib/nav.mjs` — **sidebar nav manifest and single source of truth for guide ordering**; add new guides here
- `docs/build.mjs` — build orchestrator; reads nav manifest, renders HTML, copies static files, generates sitemap
- `docs/lib/render.mjs` — markdown-it renderer (Shiki theme + linkify guard)
- `docs/lib/template.mjs` — HTML template with left-sidebar nav