[Workers] Restructure versions and deployments docs

.nimbus/routes.json

@@ -7963,7 +7963,6 @@
 		"/workers/configuration/integrations/external-services",
 		"/workers/configuration/multipart-upload-metadata",
 		"/workers/configuration/placement",
-		"/workers/configuration/previews",
 		"/workers/configuration/routing",
 		"/workers/configuration/routing/custom-domains",
 		"/workers/configuration/routing/routes",
@@ -7974,10 +7973,6 @@
 		"/workers/configuration/sites/start-from-existing",
 		"/workers/configuration/sites/start-from-scratch",
 		"/workers/configuration/sites/start-from-worker",
-		"/workers/configuration/versions-and-deployments",
-		"/workers/configuration/versions-and-deployments/gradual-deployments",
-		"/workers/configuration/versions-and-deployments/rollbacks",
-		"/workers/configuration/versions-and-deployments/version-overrides",
 		"/workers/configuration/workers-with-page-rules",
 		"/workers/databases",
 		"/workers/databases/analytics-engine",
@@ -8319,6 +8314,14 @@
 		"/workers/tutorials/upload-assets-with-r2",
 		"/workers/tutorials/using-prisma-postgres-with-workers",
 		"/workers/tutorials/workers-kv-from-rust",
+		"/workers/versions-and-deployments",
+		"/workers/versions-and-deployments/deployment-management",
+		"/workers/versions-and-deployments/gradual-deployments",
+		"/workers/versions-and-deployments/gradual-deployments/version-affinity",
+		"/workers/versions-and-deployments/gradual-deployments/with-durable-objects",
+		"/workers/versions-and-deployments/preview-urls",
+		"/workers/versions-and-deployments/rollbacks",
+		"/workers/versions-and-deployments/version-overrides",
 		"/workers/vite-plugin",
 		"/workers/vite-plugin/get-started",
 		"/workers/vite-plugin/reference",

public/__redirects

@@ -2259,7 +2259,7 @@
 /workers/platform/sites/configuration/ /workers/configuration/sites/configuration/ 301
 /workers/platform/deploy-button/ /workers/platform/deploy-buttons/ 301
 /workers/configuration/deploy-button/ /workers/platform/deploy-buttons/ 301
-/workers/platform/deployments/ /workers/configuration/versions-and-deployments/ 301
+/workers/platform/deployments/ /workers/versions-and-deployments/ 301
 /workers/platform/environment-variables/ /workers/configuration/environment-variables/ 301
 /workers/platform/smart-placement/ /workers/configuration/placement/ 301
 /workers/configuration/smart-placement/ /workers/configuration/placement/ 301
@@ -2280,7 +2280,13 @@
 /workers/runtime-apis/service-bindings/ /workers/runtime-apis/bindings/service-bindings/ 301
 /workers/observability/local-development-and-testing/ /workers/local-development/ 301
 /workers/observability/sentry-integration/ /workers/observability/integrations/sentry 301
-/workers/configuration/deployments/ /workers/configuration/versions-and-deployments/ 301
+/workers/configuration/deployments/ /workers/versions-and-deployments/ 301
+/workers/configuration/previews/ /workers/versions-and-deployments/preview-urls/ 301
+/workers/configuration/versions-and-deployments/ /workers/versions-and-deployments/ 301
+/workers/configuration/versions-and-deployments/gradual-deployments/ /workers/versions-and-deployments/gradual-deployments/ 301
+/workers/configuration/versions-and-deployments/version-overrides/ /workers/versions-and-deployments/version-overrides/ 301
+/workers/configuration/versions-and-deployments/rollbacks/ /workers/versions-and-deployments/rollbacks/ 301
+/workers/static-assets/routing/advanced/gradual-rollouts/ /workers/versions-and-deployments/gradual-deployments/version-affinity/ 301
 /workers/configuration/continuous-integration/ /workers/ci-cd/ 301
 /workers/wrangler/ci-cd/ /workers/ci-cd/external-cicd/ 301
 /workers/tutorials/hello-world-rust/ /workers/tutorials/ 301

src/content/changelog/workers/2025-02-03-workers-metrics-revamp.mdx

@@ -10,7 +10,7 @@ We've revamped the [Workers Metrics dashboard](https://dash.cloudflare.com/?to=/
 
 ![Workers Metrics dashboard](~/assets/images/workers/observability/workers-metrics.png)
 
-Now you can easily compare metrics across Worker versions, understand the current state of a [gradual deployment](/workers/configuration/versions-and-deployments/gradual-deployments/), and review key Workers metrics in a single view. This new interface enables you to:
+Now you can easily compare metrics across Worker versions, understand the current state of a [gradual deployment](/workers/versions-and-deployments/gradual-deployments/), and review key Workers metrics in a single view. This new interface enables you to:
 
 - Drag-and-select using a graphical timepicker for precise metric selection.
 

src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx

@@ -14,7 +14,7 @@ The Deploy to Cloudflare button:
 1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing. 
 2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment. 
 3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](/workers/ci-cd/builds/).
-4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/configuration/previews/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
+4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/versions-and-deployments/preview-urls/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).   
 
 ![Import repo or choose template](~/assets/images/workers/dtw-user-flow.png)
 

src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx

@@ -6,7 +6,7 @@ tags:
 date: 2025-08-14T01:00:00Z
 ---
 
-We've updated [preview URLs](/workers/configuration/previews/) for Cloudflare Workers to support long branch names.
+We've updated [preview URLs](/workers/versions-and-deployments/preview-urls/) for Cloudflare Workers to support long branch names.
 
 Previously, branch and Worker names exceeding the 63-character DNS limit would cause alias generation to fail, leaving pull requests without aliased preview URLs. This particularly impacted teams relying on descriptive branch naming.
 
@@ -22,4 +22,4 @@ Now, Cloudflare automatically truncates long branch names and appends a unique h
 ## Requirements and compatibility 
 
 - **Wrangler 4.30.0 or later**: This feature requires updating to wrangler@4.30.0+
-- **No configuration needed**: Works automatically with existing preview URL setups
+- **No configuration needed**: Works automatically with existing preview URL setups

src/content/changelog/workers/2025-09-03-new-workers-api.mdx

@@ -189,7 +189,7 @@ This dual approach means:
 ## Learn more
 - [Infrastructure as Code (IaC) guide](/workers/platform/infrastructure-as-code)
 - [API documentation](/api/resources/workers/subresources/beta/)
-- [Versions and Deployments overview](/workers/configuration/versions-and-deployments/)
+- [Versions and Deployments overview](/workers/versions-and-deployments/)
 
 ## Technical notes
 

src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx

@@ -11,8 +11,8 @@ This allows you to:
 
 * Promote any of the 100 most recent versions to be the active deployment. 
 
-* Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
+* Split traffic using [gradual deployments](/workers/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
 
 You can do this through the Cloudflare dashboard or with [Wrangler's rollback command](/workers/wrangler/commands/general/#rollback)
 
-Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/). 
+Learn more about [versioned deployments](/workers/versions-and-deployments/) and [rollbacks](/workers/versions-and-deployments/rollbacks/). 

src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx

@@ -5,7 +5,7 @@ date: 2025-09-17
 ---
 import { WranglerConfig, Aside } from "~/components";
 
-To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/configuration/previews/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
+To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/versions-and-deployments/preview-urls/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. 
 
 ## One-Time Update for Workers with workers.dev Disabled
 We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](/workers/configuration/routing/workers-dev/) was also disabled.
@@ -16,7 +16,7 @@ If your Worker was affected, its preview URL (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAI
 
 **How to Re-enable Your Preview URL**
 
-If your preview URL was disabled, you can re-enable it [via the Cloudflare dashboard](/workers/configuration/previews/#toggle-preview-urls-enable-or-disable) by navigating to your Worker's Settings page and toggling on the Preview URL.
+If your preview URL was disabled, you can re-enable it [via the Cloudflare dashboard](/workers/versions-and-deployments/preview-urls/#toggle-preview-urls-enable-or-disable) by navigating to your Worker's Settings page and toggling on the Preview URL.
 
 Alternatively, you can use Wrangler by adding the `preview_urls = true` setting to your Wrangler file and redeploying the Worker.
 

src/content/changelog/workers/2025-10-03-one-click-access-for-workers.mdx

@@ -8,7 +8,7 @@ date: 2025-10-03
 
 import { DashButton } from "~/components";
 
-You can now enable [Cloudflare Access](/cloudflare-one/access-controls/policies/) for your [`workers.dev`](/workers/configuration/routing/workers-dev/) and [Preview URLs](/workers/configuration/previews/) in a single click.
+You can now enable [Cloudflare Access](/cloudflare-one/access-controls/policies/) for your [`workers.dev`](/workers/configuration/routing/workers-dev/) and [Preview URLs](/workers/versions-and-deployments/preview-urls/) in a single click.
 
 ![Screenshot of the Enable/Disable Cloudflare Access button on the workers.dev route settings page](~/assets/images/workers/changelog/workers-access.png)
 

src/content/changelog/workers/2025-10-23-preview-url-default-behavior.mdx

@@ -3,7 +3,7 @@ title: Workers Preview URL default behavior now matches your workers.dev setting
 description: If a Workers Preview URL setting is not explicitly configured, its default behavior will now match the setting of the workers.dev subdomain.
 date: 2025-10-23
 ---
-We have updated the default behavior for Cloudflare Workers [Preview URLs](/workers/configuration/previews/). **Going forward, if a preview URL setting is not [explicitly configured](/workers/configuration/previews/#toggle-preview-urls-enable-or-disable) during deployment, its default behavior will automatically match the setting of your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/).**
+We have updated the default behavior for Cloudflare Workers [Preview URLs](/workers/versions-and-deployments/preview-urls/). **Going forward, if a preview URL setting is not [explicitly configured](/workers/versions-and-deployments/preview-urls/#toggle-preview-urls-enable-or-disable) during deployment, its default behavior will automatically match the setting of your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/).**
 
 This change is intended to provide a more intuitive and secure experience by aligning your preview URL's default state with your `workers.dev` configuration to prevent cases where a preview URL might remain public even after you disabled your `workers.dev` route.
 
@@ -12,7 +12,7 @@ This change is intended to provide a more intuitive and secure experience by ali
 - **If your workers.dev route is enabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to enabled
 - **If your workers.dev route is disabled and you do not explicitly set Preview URLs to enabled or disabled:** Preview URLs will default to disabled
 
-You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/configuration/previews/#from-the-dashboard), or [Wrangler](/workers/configuration/previews/#from-the-wrangler-configuration-file). 
+You can override the default setting by explicitly enabling or disabling the preview URL in your Worker's configuration through the [API](/api/resources/workers/subresources/scripts/subresources/subdomain/), [Dashboard](/workers/versions-and-deployments/preview-urls/#from-the-dashboard), or [Wrangler](/workers/versions-and-deployments/preview-urls/#from-the-wrangler-configuration-file). 
 
 **Wrangler Version Behavior**
 

src/content/changelog/workers/2025-10-30-builds-preview.mdx

@@ -6,7 +6,7 @@ products:
 date: 2025-10-30
 ---
 
-You can now access [preview URLs](/workers/configuration/previews/) directly from the build details page, making it easier to test your changes when reviewing builds in the dashboard.
+You can now access [preview URLs](/workers/versions-and-deployments/preview-urls/) directly from the build details page, making it easier to test your changes when reviewing builds in the dashboard.
 
 ![preview button](src/assets/images/changelog/workers/builds-preview-button.png)
 

src/content/changelog/workers/2026-02-25-wrangler-autoconfig-ga.mdx

@@ -30,7 +30,7 @@ You can also use [`wrangler setup`](/workers/wrangler/commands/general/#setup) t
 
 ![Automatic configuration pull request created by Workers Builds](~/assets/images/workers/ci-cd/builds/automatic-pr.png)
 
-When you connect a repository through the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create), a [pull request is generated](/workers/ci-cd/builds/automatic-prs/) for you with all necessary files, and a [preview deployment](/workers/configuration/previews/) to check before merging.
+When you connect a repository through the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create), a [pull request is generated](/workers/ci-cd/builds/automatic-prs/) for you with all necessary files, and a [preview deployment](/workers/versions-and-deployments/preview-urls/) to check before merging.
 
 :::note
 A pull request is only generated when your deploy command is `npx wrangler deploy`. If you use a custom deploy command, automatic configuration still runs but a PR is not created.

src/content/changelog/workers/2026-05-14-domains-tab.mdx

@@ -12,7 +12,7 @@ In your Worker's dashboard, there is now a dedicated **Domains** tab where you c
 
 ![The new Domains tab in the Workers dashboard](~/assets/images/workers/changelog/domains-tab.png)
 
-You can also enable or disable your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/) and [Preview URLs](/workers/configuration/previews/), put them behind [Cloudflare Access](/cloudflare-one/access-controls/) to require sign-in, and jump directly to [analytics](/analytics/) or domain overview for any connected domain.
+You can also enable or disable your [`workers.dev` subdomain](/workers/configuration/routing/workers-dev/) and [Preview URLs](/workers/versions-and-deployments/preview-urls/), put them behind [Cloudflare Access](/cloudflare-one/access-controls/) to require sign-in, and jump directly to [analytics](/analytics/) or domain overview for any connected domain.
 
 To get started, go to **Workers & Pages**, select a Worker, and open the **Domains** tab.
 

src/content/docs/cloudflare-for-platforms/workers-for-platforms/reference/limits.mdx

@@ -36,7 +36,7 @@ You can set a maximum of eight tags per script. Avoid special characters like `,
 
 ## Gradual Deployments
 
-[Gradual Deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) is not supported yet for user Workers. Changes made to user Workers create a new version that deployed all-at-once to 100% of traffic.
+[Gradual Deployments](/workers/versions-and-deployments/gradual-deployments/) is not supported yet for user Workers. Changes made to user Workers create a new version that deployed all-at-once to 100% of traffic.
 
 ## API Rate Limits
 

src/content/docs/containers/platform-details/limits.mdx

@@ -54,4 +54,4 @@ The following limits apply per account:
 | Image size                      | Same as [instance disk space](#instance-types) |
 | Total image storage per account | 50 GB [^1]                                     |
 
-[^1]: Delete container images with `wrangler containers delete` to free up space. If you delete a container image and then [roll back](/workers/configuration/versions-and-deployments/rollbacks/) your Worker to a previous version, this version may no longer work.
+[^1]: Delete container images with `wrangler containers delete` to free up space. If you delete a container image and then [roll back](/workers/versions-and-deployments/rollbacks/) your Worker to a previous version, this version may no longer work.

src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx

@@ -17,7 +17,7 @@ storage. Durable Objects
 <GlossaryTooltip term="Storage API">Storage API</GlossaryTooltip> provides
 access to a Durable Object's attached storage.
 
-A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/configuration/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects.
+A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects.
 
 ## Access storage
 

src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx

@@ -86,7 +86,7 @@ A Durable Object incurs charges only when it is **actively running in-memory**,
 
 Durable Objects will occasionally shut down and objects are restarted, which will run your Durable Object class constructor. This can happen for various reasons, including:
 
-- New Worker [deployments](/workers/configuration/versions-and-deployments/) with code updates
+- New Worker [deployments](/workers/versions-and-deployments/) with code updates
 - Lack of requests to an object following the state transitions documented above
 - Cloudflare updates to the Workers runtime system
 - Workers runtime decisions on where to host objects