-
Notifications
You must be signed in to change notification settings - Fork 118
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
Central API Docs #1041
base: main
Are you sure you want to change the base?
Central API Docs #1041
Changes from 3 commits
51e368b
af70516
ab6e416
ab94230
23ba7d3
205a8c8
216fed0
d0d0c97
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
API Documentation | ||
===================== | ||
|
||
NVIDIA Merlin is an open source framework. It consists a collection of libraries, designed to integrate well together. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -61,14 +61,49 @@ commands = | |
; Generates documentation with sphinx. There are other steps in the Github Actions workflow | ||
; to publish the documentation on release. | ||
changedir = {toxinidir} | ||
deps = -rdocs/requirements-doc.txt | ||
deps = | ||
-rdocs/requirements-doc.txt | ||
tensorflow | ||
torch | ||
torchmetrics | ||
git+https://github.com/NVIDIA-Merlin/core.git | ||
git+https://github.com/NVIDIA-Merlin/dataloader.git | ||
git+https://github.com/NVIDIA-Merlin/models.git | ||
git+https://github.com/NVIDIA-Merlin/NVTabular.git | ||
git+https://github.com/NVIDIA-Merlin/systems.git | ||
git+https://github.com/NVIDIA-Merlin/Transformers4Rec.git | ||
|
||
allowlist_externals = | ||
git | ||
cp | ||
commands = | ||
git clone --depth 1 https://github.com/NVIDIA-Merlin/core.git ./docs/core | ||
cp -r ./docs/core/docs/source/api ./docs/source/api_core/ | ||
git clone --depth 1 https://github.com/NVIDIA-Merlin/dataloader.git ./docs/dataloader | ||
cp ./docs/dataloader/docs/source/api.rst ./docs/source/api_dataloader.rst | ||
git clone --depth 1 https://github.com/NVIDIA-Merlin/models.git ./docs/models | ||
cp ./docs/models/docs/source/api.rst ./docs/source/api_models.rst | ||
git clone --depth 1 https://github.com/NVIDIA-Merlin/NVTabular.git ./docs/NVTabular | ||
cp ./docs/NVTabular/docs/source/api.rst ./docs/source/api_nvtabular.rst | ||
git clone --depth 1 https://github.com/NVIDIA-Merlin/systems.git ./docs/systems | ||
cp ./docs/systems/docs/source/api.rst ./docs/source/api_systems.rst | ||
git clone --depth 1 https://github.com/NVIDIA-Merlin/Transformers4Rec.git ./docs/Transformers4Rec | ||
cp -r ./docs/Transformers4Rec/docs/source/api ./docs/source/api_transformers4rec/ | ||
python -m sphinx.cmd.build -E -P -b html docs/source docs/build/html | ||
Comment on lines
+66
to
82
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If The only alternative that I'd consider is using one of the containers because the containers already have the tagged source in the container. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I wasn't sure if the documentation is build inside a container - in addition, I want to pull the latest documentation code from every repository |
||
|
||
|
||
[testenv:docs-multi] | ||
; Run the multi-version build that is shown on GitHub Pages. | ||
changedir = {toxinidir} | ||
deps = -rdocs/requirements-doc.txt | ||
deps = | ||
-rdocs/requirements-doc.txt | ||
git+https://github.com/NVIDIA-Merlin/models.git | ||
git+https://github.com/NVIDIA-Merlin/NVTabular.git | ||
git+https://github.com/NVIDIA-Merlin/core.git | ||
git+https://github.com/NVIDIA-Merlin/systems.git | ||
git+https://github.com/NVIDIA-Merlin/dataloader.git | ||
allowlist_externals = | ||
git clone https://github.com/NVIDIA-Merlin/core.git | ||
commands = | ||
sphinx-multiversion --dump-metadata docs/source docs/build/html | jq "keys" | ||
sphinx-multiversion docs/source docs/build/html | ||
sphinx-multiversion docs/source docs/build/html |
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.
The docs become a little dense with this all under one TOC item. If you are open to experimenting, consider creating another
caption
like line 3 with "API Documentation" or "Merlin API" or something along those lines.Centralizing the API is certainly better than how I left it, but I'm also wondering if adding titles would help the reader choose the correct API rather than browse.
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 feel the structure looks easy to follow - it is structured in the way how we would import Classes, functions or modules
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.
It might still be nice to organize the packages into themes or something though, because I suspect this makes the most sense to people who are already familiar with what's in each sub-package (e.g. people on the Merlin team.)
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.
@karlhigley do you have a suggestions? I thought organizing it by import statements is the way a user will search for API documentation?
If I want to know something about ColumnsSelector, I know it is in merlin.schema and I will look there first?