I really like the docs and version selecting provided by Graylog https://docs.graylog.org/en/3.2/
It says this on the bottom: Built with Sphinx <http://sphinx-doc.org/> using a theme <https://github.com/rtfd/sphinx_rtd_theme> provided by Read the Docs <https://readthedocs.org/>. I do not have any experience with Sphinx or Read the Docs. Here is the version selector and download menu: [image: Screen Shot 2020-05-04 at 8.21.52 AM.png] On Wed, Apr 29, 2020 at 11:30 AM Cassandra Targett <casstarg...@gmail.com> wrote: > > This design still has a minor annoyance that I have noted in the past: > > in the table of contents pane it is easy to open a subtree, but the > > only way to close it is to open another one. Obviously not a big > > deal. > > Thanks for pointing that out, it helped me find a big problem which was > that I used the wrong build of JQuery to support using the caret to > open/close the subtree. It should work now to open a subtree independently > of clicking the heading, and should also close the tree. > > I'll probably spend too much time researching how to widen the > > razor-thin scrollbar in the TOC panel, since it seems to be > > independent of the way I spent too much time fixing the browser's own > > inadequate scrollbar width. :-) Also, the thumb's color is so close to > > the surrounding color that it's really hard to see. And for some > > reason when I use the mouse wheel to scroll the TOC, when it gets to > > the top or the bottom the content pane starts scrolling instead, which > > is surprising and mildly inconvenient. Final picky point: the > > scrolling is *very* insensitive -- takes a lot of wheel motion to move > > the panel just a bit. > > I’m not totally following all of this, but if I assume you mean the left > sidebar navigation (and not an in-page TOC) then my answer to at least part > of it is to pare down the list of top-level topics so you don’t have to > scroll it at all and then the only scrolling you need to do is for the > content itself. That’s what I want to do in Phase 2, so there are several > things in the behavior of the sidebar I’m purposely ignoring for now. Some > will go away with a new organization and new things will be introduced that > will need to be fixed, so to save myself some time I’m waiting to fix all > of it at once. >