Thicket data repository for the EEG
anil.recoil.org
1{
2 "id": "https://jon.recoil.org/blog/2025/04/this-site.html",
3 "title": "This site",
4 "link": "https://jon.recoil.org/blog/2025/04/this-site.html",
5 "updated": "2025-04-07T00:00:00",
6 "published": "2025-04-07T00:00:00",
7 "summary": "Summary",
8 "content": "<h1><a href=\"#this-site\"></a>This site</h1><ul><li><span>libs</span> <p>mime_printer</p></li></ul><ul><li><span>published</span> <p>2025-04-07</p></li></ul><p>I've spent a <em>lot</em> of time over the past few years working on Odoc, the OCaml documentation generator, so when it came time to (re)start my own website and blog, I found it hard to resist thinking about how I might use odoc as part of it. We've spent a lot of time recently trying to make odoc more able to generate structured documentation sites, so I've gone all in and am trialling using it as a tool to generate my entire site. This is a bit of an experiment, and I don't know how well it will work out, but let's see how it goes.</p><p>Additionally, I've recently been working on a project currently called <code>odoc_notebook</code>, which is a set of tools to allow odoc <code>mld</code> files to be used as a sort of Jupyter-style notebook. The idea is that you can write both text and code in the same file, and then run the code in the notebook interactively. Since I've only got a webserver, all the execution of code has to be done client side, so I'm making extensive use of the phenomenal <a href=\"https://github.com/ocsigen/js_of_ocaml\">Js_of_ocaml</a> project to get an OCaml engine running in the browser.</p><p>My focus has initially been on getting 'toplevel-style' code execution working. As an example, let's write a little demo.</p><p>Continue reading <a href=\"https://jon.recoil.org/blog/2025/04/this-site.html\">here</a></p>",
9 "content_type": "html",
10 "author": {
11 "name": "Jon Ludlam",
12 "email": null,
13 "uri": "https://jon.recoil.org/"
14 },
15 "categories": [],
16 "source": "https://jon.recoil.org/atom.xml"
17}