Why This Work is Needed
Additional Sujin feedback on the 26.4 model serving docs (after PR #6760/#6767) requires further revisions. The runtime parameter UI now uses a tab-based layout with differentiated vLLM / SGLang variants, and several service launcher fields need clearer descriptions. The legacy 23.03-and-earlier section is no longer relevant and should be removed, with the Custom runtime workflow moved behind a collapsible block so that the default 26.4 quick-deploy flow is visible first.
Expected Outcomes
- Service Launcher field descriptions reflect current UI labels (Service Name, Open To Public, Model Storage Folder to Mount, Inference Runtime Variant, Environment / Version).
- Runtime parameters section is split into vLLM and SGLang subsections with tab-based Model Loading fields.
- Legacy 23.03-and-earlier
<details> block is removed; Custom runtime instructions moved to a collapsible block below the 26.4 quick-deploy flow.
- Refreshed screenshots for
service_launcher1.png, service_launcher_command_mode.png, and new vLLM / SGLang runtime parameter screenshots.
JIRA Issue: FR-2603
Why This Work is Needed
Additional Sujin feedback on the 26.4 model serving docs (after PR #6760/#6767) requires further revisions. The runtime parameter UI now uses a tab-based layout with differentiated vLLM / SGLang variants, and several service launcher fields need clearer descriptions. The legacy 23.03-and-earlier section is no longer relevant and should be removed, with the Custom runtime workflow moved behind a collapsible block so that the default 26.4 quick-deploy flow is visible first.
Expected Outcomes
<details>block is removed; Custom runtime instructions moved to a collapsible block below the 26.4 quick-deploy flow.service_launcher1.png,service_launcher_command_mode.png, and new vLLM / SGLang runtime parameter screenshots.JIRA Issue: FR-2603