Global navigation bar

[TheLortex]

Supersedes #48

Now that voodoo generates a package.json file for each project containing the module map, we can implement a global navigation bar.

The first commit parses the package.json, the second commit use the data structure to generate a navigation bar in the side panel along with the table of contents.

This is a first iteration as a proof of concept, work on the design is needed. Moreover I had to remove the fixed class because the two sidebars were overlapping and were too long in any case (fixed disable scrolling).

Here is how it looks for the index page

Unfolded to the current module:

[tmattio]

Thanks a lot for your work on this!

This LGTM overall - with some documentation for the added functions/modules, this is good to go I think!

[TheLortex]

@tmattio I've added a commit with the interface change. Personally I prefer the original version because the usage is more concise: the interface change requires to transform a lot of Module_map.xxx into Module_map.Module.Map.xxx.

[tmattio]

Personally I prefer the original version because the usage is more concise: the interface change requires to transform a lot of Module_map.xxx into Module_map.Module.Map.xxx

I was expecting the toplevel module to become Module, so calls to Module_map.xxx would become Module.Map.xxx. But if the approach doesn't work well in practice, feel free to revert back to Module_map, I meant it as a suggestion, it's not blocking in any way 🙂

[TheLortex]

Ah yes okay I finally get it. I think the Module name is too generic and might refer to other things in the future.
Here Module.t refers to the information we obtain from the module map (package.json). We could imagine other kinds Module.t (for example data extracted from an odoc file) so it makes sense to wrap it in the context of Module_map.

[tmattio]

LGTM, thanks @TheLortex, this is going to improve the navigation of packages documentation a lot!