- I've tried to minimize the number of "clicks" to get to some value by inlining submodules as much as possible (that's actually most of the code of the plugin)
- the "frame" that appears when mouse-overing some piece of documentation was initially for debugging but I kinda liked it, so it's still there.
More stuff could be done:
- the links to the code of function go to a page containing *only* the code of that function, it would be nice to point to a specific line of the whole ".ml", so that one can see the context and other functions/types
- using "with sexp" in the mli files messes ocamldoc up (it's not the plugin, it happens everywhere), so for now one has to write the "val sexp_of_t ... val t_of_sexp", it would be cool to have a nice general solution for boilerplate code.