{
  "id": "https://jon.recoil.org/blog/2025/04/odoc-3.html",
  "title": "Odoc 3: So what?",
  "link": "https://jon.recoil.org/blog/2025/04/odoc-3.html",
  "updated": "2025-04-25T00:00:00",
  "published": "2025-04-25T00:00:00",
  "summary": "Summary",
  "content": "<h1><a href=\"#odoc-3:-so-what?\"></a>Odoc 3: So what?</h1><ul><li><span>published</span> <p>2025-04-25</p></li></ul><p>Odoc 3 was <a href=\"https://discuss.ocaml.org/t/ann-odoc-3-0-released/16339\">released last month</a> and although we did write a list of the new features, I don't think we've made it clear enough why anyone should care.</p><p>It's <b>manuals</b>, the theme of Odoc 3 is <b>manuals</b>. It's got a load of features to make it much better for writing <code>mld</code> pages (files written using odoc's markup) to document your packages and their relationship to the surrounding ecosystem. Previous versions of Odoc were very library-centric, in that while we did have mld-file support, most of the effort went into making sure that we were generating correct per-module pages, which show the shape of your API even if you've not put in any doc comments at all. We've still got that, obviously, but we've added many features to make write <code>mld</code> pages far more useful, and we're really hoping that these will draw people in to make documenting packages a much more enjoyable experience.</p><p>Continue reading <a href=\"https://jon.recoil.org/blog/2025/04/odoc-3.html\">here</a></p>",
  "content_type": "html",
  "author": {
    "name": "Jon Ludlam",
    "email": null,
    "uri": "https://jon.recoil.org/"
  },
  "categories": [],
  "source": "https://jon.recoil.org/atom.xml"
}