Changed the root URLs to the new ones

ToriLindsay · ToriLindsay · commit 48513508cdab · 2025-06-05T09:08:04.000+01:00
diff --git a/src/content/changelog/workers/2025-04-08-fullstack-on-workers.mdx b/src/content/changelog/workers/2025-04-08-fullstack-on-workers.mdx
@@ -14,23 +14,23 @@ import fullstackWorkers from "~/assets/images/changelog/workers/fullstack-on-wor
 
 The following full-stack frameworks now have Generally Available ("GA") adapters for Cloudflare Workers, and are ready for you to use in production:
 
-- [React Router v7 (Remix)](/workers/frameworks/framework-guides/react-router/)
-- [Astro](/workers/frameworks/framework-guides/astro/)
-- [Hono](/workers/frameworks/framework-guides/hono/)
-- [Vue.js](/workers/frameworks/framework-guides/vue/)
-- [Nuxt](/workers/frameworks/framework-guides/nuxt/)
-- [Svelte (SvelteKit)](/workers/frameworks/framework-guides/svelte/)
-- And [more](/workers/frameworks/).
+- [React Router v7 (Remix)](/workers/framework-guides/web-apps/react-router/)
+- [Astro](/workers/framework-guides/web-apps/astro/)
+- [Hono](/workers/framework-guides/web-apps/more-web-frameworks/hono/)
+- [Vue.js](/workers/framework-guides/web-apps/vue/)
+- [Nuxt](/workers/framework-guides/web-apps/more-web-frameworks/nuxt/)
+- [Svelte (SvelteKit)](/workers/framework-guides/web-apps/svelte/)
+- And [more](/workers/framework-guides/).
 
 The following frameworks are now in **beta**, with GA support coming very soon:
 
-- [Next.js](/workers/frameworks/framework-guides/nextjs/), supported through [@opennextjs/cloudflare](https://opennext.js.org/cloudflare) is now `v1.0-beta`.
-- [Angular](/workers/frameworks/framework-guides/angular/)
-- [SolidJS (SolidStart)](/workers/frameworks/framework-guides/solid/)
+- [Next.js](/workers/framework-guides/web-apps/nextjs/), supported through [@opennextjs/cloudflare](https://opennext.js.org/cloudflare) is now `v1.0-beta`.
+- [Angular](/workers/framework-guides/web-apps/more-web-frameworks/angular/)
+- [SolidJS (SolidStart)](/workers/framework-guides/web-apps/more-web-frameworks/solid/)
 
 You can also build complete full-stack apps on Workers **without a framework**:
 
 - You can [“just use Vite"](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin) and React together, and build a back-end API in the same Worker. Follow our [React SPA with an API tutorial](/workers/vite-plugin/tutorial/) to learn how.
 
 
-**Get started building today with our [framework guides](/workers/frameworks/)**,  or read our [Developer Week 2025 blog post](https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers) about all the updates to building full-stack applications on Workers.
+**Get started building today with our [framework guides](/workers/framework-guides/)**,  or read our [Developer Week 2025 blog post](https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers) about all the updates to building full-stack applications on Workers.
diff --git a/src/content/changelog/workers/2025-04-08-vite-plugin.mdx b/src/content/changelog/workers/2025-04-08-vite-plugin.mdx
@@ -18,7 +18,7 @@ This lets you get the best of both worlds for a full-stack app — you can use
 
 You can build any type of application with `@cloudflare/vite-plugin`, using any rendering mode, from single page applications (SPA) and static sites to server-side rendered (SSR) pages and API routes.
 
-[React Router v7 (Remix)](/workers/frameworks/framework-guides/react-router/) is the first full-stack framework to provide full support for Cloudflare Vite plugin, allowing you to use all parts of Cloudflare's developer platform, without additional build steps.
+[React Router v7 (Remix)](/workers/framework-guides/web-apps/react-router/) is the first full-stack framework to provide full support for Cloudflare Vite plugin, allowing you to use all parts of Cloudflare's developer platform, without additional build steps.
 
 You can also build complete full-stack apps on Workers **without a framework** — ["just use Vite"](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin) and React together, and build a back-end API in the same Worker. Follow our [React SPA with an API tutorial](/workers/vite-plugin/tutorial/) to learn how.
 
diff --git a/src/content/docs/developer-spotlight/tutorials/fullstack-authentication-with-next-js-and-cloudflare-d1.mdx b/src/content/docs/developer-spotlight/tutorials/fullstack-authentication-with-next-js-and-cloudflare-d1.mdx
@@ -22,7 +22,7 @@ import {
 	FileTree,
 } from "~/components";
 
-In this tutorial, you will build a [Next.js app](/workers/frameworks/framework-guides/nextjs/) with authentication powered by Auth.js, Resend, and [Cloudflare D1](/d1/).
+In this tutorial, you will build a [Next.js app](/workers/framework-guides/web-apps/nextjs/) with authentication powered by Auth.js, Resend, and [Cloudflare D1](/d1/).
 
 Before continuing, make sure you have a Cloudflare account and have installed and [authenticated Wrangler](https://developers.cloudflare.com/workers/wrangler/commands/#login). Some experience with HTML, CSS, and JavaScript/TypeScript is helpful but not required. In this tutorial, you will learn:
 
@@ -58,7 +58,7 @@ From within the repository or directory where you want to create your project ru
 	}}
 />
 
-This will create a new Next.js project using [OpenNext](https://opennext.js.org/cloudflare) that will run in a Worker using [Workers Static Assets](/workers/frameworks/framework-guides/nextjs/#static-assets).
+This will create a new Next.js project using [OpenNext](https://opennext.js.org/) that will run in a Worker using [Workers Static Assets](#static-assets).
 
 Before we get started, open your project's `tsconfig.json` file and modify the following to the `compilerOptions` object to allow for top level await needed to let our application get the Cloudflare context:
 
diff --git a/src/content/docs/pages/framework-guides/nextjs/ssr/get-started.mdx b/src/content/docs/pages/framework-guides/nextjs/ssr/get-started.mdx
@@ -19,7 +19,7 @@ import { PackageManagers, WranglerConfig } from "~/components";
 Learn how to deploy full-stack (SSR) Next.js apps to Cloudflare Pages.
 
 :::note
-You can now also deploy Next.js apps to [Cloudflare Workers](https://developers.cloudflare.com/workers/frameworks/), including apps that use the Node.js "runtime" from Next.js. This allows you to use the [Node.js APIs that Cloudflare Workers provides](/workers/runtime-apis/nodejs/#built-in-nodejs-runtime-apis), and ensures compatibility with a broader set of Next.js features and rendering modes.
+You can now also [deploy Next.js apps to Cloudflare Workers](/workers/framework-guides/web-apps/nextjs/), including apps that use the Node.js "runtime" from Next.js. This allows you to use the [Node.js APIs that Cloudflare Workers provides](/workers/runtime-apis/nodejs/#built-in-nodejs-runtime-apis), and ensures compatibility with a broader set of Next.js features and rendering modes.
 
 Refer to the [OpenNext docs for the `@opennextjs/cloudflare` adapter](https://opennext.js.org/cloudflare) to learn how to get started.
 :::
diff --git a/src/content/docs/pipelines/tutorials/send-data-from-client/index.mdx b/src/content/docs/pipelines/tutorials/send-data-from-client/index.mdx
@@ -34,7 +34,7 @@ For this tutorial, you will build a landing page for an e-commerce website. User
 
 ## 1. Create a new Workers project
 
-You will create a new Worker project that will use [Static Assets](/workers/static-assets/) to serve the HTML file. While you can use any front-end framework, this tutorial uses plain HTML and JavaScript to keep things simple. If you are interested in learning how to build and deploy a web application on Workers with Static Assets, you can refer to the [Frameworks](/workers/frameworks/) documentation.
+You will create a new Worker project that will use [Static Assets](/workers/static-assets/) to serve the HTML file. While you can use any front-end framework, this tutorial uses plain HTML and JavaScript to keep things simple. If you are interested in learning how to build and deploy a web application on Workers with Static Assets, you can refer to the [Frameworks](/workers/framework-guides/) documentation.
 
 Create a new Worker project by running the following commands:
 
diff --git a/src/content/docs/workers/ci-cd/builds/build-caching.mdx b/src/content/docs/workers/ci-cd/builds/build-caching.mdx
@@ -43,7 +43,7 @@ The following frameworks support build output caching:
 | Nuxt       | `node_modules/.cache/nuxt`                    |
 
 :::note
-[Static assets](/workers/static-assets/) and [frameworks](/workers/frameworks/) are now supported in Cloudflare Workers.
+[Static assets](/workers/static-assets/) and [frameworks](/workers/framework-guides/) are now supported in Cloudflare Workers.
 :::
 
 ### Limits
diff --git a/src/content/docs/workers/ci-cd/builds/configuration.mdx b/src/content/docs/workers/ci-cd/builds/configuration.mdx
@@ -76,4 +76,4 @@ It is recommended to consistently use the same API token across all uploads and
 
 ## Framework support
 
-[Static assets](/workers/static-assets/) and [frameworks](/workers/frameworks/) are now supported in Cloudflare Workers. Learn to set up Workers projects and the commands for each framework in [the framework guides](/workers/framework-guides/).
+[Static assets](/workers/static-assets/) and [frameworks](/workers/framework-guides/) are now supported in Cloudflare Workers. Learn to set up Workers projects and the commands for each framework in [the framework guides](/workers/framework-guides/).
diff --git a/src/content/docs/workers/framework-guides/web-apps/react-router.mdx b/src/content/docs/workers/framework-guides/web-apps/react-router.mdx
@@ -71,7 +71,7 @@ It combines with the [Cloudflare Vite plugin](/workers/vite-plugin/) to provide
 
         :::note
         SPA mode and prerendering are not currently supported when using the [Cloudflare Vite plugin](/workers/vite-plugin/).
-        If you wish to use React Router in an SPA then we recommend starting with the [React template](/workers/frameworks/framework-guides/react/) and using React Router [as a library](https://reactrouter.com/start/data/installation).
+        If you wish to use React Router in an SPA then we recommend starting with the [React template](/workers/framework-guides/web-apps/react/) and using React Router [as a library](https://reactrouter.com/start/data/installation).
         :::
 
         `vite.config.ts` is your [Vite config file](https://vite.dev/config/).
diff --git a/src/content/docs/workers/index.mdx b/src/content/docs/workers/index.mdx
@@ -17,7 +17,7 @@ A serverless platform for building, deploying, and scaling apps across [Cloudfla
 
 With Cloudflare Workers, you can expect to:
 - Deliver fast performance with high reliability anywhere in the world
-- Build full-stack apps with your framework of choice, including [React](/workers/frameworks/framework-guides/react/), [Vue](/workers/frameworks/framework-guides/vue/), [Svelte](/workers/frameworks/framework-guides/svelte/), [Next](/workers/frameworks/framework-guides/nextjs/), [Astro](/workers/frameworks/framework-guides/astro/), [React Router](/workers/frameworks/framework-guides/react-router/), [and more](/workers/frameworks/)
+- Build full-stack apps with your framework of choice, including [React](/workers/framework-guides/web-apps/react/), [Vue](/workers/framework-guides/web-apps/vue/), [Svelte](/workers/framework-guides/web-apps/svelte/), [Next](/workers/framework-guides/web-apps/nextjs/), [Astro](/workers/framework-guides/web-apps/astro/), [React Router](/workers/framework-guides/web-apps/react-router/), [and more](/workers/framework-guides/)
 - Use your preferred language, including [JavaScript](/workers/languages/javascript/), [TypeScript](/workers/languages/typescript/), [Python](/workers/languages/python/), [Rust](/workers/languages/rust/), [and more](/workers/runtime-apis/webassembly/)
 - Gain deep visibility and insight with built-in [observability](/workers/observability/logs/)
 - Get started for free and grow with flexible [pricing](/workers/platform/pricing/), affordable at any scale
diff --git a/src/content/docs/workers/static-assets/get-started.mdx b/src/content/docs/workers/static-assets/get-started.mdx
@@ -15,7 +15,7 @@ import {
 	PackageManagers,
 } from "~/components";
 
-For most front-end applications, you'll want to use a framework. Workers supports number of popular [frameworks](/workers/frameworks/) that come with ready-to-use components, a pre-defined and structured architecture, and community support. View [framework specific guides](/workers/frameworks/) to get started using a framework.
+For most front-end applications, you'll want to use a framework. Workers supports number of popular [frameworks](/workers/framework-guides/) that come with ready-to-use components, a pre-defined and structured architecture, and community support. View [framework specific guides](/workers/framework-guides/) to get started using a framework.
 
 Alternatively, you may prefer to build your website from scratch if:
 
diff --git a/src/content/docs/workers/static-assets/index.mdx b/src/content/docs/workers/static-assets/index.mdx
@@ -34,7 +34,7 @@ You can upload static assets (HTML, CSS, images and other files) as part of your
 
 <LinkCard
 	title="Supported frameworks"
-	href="/workers/frameworks/"
+	href="/workers/framework-guides/"
 	description="Start building on Workers with our framework guides."
 />
 
@@ -353,7 +353,7 @@ Now we can see a new button **Name from API**, and if you click the button, we c
 
 <LinkCard
 	title="Supported frameworks"
-	href="/workers/frameworks/"
+	href="/workers/framework-guides/"
 	description="Start building on Workers with our framework guides."
 />
 
diff --git a/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx b/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx
@@ -32,7 +32,7 @@ Migrating from Cloudflare Pages to Cloudflare Workers is often a straightforward
 
 ### Frameworks
 
-If your Pages project uses [a popular framework](/workers/frameworks/), most frameworks already have adaptors available for Cloudflare Workers. Switch out any Pages-specific adaptors for the Workers equivalent and follow any guidance that they provide.
+If your Pages project uses [a popular framework](/workers/framework-guides/), most frameworks already have adaptors available for Cloudflare Workers. Switch out any Pages-specific adaptors for the Workers equivalent and follow any guidance that they provide.
 
 ### Project configuration
 
@@ -452,6 +452,6 @@ This compatibility matrix compares the features of Workers and Pages. Unless oth
 
 [^3]: Workers Builds supports enabling [non-production branch builds](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds), though does not yet have the same level of configurability as Pages does.
 
-[^4]: Workers [supports popular frameworks](/workers/frameworks/), many of which implement file-based routing. Additionally, you can use Wrangler to [compile your folder of `functions/`](#folder-of-functions) into a Worker to help ease the migration from Pages to Workers.
+[^4]: Workers [supports popular frameworks](/workers/framework-guides/), many of which implement file-based routing. Additionally, you can use Wrangler to [compile your folder of `functions/`](#folder-of-functions) into a Worker to help ease the migration from Pages to Workers.
 
 [^5]: As in <sup>4</sup>, Wrangler can [compile your Pages Functions into a Worker](#folder-of-functions). Or if you are starting from scratch, everything that is possible with Pages Functions can also be achieved by adding code to your Worker or by using framework-specific plugins for relevant third party tools.
diff --git a/src/content/docs/workers/static-assets/migration-guides/netlify-to-workers.mdx b/src/content/docs/workers/static-assets/migration-guides/netlify-to-workers.mdx
@@ -13,7 +13,7 @@ You should already have an existing project deployed on Netlify that you would l
 
 ## Frameworks
 
-Some frameworks like Next.js, Astro with on demand rendering, and others have specific guides for migrating to Cloudflare Workers. Refer to our [framework guides](/workers/frameworks/) for more information. If your framework has a **Deploy an existing project on Workers** guide, follow that guide for specific instructions. Otherwise, continue with the steps below.
+Some frameworks like Next.js, Astro with on demand rendering, and others have specific guides for migrating to Cloudflare Workers. Refer to our [framework guides](/workers/framework-guides/) for more information. If your framework has a **Deploy an existing project on Workers** guide, follow that guide for specific instructions. Otherwise, continue with the steps below.
 
 ## Find your build command and build directory
 
@@ -62,7 +62,7 @@ For a **Single Page Application**, you will need to add the following to your Wr
 
 </WranglerConfig>
 
-Some frameworks provide specific guides for migrating to Cloudflare Workers. Please refer to our [framework guides](/workers/frameworks/) for more information. If your framework includes a “Deploy an existing project on Workers” guide, follow it for detailed instructions.
+Some frameworks provide specific guides for migrating to Cloudflare Workers. Please refer to our [framework guides](/workers/framework-guides/) for more information. If your framework includes a “Deploy an existing project on Workers” guide, follow it for detailed instructions.
 
 ## Create a new Workers project
 
diff --git a/src/content/docs/workers/static-assets/migration-guides/vercel-to-workers.mdx b/src/content/docs/workers/static-assets/migration-guides/vercel-to-workers.mdx
@@ -13,7 +13,7 @@ You should already have an existing project deployed on Vercel that you would li
 
 ## Frameworks
 
-Some frameworks like Next.js, Astro with on demand rendering, and others have specific guides for migrating to Cloudflare Workers. Refer to our [framework guides](/workers/frameworks/) for more information. If your framework has a **Deploy an existing project on Workers** guide, follow that guide for specific instructions. Otherwise, continue with the steps below.
+Some frameworks like Next.js, Astro with on demand rendering, and others have specific guides for migrating to Cloudflare Workers. Refer to our [framework guides](/workers/framework-guides/) for more information. If your framework has a **Deploy an existing project on Workers** guide, follow that guide for specific instructions. Otherwise, continue with the steps below.
 
 ## Find your build command and build directory
 
@@ -62,7 +62,7 @@ For a **single page application**, you will need to add the following to your wr
 
 </WranglerConfig>
 
-Some frameworks provide specific guides for migrating to Cloudflare Workers. Please refer to our [framework guides](/workers/frameworks/) for more information. If your framework includes a “Deploy an existing project on Workers” guide, follow it for detailed instructions.
+Some frameworks provide specific guides for migrating to Cloudflare Workers. Please refer to our [framework guides](/workers/framework-guides/) for more information. If your framework includes a “Deploy an existing project on Workers” guide, follow it for detailed instructions.
 
 ## Create a new Workers project
 
diff --git a/src/content/docs/workers/static-assets/routing/single-page-application.mdx b/src/content/docs/workers/static-assets/routing/single-page-application.mdx
@@ -8,7 +8,7 @@ sidebar:
 
 import { WranglerConfig, Aside, TypeScriptExample, Render } from "~/components";
 
-Single Page Applications (SPAs) are web applications which are client-side rendered (CSR). They are often built with a framework such as [React](/workers/frameworks/framework-guides/react/), [Vue](/workers/frameworks/framework-guides/vue/) or [Svelte](/workers/frameworks/framework-guides/svelte/). The build process of these frameworks will produce a single `/index.html` file and accompanying client-side resources (e.g. JavaScript bundles, CSS stylesheets, images, fonts, etc.). Typically, data is fetched by the client from an API with client-side requests.
+Single Page Applications (SPAs) are web applications which are client-side rendered (CSR). They are often built with a framework such as [React](/workers/framework-guides/web-apps/react/), [Vue](/workers/framework-guides/web-apps/vue/) or [Svelte](/workers/framework-guides/web-apps/svelte/). The build process of these frameworks will produce a single `/index.html` file and accompanying client-side resources (e.g. JavaScript bundles, CSS stylesheets, images, fonts, etc.). Typically, data is fetched by the client from an API with client-side requests.
 
 ## Configuration
 
diff --git a/src/content/docs/workers/static-assets/routing/static-site-generation.mdx b/src/content/docs/workers/static-assets/routing/static-site-generation.mdx
@@ -8,7 +8,7 @@ sidebar:
 
 import { WranglerConfig, Render } from "~/components";
 
-Static Site Generation (SSG) applications are web applications which are predominantely built or "prerendered" ahead-of-time. They are often built with a framework such as [Gatsby](/workers/frameworks/framework-guides/gatsby/) or [Docusaurus](/workers/frameworks/framework-guides/docusaurus/). The build process of these frameworks will produce many HTML files and accompanying client-side resources (e.g. JavaScript bundles, CSS stylesheets, images, fonts, etc.). Data is either static, fetched and compiled into the HTML at build-time, or fetched by the client from an API with client-side requests.
+Static Site Generation (SSG) applications are web applications which are predominantely built or "prerendered" ahead-of-time. They are often built with a framework such as [Gatsby](/workers/framework-guides/web-apps/more-web-frameworks/gatsby/) or [Docusaurus](/workers/framework-guides/web-apps/more-web-frameworks/docusaurus/). The build process of these frameworks will produce many HTML files and accompanying client-side resources (e.g. JavaScript bundles, CSS stylesheets, images, fonts, etc.). Data is either static, fetched and compiled into the HTML at build-time, or fetched by the client from an API with client-side requests.
 
 Often, an SSG framework will allow you to create a custom 404 page.
 
diff --git a/src/content/docs/workers/tutorials/live-cursors-with-nextjs-rpc-do/index.mdx b/src/content/docs/workers/tutorials/live-cursors-with-nextjs-rpc-do/index.mdx
@@ -838,5 +838,5 @@ In this tutorial, you learned how to integrate Next.js with Durable Objects to b
 You can check other Cloudflare tutorials or related resources:
 
 - [Workers RPC](/workers/runtime-apis/bindings/service-bindings/rpc/).
-- [Next.js and Workers Static Assets](/workers/frameworks/web-apps/nextjs/).
+- [Next.js and Workers Static Assets](/workers/framework-guides/web-apps/nextjs/).
 - [Build a seat booking app with SQLite in Durable Objects](/durable-objects/tutorials/build-a-seat-booking-app/).
diff --git a/src/content/docs/workers/vite-plugin/get-started.mdx b/src/content/docs/workers/vite-plugin/get-started.mdx
diff --git a/src/content/docs/workers/vite-plugin/index.mdx b/src/content/docs/workers/vite-plugin/index.mdx
diff --git a/src/content/docs/workers/vite-plugin/tutorial.mdx b/src/content/docs/workers/vite-plugin/tutorial.mdx
diff --git a/src/content/videos/index.yaml b/src/content/videos/index.yaml

Original file line number	Diff line number	Diff line change
`@@ -76,4 +76,4 @@ It is recommended to consistently use the same API token across all uploads and`
`76`	`76`
`77`	`77`	`## Framework support`
`78`	`78`
`79`		`-[Static assets](/workers/static-assets/) and [frameworks](/workers/frameworks/) are now supported in Cloudflare Workers. Learn to set up Workers projects and the commands for each framework in [the framework guides](/workers/framework-guides/).`
	`79`	`+[Static assets](/workers/static-assets/) and [frameworks](/workers/framework-guides/) are now supported in Cloudflare Workers. Learn to set up Workers projects and the commands for each framework in [the framework guides](/workers/framework-guides/).`