Update docs UI and screengrabs

Author: osterman

examples/quick-start-simple/README.md

@@ -18,11 +18,17 @@ cd examples/quick-start-simple
 # List all stacks
 atmos list stacks
 
-# Describe the weather component in dev
-atmos describe component weather -s dev
+# List component instances in dev
+atmos list instances -s dev
 
-# Plan the weather component
-atmos terraform plan weather -s dev
+# Describe the station component in dev
+atmos describe component station -s dev
+
+# Preview all Terraform components in dev
+atmos terraform plan --all -s dev
+
+# Deploy all Terraform components in dev
+atmos terraform deploy --all -s dev
 ```
 
 ## Key Files

website/blog/2026-05-30-custom-commands-step-types.mdx

@@ -1,21 +1,21 @@
 ---
 slug: custom-commands-step-types
-title: "Introducing 25+ Interactive Step Types for Workflows and Custom Commands"
+title: "Introducing 25+ Interactive Step Types for Custom Commands and Workflows"
 authors: [osterman]
 tags: [feature, dx]
 date: 2026-05-30
 ---
 
-Atmos now includes 25+ interactive step types for both workflows and custom commands. Build interactive CLI wizards, collect user input, display rich output, and control execution flow—all directly in your `atmos.yaml` without external scripts.
+Atmos now includes 25+ interactive step types for custom commands and workflows. Build polished CLI commands, collect user input, display rich output, and control execution flow—all directly in your `atmos.yaml` without external scripts.
 
 <!--truncate-->
 
 ## What's New
 
-We've built a unified execution engine (`pkg/runner`) that powers both workflows and custom commands with the same rich step types:
+We've built a unified execution engine (`pkg/runner`) that powers custom commands and workflows with the same rich step types:
 
 - **Interactive**: `input`, `confirm`, `choose`, `filter`, `file`, `write`
-- **UI Messages**: `success`, `info`, `warn`, `error`, `markdown`
+- **UI Messages**: `toast`, `markdown`
 - **Output**: `spin`, `table`, `pager`, `format`, `join`, `style`, `linebreak`, `log`
 - **Terminal**: `alert`, `title`, `clear`, `env`, `exit`
 - **Command**: `shell`, `atmos`
@@ -26,18 +26,18 @@ The `shell` and `atmos` types continue to work exactly as before—this is purel
 
 Previously, building interactive CLI experiences required shell scripts and external tools like `gum` or `fzf`. Now you can create guided deployment wizards, configuration tools, and interactive runbooks natively in Atmos.
 
-**For workflows:** Define multi-step automation with user prompts, confirmations, and rich feedback.
-
 **For custom commands:** Users discover your interactive commands via `atmos help` and get a polished experience.
 
+**For workflows:** Define multi-step automation with user prompts, confirmations, and rich feedback.
+
 ## How to Use It
 
-### Workflow Example
+### Custom Command Example
 
-```yaml title="stacks/workflows/deploy.yaml"
-workflows:
-  deploy:
-    description: Interactive deployment workflow
+```yaml title="atmos.yaml"
+commands:
+  - name: deploy-wizard
+    description: Interactive deployment wizard
     steps:
       - name: env
         type: choose
@@ -48,49 +48,48 @@ workflows:
       - name: confirm
         type: confirm
         prompt: "Deploy to {{ .steps.env.value }}?"
+        default: false
 
       - name: deploy
         type: atmos
         command: terraform apply vpc -s {{ .steps.env.value }}
 
-      - type: success
+      - name: done
+        type: toast
+        level: success
         content: "Deployment to {{ .steps.env.value }} completed!"
 ```
 
-Run with: `atmos workflow deploy -f deploy`
+Run with: `atmos deploy-wizard`
 
-### Custom Command Example
+### Workflow Example
 
-```yaml title="atmos.yaml"
-commands:
-  - name: deploy-wizard
-    description: Interactive deployment wizard
+```yaml title="stacks/workflows/deploy.yaml"
+workflows:
+  deploy:
+    description: Interactive deployment workflow
     steps:
       - name: env
         type: choose
         prompt: "Select target environment"
         options: [dev, staging, prod]
         default: dev
 
-      - name: prod_warning
-        type: warn
-        content: "You are about to deploy to PRODUCTION!"
-
       - name: confirm
         type: confirm
         prompt: "Deploy to {{ .steps.env.value }}?"
-        default: false
 
       - name: deploy
         type: atmos
         command: terraform apply vpc -s {{ .steps.env.value }}
 
       - name: done
-        type: success
+        type: toast
+        level: success
         content: "Deployment to {{ .steps.env.value }} completed!"
 ```
 
-Run with: `atmos deploy-wizard`
+Run with: `atmos workflow deploy -f deploy`
 
 ### Multi-Select Components
 
@@ -147,7 +146,8 @@ commands:
         options: [low, medium, high, critical]
         default: medium
 
-      - type: success
+      - type: toast
+        level: success
         content: |
           Ticket created:
           Title: {{ .steps.title.value }}

website/docs/cli/commands/ci/cache/delete.mdx

@@ -29,7 +29,7 @@ Like [`list`](/cli/commands/ci/cache/list), `delete` administers the cache over
     </div>
 </ActionCard>
 
-<Screengrab title="atmos ci cache delete" slug="atmos-ci-cache-delete" />
+<Screengrab title="atmos ci cache delete --help" slug="atmos-ci-cache-delete--help" />
 
 ## Usage
 

website/docs/cli/commands/ci/cache/list.mdx

@@ -29,7 +29,7 @@ List CI cache entries, optionally filtered by key prefix. Newest entries are lis
     </div>
 </ActionCard>
 
-<Screengrab title="atmos ci cache list" slug="atmos-ci-cache-list" />
+<Screengrab title="atmos ci cache list --help" slug="atmos-ci-cache-list--help" />
 
 ## Usage
 

website/docs/cli/commands/ci/cache/paths.mdx

@@ -25,7 +25,7 @@ Print the resolved cache **key**, **paths**, and **restore-keys** so a native ca
     </div>
 </ActionCard>
 
-<Screengrab title="atmos ci cache paths" slug="atmos-ci-cache-paths" />
+<Screengrab title="atmos ci cache paths --help" slug="atmos-ci-cache-paths--help" />
 
 ## Usage
 

website/docs/cli/commands/ci/cache/restore.mdx

@@ -29,7 +29,7 @@ Restore the CI cache into the well-known cache directory. The exact key is looke
     </div>
 </ActionCard>
 
-<Screengrab title="atmos ci cache restore" slug="atmos-ci-cache-restore" />
+<Screengrab title="atmos ci cache restore --help" slug="atmos-ci-cache-restore--help" />
 
 ## Usage
 

website/docs/cli/commands/ci/cache/save.mdx

@@ -29,7 +29,7 @@ Archive the cache root (the toolchain and anything else under it) and upload it
     </div>
 </ActionCard>
 
-<Screengrab title="atmos ci cache save" slug="atmos-ci-cache-save" />
+<Screengrab title="atmos ci cache save --help" slug="atmos-ci-cache-save--help" />
 
 ## Usage
 

website/docs/cli/commands/ci/status.mdx

@@ -25,7 +25,7 @@ Display CI status for the current branch, including status checks, pull request
     </div>
 </ActionCard>
 
-<Screengrab title="atmos ci status" slug="atmos-ci-status" />
+<Screengrab title="atmos ci status --help" slug="atmos-ci-status--help" />
 
 ## Usage
 

website/docs/cli/commands/profile/profile-show.mdx

@@ -12,7 +12,7 @@ import Intro from '@site/src/components/Intro';
 Use this command to display detailed information about a specific configuration profile, including its metadata, configuration files, and usage instructions.
 </Intro>
 
-<Screengrab title="atmos profile show developer" slug="atmos-profile-show" />
+<Screengrab title="atmos profile show --help" slug="atmos-profile-show--help" />
 
 ## Usage
 

website/docs/cli/configuration/components/terraform.mdx

@@ -350,5 +350,5 @@ backend.tf.json
 - [Component Configuration Overview](/cli/configuration/components)
 - [Stack Configuration](/cli/configuration/stacks)
 - [Terraform Components](/components/terraform)
-- [Terraform Backend](/stacks/backend)
+- [Terraform Backend](/stacks/terraform/backend)
 - [Generate Terraform Files](/stacks/generate)