Renaming "Build with D1" to "Best practices".

Author: Oxyjun

public/_redirects

@@ -260,14 +260,23 @@
 # D1
 /d1/client-api/ /d1/worker-api/ 301
 /d1/build-with-d1/d1-client-api/ /d1/worker-api/ 301
+/d1/build-with-d1/import-data/ /d1/best-practices/import-export-data/ 301
+/d1/build-with-d1/ /d1/best-practices/ 301
+/d1/build-with-d1/import-export-data/ /d1/best-practices/import-export-data/ 301
+/d1/build-with-d1/use-indexes/ /d1/best-practices/use-indexes/ 301
+/d1/build-with-d1/remote-development/ /d1/best-practices/remote-development/ 301
+/d1/build-with-d1/local-development/ /d1/best-practices/local-development/ 301
+/d1/build-with-d1/foreign-keys/ /d1/best-practices/foreign-keys/ 301
+/d1/build-with-d1/query-json/ /d1/best-practices/query-json/ 301
+/d1/build-with-d1/use-d1-from-pages/ /d1/best-practices/use-d1-from-pages/ 301
 /d1/learning/using-d1-from-pages/ /pages/functions/bindings/#d1-databases 301
 /d1/learning/debug-d1/ /d1/observability/debug-d1/ 301
-/d1/learning/using-indexes/ /d1/build-with-d1/use-indexes/ 301
-/d1/learning/querying-json/ /d1/build-with-d1/query-json/ 301
-/d1/learning/importing-data/ /d1/build-with-d1/import-export-data/ 301
+/d1/learning/using-indexes/ /d1/best-practices/use-indexes/ 301
+/d1/learning/querying-json/ /d1/best-practices/query-json/ 301
+/d1/learning/importing-data/ /d1/best-practices/import-export-data/ 301
 /d1/learning/generated-columns/ /d1/reference/generated-columns/ 301
-/d1/learning/local-development/ /d1/build-with-d1/local-development/ 301
-/d1/learning/remote-development/ /d1/build-with-d1/remote-development/ 301
+/d1/learning/local-development/ /d1/best-practices/local-development/ 301
+/d1/learning/remote-development/ /d1/best-practices/remote-development/ 301
 /d1/learning/data-location/ /d1/configuration/data-location/ 301
 /d1/migrations/ /d1/reference/migrations/ 301
 /d1/platform/wrangler-commands/ /workers/wrangler/commands/#d1 301
@@ -281,21 +290,20 @@
 /d1/reference/environments/ /d1/configuration/environments/ 301
 /d1/reference/metrics-analytics/ /d1/observability/metrics-analytics/ 301
 /d1/reference/wrangler-commands/ / /d1/wrangler-commands/ 301
-/d1/how-to/ /d1/build-with-d1/ 301
-/d1/how-to/query-databases/ /d1/build-with-d1/query-d1/ 301
-/d1/how-to/using-indexes/ /d1/build-with-d1/use-indexes/ 301
-/d1/how-to/querying-json/ /d1/build-with-d1/query-json/ 301
-/d1/how-to/importing-data/ /d1/build-with-d1/import-export-data/ 301
+/d1/how-to/ /d1/best-practices/ 301
+/d1/how-to/query-databases/ /d1/best-practices/query-d1/ 301
+/d1/how-to/using-indexes/ /d1/best-practices/use-indexes/ 301
+/d1/how-to/querying-json/ /d1/best-practices/query-json/ 301
+/d1/how-to/importing-data/ /d1/best-practices/import-export-data/ 301
 /d1/how-to/generated-columns/ /d1/reference/generated-columns/ 301
-/d1/build-databases/ /d1/build-with-d1/ 301
-/d1/build-databases/query-databases/ /d1/build-with-d1/query-d1/ 301
-/d1/build-databases/use-indexes/ /d1/build-with-d1/use-indexes/ 301
-/d1/build-databases/import-data/ /d1/build-with-d1/import-export-data/ 301
+/d1/build-databases/ /d1/best-practices/ 301
+/d1/build-databases/query-databases/ /d1/best-practices/query-d1/ 301
+/d1/build-databases/use-indexes/ /d1/best-practices/use-indexes/ 301
+/d1/build-databases/import-data/ /d1/best-practices/import-export-data/ 301
 /d1/build-databases/client-api/ /d1/worker-api/ 301
-/d1/reference/query-json/ /d1/build-with-d1/query-json/ 301
-/d1/configuration/local-development/ /d1/build-with-d1/local-development/ 301
-/d1/configuration/remote-development/ /d1/build-with-d1/remote-development/ 301
-/d1/build-with-d1/import-data/ /d1/build-with-d1/import-export-data/ 301
+/d1/reference/query-json/ /d1/best-practices/query-json/ 301
+/d1/configuration/local-development/ /d1/best-practices/local-development/ 301
+/d1/configuration/remote-development/ /d1/best-practices/remote-development/ 301
 /d1/reference/database-commands/ /d1/reference/sql-statements/ 301
 /d1/reference/sql-statements/ /d1/sql-api/sql-statements/ 301
 

src/content/changelogs/d1.yaml

@@ -58,7 +58,7 @@ entries:
 
       * Developers with a Workers Paid plan now have a 10GB GB per-database limit (up from 2GB), which can be combined with existing limit of 50,000 databases per account.
       * Developers with a Workers Free plan retain the 500 MB per-database limit and can create up to 10 databases per account.
-      * D1 databases can be [exported](/d1/build-with-d1/import-export-data/#export-an-existing-d1-database) as a SQL file.
+      * D1 databases can be [exported](/d1/best-practices/import-export-data/#export-an-existing-d1-database) as a SQL file.
 
   - publish_date: "2024-03-12"
     title: Change in `wrangler d1 execute` default
@@ -138,7 +138,7 @@ entries:
   - publish_date: "2023-08-19"
     title: Row count now returned per query
     description: |-
-      D1 now returns a count of `rows_written` and `rows_read` for every query executed, allowing you to assess the cost of query for both [pricing](/d1/platform/pricing/) and [index optimization](/d1/build-with-d1/use-indexes/) purposes.
+      D1 now returns a count of `rows_written` and `rows_read` for every query executed, allowing you to assess the cost of query for both [pricing](/d1/platform/pricing/) and [index optimization](/d1/best-practices/use-indexes/) purposes.
 
       The `meta` object returned in [D1's Client API](/d1/worker-api/return-object/#d1result) contains a total count of the rows read (`rows_read`) and rows written (`rows_written`) by that query. For example, a query that performs a full table scan (for example, `SELECT * FROM users`) from a table with 5000 rows would return a `rows_read` value of `5000`:
       ```json
@@ -195,7 +195,7 @@ entries:
       New documentation has been published on how to use D1's support for
       [generated columns](/d1/reference/generated-columns/) to define columns that are
       dynamically generated on write (or read). Generated columns allow you to extract
-      data from [JSON objects](/d1/build-with-d1/query-json/) or use the output of other
+      data from [JSON objects](/d1/best-practices/query-json/) or use the output of other
       SQL functions.
   - publish_date: "2023-06-12"
     title: Deprecating Error.cause
@@ -223,7 +223,7 @@ entries:
   - publish_date: "2023-05-17"
     title: Query JSON
     description:
-      "[New documentation](/d1/build-with-d1/query-json/) has been published
+      "[New documentation](/d1/best-practices/query-json/) has been published
       that covers D1's extensive JSON function support. JSON functions allow you to
       parse, query and modify JSON directly from your SQL queries, reducing the number
       of round trips to your database, or data queried."

src/content/docs/d1/build-with-d1/foreign-keys.mdx renamed to src/content/docs/d1/best-practices/foreign-keys.mdx

@@ -16,7 +16,7 @@ By default, D1 enforces that foreign key constraints are valid within all querie
 
 ## Defer foreign key constraints
 
-When running a [query](/d1/worker-api/), [migration](/d1/reference/migrations/) or [importing data](/d1/build-with-d1/import-export-data/) against a D1 database, there may be situations in which you need to disable foreign key validation during table creation or changes to your schema.
+When running a [query](/d1/worker-api/), [migration](/d1/reference/migrations/) or [importing data](/d1/best-practices/import-export-data/) against a D1 database, there may be situations in which you need to disable foreign key validation during table creation or changes to your schema.
 
 D1's foreign key enforcement is equivalent to SQLite's `PRAGMA foreign_keys = on` directive. Because D1 runs every query inside an implicit transaction, user queries cannot change this during a query or migration.
 

src/content/docs/d1/build-with-d1/import-export-data.mdx renamed to src/content/docs/d1/best-practices/import-export-data.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 D1 allows you to import existing SQLite tables and their data directly, enabling you to migrate existing data into D1 quickly and easily. This can be useful when migrating applications to use Workers and D1, or when you want to prototype a schema locally before importing it to your D1 database(s).
 
-D1 also allows you to export a database. This can be useful for [local development](/d1/build-with-d1/local-development/) or testing.
+D1 also allows you to export a database. This can be useful for [local development](/d1/best-practices/local-development/) or testing.
 
 ## Import an existing database
 
@@ -194,9 +194,9 @@ VALUES
 
 ## Foreign key constraints
 
-When importing data, you may need to temporarily disable [foreign key constraints](/d1/build-with-d1/foreign-keys/). To do so, call `PRAGMA defer_foreign_keys = true` before making changes that would violate foreign keys.
+When importing data, you may need to temporarily disable [foreign key constraints](/d1/best-practices/foreign-keys/). To do so, call `PRAGMA defer_foreign_keys = true` before making changes that would violate foreign keys.
 
-Refer to the [foreign key documentation](/d1/build-with-d1/foreign-keys/) to learn more about how to work with foreign keys and D1.
+Refer to the [foreign key documentation](/d1/best-practices/foreign-keys/) to learn more about how to work with foreign keys and D1.
 
 ## Next Steps
 

src/content/docs/d1/build-with-d1/index.mdx renamed to src/content/docs/d1/best-practices/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: Build with D1
+title: Best practices
 pcx_content_type: navigation
 sidebar:
   order: 3

src/content/docs/d1/build-with-d1/local-development.mdx renamed to src/content/docs/d1/best-practices/local-development.mdx

@@ -78,7 +78,7 @@ ERROR 9015: SQL engine error: query error: Error code 1: SQL error or missing da
 
 D1's support for [generated columns](/d1/reference/generated-columns/) allows you to create dynamic columns that are generated based on the values of other columns, including extracted or calculated values of JSON data.
 
-These columns can be queried like any other column, and can have [indexes](/d1/build-with-d1/use-indexes/) defined on them. If you have JSON data that you frequently query and filter over, creating a generated column and an index can dramatically improve query performance.
+These columns can be queried like any other column, and can have [indexes](/d1/best-practices/use-indexes/) defined on them. If you have JSON data that you frequently query and filter over, creating a generated column and an index can dramatically improve query performance.
 
 For example, to define a column based on a value within a larger JSON object, use the `AS` keyword combined with a [JSON function](#supported-functions) to generate a typed column: