Model registry docs

[dberenbaum]

Report

Update the model registry docs to combine all the products (GTO, DVC, Studio) into a coherent workflow and lead DVC users to this workflow. Some possible places to update:

• Explain artifacts section in https://dvc.org/doc/user-guide/project-structure/dvcyaml-files
• Explain in https://dvc.org/doc/dvclive/api-reference/live/log_artifact
• Explain in https://dvc.org/doc/dvclive/how-it-works#track-large-artifacts-with-dvc
• https://mlem.ai/doc/gto/ (see WIP: Docs draft for integration with DVC iterative/mlem.ai#323)
• https://dvc.org/doc/studio/user-guide/model-registry/
• https://dvc.org/doc/studio/get-started#manage-models
• Mention in https://dvc.org/doc/start/experiments/experiment-versioning
• Mention in https://dvc.org/doc/user-guide/experiment-management
• Links in https://dvc.org/doc/use-cases/model-registry
• Update example repos Register models in the example repos to see them in the MR iterative/example-repos-dev#203
• Update get/import in https://dvc.org/doc/command-reference/get and https://dvc.org/doc/command-reference/import
• as discussed in Add API to add artifacts dvc#9345, providing good CI/CD examples is a priority
• Add log_artifact examples for at least the most popular frameworks in https://dvc.org/doc/dvclive/ml-frameworks

Thoughts @aguschin @tapadipti @shcheklein?

[shcheklein]

Yep, I like it. Two things come to my mind:

• It should be less about GTO and MLEM. Ideally we don't even mention them. Or only as a supportive tools that solve a very specific task inside, etc. It's not because I don't like them, etc. It's because I feel it's too complicated and confusing for users too have all of them at once in all those pages.
• I would prioritize some strong user story in the Studio docs - DVC and GTO both - are implementation details in this case.
• DVC Use case can include reference to Studio as well

[dberenbaum]

@aguschin Let's prioritize updating the DVC docs first so we have somewhere to point people with the "correct" usage today.

[dberenbaum]

We have a couple people asking about/waiting on docs in discord: https://discord.com/channels/485586884165107732/1096339522553384990/1096457228258652370

[tapadipti]

Sounds good @dberenbaum. In the Studio docs, we can restructure some of the content to unhighlight GTO, MLEM.

I would prioritize some strong user story in the Studio docs

@shcheklein Any suggestions on what user story to follow?

The current structure does follow user workflows: add models, register versions, assign stages, download files, and once we have the functionality - deploy models. Any suggestions on a better flow?

[shcheklein]

The missing part that can be useful - find the model with the right metrics before promoting / compare models.

[dberenbaum]

Need to consider where to keep GTO docs

[dberenbaum]

Added an item for https://dvc.org/doc/studio/get-started#manage-models

[dberenbaum]

Updated to reflect #4481. @aguschin Please update anything I missed.