Skip to content

[FR] Ability to link to externally hosted documentation versions from the version flyout #7526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
prashantmital opened this issue Oct 1, 2020 · 1 comment
Labels
Feature New feature Needed: design decision A core team decision is required

Comments

@prashantmital
Copy link

prashantmital commented Oct 1, 2020

Details

Older documentation versions for this package can no longer be built. Instead, we relied on the redirects feature to redirect users to https://api.mongodb.com/python/x.y.z/ when x.y.z < 3.5.1. These versions used to show up in the version picker flyout after they were 'activated' even if the build failed. In #6971 the behavior changed to only show versions with successful builds in the flyout which means that readers of the documentation must now manually edit the version in the URL to see legacy docs (as the redirects still work).

The need to redirect users to external resources hosting legacy versions of a package's documentation is a legitimate and common use case (see also #6137 (comment)). It will be especially helpful as users transition to using ReadTheDocs for hosting their docs from some other service. Consequently, there should be a way to customize the versions that show up in the version picker flyout to support this use-case. Instead of showing versions with failing builds, maybe you could allow users to specify a mapping of version names to external URLs.

Expected Result

A description of what you wanted to happen

Actual Result

A description of what actually happened

@stsewd stsewd added Feature New feature Needed: design decision A core team decision is required labels Oct 1, 2020
@stsewd
Copy link
Member

stsewd commented Dec 10, 2020

As explained in #7732 (comment) a better solution is to allow users to manipulate the version selector itself with data from the api.

@stsewd stsewd closed this as completed Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

2 participants