Model registry docs consolidation

[dberenbaum]

This is an attempt to rework the docs in response to feedback that it's confusing and makes it hard to get started with our tools. I started with model registry because it's more limited than trying to redo experiments or data management.

The goal is to address a few different issues:

• Improve MR onboarding
• Try out a style more like a quickstart
• Consolidate docs across products
• Reduce duplication

The PR drops the two model registry overview pages in the Studio docs:

• https://dvc.org/doc/studio/model-registry
• https://dvc.org/doc/studio/user-guide/model-registry

The content was integrated into other pages (often it was already in other pages). The idea is to have high-level docs in one place and product-specific docs only for detailed guides/reference.

[github-actions[bot]]

Link Check Report

There were no links to check!

[dberenbaum]

@yathomasi Heroku is throwing an error:

 !     Compiled slug size: 1.4G is too large (max is 500M).
 !     See: http://devcenter.heroku.com/articles/slug-size
 !     Push failed

Any ideas how to fix it? Can adding static files to the static repo (see https://github.com/iterative/dvc.org/issues/4837) help?

[yathomasi]

Any ideas how to fix it?

I see it didn't run the gatsby build command at all so ended with huge size of node modules and cache.

I have retriggered the build manually and hope it will be fixed. ICYMI: there is a Manual deploy section in Deploy tab

UPD: Deployed successfully.

[tapadipti]

I'd added these 2 redirects, but they seem to be not working when I run this locally:

  "^/doc/start/model-management/model-registry$                                           /doc/start/model-registry/manage-models",
  "^/doc/start/model-management(/.*)?$                                                    /doc/start/model-registry$1",

Not sure what is wrong. @yathomasi any suggestions?

Other than this, LGTM.

[yathomasi]

It seems to be working with preview deployment so we should be fine to merge. BTW, the second rule would cover the first one as well.

https://dvc-org-start-add-model-crakny.herokuapp.com/doc/start/model-management/model-registry -> https://dvc-org-start-add-model-crakny.herokuapp.com/doc/start/model-registry/manage-models

https://dvc-org-start-add-model-crakny.herokuapp.com/doc/start/model-management/test -> https://dvc-org-start-add-model-crakny.herokuapp.com/doc/start/model-registry/test

I would suggest running build mode with yarn build and then run yarn start to test the redirects.

We did have it integrated for development mode with yarn develop, but it might be broken and we are okay with that as redirect logic is little separate from the gatsby project itself.

[tapadipti]

Thanks @yathomasi

BTW, the second rule would cover the first one as well.

Probably not, coz in the first one, the sub-page is also different: model-management/model-registry redirects to model-registry/manage-models