Skip to content

docs(FR-2623): reorganize admin model serving docs and remove clone references#6844

Open
agatha197 wants to merge 1 commit into04-21-docs_fr-2603_add_health_check_svg_diagrams_for_all_4_languages_replace_ascii_artfrom
04-21-docs_fr-2623_reorganize_admin_model_serving_docs_and_remove_clone_references
Open

docs(FR-2623): reorganize admin model serving docs and remove clone references#6844
agatha197 wants to merge 1 commit into04-21-docs_fr-2603_add_health_check_svg_diagrams_for_all_4_languages_replace_ascii_artfrom
04-21-docs_fr-2623_reorganize_admin_model_serving_docs_and_remove_clone_references

Conversation

@agatha197
Copy link
Copy Markdown
Contributor

@agatha197 agatha197 commented Apr 21, 2026

Resolves #6843 (FR-2623)

Summary

  • Moved Admin features (Admin Serving Page, Admin Model Store Management) from model_serving.md to admin_menu.md across all 4 languages — admin-only content now lives in the Admin Menu section where it belongs.
  • Removed all clone-related content from admin_menu.md and model_serving.md (Clone to Folder, Create Service from This Model, Cloning a Model). The clone feature is no longer provided by the product.
  • Rewrote the model-definition.yaml description as an advanced configuration option for the Custom runtime variant during serving. The old wording incorrectly implied that uploading the file creates a model card; model cards are now managed via the Admin UI backed by the database.
  • Removed the stale old Model Store Page section along with the model_card_added.png reference.
  • Kept the Cloneable field in vfolder.md — it is still a real field in the vfolder creation modal.

Test Plan

  • Verify admin_menu.md renders correctly with the new Admin Features section in en/ko/ja/th
  • Verify model_serving.md no longer references clone or admin-only features in en/ko/ja/th
  • Verify the vfolder.md Cloneable field documentation is intact in en/ko/ja/th
  • Rebuild the PDF locally and spot-check the reorganized pages

Copy link
Copy Markdown
Contributor Author

agatha197 commented Apr 21, 2026

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • flow:merge-queue - adds this PR to the back of the merge queue
  • flow:hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@agatha197 agatha197 marked this pull request as ready for review April 21, 2026 13:18
@agatha197 agatha197 review requested due to automatic review settings April 21, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant