On Tue, Sep 25, 2018 at 12:04 PM Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > > This is interesting, because there's a conflict between using the > "stable" and current "master" branches in our docs — a lot of > documentation changes are actually general improvements which apply to > all our live releases, not just the master branch they go in on. The "version switching" I've seen in other documentation sites take the user to the functional/topic page in the context of the other version. I've never really thought about it, but now that you point out this concern, I realize that I instinctively use those "you are not on the freshest version" visual cues to get to something that is presumably the most up-to-date. Maybe that is one way to avoid an explosion of general doc backports, other than critical ones.tin
