-
Notifications
You must be signed in to change notification settings - Fork 13
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
Deprecation: Removal of Sphinx context injection at build time #216
Comments
I read thru the "Read the Docs Addons enabled by default" blog post just now. Some notes:
|
The changes upstream have caused our docs to start rendering with a floating flyout instead of a fixed docs info/version switcher. |
I updated the task list with everything that @tsibley has uncovered so far. The list seems to be comprehensive, based on my reading of the blog post and sphinx-rtd-theme 3.0.0 changes. |
I considered keeping the new floating flyout – on wide screens, it makes use of the extra space on the right side of the docs and allows for more sidebar content to be shown. But on narrower screens, it covers our actual docs. Covering sidebar content is probably a better trade-off across screen sizes? |
The floating flyout drives me batty, as it's continually in the way. Would definitely prefer to keep it in the sidebar. |
Restoring the sidebar flyout is not as simple as setting Here's an example showing why it doesn't work with nextstrain/sphinx-theme@572d534 + disabling the flyout addon (I'll fix this after we settle on a solution for other projects): Go to the PR build and use the flyout to switch to an older version. The older version no longer has a flyout. |
Given that the new flyout addon is floating-only and can only be disabled per project (not per version), these are our options:
Seems like we may have to stick with the floating flyout. |
@victorlin Gah. Rebuilding old versions, while doable in theory, is likely in practice to cause other issues. The per-project limitation is really hamstringing us here. There's discussion of that limitation and related ones (e.g. no reproducible builds) being an issue in readthedocs/addons#51, but nothing brought up there was addressed before this big addons change got pushed thru. |
Thank you for following up 🙏 |
There's one stupid thing we could do… |
Another issue with the new addons is the search switcheroo which now doesn't search subprojects by default (unlike the old search): The search results now also lack search term highlighting, and I, at least, find the search modal results much less useful and information-dense than the previous results page. Sigh. Adding to this, the old cross-project search is intentionally disabled, so disabling the new search addon doesn't even restore the previous functionality: it reverts to more limited search functionality we never used (Sphinx's built in). Double sigh. |
Looks like this is the direction we may be headed after all…? Oy vey. |
Brief summary from email:
Tasks
In our base theme (nextstrain-sphinx-theme) or across individual docs projects:
READTHEDOCS
tohtml_context
(GitHub search)display_version
withversion_selector
(GitHub search)The text was updated successfully, but these errors were encountered: