# Workflow: add a man page

Goal: get a command's man page onto Solnix so it's readable and searchable.

Man pages become searchable automatically when a **published** package ships
them. There is no separate "upload a man page" step.

1. **Ship the page in the package.** Put it under `$out/share/man/manN/<name>.N`
   (illumos sections: 1, 1m, 3*, 4, 5, 7*, 9*).
2. **Mark the recipe** `has_manpages=y` and give it a real `store_path` on a
   served arch (`x86_64-solaris`). See `conventions/recipe-schema.md`.
3. **Publish** via the signed-submit flow (`workflows/submit-a-package.md`).
4. **Within the hour**, the indexer extracts every `share/man/manN/*.N` from the
   NAR and upserts it. It then appears:
   - at <https://solnix.io/docs>,
   - via `GET /api/v1/manpages?q=<name>` and `/api/v1/manpages/<name>[/<section>]`,
   - via MCP `search_manpages`.
5. **Core-OS pages** (zfs, svcadm, dtrace, zoneadm…) come from the illumos gate.
   Those are published by the build team as a dedicated docs package — if a core
   command is missing, that's a corpus gap to raise, not something to hand-add.

Non-man docs (`share/info`, `share/doc`) use the same mechanism with `has_docs=y`.