move kv files

_config.ts

@@ -137,9 +137,9 @@ site.copy("timeUtils.ts");
 site.copy("subhosting/api/images");
 site.copy("deploy/docs-images");
 site.copy("deploy/images");
-site.copy("deploy/kv/manual/images");
+site.copy("deploy/classic/images");
+site.copy("deploy/kv/images");
 site.copy("deploy/tutorials/images");
-site.copy("deploy/kv/tutorials/images");
 site.copy("runtime/fundamentals/images");
 site.copy("runtime/getting_started/images");
 site.copy("runtime/reference/images");

deploy/_data.ts

@@ -84,6 +84,29 @@ export const sidebar = [
       },
     ],
   },
+  {
+    title: "KV",
+    items: [
+      { title: "Overview", href: "/deploy/kv/" },
+      { title: "Key space", href: "/deploy/kv/key_space/" },
+      { title: "Operations", href: "/deploy/kv/operations/" },
+      {
+        title: "Key expiration",
+        href: "/deploy/kv/key_expiration/",
+      },
+      {
+        title: "Secondary indexes",
+        href: "/deploy/kv/secondary_indexes/",
+      },
+      { title: "Transactions", href: "/deploy/kv/transactions/" },
+      { title: "Node", href: "/deploy/kv/node/" },
+      {
+        title: "Data modeling",
+        href: "/deploy/kv/data_modeling_typescript/",
+      },
+      { title: "Backup", href: "/deploy/kv/backup/" },
+    ],
+  },
   {
     title: "Policies and Limits",
     items: [

deploy/classic/_data.ts

@@ -48,36 +48,13 @@ export const sidebar = [
         title: "Logs",
         href: "/deploy/classic/logs/",
       },
-      {
-        title: "KV",
-        items: [
-          { title: "Overview", href: "/deploy/kv/manual/" },
-          { title: "Key space", href: "/deploy/kv/manual/key_space/" },
-          { title: "Operations", href: "/deploy/kv/manual/operations/" },
-          {
-            title: "Key expiration",
-            href: "/deploy/kv/manual/key_expiration/",
-          },
-          {
-            title: "Secondary indexes",
-            href: "/deploy/kv/manual/secondary_indexes/",
-          },
-          { title: "Transactions", href: "/deploy/kv/manual/transactions/" },
-          { title: "Node", href: "/deploy/kv/manual/node/" },
-          {
-            title: "Data modeling",
-            href: "/deploy/kv/manual/data_modeling_typescript/",
-          },
-          { title: "Backup", href: "/deploy/kv/manual/backup/" },
-        ],
-      },
       {
         title: "Queues",
-        href: "/deploy/kv/manual/queue_overview/",
+        href: "/deploy/classic/queues/",
       },
       {
         title: "Cron",
-        href: "/deploy/kv/manual/cron/",
+        href: "/deploy/classic/cron/",
       },
       {
         title: "Edge cache",

deploy/kv/manual/cron.md → deploy/classic/cron.md

@@ -2,6 +2,7 @@
 title: "Scheduling cron tasks"
 oldUrl:
   - /kv/manual/cron/
+  - /deploy/kv/manual/cron/
 ---
 
 :::info Legacy Documentation
@@ -76,7 +77,7 @@ Any nested `Deno.cron` definitions (e.g. inside
 in an error or will be ignored.
 
 If you need to schedule tasks dynamically during your Deno program execution,
-you can use the [Deno Queues](./queue_overview) APIs.
+you can use the [Deno Queues](/deploy/classic/queues/) APIs.
 
 ### Time zone
 

deploy/kv/manual/queue_overview.md → deploy/classic/queues.md

@@ -2,8 +2,17 @@
 title: "Using Queues"
 oldUrl:
   - /kv/manual/queue_overview/
+  - /deploy/kv/manual/queue_overview/
 ---
 
+:::info Legacy Documentation
+
+You are viewing legacy documentation for Deno Deploy Classic. We recommend
+migrating to the new
+<a href="/deploy/">Deno Deploy</a> platform.
+
+:::
+
 <deno-admonition></deno-admonition>
 
 The Deno runtime includes a queueing API that supports offloading larger
@@ -108,8 +117,9 @@ kv.listenQueue((msg: unknown) => {
 
 ## Queue API with KV atomic transactions
 
-You can combine the queue API with [KV atomic transactions](./transactions) to
-atomically enqueue messages and modify keys in the same transaction.
+You can combine the queue API with
+[KV atomic transactions](/deploy/kv/transactions/) to atomically enqueue
+messages and modify keys in the same transaction.
 
 ```ts title="kv_transaction_example.ts"
 const kv = await Deno.openKv();
@@ -160,8 +170,8 @@ It's important to design your applications such that duplicate messages are
 handled correctly.
 
 You may use queues in combination with
-[KV atomic transactions](/deploy/kv/manual/transactions) primitives to ensure
-that your queue handler KV updates are performed exactly once per message. See
+[KV atomic transactions](/deploy/kv/transactions) primitives to ensure that your
+queue handler KV updates are performed exactly once per message. See
 [Queue API with KV atomic transactions](#queue-api-with-kv-atomic-transactions).
 
 ### Automatic retries
@@ -230,9 +240,7 @@ there's no need to wait for the underlying task to be completed before returning
 a response.
 
 In these cases, you can offload work to a queue to keep your web application
-responsive and send immediate feedback to clients. To see an example of this use
-case in action, check out our
-[webhook processing example](../tutorials/webhook_processor.md).
+responsive and send immediate feedback to clients.
 
 ### Scheduling work for the future
 
@@ -242,6 +250,3 @@ to send a notification to a new customer a day after they have placed an order
 to send them a satisfaction survey. You can schedule a queue message to be
 delivered 24 hours into the future, and set up a listener to send out the
 notification at that time.
-
-To see an example of scheduling a notification to go out in the future, check
-out our [notification example](../tutorials/schedule_notification.md).

deploy/kv/manual/backup.md → deploy/kv/backup.md

@@ -2,18 +2,11 @@
 title: "Backups"
 oldUrl:
   - /kv/manual/backup/
+  - /deploy/kv/manual/backup/
 ---
 
-:::info Legacy Documentation
-
-You are viewing legacy documentation for Deno Deploy Classic. We recommend
-migrating to the new
-<a href="/deploy/">Deno Deploy</a> platform.
-
-:::
-
-KV databases hosted on Deno Deploy Classic can be continuously backed up to your
-own S3-compatible storage buckets. This is in addition to the replication and
+KV databases hosted on Deno Deploy can be continuously backed up to your own
+S3-compatible storage buckets. This is in addition to the replication and
 backups that we internally perform for all data stored in hosted Deno KV
 databases to ensure high availability and data durability.
 

deploy/kv/manual/data_modeling_typescript.md → deploy/kv/data_modeling_typescript.md

@@ -2,16 +2,9 @@
 title: "Data Modeling in TypeScript"
 oldUrl:
   - /kv/manual/data_modeling_typescript/
+  - /deploy/kv/manual/data_modeling_typescript/
 ---
 
-:::info Legacy Documentation
-
-You are viewing legacy documentation for Deno Deploy Classic. We recommend
-migrating to the new
-<a href="/deploy/">Deno Deploy</a> platform.
-
-:::
-
 In TypeScript applications, it is usually desirable to create strongly-typed,
 well-documented objects to contain the data that your application operates on.
 Using [interfaces](https://www.typescriptlang.org/docs/handbook/2/objects.html)

deploy/kv/manual/index.md → deploy/kv/index.md

@@ -4,9 +4,10 @@ oldUrl:
   - /kv/
   - /kv/manual/
   - /runtime/manual/runtime/kv/
+  - /deploy/kv/manual/
 ---
 
-**Deno KV** is a
+Deno KV is a
 [key-value database](https://en.wikipedia.org/wiki/Key%E2%80%93value_database)
 built directly into the Deno runtime, available in the
 [`Deno.Kv` namespace](https://docs.deno.com/api/deno/~/Deno.Kv). It can be used

deploy/kv/manual/key_expiration.md → deploy/kv/key_expiration.md

@@ -2,6 +2,7 @@
 title: "Key Expiration (TTL for keys)"
 oldUrl:
   - /kv/manual/key_expiration/
+  - /deploy/kv/manual/key_expiration/
 ---
 
 <deno-admonition></deno-admonition>

deploy/kv/manual/key_space.md → deploy/kv/key_space.md

@@ -3,6 +3,7 @@ title: "Key Space"
 oldUrl:
   - /runtime/manual/runtime/kv/key_space/
   - /kv/manual/key_space/
+  - /deploy/kv/manual/key_space/
 ---
 
 <deno-admonition></deno-admonition>

deploy/kv/manual/node.md → deploy/kv/node.md

@@ -4,14 +4,6 @@ oldUrl:
   - /kv/manual/node/
 ---
 
-:::info Legacy Documentation
-
-You are viewing legacy documentation for Deno Deploy Classic. We recommend
-migrating to the new
-<a href="/deploy/">Deno Deploy</a> platform.
-
-:::
-
 Connecting to a Deno KV database in Node.js is supported via our
 [official client library on npm](https://www.npmjs.com/package/@deno/kv). You
 can find usage instructions for this option below.

deploy/kv/manual/on_deploy.md → deploy/kv/on_deploy.md

@@ -3,6 +3,7 @@ title: "KV on Deno Deploy"
 oldUrl:
   - /deploy/manual/kv/
   - /kv/manual/on_deploy/
+  - /deploy/kv/manual/on_deploy/
 ---
 
 :::info Legacy Documentation
@@ -53,12 +54,6 @@ Below are the latency figures observed in our top regions:
 | California (us-west2)      | 72ms                           | 72ms                         |
 | Hong Kong (asia-east2)     | 42ms                           | 194ms                        |
 
-## Distributed queues
-
-Serverless distributed queues are available on Deno Deploy. See
-[Queues on Deno Deploy](/deploy/kv/manual/queue_overview#queues-on-deno-deploy)
-for more details.
-
 ## Connect to managed databases from outside of Deno Deploy
 
 You can connect to your Deno Deploy KV database from your Deno application

deploy/kv/manual/operations.md → deploy/kv/operations.md

@@ -3,6 +3,7 @@ title: "Operations"
 oldUrl:
   - /runtime/manual/runtime/kv/operations/
   - /kv/manual/operations/
+  - /deploy/kv/manual/operations/
 ---
 
 The Deno KV API provides a set of operations that can be performed on the key

deploy/kv/manual/secondary_indexes.md → deploy/kv/secondary_indexes.md

@@ -3,6 +3,7 @@ title: "Secondary Indexes"
 oldUrl:
   - /runtime/manual/runtime/kv/secondary_indexes
   - /kv/manual/secondary_indexes
+  - /deploy/kv/manual/secondary_indexes/
 ---
 
 Key-value stores like Deno KV organize data as collections of key-value pairs,

deploy/kv/manual/transactions.md → deploy/kv/transactions.md

@@ -3,6 +3,7 @@ title: "Transactions"
 oldUrl:
   - /runtime/manual/runtime/kv/transactions/
   - /kv/manual/transactions/
+  - /deploy/kv/manual/transactions/
 ---
 
 The Deno KV store utilizes _optimistic concurrency control transactions_ rather