-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Docs: split user and dev docs #8751
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
Conversation
5ad9935
to
efb0714
Compare
If I understand correctly, a single |
yeah, hopefully in the future we can use individual rtd config files (mostly to have different search ranking/ignore for each one). This was Anthony's idea actually :D Test are failing because https://dev.readthedocs.io/en/stable/ has the contents from master instead of the new content, it will have the new content after this PR is merged (and we push a tag, since intersphinx is pointing to "stable", could also point it to latest till we do another release). Previews at: Redirects are in place. |
@@ -66,6 +96,8 @@ def get_version(): | |||
'jupyterbook': ('https://jupyterbook.org/', None), | |||
'myst-parser': ('https://myst-parser.readthedocs.io/en/v0.15.1/', None), | |||
'rst-to-myst': ('https://rst-to-myst.readthedocs.io/en/stable/', None), | |||
'rtd': ('https://docs.readthedocs.io/en/stable/', None), | |||
'rtd-dev': ('https://dev.readthedocs.io/en/stable/', None), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Locally I'm testing this with
'rtd-dev': ('https://dev.readthedocs.io/en/stable/', None), | |
'rtd-dev': ('https://dev.readthedocs.io/en/separate-dev-docs/', None), |
@astrojuanlu we could do that, I was also thinking we could have a different logo. We may need help from @readthedocs/frontend for these visual changes :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave this a brief look and it all looks correct. I think it's easier to merge and then fix whatever breaks, since it will keep having conflicts all the time.
I will try to take care of this PR next week.
Agreed, this looks good to me, so lets move forward with it. The redirects are the main thing. |
Merging, and fixing tests later 👍 |
Looks like @stsewd already created the redirects, and they're working 🎉 |
This splits the docs in two, one set container user-facing documentation, and the other one containing development documentation. The structure is like
The user facing docs will be served from https://docs.readthedocs.io/ (just as they are today), and the dev docs will be served from https://dev.readthedocs.io/.
To build each docset you need to set the
RTD_DOCSET
env var (defaults to the user documentation), docs have been updated to mention this, there is also some explanation on the conf.py file.I'm not really sure what will happen with the localization strings (I left them in the docs/user dir)