# \#docs

**URL:** https://discuss.ocaml.org/tag/docs/143.md

[Latest](https://discuss.ocaml.org/latest.md) · [Categories](https://discuss.ocaml.org/categories.md) · [Tags](https://discuss.ocaml.org/tags.md)

---

## [v3.OCaml.org: A roadmap for OCaml's online presence](https://discuss.ocaml.org/t/v3-ocaml-org-a-roadmap-for-ocamls-online-presence/8368)

<div class="topic-metadata">

**Author:** [@avsm](https://discuss.ocaml.org/u/avsm)\
**Replies:** 31\
**Last updated:** [June 10, 2022, 5:52pm UTC](https://discuss.ocaml.org/t/v3-ocaml-org-a-roadmap-for-ocamls-online-presence/8368 "2022-06-10T17:52:12Z")

</div>

The current (“v2”) ocaml.org website was written a decade ago (presentation) and – while it has served us well – its age is showing as our community has grown. To put things in context, the opam package manager didn’t a…

---

## [Documentation for OPAM packages?](https://discuss.ocaml.org/t/documentation-for-opam-packages/1289)

<div class="topic-metadata">

**Author:** [@perry](https://discuss.ocaml.org/u/perry)\
**Replies:** 7\
**Last updated:** [December 28, 2017, 2:24pm UTC](https://discuss.ocaml.org/t/documentation-for-opam-packages/1289 "2017-12-28T14:24:17Z")

</div>

For a number of packages I’ve been using via opam, I’ve been manually reading the documentation comments in the .mli files on github or the like. It only now occurred to me that this is somewhat strange — that is to say…