New routing docs

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Angular
-head: []
+tags: ["full-stack"]
 description: Create an Angular application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Astro
-head: []
+tags: ["full-stack"]
 description: Create an Astro application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Docusaurus
-head: []
+tags: ["ssg"]
 description: Create a Docusaurus application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Gatsby
-head: []
+tags: ["ssg"]
 description: Create a Gatsby application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Next.js
-head: []
+tags: ["full-stack"]
 description: Create an Next.js application and deploy it to Cloudflare Workers with Workers Assets.
 sidebar:
   badge: Beta

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Nuxt
-head: []
+tags: ["full-stack"]
 description: Create a Nuxt application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Qwik
-head: []
+tags: ["full-stack"]
 description: Create a Qwik application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

src/content/docs/workers/frameworks/framework-guides/react-router.mdx

@@ -1,6 +1,7 @@
 ---
 pcx_content_type: how-to
 title: React Router (formerly Remix)
+tags: ["full-stack"]
 description: Create a React Router application and deploy it to Cloudflare Workers
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: React
-head: []
+tags: ["spa"]
 description: Create a React application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Solid
-head: []
+tags: ["full-stack"]
 description: Create a Solid application and deploy it to Cloudflare Workers with Workers Assets.
 sidebar:
   badge: Beta

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Svelte
-head: []
+tags: ["spa"]
 description: Create a Svelte application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: how-to
 title: Vue
-head: []
+tags: ["spa"]
 description: Create a Vue application and deploy it to Cloudflare Workers with Workers Assets.
 ---
 

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

@@ -15,6 +15,7 @@ import {
 	Render,
 	TabItem,
 	Tabs,
+	TypeScriptExample,
 } from "~/components";
 import { Icon } from "astro-icon/components";
 
@@ -213,7 +214,7 @@ Optionally, an assets binding can be provided if you wish to fetch and serve ass
 
 ## Programmatic Example
 
-<Tabs> <TabItem label="TypeScript" icon="seti:typescript">
+<TypeScriptExample>
 
 ```ts
 import * as fs from "fs";
@@ -427,4 +428,4 @@ if (buckets.length > 0) {
 await scriptUpload(completionToken);
 ```
 
-</TabItem> </Tabs>
+</TypeScriptExample>

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

@@ -23,6 +23,12 @@ When serving static assets, Workers will attach some headers to the response by
 
   This header complements the default `Cache-Control` header. Its value is a hash of the static asset file, and browsers can use this in subsequent requests with an `If-None-Match` header to check for freshness, without needing to re-download the entire file in the case of a match.
 
+- **`CF-Cache-Status`**
+
+  This header indicates whether the asset was served from the cache (`HIT`) or not (`MISS`).[^1]
+
 Cloudflare reserves the right to attach new headers to static asset responses at any time in order to improve performance or harden the security of your Worker application.
 
 <Render file="custom_headers" params={{ product: "workers" }} />
+
+[^1]: Due to a technical limitation that we hope to address in the future, the `CF-Cache-Status` header is not always entirely accurate. It is possible for false-positives and false-negatives to occur. This should be rare. In the meantime, this header should be considered as returning a "probablistic" result.