-
Notifications
You must be signed in to change notification settings - Fork 96
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
Moving documentation to docs.rapids.ai #579
Comments
Opened #580 to make a gpuCI docs build script. |
Redirecting seems like a simpler way to deal with it. |
I agree, just wasn't sure if RTD had the ability to easily manage a redirect but looks like it can. |
Adds a docs build script for gpuCI to execute on merges; addresses #579. Depends on rapidsai/integration#250 cc @quasiben Authors: - Charles Blackmon-Luca (https://github.com/charlesbluca) Approvers: - Dillon Cullinan (https://github.com/dillon-cullinan) URL: #580
This issue has been labeled |
Dask-CUDA's docs just got published to RAPIDS docs: Now we would just want to figure out redirecting the RTD version of the docs. |
In conda-forge we did this like so |
Great - thanks for that example! Do you know if we would need to keep that |
Peter was mentioning redirecting, which agree probably makes sense (there may be other links to RTD out there). So the |
Taking @jakirkham's [suggestion](#579 (comment)) for handling RTD redirects to an external site. Authors: - Charles Blackmon-Luca (https://github.com/charlesbluca) Approvers: - Peter Andreas Entschev (https://github.com/pentschev) - https://github.com/jakirkham URL: #615
With #615 merged, looks like the redirect is working and the docs migration is complete 😄 thanks for the help @jakirkham @pentschev! |
After some internal discussion, we have decided to move the documentation of Dask-CUDA from Read the Docs to RAPIDS Docs. This would make it relatively easy to set up a docs CI workflow script like this, and is motivated by the fact that there are a lot of barriers keeping this repo from migrating to Dask org.
What's a clean way to do this without causing confusion? Should we keep both sites up simultaneously for a period of time with some banner notifying the migration? Or have the RTD docs redirect straight to the RAPIDS docs?
cc @quasiben @pentschev
The text was updated successfully, but these errors were encountered: