re-order

Tanushree Sharma · Tanushree Sharma · commit f7ee7d29479b · 2024-09-24T21:29:08.000-04:00
diff --git a/src/content/docs/workers/frameworks/get-started.mdx b/src/content/docs/workers/frameworks/get-started.mdx
diff --git a/src/content/docs/workers/runtime-apis/index.mdx b/src/content/docs/workers/runtime-apis/index.mdx
@@ -2,11 +2,10 @@
 pcx_content_type: navigation
 title: Runtime APIs
 sidebar:
-  order: 7
-
+  order: 6
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 The Workers runtime is designed to be [JavaScript standards compliant](https://ecma-international.org/publications-and-standards/standards/ecma-262/) and web-interoperable. Wherever possible, it uses web platform APIs, so that code can be reused across client and server, as well as across [WinterCG](https://wintercg.org/) JavaScript runtimes.
 
diff --git a/src/content/docs/workers/static-assets/binding.mdx b/src/content/docs/workers/static-assets/binding.mdx
@@ -50,7 +50,7 @@ assets = { directory = "./public", binding = "ASSETS" }
 
 **Response**
 
-- `Promise<Response>` Returns a static static asset matching the given request.
+- `Promise<Response>` Returns a static asset matching the given request.
 
 **Example**
 
diff --git a/src/content/docs/workers/static-assets/get-started.mdx b/src/content/docs/workers/static-assets/get-started.mdx
@@ -1,12 +1,11 @@
 ---
 pcx_content_type: concept
-title: Assets
+title: Get Started
 head: []
 sidebar:
-  order: 7
+  order: 6
   badge: Beta
-description: Use [Cloudflare Pages](/pages/) for hosting full-stack applications
-  instead of Workers Sites. Do not use Workers Sites for new projects.
+description: Run frontend websites — static or dynamic — directly on Cloudflare's global network.
 ---
 
 import {
@@ -17,7 +16,7 @@ import {
 	PackageManagers,
 } from "~/components";
 
-This guide will instruct you through setting up and deploying a static site or a full-stack application from scratch on Workers. You may prefer to build your website from scratch if:
+This guide will instruct you through setting up and deploying a static site or a full-stack application without a framework on Workers. You may prefer to build your website from scratch if:
 
 - You're interested in learning by implementing core functionalities on your own.
 - You're working on a simple project where a framework might be overkill.
diff --git a/src/content/docs/workers/static-assets/index.mdx b/src/content/docs/workers/static-assets/index.mdx
@@ -0,0 +1,62 @@
+---
+pcx_content_type: navigation
+title: Static Assets
+sidebar:
+  order: 6
+  badge: Beta
+head: []
+description: Create full-stack applications deployed to Cloudflare Workers.
+---
+
+import {
+	Badge,
+	Description,
+	InlineBadge,
+	Render,
+	TabItem,
+	Tabs,
+	Feature,
+} from "~/components";
+
+<Description>
+	Create fast, scalable frontend applications deployed to Cloudflare Workers.
+</Description>
+
+---
+
+### What you can build
+
+<Feature header="Static Websites" href="/workers/frameworks/get-started/#deploying-a-static-site" cta="Deploy a static site">
+
+Deploy static sites like blogs, portfolios, or documentation pages. Serve HTML, CSS, JavaScript, and media files directly from Cloudflare's network for low-latency access worldwide.
+
+</Feature>
+
+<Feature header="Full-stack Applications" href="/workers/frameworks/get-started/#deploying-a-dynamic-site" cta="Deploy a full-stack application">
+
+Build dynamic and interactive server-side rendered (SSR) applications on Cloudflare Workers.
+
+Combine asset hosting with Cloudflare's data and storage products such as [Workers KV](/kv/), [Durable Objects](/durable-objects/), and [R2 Storage](/r2/) to build full-stack applications. Manage both frontend and backend logic on Cloudflare's Developer Platform.
+
+</Feature>
+
+### Supported frameworks
+
+The following Frameworks are currently supported on Cloudflare Workers:
+
+- Angular
+- Astro
+- Docusaurus
+- Gatsby
+- Nuxt
+- Qwik
+- Remix
+- Solid
+- Svelte
+
+:::note
+
+If you're looking for a framework not on this list, it may be supported in [Cloudflare Pages](/pages/). For example, popular frameworks such as [Next.js](/pages/framework-guides/nextjs/) and [Vue](/pages/framework-guides/deploy-a-vue-site/) are supported on Pages. Visit [Pages Frameworks guides](/pages/framework-guides/) for a full list.
+
+Have a framework you would like to see supported on Workers or a feature request? Tell us about it! [link to feedback form]
+:::
diff --git a/src/content/docs/workers/static-assets/routing.mdx b/src/content/docs/workers/static-assets/routing.mdx
@@ -18,9 +18,14 @@ import {
 	Tabs,
 } from "~/components";
 
-## How it works
+## Routing: Worker and assets
 
-Assets are served using file-based routing. The structure and organization of files in your project's directory determine the routing paths for your application. If a request is found with a matching path to the current route requested then that asset will always be served.
+Assets are served using file-based routing. The structure and organization of files in your project's directory determine the routing paths for your application. When a request invokes a Worker with assets:
+
+1. If a request is found with a matching path to the current route requested then that asset will always be served.
+2. If there are no assets that match the current route requested then the Worker will be invoked. If there is no Worker, a 404 will be served dependent on [`not_found_handling`](/workers/static-assets/routing/#not_found_handling) configuration.
+
+## Routing: Asset Serving
 
 If a request does not match an asset based on file-based routing, files are served based on the configuration options defined. There are two areas of asset handling that can be configured:
 
