-
Notifications
You must be signed in to change notification settings - Fork 284
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
Docs Revamp: Models documentation #117
Conversation
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.
Did a first pass and it looks great! I'll come back to this in a little bit once I've had some time to reflect and process everything :)
docs/hub/models-the-hub.md
Outdated
|
||
## Libraries | ||
|
||
The Hub supports many libraries, and we're working on expanding this support! We're happy to welcome to the Hub a set of Open Source libraries that are pushing Machine Learning forward. |
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 think this could be a little clearer if we briefly describe how the Hub supports third-party libraries. For example, you could say something like:
Integrating the huggingface_hub
library into your projects allows users to interact with the Hub directly from your library.
|
||
## Creating a Widget | ||
|
||
A widget is automatically created for your model when you upload it to the Hub. To determine which pipeline and widget to display (`text-classification`, `token-classification`, `translation`, etc.), we analyze information in the repo, such as the metadata provided in the model card and configuration files. This information is mapped to a single `pipeline_tag`. We choose to expose **only one** widget per model for simplicity. |
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.
Maybe link to the model-cards page so users can see where this is all controlled?
Co-authored-by: Steven Liu <[email protected]>
Add content for models, and move deprecated content to its own folder (for dev purposes). Co-authored-by: Steven Liu <[email protected]>
for the assets (screenshots), if possible upload some higher-resolution ones. Here they're a bit blurry on retina screens cc @gary149 |
(you can pass them through tinypng.com before adding them to the repo if the files are too heavy |
- [Model Cards](./models-cards) | ||
- [CO<sub>2</sub> emissions](./models-cards-co2) | ||
- [Tasks](./models-tasks) | ||
- [Interacting with models on the Hub](./models-interacting) |
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.
Interacting with models
sounds vague to me, WDYT of changing to something like downloading and uploading models to/from the hub
?
or even split into download
and upload
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.
Sounds good to me! I put that in my to-do list for the final polishing pass :)
Add content for models, and move deprecated content to its own folder (for dev purposes). Co-authored-by: Steven Liu <[email protected]>
Add content for models, and move deprecated content to its own folder (for dev purposes). Co-authored-by: Steven Liu <[email protected]>
Add content for models, and move deprecated content to its own folder (for dev purposes). Co-authored-by: Steven Liu <[email protected]>
* Docs Revamp: Models documentation (#117) Add content for models, and move deprecated content to its own folder (for dev purposes). Co-authored-by: Steven Liu <[email protected]> * [Spaces] Changelog update * Update docs/hub/spaces-changelog.md Co-authored-by: Julien Chaumond <[email protected]> * Update docs/hub/spaces-changelog.md Co-authored-by: Julien Chaumond <[email protected]> * Update docs/hub/spaces-changelog.md Co-authored-by: Omar Sanseviero <[email protected]> * Update docs/hub/spaces-changelog.md Co-authored-by: Omar Sanseviero <[email protected]> * Update docs/hub/spaces-changelog.md Co-authored-by: Omar Sanseviero <[email protected]> * Update docs/hub/spaces-changelog.md Co-authored-by: Omar Sanseviero <[email protected]> * Update docs/hub/spaces-changelog.md Co-authored-by: Omar Sanseviero <[email protected]> * Misc changes * Fix rebase mistakes * Fix merge conflict Co-authored-by: Nima Boscarino <[email protected]> Co-authored-by: Steven Liu <[email protected]> Co-authored-by: Julien Chaumond <[email protected]> Co-authored-by: Omar Sanseviero <[email protected]> Co-authored-by: Nima Boscarino <[email protected]>
Add content for models, and move deprecated content to its own folder (for dev purposes). Co-authored-by: Steven Liu <[email protected]>
* Docs Revamp: Models documentation (#117) Add content for models, and move deprecated content to its own folder (for dev purposes). Co-authored-by: Steven Liu <[email protected]> * split Repo licenses into its own page * Some initial doc about pull-requests and discussions Co-authored-by: Nima Boscarino <[email protected]> Co-authored-by: Steven Liu <[email protected]>
This PR migrates content (and introduces some new content) to form a "Models" section, with several subsections. The scope of this section is to help readers understand how to find, use, upload, and manage models on the Hub.
Anything that's specifically about using
huggingface_hub
is omitted from this section. I'm sure there are other ways to structure the hierarchy of the content in this section, so let me know if you have any ideas!Note: Images have been uploaded to the repo here, but will be moved to the documentation-images dataset repo in a future PR (I'll do all the images all at once). Also, most headings have not been renamed. If we want to go with simpler headings (i.e. from this convo #62 (comment)) then I figured that could happen in a separate PR, where all the headings in the docs get redone at the same time to ensure consistency.