Fix some links

Author: GregBrimble

src/content/compatibility-flags/assets-navigation-prefers-asset-serving.md

@@ -11,7 +11,7 @@ enable_flag: "assets_navigation_prefers_asset_serving"
 disable_flag: "assets_navigation_has_no_effect"
 ---
 
-For Workers with [static assets](/workers/static-assets/) and this compatibility flag enabled, navigation requests (requests which have a `Sec-Fetch-Mode: navigate` header) will prefer to be served by our asset-serving logic, even when an exact asset match cannot be found. This is particularly useful for applications which operate in either [Single Page Application (SPA) mode](/workers/static-assets/routing/#not_found_handling--404-page--single-page-application--none) or [404 page mode](/workers/static-assets/routing/#not_found_handling--404-page--single-page-application--none), as this now means the fallback pages of `200 /index.html` and `404 /404.html` will be served ahead of invoking a Worker script and will therefore avoid incurring a charge.
+For Workers with [static assets](/workers/static-assets/) and this compatibility flag enabled, navigation requests (requests which have a `Sec-Fetch-Mode: navigate` header) will prefer to be served by our asset-serving logic, even when an exact asset match cannot be found. This is particularly useful for applications which operate in either [Single Page Application (SPA) mode](/workers/static-assets/routing/single-page-application/) or have [custom 404 pages](/workers/static-assets/routing/static-site-generation/#custom-404-pages), as this now means the fallback pages of `200 /index.html` and `404 /404.html` will be served ahead of invoking a Worker script and will therefore avoid incurring a charge.
 
 Without this flag, the runtime will continue to apply the old behavior of invoking a Worker script (if present) for any requests which do not exactly match a static asset.
 

src/content/docs/workers/configuration/multipart-upload-metadata.mdx

@@ -43,8 +43,8 @@ At a minimum, the `main_module` key is required to upload a Worker.
 
   * [Asset](/workers/static-assets/) configuration for a Worker.
   * `config` <Type text="object" /> <MetaInfo text="optional" />
-    * [html_handling](/workers/static-assets/routing/#1-html_handling) determines the redirects and rewrites of requests for HTML content.
-    * [not_found_handling](/workers/static-assets/routing/#2-not_found_handling) determines the response when a request does not match a static asset, and there is no Worker script.
+    * [html_handling](/workers/static-assets/routing/advanced/html-handling/) determines the redirects and rewrites of requests for HTML content.
+    * [not_found_handling](/workers/static-assets/routing/) determines the response when a request does not match a static asset.
   * `jwt` field provides a token authorizing assets to be attached to a Worker.
 
 * `keep_assets` <Type text="boolean" /> <MetaInfo text="optional" />

src/content/docs/workers/frameworks/framework-guides/astro.mdx

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Astro
-tags: ["full-stack"]
+tags: ["ssg", "full-stack"]
 description: Create an Astro application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 
@@ -38,7 +38,7 @@ import {
 
 Astro emphasizes performance through minimal client-side JavaScript - by default, it renders as much content as possible at build time, or [on-demand](https://docs.astro.build/en/guides/on-demand-rendering/) on the "server" - this can be a Cloudflare Worker. [“Islands”](https://docs.astro.build/en/concepts/islands/) of JavaScript are added only where interactivity or personalization is needed.
 
-Astro is also framework-agnostic, and supports every major UI framework, including React, Preact, Svelte, Vue, SolidJS , via its official [integrations](https://astro.build/integrations/).
+Astro is also framework-agnostic, and supports every major UI framework, including React, Preact, Svelte, Vue, SolidJS, via its official [integrations](https://astro.build/integrations/).
 
 ## Deploy a new Astro project on Workers
 
@@ -96,7 +96,7 @@ If your Astro project is entirely pre-rendered, follow these steps:
     </WranglerConfig>
     <Details header="What's this configuration doing?">
     	The key part of this config is the `assets` field, which tells Wrangler where to find your static assets. In this case, we're telling Wrangler to look in the `./dist` directory. If your assets are in a different directory, update the `directory` value accordingly.
-    		Read about other [asset configuration options](/workers/static-assets/routing/).
+    		Read about other [asset configuration options](/workers/wrangler/configuration/#assets).
 
     			Also note how there's no `main` field in this config - this is because you're only serving static assets, so no Worker code is needed for on demand rendering/SSR.
     </Details>
@@ -161,7 +161,7 @@ If your Astro project uses [on demand rendering (also known as SSR)](https://doc
         	- `main` points to the entry point of your Worker script. This is generated by the Astro adaptor, and is what powers your server-rendered pages.
         	- `assets.directory` tells Wrangler where to find your static assets. In this case, we're telling Wrangler to look in the `./dist` directory. If your assets are in a different directory, update the `directory` value accordingly.
 
-        	Read more about [Wrangler configuration options](/workers/wrangler/configuration/) and [asset configuration options](/workers/static-assets/routing/).
+        	Read more about [Wrangler configuration options](/workers/wrangler/configuration/) and [asset configuration options](/workers/wrangler/configuration/#assets).
         </Details>
 
 4.  **Build and deploy your project**

src/content/docs/workers/static-assets/binding.mdx

@@ -61,7 +61,7 @@ Now Wrangler will not upload these files as client-side assets when deploying th
 
 ## `run_worker_first`
 
-Controls whether to invoke the Worker script regardless of a request which would have otherwise matched an asset. `run_worker_first = false` ([default](/workers/static-assets/routing/#default-behavior)) will serve any static asset matching a request, while `run_worker_first = true` will unconditionally [invoke your Worker script](/workers/static-assets/routing/#invoking-worker-script-ahead-of-assets).
+Controls whether to invoke the Worker script regardless of a request which would have otherwise matched an asset. `run_worker_first = false` (default) will serve any static asset matching a request, while `run_worker_first = true` will unconditionally [invoke your Worker script](/workers/static-assets/routing/worker-script/#run-your-worker-script-first).
 
 <WranglerConfig>
 
@@ -115,7 +115,7 @@ In the example above, assets would be available through `env.ASSETS`.
 
 Your dynamic code can make new, or forward incoming requests to your project's static assets using the assets binding. For example, `env.ASSETS.fetch(request)`, `env.ASSETS.fetch(new URL('https://assets.local/my-file'))` or `env.ASSETS.fetch('https://assets.local/my-file')`.
 
-Take the following example that configures a Worker script to return a response under all requests headed for `/api/`. Otherwise, the Worker script will pass the incoming request through to the asset binding. In this case, because a Worker script is only invoked when the requested route has not matched any static assets, this will always evaluate [`not_found_handling`](/workers/static-assets/routing/#routing-configuration) behavior.
+Take the following example that configures a Worker script to return a response under all requests headed for `/api/`. Otherwise, the Worker script will pass the incoming request through to the asset binding. In this case, because a Worker script is only invoked when the requested route has not matched any static assets, this will always evaluate [`not_found_handling`](/workers/static-assets/routing/) behavior.
 
 <Tabs>
 <TabItem label="JavaScript" icon="seti:javascript">
@@ -166,7 +166,7 @@ For the various static asset routing configuration options, refer to [Routing](/
 
 ### Smart Placement with Worker Code First
 
-If you desire to run your [Worker code ahead of assets](/workers/static-assets/routing/#invoking-worker-script-ahead-of-assets) by setting `run_worker_first=true`, all requests must first travel to your Smart-Placed Worker. As a result, you may experience increased latency for asset requests.
+If you desire to run your [Worker code ahead of assets](/workers/static-assets/routing/worker-script/#run-your-worker-script-first) by setting `run_worker_first=true`, all requests must first travel to your Smart-Placed Worker. As a result, you may experience increased latency for asset requests.
 
 Use Smart Placement with `run_worker_first=true` when you need to integrate with other backend services, authenticate requests before serving any assets, or if your want to make modifications to your assets before serving them.
 
@@ -178,4 +178,4 @@ Enabling Smart Placement with `run_worker_first=false` (or not specifying it) le
 
 Use Smart Placement with `run_worker_first=false` (or not specifying it) when prioritizing fast asset delivery.
 
-This will not impact the [default routing behavior](/workers/static-assets/routing/#default-behavior).
+This will not impact the [default routing behavior](/workers/static-assets/routing/).

src/content/docs/workers/static-assets/direct-upload.mdx

@@ -177,7 +177,7 @@ If this is a Worker which already has assets, and you wish to just re-use the ex
 }
 ```
 
-Asset [routing configuration](/workers/static-assets/routing/#routing-configuration) can be provided in the `assets` object, such as `html_handling` and `not_found_handling`.
+Asset [routing configuration](/workers/wrangler/configuration/#assets) can be provided in the `assets` object, such as `html_handling` and `not_found_handling`.
 
 ```bash title="Example Worker Metadata Specifying Asset Configuration"
 {

src/content/docs/workers/static-assets/index.mdx

@@ -85,7 +85,7 @@ export default {
 
 By default, if a requested URL matches a file in the static assets directory, that file will always be served — without running Worker code. If no matching asset is found and a Worker is configured, the request will be processed by the Worker instead.
 
-- If no Worker is set up, the [`not_found_handling`](/workers/static-assets/routing/#2-not_found_handling-1) setting in your Wrangler configuration determines what happens next. By default, a `404 Not Found` response is returned.
+- If no Worker is set up, the [`not_found_handling`](/workers/static-assets/routing/) setting in your Wrangler configuration determines what happens next. By default, a `404 Not Found` response is returned.
 
 - If a Worker is configured and a request does not match a static asset, the Worker will handle the request. The Worker can choose to pass the request to the asset binding (through `env.ASSETS.fetch()`), following the `not_found_handling` rules.
 
@@ -117,7 +117,7 @@ If you want the Worker code to execute before serving an asset (for example, to
 
 <LinkCard
 	title="Routing options"
-	href="/workers/static-assets/routing/#routing-configuration"
+	href="/workers/static-assets/routing/"
 	description="Learn more about how you can customize routing behavior."
 />
 

src/content/docs/workers/static-assets/migrations/migrate-from-pages.mdx

@@ -193,7 +193,7 @@ Once the Worker script has been compiled, you can update your configuration file
 
 If you authored [a `_routes.json` file](/pages/functions/routing/#create-a-_routesjson-file) in your Pages project, or used [middleware](/pages/functions/middleware/) in Pages Functions, you must pay close attention to the configuration of your Worker script. Pages would default to serving your Pages Functions ahead of static assets and `_routes.json` and Pages Functions middleware allowed you to customize this behavior.
 
-Workers, on the other hand, will default to serving static assets ahead of your Worker script, unless you have configured [`assets.run_worker_first`](/workers/static-assets/routing/#invoking-worker-script-ahead-of-assets). This option is required if you are, for example, performing any authentication checks or logging requests before serving static assets.
+Workers, on the other hand, will default to serving static assets ahead of your Worker script, unless you have configured [`assets.run_worker_first`](/workers/static-assets/routing/worker-script/#run-your-worker-script-first). This option is required if you are, for example, performing any authentication checks or logging requests before serving static assets.
 
 <WranglerConfig>
 
@@ -400,7 +400,7 @@ This compatibility matrix compares the features of Workers and Pages. Unless oth
 | [Middleware](/workers/static-assets/binding/#run_worker_first)                                              | ✅ [^1] | ✅      |
 | [Redirects](/workers/static-assets/redirects/)                                                              | ✅      | ✅      |
 | [Smart Placement](/workers/configuration/smart-placement/)                                                  | ✅      | ✅      |
-| [Serve assets on a path](/workers/static-assets/routing/)                                                   | ✅      | ❌      |
+| [Serve assets on a path](/workers/static-assets/routing/advanced/serving-a-subdirectory/)                   | ✅      | ❌      |
 | **Observability**                                                                                           |         |         |
 | [Workers Logs](/workers/observability/)                                                                     | ✅      | ❌      |
 | [Logpush](/workers/observability/logs/logpush/)                                                             | ✅      | ❌      |

src/content/docs/workers/static-assets/routing/server-side-generated.mdx renamed to src/content/docs/workers/static-assets/routing/static-site-generation.mdx

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: concept
-title: Static-Site Generation (SSG) application
-description: How to configure and use a Static Site Generation (SSG) application with Workers.
+title: Static Site Generation (SSG) and custom 404 pages
+description: How to configure a Static Site Generation (SSG) application and custom 404 pages with Workers.
 sidebar:
   order: 3
 ---
@@ -32,10 +32,12 @@ In order to deploy a Static Site Generation application to Workers, you must con
 
 </WranglerConfig>
 
-Configuring `assets.not_found_handling` to `404-page` overrides the default serving behavior of Workers for static assets. When an incoming request does not match a file in the `assets.directory`, Workers will serve the contents of the nearest `404.html` file with a `404 Not Found` status.
-
 `assets.html_handling` defaults to `auto-trailing-slash` and this will usually give you the desired behavior automatically: individual files (e.g. `foo.html`) will be served _without_ a trailing flash and folder index files (e.g. `foo/index.html`) will be served _with_ a trailing slash. Alternatively, you can force trailing slashes (`force-trailing-slash`) or drop trailing slashes (`drop-trailing-slash`) on requests for HTML pages.
 
+### Custom 404 pages
+
+Configuring `assets.not_found_handling` to `404-page` overrides the default serving behavior of Workers for static assets. When an incoming request does not match a file in the `assets.directory`, Workers will serve the contents of the nearest `404.html` file with a `404 Not Found` status.
+
 <Render file="navigation_requests" />
 
 ## Local Development

src/content/docs/workers/vite-plugin/reference/static-assets.mdx

@@ -21,7 +21,7 @@ On running `vite build`, an output `wrangler.json` configuration file is generat
 The `assets.directory` field in this file is automatically populated with the path to your `client` build output.
 It is therefore not necessary to provide the `assets.directory` field in your input Worker configuration.
 
-The `assets` configuration should be used, however, if you wish to set [routing configuration](/workers/static-assets/routing/#routing-configuration) or enable the [assets binding](/workers/static-assets/binding/#binding).
+The `assets` configuration should be used, however, if you wish to set [routing configuration](/workers/static-assets/routing/) or enable the [assets binding](/workers/static-assets/binding/#binding).
 The following example configures the `not_found_handling` for a single-page application so that the fallback will always be the root `index.html` file.
 
 <WranglerConfig>

src/content/docs/workers/vite-plugin/tutorial.mdx

@@ -68,10 +68,10 @@ assets = { not_found_handling = "single-page-application" }
 
 </WranglerConfig>
 
-The [`not_found_handling`](/workers/static-assets/routing/#not_found_handling--404-page--single-page-application--none) value has been set to `single-page-application`.
+The [`not_found_handling`](/workers/single-page-application/) value has been set to `single-page-application`.
 This means that all not found requests will serve the `index.html` file.
 With the Cloudflare plugin, the `assets` routing configuration is used in place of Vite's default behavior.
-This ensures that your application's [routing configuration](/workers/static-assets/routing/#routing-configuration) works the same way while developing as it does when deployed to production.
+This ensures that your application's [routing configuration](/workers/static-assets/routing/) works the same way while developing as it does when deployed to production.
 
 Note that the [`directory`](/workers/static-assets/binding/#directory) field is not used when configuring assets with Vite.
 The `directory` in the output configuration will automatically point to the client build output.