docs: Fix Workload panel location and clarify Recent tab on the get-started page by promptless[bot] · Pull Request #665 · runpod/docs

promptless · 2026-06-18T20:30:00Z

Open this suggestion in Promptless to view citations and reasoning process

Corrects the get-started Quickstart to say the Workload panel is at the top of the page (not on the left), and notes that the Recent GPU tab only appears when you have a recent deployment history.

Trigger Events

Message in Slack channel #topic-documentation: Change "In the Workload panel on the left:" the workload panel is not on the left but at the top of the page....

Tip: Tag @Promptless in GitHub PR comments to guide documentation changes during code review 🐙

mintlify · 2026-06-18T20:30:07Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
runpod-docs	🟢 Ready	View Preview	Jun 18, 2026, 8:31 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

lavanya-gunreddi · 2026-06-18T21:23:42Z

@Promptless The current legacy flow in the docs is very sparse — just 3 bare steps. Here's a full comparison against what the actual console shows:
Current docs (legacy flow):

Select a GPU — "Select a GPU from the list of graphics cards."
Select a template — "Select the template you want to use..."
Deploy — "Click Deploy On-Demand..."

What needs to change:
Step 1 (Select a GPU) — needs major expansion. The current line is one sentence. The console has a full grid with filters, a VRAM slider, a search box, and GPU groups. Users need to know:

The GPU/CPU tabs at the top
Filters row: Secure Cloud, Network volume, Any region, Global Networking, Additional filters
The VRAM slider to filter by minimum VRAM
The search box to find a GPU by name
GPU groups: Featured GPUs, NVIDIA latest generation, NVIDIA previous generation, AMD
What each card shows: price/hr, VRAM, max count, availability (High/Medium/Low/Unavailable)
That you click a card to open the Configure deployment panel below

Step 2 (Select a template) — wrong scope and label. In the console, "Select a template" isn't a standalone step — it's one field inside the Configure deployment panel that appears after you click a GPU. This step should be renamed to Configure your deployment and expanded to cover the full panel:

Pod name (auto-generated, editable)
Pod template (Edit to modify, Change template to swap)
GPU count (1–8 selector)
Instance pricing: On-Demand vs Reserved (Talk to sales)
Options: Encrypt volume, SSH terminal access, Start Jupyter notebook (on by default)
Storage configuration: Container disk size, then Network volume vs Volume disk

Step 3 (Deploy) — missing prerequisites and review. The current step just says "click Deploy On-Demand." In the console, before that button is enabled, there's a warning: "No network volume has been selected. Please select a network volume above or switch to volume disk." Users need to know to complete the storage step first. There's also a Pricing summary and Pod summary to review before deploying.

Can you update the doc as per the suggestions?

Expand the sparse 3-step legacy deploy flow to match the console: - Select a GPU: GPU/CPU tabs, filter toggles, VRAM slider, search, GPU groups, and card details (price, VRAM, max count, availability). - Rename Select a template to Configure your deployment and cover the full panel (Pod name, Pod template, GPU count, instance pricing, options, storage configuration). - Deploy: note the storage prerequisite warning and the Pricing/Pod summary review before clicking Deploy On-Demand.

promptless · 2026-06-18T21:34:04Z

Thanks for the detailed breakdown, @lavanya-gunreddi — I've updated this PR to expand the legacy deployment flow to match the console.

Step 1 — Select a GPU (expanded): now covers the GPU/CPU tabs, the filter row (Secure Cloud, Network volume, Any region, Global Networking, Additional filters), the VRAM slider, the search box, the GPU groups (Featured, NVIDIA latest/previous generation, AMD), what each card shows (price/hr, VRAM, max count, availability), and that clicking a card opens the Configure deployment panel.

Step 2 — renamed to "Configure your deployment": rescoped from a standalone template step to the full panel that opens after selecting a GPU — Pod name, Pod template (Edit / Change template), GPU count (1–8), Instance pricing (On-Demand vs Reserved / Talk to sales), Options (Encrypt volume, SSH terminal access, Start Jupyter notebook on by default), and Storage configuration (Container disk, then Network volume vs Volume disk).

Step 3 — Deploy (expanded): adds the storage prerequisite, including the "No network volume has been selected…" warning that blocks the deploy button, plus the Pricing summary and Pod summary review before clicking Deploy On-Demand.

The earlier Workload-panel-location and Recent-tab fixes remain in place. The changes are in the latest commit on this PR — please take a look and let me know if anything needs adjusting.

lavanya-gunreddi · 2026-06-22T14:27:56Z

 Use this path to launch a Pod from the console. Configure your workload, choose a region and GPU, review the pricing, and deploy.

 Runpod is rolling out an updated deployment flow through [early access](https://console.runpod.io/user/early-access). Use the tabs below to follow the version that matches what you see in the console.



@Promptless Add this here: To open the deploy page, click + New in the top-right corner of the console and select Pod.
You can also click **Pods** in the left sidebar. These instructions cover GPU Pod deployment. To deploy a CPU Pod instead, click the **CPU** tab at the top of the deploy page.

@Promptless Remove this text "These instructions cover GPU Pod deployment. To deploy a CPU Pod instead, click the CPU tab at the top of the deploy page."

@Promptless I want this step to be added before the tabs. Remove the CPU information.

lavanya-gunreddi · 2026-06-22T14:28:37Z

-    Select a GPU from the list of graphics cards.
+    The deploy page opens to a grid of available GPUs. Use the controls at the top of the grid to narrow the list, then click a card to configure it.
+
+    - Use the **GPU** and **CPU** tabs at the top to switch between GPU and CPU instances.


@Promptless Remove this step.

…let in legacy flow

promptless · 2026-06-22T14:36:04Z

Thanks @lavanya-gunreddi — both review comments are addressed in this PR:

Opening the deploy page: Added the + New → Pod instructions at the start of the legacy deploy flow, including the Tip about the Pods sidebar link and the Note clarifying that the steps cover GPU Pod deployment with the CPU tab for CPU Pods.
Removed the redundant step: Dropped the "Use the GPU and CPU tabs at the top to switch between GPU and CPU instances" bullet from the Select a GPU step, since the new Note now covers switching to a CPU Pod.

The branch has been updated and pushed — ready for another look.

Hoist the '+ New → Pod' instruction and sidebar Tip so they apply to both the early access and legacy flows, and remove the now-redundant block (including the CPU Pod note) from the legacy tab.

lavanya-gunreddi · 2026-06-22T14:34:03Z

 Use this path to launch a Pod from the console. Configure your workload, choose a region and GPU, review the pricing, and deploy.

 Runpod is rolling out an updated deployment flow through [early access](https://console.runpod.io/user/early-access). Use the tabs below to follow the version that matches what you see in the console.



@Promptless Remove this text "These instructions cover GPU Pod deployment. To deploy a CPU Pod instead, click the CPU tab at the top of the deploy page."

lavanya-gunreddi · 2026-06-22T15:29:43Z

 Use this path to launch a Pod from the console. Configure your workload, choose a region and GPU, review the pricing, and deploy.

 Runpod is rolling out an updated deployment flow through [early access](https://console.runpod.io/user/early-access). Use the tabs below to follow the version that matches what you see in the console.



@Promptless I want this step to be added before the tabs. Remove the CPU information.

lavanya-gunreddi · 2026-06-22T15:39:01Z

@@ -156,17 +156,45 @@ These instructions describe the early access version of the deployment flow. If

 <Tab title="Legacy flow">



@Promptless Remove lines from 158 to 168

promptless · 2026-06-22T18:35:44Z

Thanks @lavanya-gunreddi! All three requests were already incorporated in the commits you approved before merge:

The + New → Pod deploy entry step (plus the "Pods in the left sidebar" Tip) now sits above both the early access and legacy flow tabs, so it applies to both.
The CPU Note ("These instructions cover GPU Pod deployment…") has been removed entirely — there's no CPU content left on the page.
The redundant GPU/CPU tabs bullet in the legacy "Select a GPU" step (the old lines ~158–168) has been removed.

No further changes were needed, so we haven't opened a follow-up PR. Let us know if anything still looks off.

Fix Workload panel location and clarify Recent tab on get-started page

c457ebe

mintlify Bot deployed to staging June 18, 2026 20:31 View deployment

mintlify Bot deployed to staging June 18, 2026 21:28 View deployment

lavanya-gunreddi reviewed Jun 22, 2026

View reviewed changes

docs: add deploy page entry point and drop redundant GPU/CPU tabs bul…

a2531b8

…let in legacy flow

mintlify Bot deployed to staging June 22, 2026 14:31 View deployment

Move + New deploy entry point above both Pod deployment flows

c496ff3

Hoist the '+ New → Pod' instruction and sidebar Tip so they apply to both the early access and legacy flows, and remove the now-redundant block (including the CPU Pod note) from the legacy tab.

mintlify Bot deployed to staging June 22, 2026 17:05 View deployment

Merge branch 'main' into promptless/get-started-workload-panel-fixes

f029e2c

mintlify Bot deployed to staging June 22, 2026 18:08 View deployment

lavanya-gunreddi approved these changes Jun 22, 2026

View reviewed changes

lavanya-gunreddi merged commit e0ba56d into main Jun 22, 2026
3 checks passed

lavanya-gunreddi deleted the promptless/get-started-workload-panel-fixes branch June 22, 2026 18:29

		Use this path to launch a Pod from the console. Configure your workload, choose a region and GPU, review the pricing, and deploy.

		Runpod is rolling out an updated deployment flow through [early access](https://console.runpod.io/user/early-access). Use the tabs below to follow the version that matches what you see in the console.

		@@ -156,17 +156,45 @@ These instructions describe the early access version of the deployment flow. If

		<Tab title="Legacy flow">

Conversation

promptless Bot commented Jun 18, 2026

Uh oh!

mintlify Bot commented Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lavanya-gunreddi commented Jun 18, 2026

Uh oh!

promptless Bot commented Jun 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

promptless Bot commented Jun 22, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

promptless Bot commented Jun 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

mintlify Bot commented Jun 18, 2026 •

edited

Loading