Improve sandbox getting started links

Author: ghostwriternr

src/content/docs/containers/get-started.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { WranglerConfig, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 In this guide, you will deploy a Worker that can make requests to one or more Containers in response to end-user requests.
 In this example, each container runs a small webserver written in Go.
@@ -17,10 +17,9 @@ This example Worker should give you a sense for simple Container use, and provid
 ### Ensure Docker is running locally
 
 In this guide, we will build and push a container image alongside your Worker code. By default, this process uses
-[Docker](https://www.docker.com/) to do so. You must have Docker running locally when you run `wrangler deploy`. For most people, the best way to install Docker is to follow the [docs for installing Docker Desktop](https://docs.docker.com/desktop/). Other tools like [Colima](https://github.com/abiosoft/colima) may also work.
+[Docker](https://www.docker.com/) to do so.
 
-You can check that Docker is running properly by running the `docker info` command in your terminal. If Docker is running, the command will succeed. If Docker is not running,
-the `docker info` command will hang or return an error including the message "Cannot connect to the Docker daemon".
+<Render product="containers" file="docker-setup" />
 
 {/* FUTURE CHANGE: Add some image you can use if you don't have Docker running. */}
 {/* FUTURE CHANGE: Link to docs on alternative build/push options */}

src/content/docs/sandbox/get-started.mdx

@@ -19,17 +19,9 @@ A simple API that can safely execute Python code and perform file operations in
 
 ### Ensure Docker is running locally
 
-Sandbox SDK uses [Docker](https://www.docker.com/) to build container images alongside your Worker. Docker must be running when you deploy or run locally.
+Sandbox SDK uses [Docker](https://www.docker.com/) to build container images alongside your Worker.
 
-Install Docker by following the [Docker Desktop installation guide](https://docs.docker.com/desktop/).
-
-Verify Docker is running:
-
-```sh
-docker info
-```
-
-If Docker is not running, this command will hang or return "Cannot connect to the Docker daemon".
+<Render product="containers" file="docker-setup" />
 
 ## 1. Create a new project
 
@@ -56,61 +48,58 @@ cd my-sandbox
 The template provides a minimal Worker that demonstrates core sandbox capabilities:
 
 ```typescript
-import { getSandbox, proxyToSandbox, type Sandbox } from '@cloudflare/sandbox';
+import { getSandbox, proxyToSandbox, type Sandbox } from "@cloudflare/sandbox";
 
-export { Sandbox } from '@cloudflare/sandbox';
+export { Sandbox } from "@cloudflare/sandbox";
 
 type Env = {
-  Sandbox: DurableObjectNamespace<Sandbox>;
+	Sandbox: DurableObjectNamespace<Sandbox>;
 };
 
 export default {
-  async fetch(request: Request, env: Env): Promise<Response> {
-    // Required for preview URLs (if you expose ports later)
-    const proxyResponse = await proxyToSandbox(request, env);
-    if (proxyResponse) return proxyResponse;
-
-    const url = new URL(request.url);
-
-    // Get or create a sandbox instance
-    const sandbox = getSandbox(env.Sandbox, 'my-sandbox');
-
-    // Execute Python code
-    if (url.pathname === '/run') {
-      const result = await sandbox.exec('python -c "print(2 + 2)"');
-      return Response.json({
-        output: result.stdout,
-        success: result.success
-      });
-    }
-
-    // Work with files
-    if (url.pathname === '/file') {
-      await sandbox.writeFile('/workspace/hello.txt', 'Hello, Sandbox!');
-      const file = await sandbox.readFile('/workspace/hello.txt');
-      return Response.json({
-        content: file.content
-      });
-    }
-
-    return new Response('Try /run or /file');
-  },
+	async fetch(request: Request, env: Env): Promise<Response> {
+		const url = new URL(request.url);
+
+		// Get or create a sandbox instance
+		const sandbox = getSandbox(env.Sandbox, "my-sandbox");
+
+		// Execute Python code
+		if (url.pathname === "/run") {
+			const result = await sandbox.exec('python3 -c "print(2 + 2)"');
+			return Response.json({
+				output: result.stdout,
+				error: result.stderr,
+				exitCode: result.exitCode,
+				success: result.success,
+			});
+		}
+
+		// Work with files
+		if (url.pathname === "/file") {
+			await sandbox.writeFile("/workspace/hello.txt", "Hello, Sandbox!");
+			const file = await sandbox.readFile("/workspace/hello.txt");
+			return Response.json({
+				content: file.content,
+			});
+		}
+
+		return new Response("Try /run or /file");
+	},
 };
 ```
 
 **Key concepts**:
 
-- `getSandbox()` - Gets or creates a sandbox instance by ID
-- `proxyToSandbox()` - Required at the top for preview URLs to work
-- `sandbox.exec()` - Execute commands and capture output
-- `sandbox.writeFile()` / `readFile()` - File operations
+- `getSandbox()` - Gets or creates a sandbox instance by ID. Use the same ID to reuse the same sandbox instance across requests.
+- `sandbox.exec()` - Execute shell commands in the sandbox and capture stdout, stderr, and exit codes.
+- `sandbox.writeFile()` / `readFile()` - Write and read files in the sandbox filesystem.
 
 ## 3. Test locally
 
 Start the development server:
 
 ```sh
-npm run dev
+npm run dev. If you expect to have multiple sandbox instances, you can increase `max_instances`.
 ```
 
 :::note
@@ -138,6 +127,7 @@ npx wrangler deploy
 ```
 
 This will:
+
 1. Build your container image using Docker
 2. Push it to Cloudflare's Container Registry
 3. Deploy your Worker globally
@@ -171,34 +161,36 @@ Your `wrangler.jsonc` connects three pieces together:
 
 ```jsonc
 {
-  "containers": [
-    {
-      "class_name": "Sandbox",
-      "image": "./Dockerfile"
-    }
-  ],
-  "durable_objects": {
-    "bindings": [
-      {
-        "class_name": "Sandbox",
-        "name": "Sandbox"
-      }
-    ]
-  },
-  "migrations": [
-    {
-      "new_sqlite_classes": ["Sandbox"],
-      "tag": "v1"
-    }
-  ]
+	"containers": [
+		{
+			"class_name": "Sandbox",
+			"image": "./Dockerfile",
+			"instance_type": "lite",
+			"max_instances": 1,
+		},
+	],
+	"durable_objects": {
+		"bindings": [
+			{
+				"class_name": "Sandbox",
+				"name": "Sandbox",
+			},
+		],
+	},
+	"migrations": [
+		{
+			"new_sqlite_classes": ["Sandbox"],
+			"tag": "v1",
+		},
+	],
 }
 ```
 
 </WranglerConfig>
 
-- **containers** - Your Dockerfile defines the execution environment
-- **durable_objects** - Makes the `Sandbox` binding available in your Worker
-- **migrations** - Initializes Durable Object storage (required once)
+- **containers** - Defines the [container image, instance type, and resource limits](/workers/wrangler/configuration/#containers) for your sandbox environment. If you expect to have multiple sandbox instances, you can increase `max_instances`.
+- **durable_objects** - You need not be familiar with [Durable Objects](/durable-objects) to use Sandbox SDK, but if you'd like, you can [learn more about Cloudflare Containers and Durable Objects](/containers/get-started/#each-container-is-backed-by-its-own-durable-object). This configuration creates a [binding](/workers/runtime-apis/bindings#what-is-a-binding) that makes the `Sandbox` Durable Object accessible in your Worker code.
+- **migrations** - Registers the `Sandbox` class, implemented by the Sandbox SDK, with [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage) (required once)
 
 For detailed configuration options including environment variables, secrets, and custom images, see the [Wrangler configuration reference](/sandbox/configuration/wrangler/).
 

src/content/docs/sandbox/index.mdx

@@ -128,7 +128,7 @@ df['sales'].sum()  # Last expression is automatically returned
 
 <Feature header="Execute commands securely" href="/sandbox/guides/execute-commands/" cta="Learn about command execution">
 
-Run shell commands, Python scripts, Node.js applications, and more in isolated containers with streaming output support and automatic timeout handling.
+Run shell commands, Python scripts, Node.js applications, and more with streaming output support and automatic timeout handling.
 
 </Feature>
 
@@ -144,6 +144,12 @@ Expose HTTP services running in your sandbox with automatically generated previe
 
 </Feature>
 
+<Feature header="Execute code directly" href="/sandbox/guides/code-execution/" cta="Learn about code execution">
+
+Execute Python and JavaScript code with rich outputs including charts, tables, and images. Maintain persistent state between executions for AI-generated code and interactive workflows.
+
+</Feature>
+
 ---
 
 ## Use Cases
@@ -156,7 +162,7 @@ Execute code generated by Large Language Models safely and reliably. Perfect for
 
 ### Data Analysis & Notebooks
 
-Create interactive data analysis environments with Python, pandas, and visualization libraries. Build notebook-like experiences at the edge.
+Create interactive data analysis environments with pandas, NumPy, and Matplotlib. Generate charts, tables, and visualizations with automatic rich output formatting.
 
 ### Interactive Development Environments
 
@@ -194,35 +200,34 @@ Stateful coordination layer that enables Sandbox to maintain persistent environm
 
 <CardGrid>
 
-<LinkTitleCard title="Tutorials" href="/sandbox/tutorials/" icon="pen">
+<LinkTitleCard title="Tutorials" href="/sandbox/tutorials/" icon="open-book">
 	Explore complete examples including AI code execution, data analysis, and
 	interactive environments.
 </LinkTitleCard>
 
 <LinkTitleCard
-	title="Beta Information"
-	href="/sandbox/platform/beta-info/"
-	icon="seti:shell"
+	title="How-to Guides"
+	href="/sandbox/guides/"
+	icon="seti:notebook"
 >
-	Learn about the Sandbox Beta, current status, and upcoming features.
+	Learn how to solve specific problems and implement features with the Sandbox
+	SDK.
 </LinkTitleCard>
 
-<LinkTitleCard
-	title="Pricing"
-	href="/sandbox/platform/pricing/"
-	icon="document"
->
-	Understand Sandbox pricing based on the underlying Containers platform.
+<LinkTitleCard title="API Reference" href="/sandbox/api/" icon="seti:json">
+	Explore the complete API documentation for the Sandbox SDK.
 </LinkTitleCard>
 
-<LinkTitleCard title="Limits" href="/sandbox/platform/limits/" icon="document">
-	Learn about resource limits, quotas, and best practices for working within
-	them.
+<LinkTitleCard title="Concepts" href="/sandbox/concepts/" icon="seti:info">
+	Learn about the key concepts and architecture of the Sandbox SDK.
 </LinkTitleCard>
 
-<LinkTitleCard title="How-to Guides" href="/sandbox/guides/" icon="seti:lock">
-	Learn how to solve specific problems and implement features with the Sandbox
-	SDK.
+<LinkTitleCard
+	title="Configuration"
+	href="/sandbox/configuration/"
+	icon="setting"
+>
+	Learn about the configuration options for the Sandbox SDK.
 </LinkTitleCard>
 
 <LinkTitleCard
@@ -234,12 +239,33 @@ Stateful coordination layer that enables Sandbox to maintain persistent environm
 </LinkTitleCard>
 
 <LinkTitleCard
-	title="Developer Discord"
+	title="Beta Information"
+	href="/sandbox/platform/beta-info/"
+	icon="warning"
+>
+	Learn about the Sandbox Beta, current status, and upcoming features.
+</LinkTitleCard>
+
+<LinkTitleCard
+	title="Pricing"
+	href="/sandbox/platform/pricing/"
+	icon="seti:shell"
+>
+	Understand Sandbox pricing based on the underlying Containers platform.
+</LinkTitleCard>
+
+<LinkTitleCard title="Limits" href="/sandbox/platform/limits/" icon="error">
+	Learn about resource limits, quotas, and best practices for working within
+	them.
+</LinkTitleCard>
+
+<LinkTitleCard
+	title="Discord Community"
 	href="https://discord.cloudflare.com"
 	icon="discord"
 >
-	Connect with the Workers community on Discord. Ask questions, share what
-	you're building, and get help from other developers.
+	Connect with the community on Discord. Ask questions, share what you're
+	building, and get help from other developers.
 </LinkTitleCard>
 
 </CardGrid>

src/content/partials/containers/docker-setup.mdx

@@ -0,0 +1,4 @@
+You must have Docker running locally when you run `wrangler deploy`. For most people, the best way to install Docker is to follow the [docs for installing Docker Desktop](https://docs.docker.com/desktop/). Other tools like [Colima](https://github.com/abiosoft/colima) may also work.
+
+You can check that Docker is running properly by running the `docker info` command in your terminal. If Docker is running, the command will succeed. If Docker is not running,
+the `docker info` command will hang or return an error including the message "Cannot connect to the Docker daemon".