-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Update RTD to include multiple versions of Lumino #336
Comments
I need to familiarize myself more with Read the Docs, so I'm willing to try to figure out how to
But I don't think I have enough of the big picture of Lumino to make content/copy changes and contributions here. |
Don't worry, the content for now is all contained within doc strings, so if you can generate an RTD page that shows the API documentation for the current version and the previous version, we are good. |
@gabalafou, what is your ReadTheDocs username? |
I didn't have a Read the Docs username before, but it is now the same as my GitHub username: gabalafou. |
Great, you should have an invite now! |
With #354 merged, I went ahead and made the following changes in the Read The Docs settings:
I discussed the desired final config with @afshin on Tuesday, and the above changes reflect that conversation. He said that he envisioned just two RTD versions: 1.x and latest. You should now be able to see all of these changes (RTD settings plus code changes from #354) at https://lumino.readthedocs.io. Therefore, I'm going to close this issue for now. |
Oh, I almost forgot: a few things before we completely move on from this issue. I created several follow-up issues from this work:
|
I would prefer to keep it. It is a good practice to provide a default endpoint that people can bookmark. |
@afshin can you respond to @fcollonval's comment above? I was just following your guidance when setting up RTD to just have Reminder that |
|
The Lumino
readthedocs.io
site should support both Lumino 1 and Lumino 2 docs and needs a re-visit for maintenance.The text was updated successfully, but these errors were encountered: