Alfredo, If we were to resurrect this feature, I'm wondering about methods for making sure it doesn't fall out of date. Since the master branch is always being re-built, if we can extract as part of the doc build process a list of versions from a data source that is always up-to-date (i dunno where this is, but maybe something like src/include/rados.h ?). This extracted version list could then be published as a json file along with the rest of the master branch documentation at a fixed URL: https://docs.ceph.com/master/versions.json and then have the version selector javascript widget just load that file. Would this perhaps resolve the issue? On Tue, Sep 25, 2018 at 4:34 AM Alfredo Deza <adeza@xxxxxxxxxx> wrote: > > One thing we had that was useful was a menu at the bottom (similar to > what ReadTheDocs sites have) that would: > > * allow you to quickly move to a different version > * inform you of what version you are looking at > > It got removed because it fell out of date. It required updates once > releases were done: > > http://tracker.ceph.com/issues/18075 > On Mon, Sep 24, 2018 at 7:48 PM Noah Watkins <noahwatkins@xxxxxxxxx> wrote: > > > > I was googling this morning for random ceph terminology, as one does, > > and noticed that the top 5 results often included some deep cuts like > > kraken/bobtail/giant etc... it'd be really nice to have some sort of > > visual cue about the freshness of the docs being viewed. > > > > Following up on Neha's comments from this morning's meeting regarding > > documentation improvements, Neha and I brainstormed some ideas this > > afternoon and tossed them in an etherpad: > > > > https://pad.ceph.com/p/Ceph_Documentation > > > > Please feel free to add / edit / comment.
