restructure

Author: emily-shen

src/content/docs/containers/beta-info.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: reference
 title: Beta Info & Roadmap
 sidebar:
-  order: 2
+  order: 9
 ---
 
 Currently, Containers are in beta. There are several changes we plan to make prior to GA:

src/content/docs/containers/container-package.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: navigation
 title: Container Package
 sidebar:
-  order: 8
+  order: 5
 ---
 
 When writing code that interacts with a container instance, you can either use a

src/content/docs/containers/faq.mdx

@@ -2,9 +2,7 @@
 pcx_content_type: navigation
 title: Frequently Asked Questions
 sidebar:
-  order: 5
-  group:
-    hideIndex: true
+  order: 10
 ---
 
 import { WranglerConfig } from "~/components";

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

@@ -2,7 +2,7 @@
 pcx_content_type: get-started
 title: Getting started
 sidebar:
-  order: 1
+  order: 2
 ---
 
 import { WranglerConfig, PackageManagers } from "~/components";

src/content/docs/containers/local-dev.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: reference
 title: Local Development
 sidebar:
-  order: 3
+  order: 6
 ---
 
 You can run both your container and your Worker locally, without additional configuration, by running [`npx wrangler dev`](/workers/wrangler/commands/#dev) (or `vite dev` for Vite projects using the [Cloudflare Vite plugin](/workers/vite-plugin/)) in your project's directory.

src/content/docs/containers/architecture.mdx renamed to src/content/docs/containers/platform-details/architecture.mdx

@@ -1,12 +1,10 @@
 ---
 pcx_content_type: reference
-title: Architecture
+title: Container Lifecycle
 sidebar:
-  order: 9
+  order: 1
 ---
 
-This page describes the architecture of Cloudflare Containers.
-
 ## How and where containers run
 
 After you deploy a Worker that uses a Container, your image is uploaded to

src/content/docs/containers/durable-object-methods.mdx renamed to src/content/docs/containers/platform-details/durable-object-methods.mdx

@@ -0,0 +1,38 @@
+---
+pcx_content_type: reference
+title: Environment Variables
+sidebar:
+  order: 7
+---
+
+import { WranglerConfig } from "~/components";
+
+## Runtime environment variables
+
+The container runtime automatically sets the following variables:
+
+- `CLOUDFLARE_APPLICATION_ID` - the ID of the Containers application
+- `CLOUDFLARE_COUNTRY_A2` - the [ISO 3166-1 Alpha 2 code](https://www.iso.org/obp/ui/#search/code/) of a country the container is placed in
+- `CLOUDFLARE_DEPLOYMENT_ID` - the ID of the container instance
+- `CLOUDFLARE_LOCATION` - a name of a location the container is placed in
+- `CLOUDFLARE_PLACEMENT_ID` - a placement ID
+- `CLOUDFLARE_REGION` - a region name
+- `CLOUDFLARE_DURABLE_OBJECT_ID` - the ID of the Durable Object that the container is bound to
+
+## Custom environment variables
+
+Custom environment variables can be set when defining a Container in your Worker:
+
+```javascript
+class MyContainer extends Container {
+	defaultPort = 4000;
+	envVars = {
+		MY_CUSTOM_VAR: "value",
+		ANOTHER_VAR: "another_value",
+	};
+}
+```
+
+:::note
+If you supply environment variables with the same names, supplied values will override predefined values.
+:::

src/content/docs/containers/platform-details/environment-variables.mdx

@@ -0,0 +1,8 @@
+---
+pcx_content_type: navigation
+title: Platform Reference
+sidebar:
+  order: 4
+  group:
+    hideIndex: true
+---