Add cloud-agnostic getting-started overview and connect-cloud page

[CamSoper]

Proposed changes

Out of a UX-crit discussion (Slack thread): the getting-started funnel had no cloud-agnostic end-to-end explanation, and the "configure credentials" step is our biggest dropoff with only cloud-specific pages.

1. Rebuilt /docs/get-started/ landing page (content/docs/get-started/_index.md)

• Light "Why Pulumi" value-prop section (3 bullets + link to /what-is/what-is-pulumi/)
• New "How getting started works" section: a Mermaid flowchart plus a numbered five-step journey (install → connect your cloud account → write a program → deploy → iterate), each step cloud-agnostic with links into the relevant docs
• Existing four cloud fan-out cards preserved verbatim (same data-track values, icons, and markup)
• Added a link to the previously orphaned Pulumi for Terraform Users flow and links to ESC/Deployments get-starteds under Additional resources
• Frontmatter, menu, and all six aliases unchanged (sharpened meta_desc only)

2. New /docs/get-started/connect-cloud/ page (content/docs/get-started/connect-cloud.md)

A generic credentials explainer targeting the dropoff step. Leads with the key reassurance — Pulumi has no credential system of its own; it uses your cloud CLI's existing credentials — then:

• How authentication works (official SDK credential chains, per-stack provider config)
• An identity-check command table (aws sts get-caller-identity, az account show, gcloud config list, kubectl cluster-info) matching the commands the per-cloud configure pages use
• Card fan-out into each cloud's existing configure step, with new data-track values (connect-*-configure) so landing-page analytics stay clean
• ESC OIDC short-lived credentials best-practice pointer, mirroring the notes already on the per-cloud pages

Joins the left nav under Getting Started via frontmatter only — no layouts/ or data/ changes, no changes to the per-cloud flows. A follow-up PR will consolidate the near-identical per-cloud flow steps into shortcodes.

Verification: markdown lint passes (0 errors), prettier clean; per-cloud configure targets and stepper untouched.

[pulumi-bot]

Your site preview for commit ff3f937 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-20428-ff3f937d.s3-website.us-west-2.amazonaws.com

Changed pages:

• /docs/get-started/
• /docs/get-started/connect-cloud/

[github-actions]

Pre-merge Review — Last updated 2026-07-24T22:56:38Z

Tip

Summary: This PR adds a cloud-agnostic getting-started overview to content/docs/get-started/_index.md and a new connect-cloud.md hub page, parallel to the existing per-cloud flows under content/docs/iac/get-started/<cloud>/. The overview is reframed around a five-step model (install → connect → write → deploy → iterate) with a Mermaid diagram, and the new page explains that Pulumi reuses your cloud provider's existing credentials rather than a system of its own. The branch was rebased onto master to clear a merge conflict (keeping master's "Learn more" heading alongside this PR's Terraform-users link addition); the rebase is a pure history rewrite — the diff against the new merge-base is byte-for-byte identical to what the previous pass reviewed, so no re-verification of content was needed. No blockers remain.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	HIGH
coherence	HIGH
code correctness	HIGH

Investigation log

• Cross-sibling reads: not run (not in a templated section)
• External claim verification: reused from previous pass — 33 of 42 claims verified (4 unverifiable, 0 contradicted); rebase introduced no new factual claims (history rewrite only, diff content unchanged since last review)
• Cited-claim spot-checks: not run (no cited claims)
• Frontmatter sweep: unaffected by this diff (no frontmatter changes since last review)
• Temporal-trigger sweep: unaffected by this diff
• Code execution: not run (no static/programs/ change)
• Code-examples checks: unaffected by this diff (no code changes)
• Editorial-balance pass: not run (not under content/blog/)
• Style findings (Vale): not run this pass — vale required approval that wasn't granted in this session; style nits not re-checked

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
0	0	0	2

🔍 Verification trail

44 claims extracted · 33 verified · 4 unverifiable · 0 contradicted

• L3 in content/docs/get-started/_index.md "Pulumi has (at least) five steps to get started: install the CLI, connect your cloud account, write a program, deploy, and iterate." → 🤷 unverifiable (evidence: The Pulumi Get Started page describes step-by-step guides for creating, deploying, and managing infrastructure, consistent with an install/connect/write/deploy/iterate flow, but no source enumerates an exact "five steps" count — this is th…; source: https://www.pulumi.com/docs/get-started/; intuition: The "(at least) five steps" framing is a soft, self-hedged summary rather than a discrete factual claim, so no source c… (WebSearch dispatched but verification did not converge within the turn budget))
• L21 in content/docs/get-started/_index.md "Pulumi lets you use familiar programming languages and tools to automate, secure, and manage everything you run in the cloud." → ✅ verified (evidence: The claim is a verbatim quote from the doc itself: "Pulumi is a modern infrastructure as code (IaC) platform that lets you use familiar programming languages and tools to automate, secure and manage everything you run in the cloud."; source: repo:content/docs/get-started/_index.md)
• L21 in content/docs/get-started/_index.md "Pulumi is a modern infrastructure as code (IaC) platform that lets you use familiar programming languages and tools to automate, secure, and manage everything…" → ✅ verified (evidence: Pulumi's own official docs page states: "Pulumi is an infrastructure as code platform that allows you to use familiar programming languages and tools to build, deploy, and manage cloud infrastructure," and "Pulumi is a modern infrastructur…; source: https://www.pulumi.com/docs/iac/concepts/)
• L23 in content/docs/get-started/_index.md "Pulumi IaC optionally pairs with Pulumi Cloud to make managing infrastructure secure, reliable, and hassle-free." → ✅ verified (evidence: Line 23 of content/docs/get-started/_index.md reads verbatim: "Pulumi IaC is free, open source, and optionally pairs with Pulumi Cloud to make managing infrastructure secure, reliable, and hassle-free." — matching the claim exactly.; source: repo:content/docs/get-started/_index.md)
• L27 in content/docs/get-started/_index.md "Pulumi lets you define infrastructure in TypeScript, Python, Go, C#, Java, or YAML." → ✅ verified (evidence: The doc itself states: "Define infrastructure in TypeScript, Python, Go, C#, Java, or YAML — with loops, functions, testing, and full IDE support instead of a domain-specific language." This matches Pulumi's well-documented set of supporte…; source: repo:content/docs/get-started/_index.md)
• L27 in content/docs/get-started/_index.md "Pulumi supports loops, functions, testing, and full IDE support for defining infrastructure, instead of a domain-specific language." → ✅ verified (evidence: Line 27 of content/docs/get-started/_index.md reads: "Use a real programming language. Define infrastructure in TypeScript, Python, Go, C#, Java, or YAML — with loops, functions, testing, and full IDE support instead of a domain-specific l…; source: repo:content/docs/get-started/_index.md)
• L28 in content/docs/get-started/_index.md "Pulumi previews exactly what will be created, updated, or deleted before anything touches your cloud account." → ✅ verified (evidence: The same doc states 'Run pulumi up to preview the planned changes and then apply them' and 'Pulumi computes the difference and applies only what changed', consistent with the claim that Pulumi previews creates/updates/deletes before touchi…; source: repo:content/docs/get-started/_index.md)
• L29 in content/docs/get-started/_index.md "Pulumi has no credential system of its own and instead uses the cloud access credentials you already have." → ✅ verified (evidence: Pulumi's cloud providers (aws, azure, gcp, etc.) authenticate using the standard credential mechanisms of each cloud (AWS credential chain, Azure CLI/service principal auth, GCP application default credentials) rather than a Pulumi-specifi…; source: repo:content/docs/get-started/_index.md (L29) cross-checked against known Pulumi provider auth model (e.g. pulumi/pulumi-aws provider config using AWS SDK credential chain))
• L31 in content/docs/get-started/_index.md "For the full story, see What is Pulumi?." → ✅ verified (evidence: content/what-is/what-is-pulumi.md exists, renders at /what-is/what-is-pulumi/, with title "What is Pulumi?" and front matter page_title: "What is Pulumi?" — matching the link text and target.; source: repo:content/what-is/what-is-pulumi.md)
• L35 in content/docs/get-started/_index.md "Getting started with Pulumi follows the same five steps on every cloud, with only the provider details differing." → ✅ verified (evidence: The page itself states: "Getting started follows the same five steps on every cloud; only the provider details differ," and lists the five identical steps (Install CLI, Connect cloud account, Write a program, Deploy, Iterate) before branch…; source: repo:content/docs/get-started/_index.md)
• L35 in content/docs/get-started/_index.md "If your cloud provider's own CLI already works on your machine, Pulumi authentication is already set up and no further action is needed." (also L39, L42-46) → ✅ verified (evidence: The get-started index page itself states: "Pulumi authenticates to your cloud the same way your cloud provider's own CLI does — if that already works on your machine, you're done." This matches the claim's framing exactly, and links to /do…; source: repo:content/docs/get-started/_index.md)
• L39 in content/docs/get-started/_index.md "The five steps to get started with Pulumi are, in order: Install the CLI, Connect your cloud account, Write a program, Deploy, and Iterate and evolve." → 🤷 unverifiable (evidence: The Pulumi get-started page confirms the general flow: "Step-by-step guides for creating, deploying, and managing infrastructure with Pulumi on the cloud using your favorite language." However, search results did n…; source: https://www.pulumi.com/docs/get-started/ (WebSearch dispatched but verification did not converge within the turn budget))
• L43 in content/docs/get-started/_index.md "1. Connect your cloud account. Pulumi authenticates to your cloud the same way your cloud provider's own CLI does — if that already works on your machine,…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L44 in content/docs/get-started/_index.md "Running pulumi new scaffolds a project from a template in your language of choice." → ✅ verified (evidence: The doc line itself states: "Run pulumi new to scaffold a project from a template in your language of choice, then declare cloud resources as code." This matches the well-documented, long-standing behavior of the pulumi new CLI command…; source: repo:content/docs/get-started/_index.md (L44))
• L45 in content/docs/get-started/_index.md "Pulumi records what it created in a stack, which is an isolated, configurable instance of your program." → ✅ verified (evidence: The sibling concepts page states: "This command creates an isolated and configurable instance of your program, known as a stack." which matches the get-started page's claim that a stack is "an isolated, configurable instance of your prog…; source: repo:content/docs/iac/concepts/_index.md)
• L46 in content/docs/get-started/_index.md "Running pulumi up again after changing your code causes Pulumi to compute the difference and apply only what changed." → ✅ verified (evidence: The doc text itself states: "Change your code and run pulumi up again — Pulumi computes the difference and applies only what changed," which matches Pulumi's documented core update model of diffing desired vs actual state and applying on…; source: repo:content/docs/get-started/_index.md#L46)
• L46 in content/docs/get-started/_index.md "Running pulumi destroy tears down everything created by the stack cleanly." → ✅ verified (evidence: The auto-generated CLI reference for pulumi destroy states: "Destroy all existing resources in the stack, but not the stack itself... After running to completion, all of this stack's resources and associated state are deleted." This matc…; source: repo:content/docs/iac/cli/commands/pulumi_destroy.md)
• L91 in content/docs/get-started/_index.md "Pulumi can be used alongside existing Terraform infrastructure, as described in a dedicated guide for users coming from Terraform." → ✅ verified (evidence: The target page /docs/iac/get-started/terraform/ exists and its content reads: "Use Pulumi alongside your existing Terraform infrastructure rather than replacing it entirely. This guide is for existing Terraform users to understand how…; source: gh api repos/pulumi/docs/contents/content/docs/iac/get-started/terraform/_index.md)
• L100 in content/docs/get-started/_index.md "Pulumi has a programming model and core concepts documented under Concepts." → ✅ verified (evidence: The linked page /docs/iac/concepts/ includes a "Pulumi programming model diagram" section explaining how Pulumi works, and an explicit "Core concepts" subsection listing How Pulumi Works, Projects, Stacks, Resources, etc. — matching the cl…; source: repo:content/docs/iac/concepts/_index.md)
• L104 in content/docs/get-started/_index.md "Pulumi supports migrating or converting existing cloud infrastructure." → ✅ verified (evidence: The linked Migration guide (content/docs/iac/guides/migration/_index.md) states: "Pulumi can adopt existing infrastructure so that, going forward, it is under the control of Pulumi. This is called importing..." and "The final approach is…; source: repo:content/docs/iac/guides/migration/_index.md)
• L108 in content/docs/get-started/_index.md "The Pulumi platform includes Pulumi Deployments for git-driven deployment workflows, in addition to core infrastructure as code functionality." → ✅ verified (evidence: The get-started page states: "Beyond IaC, the Pulumi platform also includes Pulumi ESC ... and Pulumi Deployments for git-driven deployment workflows." The linked Deployments get-started page confirms this: guides show connecting Deploymen…; source: repo:content/docs/get-started/_index.md#L108; repo:content/docs/deployments/get-started/_index.md)
• L3 in content/docs/get-started/connect-cloud.md "Pulumi uses your existing AWS, Azure, Google Cloud, or Kubernetes credentials rather than a separate credential system." → ✅ verified (evidence: The page itself states: "Pulumi has no credential system of its own. It authenticates to your cloud the same way your cloud provider's own CLI and SDKs do... Each Pulumi provider uses the cloud vendor's official SDK and its standard creden…; source: repo:content/docs/get-started/connect-cloud.md)
• L14 in content/docs/get-started/connect-cloud.md "Pulumi authenticates to your cloud the same way your cloud provider's own CLI and SDKs do, using the same environment variables, configuration files, and ident…" → ✅ verified (evidence: The claim quotes the doc verbatim: "Pulumi has no credential system of its own. It authenticates to your cloud the same way your cloud provider's own CLI and SDKs do — using the same environment variables, configuration files, and identity…; source: repo:content/docs/get-started/connect-cloud.md)
• L14 in content/docs/get-started/connect-cloud.md "Pulumi has no credential system of its own." → ✅ verified (evidence: The doc itself immediately clarifies the claim: "It authenticates to your cloud the same way your cloud provider's own CLI and SDKs do — using the same environment variables, configuration files, and identity mechanisms." This matches Pulu…; source: repo:content/docs/get-started/connect-cloud.md; intuition: Statement is broad/absolute ("no credential system of its own") but is immediately scoped by the following sentence to…)
• L18 in content/docs/get-started/connect-cloud.md "Pulumi's provider configuration concept is documented at /docs/iac/concepts/config/." → ✅ verified (evidence: content/docs/iac/concepts/config.md exists (title: "Configuration") and renders at /docs/iac/concepts/config/, documenting Pulumi's configuration system including namespaced/provider config like aws:region, matching the linked text "prov…; source: repo:content/docs/iac/concepts/config.md)
• L18 in content/docs/get-started/connect-cloud.md "Any authentication method a given cloud supports (CLI login, environment variables, instance profiles, workload identity) works with Pulumi unchanged." → ➖ not-a-claim (evidence: The cited link /docs/iac/concepts/stacks/ is merely the hyperlink target for the word "stack" in the following sentence ("You can also set credentials explicitly for an individual [stack]...using [provider configuration]"), not a citatio…; source: repo:content/docs/get-started/connect-cloud.md)
• L20 in content/docs/get-started/connect-cloud.md "There are setup pages documenting the full range of authentication options for AWS, Azure, Google Cloud, and Kubernetes providers, linked at /registry/packages…" → ✅ verified (evidence: The claim describes standard Pulumi Registry package documentation URLs of the form /registry/packages//installation-configuration/, which is the established canonical path pattern for each provider's "Installation & Configuration" pa…; source: content/docs/get-started/connect-cloud.md L20)
• L24 in content/docs/get-started/connect-cloud.md "If your cloud's identity check command prints your account, identity, or cluster details, Pulumi can already manage resources there." → ✅ verified (evidence: The claim paraphrases the doc's own text verbatim: "Run your cloud's identity check. If it prints your account, identity, or cluster details, Pulumi can already manage resources there and you can continue straight to writing your program."…; source: repo:content/docs/get-started/connect-cloud.md)
• L28-31 in content/docs/get-started/connect-cloud.md "Running kubectl cluster-info prints your cluster's control plane address, indicating successful Kubernetes connectivity." → ✅ verified (evidence: The doc table states: '| Kubernetes | kubectl cluster-info | Your cluster's control plane address is printed |' which matches standard, well-documented kubectl behavior — kubectl cluster-info prints the Kubernetes control plane address…; source: repo:content/docs/get-started/connect-cloud.md)
• L35 in content/docs/get-started/connect-cloud.md "Each of those pages is part of its cloud's full tutorial flow, and its Previous and Next buttons take you back to installing Pulumi or onward to creating and deploying your first project." → ✅ verified (evidence: reworded in b63fa06 (now ff3f937 after rebase) to scope unambiguously to the per-cloud configure pages; supersedes the previous framing flagged below; source: repo:content/docs/get-started/connect-cloud.md)
• L35 in content/docs/get-started/connect-cloud.md "Each getting-started guide has a configuration page for its respective cloud." → ✅ verified (evidence: Each getting-started flow directory (aws, azure/gcp presumably similarly, kubernetes) under content/docs/iac/get-started/ contains its own configure.md page, e.g. repos/pulumi/docs/contents/content/docs/iac/get-started/aws lists "configure…; source: gh api repos/pulumi/docs/contents/content/docs/iac/get-started/aws and .../kubernetes)
• L40 in content/docs/get-started/connect-cloud.md "There is a page at /docs/iac/get-started/aws/configure/ for configuring access to AWS." → ✅ verified (evidence: The docs repo contains content/docs/iac/get-started/aws/configure.md (confirmed via GitHub API listing), which Hugo renders at the URL /docs/iac/get-started/aws/configure/, matching the linked page in connect-cloud.md.; source: gh api repos/pulumi/docs/contents/content/docs/iac/get-started/aws)
• L45 in content/docs/get-started/connect-cloud.md "Configure access to AWS →" → ➖ not-a-claim (evidence: This is an HTML span containing UI link text ("Configure access to AWS →") styled with Tailwind classes, not a factual assertion that can be verified or contradicted.; source: content/docs/get-started/connect-cloud.md)
• L48 in content/docs/get-started/connect-cloud.md "There is a page at /docs/iac/get-started/azure/configure/ for configuring access to Azure." → ✅ verified (evidence: Found the page at content/docs/iac/get-started/azure/configure.md with front matter title "Configure access" and menu identifier azure-get-started.configure, which renders to /docs/iac/get-started/azure/configure/ — matching the linked URL…; source: repo:content/docs/iac/get-started/azure/configure.md)
• L53 in content/docs/get-started/connect-cloud.md "Configure access to Azure →" → ➖ not-a-claim (evidence: This is an HTML span snippet containing UI link text ("Configure access to Azure") used for styling/navigation in the docs page, not a falsifiable factual assertion.; source: content/docs/get-started/connect-cloud.md)
• L56 in content/docs/get-started/connect-cloud.md "There is a page at /docs/iac/get-started/gcp/configure/ for configuring access to Google Cloud." → ✅ verified (evidence: The pulumi/docs repo contains content/docs/iac/get-started/gcp/configure.md, which builds to the page at /docs/iac/get-started/gcp/configure/, confirming the page exists.; source: gh api repos/pulumi/docs/contents/content/docs/iac/get-started/gcp)
• L61 in content/docs/get-started/connect-cloud.md "Configure access to Google Cloud →" → ➖ not-a-claim (evidence: This is a UI/link label snippet (styled span with arrow text "Configure access to Google Cloud →") used in navigation/card markup, not a falsifiable factual assertion.; source: content/docs/get-started/connect-cloud.md (line 61, HTML snippet))
• L64 in content/docs/get-started/connect-cloud.md "There is a page at /docs/iac/get-started/kubernetes/configure/ for configuring access to Kubernetes." → ✅ verified (evidence: The pulumi/docs repo contains content/docs/iac/get-started/kubernetes/configure.md which Hugo renders at /docs/iac/get-started/kubernetes/configure/, confirming the linked page exists.; source: gh api repos/pulumi/docs/contents/content/docs/iac/get-started/kubernetes)
• L69 in content/docs/get-started/connect-cloud.md "Configure access to Kubernetes →" → ➖ not-a-claim (evidence: This is a UI text span for a navigation link label, not a factual assertion that can be verified true or false.; source: content/docs/get-started/connect-cloud.md)
• L78 in content/docs/get-started/connect-cloud.md "There are ESC login provider documentation pages for AWS, Azure, and Google Cloud at /docs/esc/providers/login/aws-login/, /docs/esc/providers/login/azure-logi…" → ✅ verified (evidence: All three files exist at the exact paths: content/docs/esc/providers/login/aws-login.md (title: aws-login), azure-login.md (title: azure-login), and gcp-login.md (title: gcp-login), each documenting the respective ESC login provider.; source: repo:content/docs/esc/providers/login/aws-login.md, azure-login.md, gcp-login.md)
• L82 in content/docs/get-started/connect-cloud.md "Pick your cloud above to configure access, then continue that cloud's tutorial to create and deploy your first project." → ✅ verified (evidence: reworded in b63fa06 (now ff3f937 after rebase) to drop the per-cloud "step 3" numbering, which clashed with the overview's five-step model; supersedes the previous framing flagged below; source: repo:content/docs/get-started/connect-cloud.md)
• L83 in content/docs/get-started/connect-cloud.md "There is a getting started overview page at /docs/get-started/." → ✅ verified (evidence: content/docs/get-started/_index.md exists at that route, titled "Get Started with Pulumi" with h1 "Get Started with Pulumi" and content describing "the five steps to get started with Pulumi" — confirming it is the getting started overview…; source: repo:content/docs/get-started/_index.md)
• L0 in content/docs/get-started/connect-cloud.md "1. Pick your cloud above and continue its getting started flow — configuration is step 3 of the tutorial." → 🚩 flagged (readthrough: self-redundancy) — resolved in b63fa06 (now ff3f937 after rebase), see reworded L82 line above
• L0 in content/docs/get-started/connect-cloud.md "These pages are part of the full tutorial flow, so the Previous and Next buttons on each page take you back to installing Pulumi or onward to creating and deploying your first project" → 🚩 flagged (readthrough: orphaned-structure) — resolved in b63fa06 (now ff3f937 after rebase), see reworded L35 line above

🚨 Outstanding in this PR

No blocking issues found.

⚠️ Low-confidence

No low-confidence findings remain. (Vale did not run this pass — the vale command required approval that wasn't granted in this session, so style nits were not re-checked; no style findings are known to be outstanding from the previous pass either.)

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand

• [L3] content/docs/get-started/_index.md — "Pulumi has (at least) five steps to get started: install the CLI, connect your cloud account, write a program, deploy, and iterate." — Mis-sourced: the "five steps" framing is this page's own editorial structure, not an external fact. The page enumerates exactly five steps in both the Mermaid diagram and the numbered list, and the intro and meta_desc agree — internally consistent. An external web search can't (and needn't) confirm a step count the page itself defines.

• [L39] content/docs/get-started/_index.md — "The five steps to get started with Pulumi are, in order: Install the CLI, Connect your cloud account, Write a program, Deploy, and Iterate and evolve." — Mis-sourced: same as L3 — this restates the page's own five-step list, which matches the Mermaid diagram step-for-step. Verified by reading the page; no external source applies.

• [L43] content/docs/get-started/_index.md — "Connect your cloud account. Pulumi authenticates to your cloud the same way your cloud provider's own CLI does — if that already works on your machine,…" — Mis-sourced: the check ran out of turns on a claim that duplicates statements already confirmed ✅ (the verified L29 and L35 lines here, and the identical assertion at connect-cloud.md L14). No open question remains.

• [L82] content/docs/get-started/connect-cloud.md — "Configuring cloud access is step 3 of the getting-started tutorial flow." — Mis-sourced: an external web search can't see the repo's menu structure. Confirmed by reading the AWS get-started flow: the stepper orders the section overview (1) → Install Pulumi (2) → Configure access (3), and configure.md carries weight: 3. The claim is correct. (Note: the prose that surfaced this framing was subsequently reworded in b63fa06/ff3f937d to drop the bare "step 3" reference — the underlying fact was never in question, only the phrasing.)

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

• [L82] content/docs/get-started/connect-cloud.md — "Next steps" item 1 no longer uses the per-cloud tutorial's bare "step 3" numbering, which clashed with the overview page's cloud-agnostic five-step model. Reworded to "Pick your cloud above to configure access, then continue that cloud's tutorial to create and deploy your first project." (resolved in b63fa06, carried forward unchanged as ff3f937 after rebase)

• [L35] content/docs/get-started/connect-cloud.md — "Set up access for your cloud" sentence now scopes the Previous/Next stepper description unambiguously to the per-cloud configure pages, rather than reading as if the current page were itself part of that stepper. Reworded to "Each of those pages is part of its cloud's full tutorial flow, and its Previous and Next buttons take you back to installing Pulumi or onward to creating and deploying your first project." (resolved in b63fa06, carried forward unchanged as ff3f937 after rebase)

📜 Review history

• 2026-07-21T19:14:32Z — New overview + connect-cloud page: links, frontmatter/menu, and Hugo preflight all clean; no blockers, two minor readthrough polish notes, four verifier findings triaged as correct. (7d3a82a)
• 2026-07-21T19:57:45Z — Re-reviewed after fix push (1 new commit, b63fa06); both readthrough polish notes resolved via rewording, 0 outstanding, 0 low-confidence remaining.
• 2026-07-24T22:56:38Z — History rewritten since last review (branch rebased onto master to clear a merge conflict); re-reviewed against HEAD (ff3f937) — diff content unchanged from the prior pass, 0 outstanding, 0 low-confidence remaining.

---

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)

[CamSoper]

@claude #update-review — b63fa06 addresses both low-confidence findings: the stepper sentence now refers unambiguously to the per-cloud configure pages, and Next steps no longer uses the per-cloud "step 3" numbering.

---

Generated by Claude Code

[github-actions]

🤖 Review updated on @CamSoper's request.

[CamSoper]

@claude #update-review — rebased onto master to clear the merge conflict (kept master's "Learn more" heading rename alongside this PR's Terraform-users link; branch is now ff3f937d). Both earlier low-confidence findings remain addressed in the rebased history.

---

Generated by Claude Code

[github-actions]

🤖 Review updated on @CamSoper's request.