Documentation in dune is done courtesy of the odoc tool. Therefore, to generate documentation in dune, you will need to install this tool. This should likely be done with opam:
$ opam install odoc
Documentation comments will be automatically extracted from your OCaml source
files following the syntax described in the the section
Text formatting of
the OCaml manual.
Additional documentation pages may by attached to a package can be attached using the Documentation Stanza.
Building the documentation using the
@doc alias. Hence, all that is required
to generate documentation for your project is building this alias:
$ dune build @doc
An index page containing links to all the opam packages in your project can be found in:
$ open _build/default/_doc/_html/index.html
Documentation for private libraries may also be built with:
$ dune build @doc-private
But this libraries will not be in the main html listing above, since they do not
belong to any particular package. But the generated html will still be found in
Documentation pages will be automatically generated for from .ml and .mli files
that include ocamldoc fragments. Additional manual pages may be attached to
packages using the
documentation stanza. These .mld files must contain text
in the same syntax as ocamldoc comments.
(package <name>)the package this documentation should be attached to. If this absent, dune will try to infer it based on the location of the stanza.
<arg>field follows the Ordered set language. This is a set of extension-less, mld file base names that are attached to the package. Where
:standardrefers to all the
.mldfiles in the stanza’s directory.
index.mld file (specified as
mld_files) is treated
specially by dune. This will be the file used to generate the entry page for the
package. This is the page that will be linked from the main package listing. If
you omit writing an
index.mld, dune will generate one with the entry modules
for your package. But this generated will not be installed.
All mld files attached to a package will be included in the generated
.install file for that package, and hence will be installed by opam.
This stanza use attach all the .mld files in the current directory in a project with a single package.
This stanza will attach three mld files to package foo. The
mld files should
(documentation ((package foo) (mld_files (foo bar baz))))
This stanza will attach all mld files excluding
wip.mld in the current
directory to the inferred package:
(documentation ((mld_files (:standard \ wip))))