docs(FR-2623): reorganize admin model serving docs and remove clone references#6844
Merged
graphite-app[bot] merged 1 commit intomainfrom Apr 22, 2026
Conversation
This was referenced Apr 21, 2026
Contributor
Author
3 tasks
7469bb2 to
36a0f74
Compare
a73d29b to
47657dd
Compare
Merge activity
|
47657dd to
5b25c38
Compare
graphite-app Bot
pushed a commit
that referenced
this pull request
Apr 22, 2026
…eferences (#6844) Resolves #6843 ([FR-2623](https://lablup.atlassian.net/browse/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 [FR-2623]: https://lablup.atlassian.net/browse/FR-2623?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
36a0f74 to
d09a116
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Reorganizes the Model Serving and Admin Menu documentation to move admin-only content into the Admin Menu section and remove deprecated clone-related guidance, while updating the model-definition.yaml description to reflect its current role in serving.
Changes:
- Moved “Admin Features” (Admin Serving + Model Store Management) out of
model_serving.mdand intoadmin_menu.mdacross en/ko/ja/th. - Removed clone-related documentation from Model Serving and Admin Menu pages across all languages.
- Reframed
model-definition.yamlas an advanced/optional configuration for theCustomruntime variant and removed stale “upload creates model card” wording and related screenshot references.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/backend.ai-webui-docs/src/en/model_serving/model_serving.md | Removes clone/admin-only sections from the user-facing Model Serving page. |
| packages/backend.ai-webui-docs/src/en/admin_menu/admin_menu.md | Adds Admin Features + revises Model Store/model-definition guidance; removes clone sections. |
| packages/backend.ai-webui-docs/src/ko/model_serving/model_serving.md | Removes clone/admin-only sections from the user-facing Model Serving page. |
| packages/backend.ai-webui-docs/src/ko/admin_menu/admin_menu.md | Adds Admin Features + revises Model Store/model-definition guidance; removes clone sections. |
| packages/backend.ai-webui-docs/src/ja/model_serving/model_serving.md | Removes clone/admin-only sections from the user-facing Model Serving page; minor label updates. |
| packages/backend.ai-webui-docs/src/ja/admin_menu/admin_menu.md | Adds Admin Features + revises Model Store/model-definition guidance; removes clone sections. |
| packages/backend.ai-webui-docs/src/th/model_serving/model_serving.md | Removes clone/admin-only sections from the user-facing Model Serving page; minor terminology/label updates. |
| packages/backend.ai-webui-docs/src/th/admin_menu/admin_menu.md | Adds Admin Features + revises Model Store/model-definition guidance; removes clone sections. |
Base automatically changed from
04-21-docs_fr-2603_add_health_check_svg_diagrams_for_all_4_languages_replace_ascii_art
to
main
April 22, 2026 03:44
…eferences (#6844) Resolves #6843 ([FR-2623](https://lablup.atlassian.net/browse/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 [FR-2623]: https://lablup.atlassian.net/browse/FR-2623?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
d09a116 to
774580f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Resolves #6843 (FR-2623)
Summary
model_serving.mdtoadmin_menu.mdacross all 4 languages — admin-only content now lives in the Admin Menu section where it belongs.admin_menu.mdandmodel_serving.md(Clone to Folder, Create Service from This Model, Cloning a Model). The clone feature is no longer provided by the product.model-definition.yamldescription 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.model_card_added.pngreference.vfolder.md— it is still a real field in the vfolder creation modal.Test Plan
admin_menu.mdrenders correctly with the new Admin Features section in en/ko/ja/thmodel_serving.mdno longer references clone or admin-only features in en/ko/ja/thvfolder.mdCloneable field documentation is intact in en/ko/ja/th