post-processing: update and expand docs #668
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-rapids-ai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
bdice
approved these changes
Aug 13, 2025
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
ajschmidt8
approved these changes
Aug 13, 2025
Member
Author
|
Thanks! @AyodeAwe if you see anything that looks incorrect or that you want more information on, let me know and I'd be happy to do a follow-up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
API documentation for RAPIDS projects are built in those projects' CI and uploaded to an S3 bucket.
CI in this repo then downloads those files and does some post-processing to integrate them into the rest of the docs site, resulting in this page: https://docs.rapids.ai/api/
I've been making some changes to the process recently, and @AyodeAwe asked if I could update / expand the docs on how everything fits together: #664 (comment)
This PR has those docs updates.