Skip to content
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

Figure out how to make docs of cuda.core and cuda.bindings coexist #94

Closed
leofang opened this issue Sep 10, 2024 · 3 comments · Fixed by #165
Closed

Figure out how to make docs of cuda.core and cuda.bindings coexist #94

leofang opened this issue Sep 10, 2024 · 3 comments · Fixed by #165
Assignees
Labels
cuda.core Everything related to the cuda.core module documentation Improvements or additions to documentation P0 High priority - Must do!

Comments

@leofang
Copy link
Member

leofang commented Sep 10, 2024

Main question: Do we want to the same project docs with cuda.core (#70) & cuda.bindings (#75) coexist say under separate tabs or pages, or do we want each namespace package to have their own doc pages (similar to cuda.{parallel,cooperative})?

@github-actions github-actions bot added the triage Needs the team's attention label Sep 10, 2024
@leofang
Copy link
Member Author

leofang commented Sep 10, 2024

cc: @aterrel in case you have thoughts

@leofang leofang added documentation Improvements or additions to documentation P0 High priority - Must do! cuda.py EA and removed triage Needs the team's attention labels Sep 10, 2024
@bryevdv
Copy link
Collaborator

bryevdv commented Sep 11, 2024

These are separately published / installable packages, is that correct? If so my offhand suggestion is separate docs pages, so that e.g. the PyPI project pages, etc. can have unique landing targets for docs for each.

@leofang
Copy link
Member Author

leofang commented Sep 16, 2024

Yes, the intent is to have separate packages (eventually, see #105). I also like the separate page idea. One minor concern I have is if this could cause confusion to the branding, since what I had in mind was that all packages we publish should be considered as components of CUDA Python. It's just that users have the freedom to install only the components that they need.

@leofang leofang changed the title Figure out how to make docs of cuda.py and cuda.bindings coexist Figure out how to make docs of cuda.core and cuda.bindings coexist Oct 9, 2024
@leofang leofang added the cuda.core Everything related to the cuda.core module label Oct 10, 2024
@leofang leofang self-assigned this Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cuda.core Everything related to the cuda.core module documentation Improvements or additions to documentation P0 High priority - Must do!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants