Backward compatibility

[humitos]

How much backward compatibility we want to go?

There are bunch of things that are tied to Sphinx in our javascript code (e.g. rst-versions, is_alabaster_like_theme and others). I think that some of these stuffs should be moved to our Sphinx theme itself (e.g. disable default search when if READTHEDOCS) and there are some other stuffs we should stop supporting, I'd say.

[humitos]

From our last meeting, I understand that we want to re-design a lot of stuffs and the HTML structure, CSS classes and others will be different. We even talked about re-designing the flyout completely. We already started re-designing the external version warning in #18.

That said, I think it's fine to remove all the old code that it's there to support edge cases and old Sphinx/MkDocs versions. I'd like to simplify as much as we can the new code removing backward compatibility and starting "fresh", if that's possible. New projects will want to opt-in into the new javascript client because it's gonna be awesome 😄

[humitos]

Lot of things have changed since I opened this issue. The flyout addons looks exactly the same as the old addon and users can opt-in into it now using https://beta.readthedocs.org/ and going to their project's settings.

We have everything from the old integration already implemented in the new addons. I'm closing this issue.