OCaml’s centrally-generated documentation site, ocaml.org, serves API documentation for almost every opam package, complete with rendered source, type-aware search and cross- package links. Locally, however, documentation remains sec- ond class: building the docs for a project and its dependencies requires slow, non-incremental tooling that must rediscover information the build system already had. We propose a sim- ple change with far-reaching consequences: each package should build and install its own odoc files, just as it installs its compiled artifacts today. This removes the discovery problem that complicates every existing documentation driver, and makes first-class experiences straightforward to build: docu- mentation available on install, fast incremental rebuilds with actionable errors in the IDE, CI checks for broken docs, and local search. We survey the current documentation pipeline, describe the challenges facing per-package build rules, and outline a migration path, including an opam-hook-based emulation that is usable today.