From e19d6a8507d7105920115da1a2270fb903b9a6d1 Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Tue, 25 Apr 2023 19:01:55 +0200
Subject: [PATCH 01/14] chore: reorganize Prisma CLI reference

---
 .../170-baseline-your-database.mdx            |   2 +-
 .../275-evolve-your-schema.mdx                |   2 +-
 .../250-should-you-use-prisma.mdx             |   4 +-
 .../01-prisma-schema/06-relations/index.mdx   |   2 +-
 .../100-components/01-prisma-schema/index.mdx |   4 +-
 .../03-prisma-migrate/010-mental-model.mdx    |  10 +-
 .../03-prisma-migrate/100-legacy-migrate.mdx  |   2 +-
 .../03-prisma-migrate/150-db-push.mdx         |   2 +-
 .../03-prisma-migrate/200-shadow-database.mdx |   2 +-
 .../index.mdx => 05-prisma-cli.mdx}           |   2 +-
 .../080-cli-preview-features.mdx              |   4 +-
 .../175-squashing-migrations.mdx              |   4 +-
 .../180-generating-down-migrations.mdx        |   4 +-
 .../200-troubleshooting-development.mdx       |   2 +-
 .../index.mdx                                 |   2 +-
 .../400-prototyping-schema-db-push.mdx        |   2 +-
 .../800-production-troubleshooting.mdx        |   4 +-
 .../150-deploying-to-azure-functions.mdx      |   2 +-
 ...y-database-changes-with-prisma-migrate.mdx |   2 +-
 .../100-named-constraints.mdx                 |   2 +-
 .../prisma-cli}/01-installation.mdx           |   0
 .../02-command-reference.mdx}                 |   0
 .../200-api-reference/prisma-cli/index.mdx    |  19 ++++
 content/600-about/100-prisma/40-faq.mdx       |   2 +-
 .../20-style-guide/02-word-choice.mdx         |   2 +-
 .../700-prisma-cli-with-data-proxy.mdx        |   4 +-
 .../200-projects/100-create.mdx               |   2 +-
 vercel.json                                   | 102 +-----------------
 28 files changed, 55 insertions(+), 136 deletions(-)
 rename content/200-concepts/100-components/{05-prisma-cli/index.mdx => 05-prisma-cli.mdx} (79%)
 rename content/{200-concepts/100-components/05-prisma-cli => 400-reference/200-api-reference/prisma-cli}/01-installation.mdx (100%)
 rename content/400-reference/200-api-reference/{200-command-reference.mdx => prisma-cli/02-command-reference.mdx} (100%)
 create mode 100644 content/400-reference/200-api-reference/prisma-cli/index.mdx

diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx
index b3325029b9..6df5bfd25a 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx
@@ -13,7 +13,7 @@ To use Prisma Migrate with the database you introspected in the last section, yo
 
 Baselining refers to initializing your migration history for a database that might already contain data and **cannot be reset**, such as your production database. Baselining tells Prisma Migrate to assume that one or more migrations have already been applied to your database.
 
-To baseline your database, use [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) to compare your schema and database, and save the output into a SQL file.
+To baseline your database, use [`prisma migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) to compare your schema and database, and save the output into a SQL file.
 
 First, create a `migrations` directory and add a directory inside with your preferred name for the migration. In this example, we will use `0_init` as the migration name:
 
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx
index 1c082693de..ea3e3758ab 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx
@@ -9,7 +9,7 @@ toc: false
 
 ## Add a `Tag` model to your schema
 
-In this section, you will evolve your Prisma schema and then generate and apply the migration to your database with [`prisma migrate dev`](/reference/api-reference/command-reference#migrate-dev).
+In this section, you will evolve your Prisma schema and then generate and apply the migration to your database with [`prisma migrate dev`](/reference/api-reference/prisma-cli/command-reference#migrate-dev).
 
 For the purpose of this guide, we'll make the following changes to the Prisma schema:
 
diff --git a/content/200-concepts/050-overview/250-should-you-use-prisma.mdx b/content/200-concepts/050-overview/250-should-you-use-prisma.mdx
index b3d914b694..77b48b573a 100644
--- a/content/200-concepts/050-overview/250-should-you-use-prisma.mdx
+++ b/content/200-concepts/050-overview/250-should-you-use-prisma.mdx
@@ -80,8 +80,8 @@ Prisma is a lot more than "just another ORM". We are building a database toolkit
 - querying (with [Prisma Client](/concepts/components/prisma-client))
 - data modeling (in the [Prisma schema](/concepts/components/prisma-schema))
 - migrations (with [Prisma Migrate](/concepts/components/prisma-migrate))
-- prototyping (via [`prisma db push`](/reference/api-reference/command-reference#db-push))
-- seeding (via [`prisma db seed`](/reference/api-reference/command-reference#db-seed))
+- prototyping (via [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db-push))
+- seeding (via [`prisma db seed`](/reference/api-reference/prisma-cli/command-reference#db-seed))
 - visual viewing and editing (with [Prisma Studio](https://www.prisma.io/studio))
 
 ### ... you value type-safety
diff --git a/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx b/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx
index 344db4e901..61b6bdbf7b 100644
--- a/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx
+++ b/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx
@@ -574,7 +574,7 @@ For **implicit m-n-relations**, both relation fields are virtual since neither o
 
 ![](../../../../doc-images/unused/DxuOs88.png)
 
-Prisma always requires both sides of a relation to be present, this means that one virtual relation field always needs to be added per relation. When [formatting the Prisma schema](/reference/api-reference/command-reference#format), the formatter automatically inserts any missing virtual relation fields for you to save some typing work.
+Prisma always requires both sides of a relation to be present, this means that one virtual relation field always needs to be added per relation. When [formatting the Prisma schema](/reference/api-reference/prisma-cli/command-reference#format), the formatter automatically inserts any missing virtual relation fields for you to save some typing work.
 
 Virtual relation fields are also present in the generated [Prisma CLI](/concepts/components/prisma-client) which makes working with relations more convenient as you can traverse relationships in your code in both directions, for example:
 
diff --git a/content/200-concepts/100-components/01-prisma-schema/index.mdx b/content/200-concepts/100-components/01-prisma-schema/index.mdx
index 7848c4aeaf..f994107a2c 100644
--- a/content/200-concepts/100-components/01-prisma-schema/index.mdx
+++ b/content/200-concepts/100-components/01-prisma-schema/index.mdx
@@ -148,7 +148,7 @@ model User {
 
 The Prisma CLI looks for the Prisma schema file in the following locations, in the following order:
 
-1.  The location specified by the [`--schema` flag](/reference/api-reference/command-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`:
+1.  The location specified by the [`--schema` flag](/reference/api-reference/prisma-cli/command-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`:
 
     ```terminal
     prisma generate --schema=./alternative/schema.prisma
@@ -232,7 +232,7 @@ model Customer {}
 
 Prisma supports formatting `.prisma` files automatically. There are two ways to format `.prisma` files:
 
-- Run the [`prisma format`](/reference/api-reference/command-reference#format) <span class="api"></span> command.
+- Run the [`prisma format`](/reference/api-reference/prisma-cli/command-reference#format) <span class="api"></span> command.
 - Install the [Prisma VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) and invoke the [VS Code format action](https://code.visualstudio.com/docs/editor/codebasics#_formatting) - manually or on save.
 
 There are no configuration options - [formatting rules](#formatting-rules) are fixed (similar to Golang's `gofmt` but unlike Javascript's `prettier`):
diff --git a/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx b/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx
index 113dbc3693..165c523923 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx
@@ -96,7 +96,7 @@ This section describes how you can evolve your database schema in different envi
 
 #### Track your migration history with <inlinecode>prisma migrate dev</inlinecode>
 
-The [`prisma migrate dev`](/reference/api-reference/command-reference#migrate-dev) command allows you to track the changes you make to your database. The `prisma migrate dev` command automatically generates SQL migration files (saved in `/prisma/migrations`) and applies them to the database. When a migration is applied to the database, the migrations table (`_prisma_migrations`) in your database is also updated.
+The [`prisma migrate dev`](/reference/api-reference/prisma-cli/command-reference#migrate-dev) command allows you to track the changes you make to your database. The `prisma migrate dev` command automatically generates SQL migration files (saved in `/prisma/migrations`) and applies them to the database. When a migration is applied to the database, the migrations table (`_prisma_migrations`) in your database is also updated.
 
 ![Prisma Migrate dev flow](./mental-model-illustrations/prisma-migrate-dev-flow.png)
 
@@ -129,7 +129,7 @@ If `prisma migrate dev` detects a schema drift or a migration history conflict,
 
 A schema drift occurs when the expected database schema is different from what is in the migration history. For example, this can occur when you manually update the database schema without also updating the Prisma schema and `prisma/migrations` accordingly.
 
-For such instances, you can use the [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) command to compare your migration history and revert changes made to your database schema.
+For such instances, you can use the [`prisma migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) command to compare your migration history and revert changes made to your database schema.
 
 ![Revert database schema with `migrate diff`](./mental-model-illustrations/prisma-migrate-diff-flow.png)
 
@@ -138,11 +138,11 @@ You can use `migrate diff` to generate the SQL that either:
 - Reverts the changes made in the database schema to synchronize it with the current Prisma schema
 - Moves your database schema forward to apply missing changes from the Prisma schema and `/migrations`
 
-You can then apply the changes to your database using [`prisma db execute`](/reference/api-reference/command-reference#db-execute) command.
+You can then apply the changes to your database using [`prisma db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) command.
 
 #### Prototype your schema
 
-The [`prisma db push`](/reference/api-reference/command-reference#db-push) command allows you to sync your Prisma schema and database schema without persisting a migration (`/prisma/migrations`). The `prisma db push` command tracks the state of the database using the following pieces of state:
+The [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db-push) command allows you to sync your Prisma schema and database schema without persisting a migration (`/prisma/migrations`). The `prisma db push` command tracks the state of the database using the following pieces of state:
 
 - the Prisma schema
 - the database schema
@@ -163,7 +163,7 @@ If the `prisma db push` command detects destructive change to your database sche
 
 #### Sync your migration histories
 
-The [`prisma migrate deploy`](/reference/api-reference/command-reference#migrate-deploy) command allows you to sync your migration history from your development environment with your database in your **staging or production environment**.
+The [`prisma migrate deploy`](/reference/api-reference/prisma-cli/command-reference#migrate-deploy) command allows you to sync your migration history from your development environment with your database in your **staging or production environment**.
 
 Under the hood, the `migrate deploy` command:
 
diff --git a/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx b/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
index 5d4fa8e20f..b475381667 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
@@ -18,7 +18,7 @@ Legacy Prisma Migrate is a tool that lets you _change your database schema_, e.g
 
 ### Legacy Prisma Migrate vs the `db push` command
 
-If you want to prototype or iterate on a schema design in a development environment, consider the [`db push` command](/reference/api-reference/command-reference#db-push).
+If you want to prototype or iterate on a schema design in a development environment, consider the [`db push` command](/reference/api-reference/prisma-cli/command-reference#db-push).
 
 ### Legacy Prisma Migrate vs SQL migrations
 
diff --git a/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx b/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx
index 6a9400bf91..ece919cd28 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx
@@ -7,7 +7,7 @@ codeStyle: false
 
 <TopBlock>
 
-The Prisma CLI has a dedicated command for prototyping schemas: [`db push`](/reference/api-reference/command-reference#db-push) <span class="api"></span>
+The Prisma CLI has a dedicated command for prototyping schemas: [`db push`](/reference/api-reference/prisma-cli/command-reference#db-push) <span class="api"></span>
 
 `db push` uses the same engine as Prisma Migrate to synchronize your Prisma schema with your database schema. The `db push` command:
 
diff --git a/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx b/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx
index 3cddfd081d..18442bca06 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx
@@ -126,6 +126,6 @@ To resolve this error:
 
 - If you are working locally, we recommend that you update the database user's privileges.
 - If you are developing against a cloud-based database (for example, on Heroku and Digital Ocean) see: [Cloud-hosted shadow databases](#cloud-hosted-shadow-databases-must-be-created-manually).
-- If you are developing against a cloud-based database (for example, on Heroku and Digital Ocean) and are currently **prototyping** such that you don't care about generated migration files and only need to apply your Prisma data model to the database schema, you can run [`prisma db push`](/reference/api-reference/command-reference#db) instead of the `prisma migrate dev` command.
+- If you are developing against a cloud-based database (for example, on Heroku and Digital Ocean) and are currently **prototyping** such that you don't care about generated migration files and only need to apply your Prisma data model to the database schema, you can run [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db) instead of the `prisma migrate dev` command.
 
 > **Important**: The shadow database is _only_ required in a development environment (specifically for the `prisma migrate dev` command) - you **do not** need to make any changes to your production environment.
diff --git a/content/200-concepts/100-components/05-prisma-cli/index.mdx b/content/200-concepts/100-components/05-prisma-cli.mdx
similarity index 79%
rename from content/200-concepts/100-components/05-prisma-cli/index.mdx
rename to content/200-concepts/100-components/05-prisma-cli.mdx
index 2e4c9e5710..e5afc5533f 100644
--- a/content/200-concepts/100-components/05-prisma-cli/index.mdx
+++ b/content/200-concepts/100-components/05-prisma-cli.mdx
@@ -15,4 +15,4 @@ The Prisma command line interface (CLI) is the primary way to interact with your
 
 ## Prisma CLI command reference
 
-See [Prisma CLI command reference](/reference/api-reference/command-reference) <span class="api"></span> for a complete list of commands.
+See [Prisma CLI command reference](/reference/api-reference/prisma-cli/command-reference) <span class="api"></span> for a complete list of commands.
diff --git a/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx b/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx
index 6b763cd27e..0ecb5c381e 100644
--- a/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx
+++ b/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx
@@ -19,8 +19,8 @@ There are currently no [Preview](/about/prisma/releases#preview) features for Pr
 <!--
 The following [Preview](/about/prisma/releases#preview) CLI features are available:
 
-- [`migrate diff`](/reference/api-reference/command-reference#migrate-diff) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
-- [`db execute`](/reference/api-reference/command-reference#db-execute) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
+- [`migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
+- [`db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
 
 </TopBlock>
 
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx
index f55c197288..124afba397 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx
@@ -17,7 +17,7 @@ It is sometimes useful to squash either some or all migration files into a singl
 - [Migrating cleanly from a development environment](#migrating-cleanly-from-a-development-environment) by squashing your local migrations into one before merging
 - [Creating a clean history in a production environment](#creating-a-clean-history-in-a-production-environment) by squashing all migrations into a single file
 
-In both cases, Prisma Migrate provides the tools for doing this, by using the [`migrate diff`](/reference/api-reference/command-reference#migrate-diff) command to compare two database schemas and output a single SQL file that takes you from one to the other. The rest of this guide gives detailed instructions on how to carry this out in these two scenarios.
+In both cases, Prisma Migrate provides the tools for doing this, by using the [`migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) command to compare two database schemas and output a single SQL file that takes you from one to the other. The rest of this guide gives detailed instructions on how to carry this out in these two scenarios.
 
 ### Migrating cleanly from a development environment
 
@@ -117,7 +117,7 @@ Then follow these steps, either on your `main` branch or on a newly checked out
 
 4. Mark this migration as having been applied on production, to prevent it from being run there:
 
-   You can do this using the [`migrate resolve`](/reference/api-reference/command-reference#migrate-resolve) command to mark the migration in the `000000000000_squashed_migrations` directory as already applied:
+   You can do this using the [`migrate resolve`](/reference/api-reference/prisma-cli/command-reference#migrate-resolve) command to mark the migration in the `000000000000_squashed_migrations` directory as already applied:
 
    ```terminal
    npx prisma migrate resolve \
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx
index f1ea6c0728..a732bc80b6 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx
@@ -15,7 +15,7 @@ This guide describes how to generate a down migration SQL file that reverses a g
 
 When generating a migration SQL file, you may wish to also create a "down migration" SQL file that reverses the schema changes in the corresponding "up migration" file. Note that "down migrations" are also sometimes called "migration rollbacks".
 
-This guide explains how to use Prisma Migrate's [`migrate diff` command](/reference/api-reference/command-reference#migrate-diff) to create a down migration, and how to apply it to your production database with the [`db execute`](/reference/api-reference/command-reference#db-execute) command in the case of a failed up migration.
+This guide explains how to use Prisma Migrate's [`migrate diff` command](/reference/api-reference/prisma-cli/command-reference#migrate-diff) to create a down migration, and how to apply it to your production database with the [`db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) command in the case of a failed up migration.
 
 <Admonition type="info">
 
@@ -37,7 +37,7 @@ When generating a down migration file, there are some considerations to be aware
 - The down migration will revert your database schema, but other changes to data and application code that are carried out as part of the up migration will not be reverted. For example, if you have a script that changes data during the migration, this data will not be changed back when you run the down migration.
 - You will not be able to use `migrate diff` to revert manually changed or added SQL in your migration files. If you have any custom additions, such as a view or trigger, you will need to:
   - Create the down migration following [the instructions below](#how-to-generate-and-run-down-migrations)
-  - Create the up migration using [`migrate dev --create-only`](/reference/api-reference/command-reference#options-6), so that it can be edited before it is applied to the database
+  - Create the up migration using [`migrate dev --create-only`](/reference/api-reference/prisma-cli/command-reference#options-6), so that it can be edited before it is applied to the database
   - Manually add your custom SQL to the up migration (e.g. adding a view)
   - Manually add the inverted custom SQL to the down migration (e.g. dropping the view)
 
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx
index a58da30bda..6408262c37 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx
@@ -44,7 +44,7 @@ Database schema drift occurs when your database schema is out of sync with your
 
 Schema drift can occur if:
 
-- The database schema was changed _without_ using migrations - for example, by using [`prisma db push`](/reference/api-reference/command-reference#db-push) or manually changing the database schema.
+- The database schema was changed _without_ using migrations - for example, by using [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db-push) or manually changing the database schema.
 
 > **Note**: The [shadow database](/concepts/components/prisma-migrate/shadow-database) is required to detect schema drift, and can therefore only be done in a development environment.
 
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx
index 848052df76..e788dcb2dc 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx
@@ -14,7 +14,7 @@ In a development environment, you use the `migrate dev` command to create and ap
 npx prisma migrate dev
 ```
 
-> **Prototyping?** Use the [`db push`](/reference/api-reference/command-reference#db-push) command if you are [prototyping](/guides/migrate/prototyping-schema-db-push) and are not concerned with data loss or replicating your changes in other environments. You can start or continue your migration history when you are happy with your changes.
+> **Prototyping?** Use the [`db push`](/reference/api-reference/prisma-cli/command-reference#db-push) command if you are [prototyping](/guides/migrate/prototyping-schema-db-push) and are not concerned with data loss or replicating your changes in other environments. You can start or continue your migration history when you are happy with your changes.
 
 When you are comfortable with using Prisma Migrate in development, consider the following more advanced guides:
 
diff --git a/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx b/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx
index 20cb7b7cd9..46e1f6d280 100644
--- a/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx
+++ b/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx
@@ -5,7 +5,7 @@ metaDescription: How to use db push to prototype a new feature or an entirely ne
 
 <TopBlock>
 
-This guide demonstrates how to use [`db push`](/reference/api-reference/command-reference#db-push) to prototype a new schema or a new feature for an existing schema.
+This guide demonstrates how to use [`db push`](/reference/api-reference/prisma-cli/command-reference#db-push) to prototype a new schema or a new feature for an existing schema.
 
 Although `db push` and Prisma Migrate both synchronize your Prisma schema and database schema, they play [different roles in the development workflow](/concepts/components/prisma-migrate/db-push#choosing-db-push-or-prisma-migrate) and should not be used interchangeably.
 
diff --git a/content/300-guides/025-migrate/800-production-troubleshooting.mdx b/content/300-guides/025-migrate/800-production-troubleshooting.mdx
index d62be320de..bd02c8bc36 100644
--- a/content/300-guides/025-migrate/800-production-troubleshooting.mdx
+++ b/content/300-guides/025-migrate/800-production-troubleshooting.mdx
@@ -74,8 +74,8 @@ The following example demonstrates how to manually complete the steps of a migra
 
 To help with fixing a failed migration, Prisma provides the following commands for creating and executing a migration file:
 
-- [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) <span class="api"></span> which diffs two database schema sources to create a migration taking one to the state of the second. You can output either a summary of the difference or a sql script. The script can be output into a file via `> file_name.sql` or be piped to the `db execute --stdin` command.
-- [`prisma db execute`](/reference/api-reference/command-reference#db-execute) <span class="api"></span> which applies a SQL script to the database without interacting with the Prisma migrations table.
+- [`prisma migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) <span class="api"></span> which diffs two database schema sources to create a migration taking one to the state of the second. You can output either a summary of the difference or a sql script. The script can be output into a file via `> file_name.sql` or be piped to the `db execute --stdin` command.
+- [`prisma db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) <span class="api"></span> which applies a SQL script to the database without interacting with the Prisma migrations table.
 
 These commands are available in Preview in versions `3.9.0` and later (with the `--preview-feature` CLI flag), and generally available in versions `3.13.0` and later.
 
diff --git a/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx b/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx
index f18ce0fa22..123a31bcac 100644
--- a/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx
+++ b/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx
@@ -377,7 +377,7 @@ Add the following contents to the file:
 
 ## 11. Create the database schema
 
-You can now create the database schema with the [`prisma migrate deploy`](/reference/api-reference/command-reference#migrate-deploy) command.
+You can now create the database schema with the [`prisma migrate deploy`](/reference/api-reference/prisma-cli/command-reference#migrate-deploy) command.
 
 <Admonition type="info">
 
diff --git a/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx b/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx
index 19deaeaf58..536dcebae3 100644
--- a/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx
+++ b/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx
@@ -29,7 +29,7 @@ Ideally, `migrate deploy` should be part of an automated CI/CD pipeline, and we
 Beware that in order to run the `prisma migrate deploy` command, you need access to the `prisma` dependency that is typically added to the `devDependencies`. Some platforms like Vercel, prune development dependencies during the build, thereby preventing you from calling the command. This can be worked around by making the `prisma` a production dependency, by moving it to `dependencies` in your `package.json`.
 For more information about the `migrate deploy` command, see:
 
-- [`migrate deploy` reference](/reference/api-reference/command-reference#migrate-deploy) <span class="api"></span>
+- [`migrate deploy` reference](/reference/api-reference/prisma-cli/command-reference#migrate-deploy) <span class="api"></span>
 - [How `migrate deploy` works](/concepts/components/prisma-migrate#production-and-testing-environments) <span class="concept"></span>
 - [Production troubleshooting](/guides/migrate/production-troubleshooting)
 
diff --git a/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx b/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx
index 1226b7de8a..777fa9502c 100644
--- a/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx
+++ b/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx
@@ -119,7 +119,7 @@ Since Prisma did not offer a way to define constraint or index names explicitly
 In order to detect this:
 
 - Create a backup of your current `schema.prisma` file.
-- Run `prisma db pull` against each database environment, by saving the results to their own separate files using the `--schema` option. [See reference](/reference/api-reference/command-reference#arguments-1)
+- Run `prisma db pull` against each database environment, by saving the results to their own separate files using the `--schema` option. [See reference](/reference/api-reference/prisma-cli/command-reference#arguments-1)
 
 Then you can either manually inspect both files or use a `diff` tool in your IDE or in the terminal. If you see differences in constraint names, your production and local environments are out of sync and should be aligned.
 
diff --git a/content/200-concepts/100-components/05-prisma-cli/01-installation.mdx b/content/400-reference/200-api-reference/prisma-cli/01-installation.mdx
similarity index 100%
rename from content/200-concepts/100-components/05-prisma-cli/01-installation.mdx
rename to content/400-reference/200-api-reference/prisma-cli/01-installation.mdx
diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx
similarity index 100%
rename from content/400-reference/200-api-reference/200-command-reference.mdx
rename to content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx
diff --git a/content/400-reference/200-api-reference/prisma-cli/index.mdx b/content/400-reference/200-api-reference/prisma-cli/index.mdx
new file mode 100644
index 0000000000..a1f75e9b9e
--- /dev/null
+++ b/content/400-reference/200-api-reference/prisma-cli/index.mdx
@@ -0,0 +1,19 @@
+---
+title: 'Prisma CLI'
+metaTitle: ''
+metaDescription: ''
+toc: false
+---
+
+<TopBlock>
+
+The Prisma command line interface (CLI) is the primary way to interact with your Prisma project from the command line. It can initialize new project assets, generate Prisma Client, and analyze existing database structures through introspection to automatically create your application models.
+
+> There are also a few Preview commands that you can access with the `--preview-feature` flag if you'd like to use in-progress functionality
+
+</TopBlock>
+
+## Prisma CLI
+
+- [Installing the Prisma CLI](/rreference/api-reference/prisma-cli/installation) <span class="api"></span> for a complete list of commands.
+- [Prisma CLI command reference](/reference/api-reference/prisma-cli/command-reference) <span class="api"></span> for a complete list of commands.
diff --git a/content/600-about/100-prisma/40-faq.mdx b/content/600-about/100-prisma/40-faq.mdx
index 0a84662c03..0cebc8e7e5 100644
--- a/content/600-about/100-prisma/40-faq.mdx
+++ b/content/600-about/100-prisma/40-faq.mdx
@@ -59,7 +59,7 @@ There's no lock-in when using Prisma Migrate. To stop using Prisma for your migr
 
 Each migration is represented via its own directory on your file system inside a directory called `migrations`. The name of each directory contains a timestamp so that the order of all migrations in the project history can be maintained.
 
-Each of these migration directories contain a `migration.sql` file about the respective migration. The status of the migrations is tracked in the `_prisma_migrations` table in your database/schema. See [migrate status](/reference/api-reference/command-reference#migrate-status).
+Each of these migration directories contain a `migration.sql` file about the respective migration. The status of the migrations is tracked in the `_prisma_migrations` table in your database/schema. See [migrate status](/reference/api-reference/prisma-cli/command-reference#migrate-status).
 
 ## Where can I get more information about the plans for Prisma?
 
diff --git a/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx b/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
index eb7505f632..d71b99bfc7 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
@@ -249,7 +249,7 @@ Use the long form in these circumstances:
 It is OK to use the short form in the following circumstances. This can help with brevity and readability in the docs.
 
 - When you discuss a `prisma` command, for example in reference material. Example: ["`db push` uses the same engine as Prisma Migrate..."](/concepts/components/prisma-migrate/db-push)
-- When you mention a `prisma` command in a heading. [Example](/reference/api-reference/command-reference#init)
+- When you mention a `prisma` command in a heading. [Example](/reference/api-reference/prisma-cli/command-reference#init)
 
 ### Possessive s
 
diff --git a/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx b/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx
index 8d875099dc..7c87b1375e 100644
--- a/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx
+++ b/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx
@@ -19,7 +19,7 @@ In earlier versions, you must add an [environment variable](/guides/development-
 
 ## Prisma CLI commands that require a direct database connection
 
-The following [Prisma CLI commands](/reference/api-reference/command-reference) require a direct connection:
+The following [Prisma CLI commands](/reference/api-reference/prisma-cli/command-reference) require a direct connection:
 
 - `prisma db pull`
 - `prisma migrate deploy`
@@ -52,7 +52,7 @@ datasource db {
 <Admonition type="warn">
 
 `prisma studio` currently doesn't support the `directUrl` property.
- 
+
 </Admonition>
 
 Then add the `DIRECT_URL` environment variable to your [`.env` file](/guides/development-environment/environment-variables#using-env-files):
diff --git a/content/800-data-platform/200-projects/100-create.mdx b/content/800-data-platform/200-projects/100-create.mdx
index 71f9a457a3..ca40aab49a 100644
--- a/content/800-data-platform/200-projects/100-create.mdx
+++ b/content/800-data-platform/200-projects/100-create.mdx
@@ -248,7 +248,7 @@ With your project created in the Prisma Data Platform, you can explore your proj
 - [Test and run queries with Query Console](/data-platform/query-console)
 - [Manage schema updates with Schema Viewer](/data-platform/schema-viewer)
 
-Next, you can [develop your Prisma schema and your database models](/concepts/components/prisma-schema/data-model) further and [migrate any schema changes to your database](/concepts/components/prisma-migrate) with [`prisma migrate dev`](/reference/api-reference/command-reference#migrate-dev).
+Next, you can [develop your Prisma schema and your database models](/concepts/components/prisma-schema/data-model) further and [migrate any schema changes to your database](/concepts/components/prisma-migrate) with [`prisma migrate dev`](/reference/api-reference/prisma-cli/command-reference#migrate-dev).
 
 You can also change your project settings or add new environments if you want to isolate development activities with test databases and test branches, and select a different Data Proxy region for an environment.
 
diff --git a/vercel.json b/vercel.json
index f98a6eaafd..ffc0f50b24 100644
--- a/vercel.json
+++ b/vercel.json
@@ -417,7 +417,7 @@
     },
     {
       "source": "/docs/reference/tools-and-interfaces/prisma-cli/command-reference",
-      "destination": "/docs/reference/api-reference/command-reference"
+      "destination": "/docs/reference/api-reference/prisma-cli/command-reference"
     },
     {
       "source": "/docs/reference/database-connectors/database-features",
@@ -475,502 +475,402 @@
       "source": "/docs/guides/prisma-guides/prisma-migrate-guides",
       "destination": "/docs/guides/prisma-guides/add-prisma-migrate-to-a-project"
     },
-
     {
       "source": "/docs/guides/prisma-guides/prisma-migrate-guides/add-prisma-migrate-to-a-project",
       "destination": "/docs/guides/prisma-guides/add-prisma-migrate-to-a-project"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/distinct",
       "destination": "/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#select-distinct"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/configuring-the-prisma-client-api",
       "destination": "/docs/concepts/components/prisma-client/generating-prisma-client/customizing-the-prisma-client-api"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/constructor",
       "destination": "/docs/reference/api-reference/prisma-client-reference#prismaclient"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/field-selection",
       "destination": "/docs/concepts/components/prisma-client/select-fields"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/error-reference",
       "destination": "/docs/reference/api-reference/error-reference"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/sorting",
       "destination": "/docs/concepts/components/prisma-client/filtering-and-sorting"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/filtering",
       "destination": "/docs/concepts/components/prisma-client/filtering-and-sorting"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/aggregations",
       "destination": "/docs/concepts/components/prisma-client/aggregation-grouping-summarizing"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/working-with-json",
       "destination": "/docs/concepts/components/prisma-client/working-with-advanced-types"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/group-by",
       "destination": "/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#group-by-preview"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/advanced-usage-of-generated-types",
       "destination": "/docs/concepts/components/prisma-client/working-with-generated-types"
     },
-
     {
       "source": "/docs/concepts/components/preview-features/native-types/native-types-mappings",
       "destination": "/docs/reference/api-reference/prisma-schema-reference#model-field-scalar-types"
     },
-
     {
       "source": "/docs/concepts/components/preview-features/native-types",
       "destination": "/docs/concepts/components/prisma-schema/data-model#native-types-mapping"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/generating-prisma-client",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/generating-prisma-client"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/generating-prisma-client/customizing-the-prisma-client-api",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/use-custom-model-and-field-names"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/connection-management",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/connection-management"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/logging",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/logging"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/error-formatting",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/error-formatting"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/deployment",
       "destination": "/docs/guides/deployment/deployment"
     },
-
     {
       "source": "/docs/concepts/components/prisma-migrate/prisma-migrate-flows",
       "destination": "/docs/concepts/components/prisma-migrate"
     },
-
     {
       "source": "/docs/guides/prisma-guides/seed-database",
       "destination": "/docs/guides/application-lifecycle/seed-database"
     },
-
     {
       "source": "/docs/guides/prisma-guides/add-prisma-migrate-to-a-project",
       "destination": "/docs/guides/database/developing-with-prisma-migrate/add-prisma-migrate-to-a-project"
     },
-
     {
       "source": "/docs/about/creating-bug-reports",
       "destination": "/docs/support/creating-bug-reports"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/working-with-generated-types",
       "destination": "/docs/concepts/components/prisma-client/advanced-type-safety/operating-against-partial-structures-of-model-types"
     },
-
     {
       "source": "/docs/reference/utility-types-reference",
       "destination": "/docs/reference/api-reference/prisma-client-reference#prismavalidator"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/query-engine",
       "destination": "/docs/concepts/components/prisma-engines/query-engine"
     },
-
     {
       "source": "/docs/concepts/overview/under-the-hood",
       "destination": "/docs/concepts/components/prisma-engines"
     },
-
     {
       "source": "/docs/guides/application-lifecycle/add-prisma-migrate-to-a-project",
       "destination": "/docs/guides/database/developing-with-prisma-migrate/add-prisma-migrate-to-a-project"
     },
-
     {
       "source": "/docs/guides/deployment/patching-production",
       "destination": "/docs/guides/database/patching-production"
     },
-
     {
       "source": "/docs/guides/deployment/production-troubleshooting",
       "destination": "/docs/guides/database/production-troubleshooting"
     },
-
     {
       "source": "/docs/guides/application-lifecycle/:any*",
       "destination": "/docs/guides/database/:any*"
     },
-
     {
       "source": "/docs/guides/deployment/deploying-to-azure-functions",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-azure-functions"
     },
-
     {
       "source": "/docs/guides/deployment/deploying-to-heroku",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-heroku"
     },
-
     {
       "source": "/docs/guides/deployment/deploying-to-vercel",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-vercel"
     },
-
     {
       "source": "/docs/guides/deployment/deploying-to-aws-lambda",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-aws-lambda"
     },
-
     {
       "source": "/docs/guides/deployment/deploying-to-netlify",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-netlify"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/cascading-deletes/:any*",
       "destination": "/docs/concepts/components/prisma-schema/relations/referential-actions"
     },
-
     {
       "source": "/docs/guides/database/advanced-database-tasks/cascading-deletes/:any*",
       "destination": "/docs/concepts/components/prisma-schema/relations/referential-actions"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/data-validation/:any*",
       "destination": "/docs/guides/database/advanced-database-tasks/data-validation/:any*"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/sql-views",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/sql-views-postgres",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
-
     {
       "source": "/docs/guides/database/advanced-database-tasks/sql-views-postgres",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/sql-views-mysql",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
-
     {
       "source": "/docs/guides/database/advanced-database-tasks/sql-views-mysql",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/unique-constraints-and-indexes",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/unique-constraints-and-indexes/mysql",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
-
     {
       "source": "/docs/guides/database/advanced-database-tasks/unique-constraints-and-indexes/postgresql",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/unique-constraints-and-indexes/sqlite",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys/mysql",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys/postgresql",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
-
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys/sqlite",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
-
     {
       "source": "/docs/guides/prisma-guides/:any*",
       "destination": "/docs/guides/performance-and-optimization/:any*"
     },
-
     {
       "source": "/docs/mongodb",
       "destination": "/docs/concepts/database-connectors/mongodb"
     },
-
     {
       "source": "/docs/guides/database/developing-with-prisma-migrate/advanced-migrate-scenarios",
       "destination": "/docs/guides/database/developing-with-prisma-migrate/customizing-migrations"
     },
-
     {
       "source": "/docs/concepts/components/prisma-migrate/type-mapping",
       "destination": "/docs/concepts/components/prisma-migrate/supported-types-and-db-features"
     },
-
     {
       "source": "/docs/concepts/components/prisma-client/working-with-advanced-types",
       "destination": "/docs/concepts/components/prisma-client/working-with-fields"
     },
-
     {
       "source": "/docs/concepts/more/codemod",
       "destination": "/docs/guides/upgrade-guides/upgrading-versions/codemods"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/next-steps-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/next-steps-typescript-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/next-steps-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/next-steps-node-postgres"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/next-steps-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/next-steps-typescript-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-node-mysql"
     },
-
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-node-mysql"

From f150c3d9a51e09078bfe3b7dec90ab3991edaac9 Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Tue, 25 Apr 2023 19:11:33 +0200
Subject: [PATCH 02/14] chore: update command reference title

---
 .../200-api-reference/prisma-cli/02-command-reference.mdx       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx b/content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx
index 5f3475231c..faf05e942e 100644
--- a/content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx
+++ b/content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Prisma CLI reference'
+title: 'Commands'
 metaTitle: 'Prisma CLI Command Reference'
 metaDescription: 'This page gives an overview of all available Prisma CLI commands, explains their options and shows numerous usage examples.'
 tocDepth: 2

From 02c03ea384e1efd5287a3491f6d08720ee3b4110 Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Wed, 26 Apr 2023 08:05:26 +0200
Subject: [PATCH 03/14] Revert "chore: reorganize Prisma CLI reference"

This reverts commit e19d6a8507d7105920115da1a2270fb903b9a6d1.
---
 .../170-baseline-your-database.mdx            |   2 +-
 .../275-evolve-your-schema.mdx                |   2 +-
 .../250-should-you-use-prisma.mdx             |   4 +-
 .../01-prisma-schema/06-relations/index.mdx   |   2 +-
 .../100-components/01-prisma-schema/index.mdx |   4 +-
 .../03-prisma-migrate/010-mental-model.mdx    |  10 +-
 .../03-prisma-migrate/100-legacy-migrate.mdx  |   2 +-
 .../03-prisma-migrate/150-db-push.mdx         |   2 +-
 .../03-prisma-migrate/200-shadow-database.mdx |   2 +-
 .../05-prisma-cli}/01-installation.mdx        |   0
 .../index.mdx}                                |   2 +-
 .../080-cli-preview-features.mdx              |   4 +-
 .../175-squashing-migrations.mdx              |   4 +-
 .../180-generating-down-migrations.mdx        |   4 +-
 .../200-troubleshooting-development.mdx       |   2 +-
 .../index.mdx                                 |   2 +-
 .../400-prototyping-schema-db-push.mdx        |   2 +-
 .../800-production-troubleshooting.mdx        |   4 +-
 .../150-deploying-to-azure-functions.mdx      |   2 +-
 ...y-database-changes-with-prisma-migrate.mdx |   2 +-
 .../100-named-constraints.mdx                 |   2 +-
 ...eference.mdx => 200-command-reference.mdx} |   0
 .../200-api-reference/prisma-cli/index.mdx    |  19 ----
 content/600-about/100-prisma/40-faq.mdx       |   2 +-
 .../20-style-guide/02-word-choice.mdx         |   2 +-
 .../700-prisma-cli-with-data-proxy.mdx        |   2 +-
 .../200-projects/100-create.mdx               |   2 +-
 vercel.json                                   | 102 +++++++++++++++++-
 28 files changed, 135 insertions(+), 54 deletions(-)
 rename content/{400-reference/200-api-reference/prisma-cli => 200-concepts/100-components/05-prisma-cli}/01-installation.mdx (100%)
 rename content/200-concepts/100-components/{05-prisma-cli.mdx => 05-prisma-cli/index.mdx} (79%)
 rename content/400-reference/200-api-reference/{prisma-cli/02-command-reference.mdx => 200-command-reference.mdx} (100%)
 delete mode 100644 content/400-reference/200-api-reference/prisma-cli/index.mdx

diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx
index 6df5bfd25a..b3325029b9 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database.mdx
@@ -13,7 +13,7 @@ To use Prisma Migrate with the database you introspected in the last section, yo
 
 Baselining refers to initializing your migration history for a database that might already contain data and **cannot be reset**, such as your production database. Baselining tells Prisma Migrate to assume that one or more migrations have already been applied to your database.
 
-To baseline your database, use [`prisma migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) to compare your schema and database, and save the output into a SQL file.
+To baseline your database, use [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) to compare your schema and database, and save the output into a SQL file.
 
 First, create a `migrations` directory and add a directory inside with your preferred name for the migration. In this example, we will use `0_init` as the migration name:
 
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx
index ea3e3758ab..1c082693de 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema.mdx
@@ -9,7 +9,7 @@ toc: false
 
 ## Add a `Tag` model to your schema
 
-In this section, you will evolve your Prisma schema and then generate and apply the migration to your database with [`prisma migrate dev`](/reference/api-reference/prisma-cli/command-reference#migrate-dev).
+In this section, you will evolve your Prisma schema and then generate and apply the migration to your database with [`prisma migrate dev`](/reference/api-reference/command-reference#migrate-dev).
 
 For the purpose of this guide, we'll make the following changes to the Prisma schema:
 
diff --git a/content/200-concepts/050-overview/250-should-you-use-prisma.mdx b/content/200-concepts/050-overview/250-should-you-use-prisma.mdx
index 77b48b573a..b3d914b694 100644
--- a/content/200-concepts/050-overview/250-should-you-use-prisma.mdx
+++ b/content/200-concepts/050-overview/250-should-you-use-prisma.mdx
@@ -80,8 +80,8 @@ Prisma is a lot more than "just another ORM". We are building a database toolkit
 - querying (with [Prisma Client](/concepts/components/prisma-client))
 - data modeling (in the [Prisma schema](/concepts/components/prisma-schema))
 - migrations (with [Prisma Migrate](/concepts/components/prisma-migrate))
-- prototyping (via [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db-push))
-- seeding (via [`prisma db seed`](/reference/api-reference/prisma-cli/command-reference#db-seed))
+- prototyping (via [`prisma db push`](/reference/api-reference/command-reference#db-push))
+- seeding (via [`prisma db seed`](/reference/api-reference/command-reference#db-seed))
 - visual viewing and editing (with [Prisma Studio](https://www.prisma.io/studio))
 
 ### ... you value type-safety
diff --git a/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx b/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx
index 61b6bdbf7b..344db4e901 100644
--- a/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx
+++ b/content/200-concepts/100-components/01-prisma-schema/06-relations/index.mdx
@@ -574,7 +574,7 @@ For **implicit m-n-relations**, both relation fields are virtual since neither o
 
 ![](../../../../doc-images/unused/DxuOs88.png)
 
-Prisma always requires both sides of a relation to be present, this means that one virtual relation field always needs to be added per relation. When [formatting the Prisma schema](/reference/api-reference/prisma-cli/command-reference#format), the formatter automatically inserts any missing virtual relation fields for you to save some typing work.
+Prisma always requires both sides of a relation to be present, this means that one virtual relation field always needs to be added per relation. When [formatting the Prisma schema](/reference/api-reference/command-reference#format), the formatter automatically inserts any missing virtual relation fields for you to save some typing work.
 
 Virtual relation fields are also present in the generated [Prisma CLI](/concepts/components/prisma-client) which makes working with relations more convenient as you can traverse relationships in your code in both directions, for example:
 
diff --git a/content/200-concepts/100-components/01-prisma-schema/index.mdx b/content/200-concepts/100-components/01-prisma-schema/index.mdx
index f994107a2c..7848c4aeaf 100644
--- a/content/200-concepts/100-components/01-prisma-schema/index.mdx
+++ b/content/200-concepts/100-components/01-prisma-schema/index.mdx
@@ -148,7 +148,7 @@ model User {
 
 The Prisma CLI looks for the Prisma schema file in the following locations, in the following order:
 
-1.  The location specified by the [`--schema` flag](/reference/api-reference/prisma-cli/command-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`:
+1.  The location specified by the [`--schema` flag](/reference/api-reference/command-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`:
 
     ```terminal
     prisma generate --schema=./alternative/schema.prisma
@@ -232,7 +232,7 @@ model Customer {}
 
 Prisma supports formatting `.prisma` files automatically. There are two ways to format `.prisma` files:
 
-- Run the [`prisma format`](/reference/api-reference/prisma-cli/command-reference#format) <span class="api"></span> command.
+- Run the [`prisma format`](/reference/api-reference/command-reference#format) <span class="api"></span> command.
 - Install the [Prisma VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) and invoke the [VS Code format action](https://code.visualstudio.com/docs/editor/codebasics#_formatting) - manually or on save.
 
 There are no configuration options - [formatting rules](#formatting-rules) are fixed (similar to Golang's `gofmt` but unlike Javascript's `prettier`):
diff --git a/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx b/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx
index 165c523923..113dbc3693 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/010-mental-model.mdx
@@ -96,7 +96,7 @@ This section describes how you can evolve your database schema in different envi
 
 #### Track your migration history with <inlinecode>prisma migrate dev</inlinecode>
 
-The [`prisma migrate dev`](/reference/api-reference/prisma-cli/command-reference#migrate-dev) command allows you to track the changes you make to your database. The `prisma migrate dev` command automatically generates SQL migration files (saved in `/prisma/migrations`) and applies them to the database. When a migration is applied to the database, the migrations table (`_prisma_migrations`) in your database is also updated.
+The [`prisma migrate dev`](/reference/api-reference/command-reference#migrate-dev) command allows you to track the changes you make to your database. The `prisma migrate dev` command automatically generates SQL migration files (saved in `/prisma/migrations`) and applies them to the database. When a migration is applied to the database, the migrations table (`_prisma_migrations`) in your database is also updated.
 
 ![Prisma Migrate dev flow](./mental-model-illustrations/prisma-migrate-dev-flow.png)
 
@@ -129,7 +129,7 @@ If `prisma migrate dev` detects a schema drift or a migration history conflict,
 
 A schema drift occurs when the expected database schema is different from what is in the migration history. For example, this can occur when you manually update the database schema without also updating the Prisma schema and `prisma/migrations` accordingly.
 
-For such instances, you can use the [`prisma migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) command to compare your migration history and revert changes made to your database schema.
+For such instances, you can use the [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) command to compare your migration history and revert changes made to your database schema.
 
 ![Revert database schema with `migrate diff`](./mental-model-illustrations/prisma-migrate-diff-flow.png)
 
@@ -138,11 +138,11 @@ You can use `migrate diff` to generate the SQL that either:
 - Reverts the changes made in the database schema to synchronize it with the current Prisma schema
 - Moves your database schema forward to apply missing changes from the Prisma schema and `/migrations`
 
-You can then apply the changes to your database using [`prisma db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) command.
+You can then apply the changes to your database using [`prisma db execute`](/reference/api-reference/command-reference#db-execute) command.
 
 #### Prototype your schema
 
-The [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db-push) command allows you to sync your Prisma schema and database schema without persisting a migration (`/prisma/migrations`). The `prisma db push` command tracks the state of the database using the following pieces of state:
+The [`prisma db push`](/reference/api-reference/command-reference#db-push) command allows you to sync your Prisma schema and database schema without persisting a migration (`/prisma/migrations`). The `prisma db push` command tracks the state of the database using the following pieces of state:
 
 - the Prisma schema
 - the database schema
@@ -163,7 +163,7 @@ If the `prisma db push` command detects destructive change to your database sche
 
 #### Sync your migration histories
 
-The [`prisma migrate deploy`](/reference/api-reference/prisma-cli/command-reference#migrate-deploy) command allows you to sync your migration history from your development environment with your database in your **staging or production environment**.
+The [`prisma migrate deploy`](/reference/api-reference/command-reference#migrate-deploy) command allows you to sync your migration history from your development environment with your database in your **staging or production environment**.
 
 Under the hood, the `migrate deploy` command:
 
diff --git a/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx b/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
index b475381667..5d4fa8e20f 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
@@ -18,7 +18,7 @@ Legacy Prisma Migrate is a tool that lets you _change your database schema_, e.g
 
 ### Legacy Prisma Migrate vs the `db push` command
 
-If you want to prototype or iterate on a schema design in a development environment, consider the [`db push` command](/reference/api-reference/prisma-cli/command-reference#db-push).
+If you want to prototype or iterate on a schema design in a development environment, consider the [`db push` command](/reference/api-reference/command-reference#db-push).
 
 ### Legacy Prisma Migrate vs SQL migrations
 
diff --git a/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx b/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx
index ece919cd28..6a9400bf91 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/150-db-push.mdx
@@ -7,7 +7,7 @@ codeStyle: false
 
 <TopBlock>
 
-The Prisma CLI has a dedicated command for prototyping schemas: [`db push`](/reference/api-reference/prisma-cli/command-reference#db-push) <span class="api"></span>
+The Prisma CLI has a dedicated command for prototyping schemas: [`db push`](/reference/api-reference/command-reference#db-push) <span class="api"></span>
 
 `db push` uses the same engine as Prisma Migrate to synchronize your Prisma schema with your database schema. The `db push` command:
 
diff --git a/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx b/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx
index 18442bca06..3cddfd081d 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/200-shadow-database.mdx
@@ -126,6 +126,6 @@ To resolve this error:
 
 - If you are working locally, we recommend that you update the database user's privileges.
 - If you are developing against a cloud-based database (for example, on Heroku and Digital Ocean) see: [Cloud-hosted shadow databases](#cloud-hosted-shadow-databases-must-be-created-manually).
-- If you are developing against a cloud-based database (for example, on Heroku and Digital Ocean) and are currently **prototyping** such that you don't care about generated migration files and only need to apply your Prisma data model to the database schema, you can run [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db) instead of the `prisma migrate dev` command.
+- If you are developing against a cloud-based database (for example, on Heroku and Digital Ocean) and are currently **prototyping** such that you don't care about generated migration files and only need to apply your Prisma data model to the database schema, you can run [`prisma db push`](/reference/api-reference/command-reference#db) instead of the `prisma migrate dev` command.
 
 > **Important**: The shadow database is _only_ required in a development environment (specifically for the `prisma migrate dev` command) - you **do not** need to make any changes to your production environment.
diff --git a/content/400-reference/200-api-reference/prisma-cli/01-installation.mdx b/content/200-concepts/100-components/05-prisma-cli/01-installation.mdx
similarity index 100%
rename from content/400-reference/200-api-reference/prisma-cli/01-installation.mdx
rename to content/200-concepts/100-components/05-prisma-cli/01-installation.mdx
diff --git a/content/200-concepts/100-components/05-prisma-cli.mdx b/content/200-concepts/100-components/05-prisma-cli/index.mdx
similarity index 79%
rename from content/200-concepts/100-components/05-prisma-cli.mdx
rename to content/200-concepts/100-components/05-prisma-cli/index.mdx
index e5afc5533f..2e4c9e5710 100644
--- a/content/200-concepts/100-components/05-prisma-cli.mdx
+++ b/content/200-concepts/100-components/05-prisma-cli/index.mdx
@@ -15,4 +15,4 @@ The Prisma command line interface (CLI) is the primary way to interact with your
 
 ## Prisma CLI command reference
 
-See [Prisma CLI command reference](/reference/api-reference/prisma-cli/command-reference) <span class="api"></span> for a complete list of commands.
+See [Prisma CLI command reference](/reference/api-reference/command-reference) <span class="api"></span> for a complete list of commands.
diff --git a/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx b/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx
index 0ecb5c381e..6b763cd27e 100644
--- a/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx
+++ b/content/200-concepts/100-components/250-preview-features/080-cli-preview-features.mdx
@@ -19,8 +19,8 @@ There are currently no [Preview](/about/prisma/releases#preview) features for Pr
 <!--
 The following [Preview](/about/prisma/releases#preview) CLI features are available:
 
-- [`migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
-- [`db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
+- [`migrate diff`](/reference/api-reference/command-reference#migrate-diff) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
+- [`db execute`](/reference/api-reference/command-reference#db-execute) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
 
 </TopBlock>
 
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx
index 124afba397..f55c197288 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/175-squashing-migrations.mdx
@@ -17,7 +17,7 @@ It is sometimes useful to squash either some or all migration files into a singl
 - [Migrating cleanly from a development environment](#migrating-cleanly-from-a-development-environment) by squashing your local migrations into one before merging
 - [Creating a clean history in a production environment](#creating-a-clean-history-in-a-production-environment) by squashing all migrations into a single file
 
-In both cases, Prisma Migrate provides the tools for doing this, by using the [`migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) command to compare two database schemas and output a single SQL file that takes you from one to the other. The rest of this guide gives detailed instructions on how to carry this out in these two scenarios.
+In both cases, Prisma Migrate provides the tools for doing this, by using the [`migrate diff`](/reference/api-reference/command-reference#migrate-diff) command to compare two database schemas and output a single SQL file that takes you from one to the other. The rest of this guide gives detailed instructions on how to carry this out in these two scenarios.
 
 ### Migrating cleanly from a development environment
 
@@ -117,7 +117,7 @@ Then follow these steps, either on your `main` branch or on a newly checked out
 
 4. Mark this migration as having been applied on production, to prevent it from being run there:
 
-   You can do this using the [`migrate resolve`](/reference/api-reference/prisma-cli/command-reference#migrate-resolve) command to mark the migration in the `000000000000_squashed_migrations` directory as already applied:
+   You can do this using the [`migrate resolve`](/reference/api-reference/command-reference#migrate-resolve) command to mark the migration in the `000000000000_squashed_migrations` directory as already applied:
 
    ```terminal
    npx prisma migrate resolve \
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx
index a732bc80b6..f1ea6c0728 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/180-generating-down-migrations.mdx
@@ -15,7 +15,7 @@ This guide describes how to generate a down migration SQL file that reverses a g
 
 When generating a migration SQL file, you may wish to also create a "down migration" SQL file that reverses the schema changes in the corresponding "up migration" file. Note that "down migrations" are also sometimes called "migration rollbacks".
 
-This guide explains how to use Prisma Migrate's [`migrate diff` command](/reference/api-reference/prisma-cli/command-reference#migrate-diff) to create a down migration, and how to apply it to your production database with the [`db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) command in the case of a failed up migration.
+This guide explains how to use Prisma Migrate's [`migrate diff` command](/reference/api-reference/command-reference#migrate-diff) to create a down migration, and how to apply it to your production database with the [`db execute`](/reference/api-reference/command-reference#db-execute) command in the case of a failed up migration.
 
 <Admonition type="info">
 
@@ -37,7 +37,7 @@ When generating a down migration file, there are some considerations to be aware
 - The down migration will revert your database schema, but other changes to data and application code that are carried out as part of the up migration will not be reverted. For example, if you have a script that changes data during the migration, this data will not be changed back when you run the down migration.
 - You will not be able to use `migrate diff` to revert manually changed or added SQL in your migration files. If you have any custom additions, such as a view or trigger, you will need to:
   - Create the down migration following [the instructions below](#how-to-generate-and-run-down-migrations)
-  - Create the up migration using [`migrate dev --create-only`](/reference/api-reference/prisma-cli/command-reference#options-6), so that it can be edited before it is applied to the database
+  - Create the up migration using [`migrate dev --create-only`](/reference/api-reference/command-reference#options-6), so that it can be edited before it is applied to the database
   - Manually add your custom SQL to the up migration (e.g. adding a view)
   - Manually add the inverted custom SQL to the down migration (e.g. dropping the view)
 
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx
index 6408262c37..a58da30bda 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/200-troubleshooting-development.mdx
@@ -44,7 +44,7 @@ Database schema drift occurs when your database schema is out of sync with your
 
 Schema drift can occur if:
 
-- The database schema was changed _without_ using migrations - for example, by using [`prisma db push`](/reference/api-reference/prisma-cli/command-reference#db-push) or manually changing the database schema.
+- The database schema was changed _without_ using migrations - for example, by using [`prisma db push`](/reference/api-reference/command-reference#db-push) or manually changing the database schema.
 
 > **Note**: The [shadow database](/concepts/components/prisma-migrate/shadow-database) is required to detect schema drift, and can therefore only be done in a development environment.
 
diff --git a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx
index e788dcb2dc..848052df76 100644
--- a/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx
+++ b/content/300-guides/025-migrate/100-developing-with-prisma-migrate/index.mdx
@@ -14,7 +14,7 @@ In a development environment, you use the `migrate dev` command to create and ap
 npx prisma migrate dev
 ```
 
-> **Prototyping?** Use the [`db push`](/reference/api-reference/prisma-cli/command-reference#db-push) command if you are [prototyping](/guides/migrate/prototyping-schema-db-push) and are not concerned with data loss or replicating your changes in other environments. You can start or continue your migration history when you are happy with your changes.
+> **Prototyping?** Use the [`db push`](/reference/api-reference/command-reference#db-push) command if you are [prototyping](/guides/migrate/prototyping-schema-db-push) and are not concerned with data loss or replicating your changes in other environments. You can start or continue your migration history when you are happy with your changes.
 
 When you are comfortable with using Prisma Migrate in development, consider the following more advanced guides:
 
diff --git a/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx b/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx
index 46e1f6d280..20cb7b7cd9 100644
--- a/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx
+++ b/content/300-guides/025-migrate/400-prototyping-schema-db-push.mdx
@@ -5,7 +5,7 @@ metaDescription: How to use db push to prototype a new feature or an entirely ne
 
 <TopBlock>
 
-This guide demonstrates how to use [`db push`](/reference/api-reference/prisma-cli/command-reference#db-push) to prototype a new schema or a new feature for an existing schema.
+This guide demonstrates how to use [`db push`](/reference/api-reference/command-reference#db-push) to prototype a new schema or a new feature for an existing schema.
 
 Although `db push` and Prisma Migrate both synchronize your Prisma schema and database schema, they play [different roles in the development workflow](/concepts/components/prisma-migrate/db-push#choosing-db-push-or-prisma-migrate) and should not be used interchangeably.
 
diff --git a/content/300-guides/025-migrate/800-production-troubleshooting.mdx b/content/300-guides/025-migrate/800-production-troubleshooting.mdx
index bd02c8bc36..d62be320de 100644
--- a/content/300-guides/025-migrate/800-production-troubleshooting.mdx
+++ b/content/300-guides/025-migrate/800-production-troubleshooting.mdx
@@ -74,8 +74,8 @@ The following example demonstrates how to manually complete the steps of a migra
 
 To help with fixing a failed migration, Prisma provides the following commands for creating and executing a migration file:
 
-- [`prisma migrate diff`](/reference/api-reference/prisma-cli/command-reference#migrate-diff) <span class="api"></span> which diffs two database schema sources to create a migration taking one to the state of the second. You can output either a summary of the difference or a sql script. The script can be output into a file via `> file_name.sql` or be piped to the `db execute --stdin` command.
-- [`prisma db execute`](/reference/api-reference/prisma-cli/command-reference#db-execute) <span class="api"></span> which applies a SQL script to the database without interacting with the Prisma migrations table.
+- [`prisma migrate diff`](/reference/api-reference/command-reference#migrate-diff) <span class="api"></span> which diffs two database schema sources to create a migration taking one to the state of the second. You can output either a summary of the difference or a sql script. The script can be output into a file via `> file_name.sql` or be piped to the `db execute --stdin` command.
+- [`prisma db execute`](/reference/api-reference/command-reference#db-execute) <span class="api"></span> which applies a SQL script to the database without interacting with the Prisma migrations table.
 
 These commands are available in Preview in versions `3.9.0` and later (with the `--preview-feature` CLI flag), and generally available in versions `3.13.0` and later.
 
diff --git a/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx b/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx
index 123a31bcac..f18ce0fa22 100644
--- a/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx
+++ b/content/300-guides/200-deployment/110-deployment-guides/150-deploying-to-azure-functions.mdx
@@ -377,7 +377,7 @@ Add the following contents to the file:
 
 ## 11. Create the database schema
 
-You can now create the database schema with the [`prisma migrate deploy`](/reference/api-reference/prisma-cli/command-reference#migrate-deploy) command.
+You can now create the database schema with the [`prisma migrate deploy`](/reference/api-reference/command-reference#migrate-deploy) command.
 
 <Admonition type="info">
 
diff --git a/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx b/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx
index 536dcebae3..19deaeaf58 100644
--- a/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx
+++ b/content/300-guides/200-deployment/150-deploy-database-changes-with-prisma-migrate.mdx
@@ -29,7 +29,7 @@ Ideally, `migrate deploy` should be part of an automated CI/CD pipeline, and we
 Beware that in order to run the `prisma migrate deploy` command, you need access to the `prisma` dependency that is typically added to the `devDependencies`. Some platforms like Vercel, prune development dependencies during the build, thereby preventing you from calling the command. This can be worked around by making the `prisma` a production dependency, by moving it to `dependencies` in your `package.json`.
 For more information about the `migrate deploy` command, see:
 
-- [`migrate deploy` reference](/reference/api-reference/prisma-cli/command-reference#migrate-deploy) <span class="api"></span>
+- [`migrate deploy` reference](/reference/api-reference/command-reference#migrate-deploy) <span class="api"></span>
 - [How `migrate deploy` works](/concepts/components/prisma-migrate#production-and-testing-environments) <span class="concept"></span>
 - [Production troubleshooting](/guides/migrate/production-troubleshooting)
 
diff --git a/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx b/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx
index 777fa9502c..1226b7de8a 100644
--- a/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx
+++ b/content/300-guides/300-upgrade-guides/200-upgrading-versions/050-upgrading-to-prisma-3/100-named-constraints.mdx
@@ -119,7 +119,7 @@ Since Prisma did not offer a way to define constraint or index names explicitly
 In order to detect this:
 
 - Create a backup of your current `schema.prisma` file.
-- Run `prisma db pull` against each database environment, by saving the results to their own separate files using the `--schema` option. [See reference](/reference/api-reference/prisma-cli/command-reference#arguments-1)
+- Run `prisma db pull` against each database environment, by saving the results to their own separate files using the `--schema` option. [See reference](/reference/api-reference/command-reference#arguments-1)
 
 Then you can either manually inspect both files or use a `diff` tool in your IDE or in the terminal. If you see differences in constraint names, your production and local environments are out of sync and should be aligned.
 
diff --git a/content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
similarity index 100%
rename from content/400-reference/200-api-reference/prisma-cli/02-command-reference.mdx
rename to content/400-reference/200-api-reference/200-command-reference.mdx
diff --git a/content/400-reference/200-api-reference/prisma-cli/index.mdx b/content/400-reference/200-api-reference/prisma-cli/index.mdx
deleted file mode 100644
index a1f75e9b9e..0000000000
--- a/content/400-reference/200-api-reference/prisma-cli/index.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: 'Prisma CLI'
-metaTitle: ''
-metaDescription: ''
-toc: false
----
-
-<TopBlock>
-
-The Prisma command line interface (CLI) is the primary way to interact with your Prisma project from the command line. It can initialize new project assets, generate Prisma Client, and analyze existing database structures through introspection to automatically create your application models.
-
-> There are also a few Preview commands that you can access with the `--preview-feature` flag if you'd like to use in-progress functionality
-
-</TopBlock>
-
-## Prisma CLI
-
-- [Installing the Prisma CLI](/rreference/api-reference/prisma-cli/installation) <span class="api"></span> for a complete list of commands.
-- [Prisma CLI command reference](/reference/api-reference/prisma-cli/command-reference) <span class="api"></span> for a complete list of commands.
diff --git a/content/600-about/100-prisma/40-faq.mdx b/content/600-about/100-prisma/40-faq.mdx
index 0cebc8e7e5..0a84662c03 100644
--- a/content/600-about/100-prisma/40-faq.mdx
+++ b/content/600-about/100-prisma/40-faq.mdx
@@ -59,7 +59,7 @@ There's no lock-in when using Prisma Migrate. To stop using Prisma for your migr
 
 Each migration is represented via its own directory on your file system inside a directory called `migrations`. The name of each directory contains a timestamp so that the order of all migrations in the project history can be maintained.
 
-Each of these migration directories contain a `migration.sql` file about the respective migration. The status of the migrations is tracked in the `_prisma_migrations` table in your database/schema. See [migrate status](/reference/api-reference/prisma-cli/command-reference#migrate-status).
+Each of these migration directories contain a `migration.sql` file about the respective migration. The status of the migrations is tracked in the `_prisma_migrations` table in your database/schema. See [migrate status](/reference/api-reference/command-reference#migrate-status).
 
 ## Where can I get more information about the plans for Prisma?
 
diff --git a/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx b/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
index d71b99bfc7..eb7505f632 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
@@ -249,7 +249,7 @@ Use the long form in these circumstances:
 It is OK to use the short form in the following circumstances. This can help with brevity and readability in the docs.
 
 - When you discuss a `prisma` command, for example in reference material. Example: ["`db push` uses the same engine as Prisma Migrate..."](/concepts/components/prisma-migrate/db-push)
-- When you mention a `prisma` command in a heading. [Example](/reference/api-reference/prisma-cli/command-reference#init)
+- When you mention a `prisma` command in a heading. [Example](/reference/api-reference/command-reference#init)
 
 ### Possessive s
 
diff --git a/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx b/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx
index 7c87b1375e..571b07d405 100644
--- a/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx
+++ b/content/800-data-platform/050-data-proxy/700-prisma-cli-with-data-proxy.mdx
@@ -19,7 +19,7 @@ In earlier versions, you must add an [environment variable](/guides/development-
 
 ## Prisma CLI commands that require a direct database connection
 
-The following [Prisma CLI commands](/reference/api-reference/prisma-cli/command-reference) require a direct connection:
+The following [Prisma CLI commands](/reference/api-reference/command-reference) require a direct connection:
 
 - `prisma db pull`
 - `prisma migrate deploy`
diff --git a/content/800-data-platform/200-projects/100-create.mdx b/content/800-data-platform/200-projects/100-create.mdx
index ca40aab49a..71f9a457a3 100644
--- a/content/800-data-platform/200-projects/100-create.mdx
+++ b/content/800-data-platform/200-projects/100-create.mdx
@@ -248,7 +248,7 @@ With your project created in the Prisma Data Platform, you can explore your proj
 - [Test and run queries with Query Console](/data-platform/query-console)
 - [Manage schema updates with Schema Viewer](/data-platform/schema-viewer)
 
-Next, you can [develop your Prisma schema and your database models](/concepts/components/prisma-schema/data-model) further and [migrate any schema changes to your database](/concepts/components/prisma-migrate) with [`prisma migrate dev`](/reference/api-reference/prisma-cli/command-reference#migrate-dev).
+Next, you can [develop your Prisma schema and your database models](/concepts/components/prisma-schema/data-model) further and [migrate any schema changes to your database](/concepts/components/prisma-migrate) with [`prisma migrate dev`](/reference/api-reference/command-reference#migrate-dev).
 
 You can also change your project settings or add new environments if you want to isolate development activities with test databases and test branches, and select a different Data Proxy region for an environment.
 
diff --git a/vercel.json b/vercel.json
index ffc0f50b24..f98a6eaafd 100644
--- a/vercel.json
+++ b/vercel.json
@@ -417,7 +417,7 @@
     },
     {
       "source": "/docs/reference/tools-and-interfaces/prisma-cli/command-reference",
-      "destination": "/docs/reference/api-reference/prisma-cli/command-reference"
+      "destination": "/docs/reference/api-reference/command-reference"
     },
     {
       "source": "/docs/reference/database-connectors/database-features",
@@ -475,402 +475,502 @@
       "source": "/docs/guides/prisma-guides/prisma-migrate-guides",
       "destination": "/docs/guides/prisma-guides/add-prisma-migrate-to-a-project"
     },
+
     {
       "source": "/docs/guides/prisma-guides/prisma-migrate-guides/add-prisma-migrate-to-a-project",
       "destination": "/docs/guides/prisma-guides/add-prisma-migrate-to-a-project"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/distinct",
       "destination": "/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#select-distinct"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/configuring-the-prisma-client-api",
       "destination": "/docs/concepts/components/prisma-client/generating-prisma-client/customizing-the-prisma-client-api"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/constructor",
       "destination": "/docs/reference/api-reference/prisma-client-reference#prismaclient"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/field-selection",
       "destination": "/docs/concepts/components/prisma-client/select-fields"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/error-reference",
       "destination": "/docs/reference/api-reference/error-reference"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/sorting",
       "destination": "/docs/concepts/components/prisma-client/filtering-and-sorting"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/filtering",
       "destination": "/docs/concepts/components/prisma-client/filtering-and-sorting"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/aggregations",
       "destination": "/docs/concepts/components/prisma-client/aggregation-grouping-summarizing"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/working-with-json",
       "destination": "/docs/concepts/components/prisma-client/working-with-advanced-types"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/group-by",
       "destination": "/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#group-by-preview"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/advanced-usage-of-generated-types",
       "destination": "/docs/concepts/components/prisma-client/working-with-generated-types"
     },
+
     {
       "source": "/docs/concepts/components/preview-features/native-types/native-types-mappings",
       "destination": "/docs/reference/api-reference/prisma-schema-reference#model-field-scalar-types"
     },
+
     {
       "source": "/docs/concepts/components/preview-features/native-types",
       "destination": "/docs/concepts/components/prisma-schema/data-model#native-types-mapping"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/generating-prisma-client",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/generating-prisma-client"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/generating-prisma-client/customizing-the-prisma-client-api",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/use-custom-model-and-field-names"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/connection-management",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/connection-management"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/logging",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/logging"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/error-formatting",
       "destination": "/docs/concepts/components/prisma-client/working-with-prismaclient/error-formatting"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/deployment",
       "destination": "/docs/guides/deployment/deployment"
     },
+
     {
       "source": "/docs/concepts/components/prisma-migrate/prisma-migrate-flows",
       "destination": "/docs/concepts/components/prisma-migrate"
     },
+
     {
       "source": "/docs/guides/prisma-guides/seed-database",
       "destination": "/docs/guides/application-lifecycle/seed-database"
     },
+
     {
       "source": "/docs/guides/prisma-guides/add-prisma-migrate-to-a-project",
       "destination": "/docs/guides/database/developing-with-prisma-migrate/add-prisma-migrate-to-a-project"
     },
+
     {
       "source": "/docs/about/creating-bug-reports",
       "destination": "/docs/support/creating-bug-reports"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/working-with-generated-types",
       "destination": "/docs/concepts/components/prisma-client/advanced-type-safety/operating-against-partial-structures-of-model-types"
     },
+
     {
       "source": "/docs/reference/utility-types-reference",
       "destination": "/docs/reference/api-reference/prisma-client-reference#prismavalidator"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/query-engine",
       "destination": "/docs/concepts/components/prisma-engines/query-engine"
     },
+
     {
       "source": "/docs/concepts/overview/under-the-hood",
       "destination": "/docs/concepts/components/prisma-engines"
     },
+
     {
       "source": "/docs/guides/application-lifecycle/add-prisma-migrate-to-a-project",
       "destination": "/docs/guides/database/developing-with-prisma-migrate/add-prisma-migrate-to-a-project"
     },
+
     {
       "source": "/docs/guides/deployment/patching-production",
       "destination": "/docs/guides/database/patching-production"
     },
+
     {
       "source": "/docs/guides/deployment/production-troubleshooting",
       "destination": "/docs/guides/database/production-troubleshooting"
     },
+
     {
       "source": "/docs/guides/application-lifecycle/:any*",
       "destination": "/docs/guides/database/:any*"
     },
+
     {
       "source": "/docs/guides/deployment/deploying-to-azure-functions",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-azure-functions"
     },
+
     {
       "source": "/docs/guides/deployment/deploying-to-heroku",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-heroku"
     },
+
     {
       "source": "/docs/guides/deployment/deploying-to-vercel",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-vercel"
     },
+
     {
       "source": "/docs/guides/deployment/deploying-to-aws-lambda",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-aws-lambda"
     },
+
     {
       "source": "/docs/guides/deployment/deploying-to-netlify",
       "destination": "/docs/guides/deployment/deployment-guides/deploying-to-netlify"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/cascading-deletes/:any*",
       "destination": "/docs/concepts/components/prisma-schema/relations/referential-actions"
     },
+
     {
       "source": "/docs/guides/database/advanced-database-tasks/cascading-deletes/:any*",
       "destination": "/docs/concepts/components/prisma-schema/relations/referential-actions"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/data-validation/:any*",
       "destination": "/docs/guides/database/advanced-database-tasks/data-validation/:any*"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/sql-views",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/sql-views-postgres",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
+
     {
       "source": "/docs/guides/database/advanced-database-tasks/sql-views-postgres",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/sql-views-mysql",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
+
     {
       "source": "/docs/guides/database/advanced-database-tasks/sql-views-mysql",
       "destination": "https://github.com/prisma/prisma/issues/678"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/unique-constraints-and-indexes",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/unique-constraints-and-indexes/mysql",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
+
     {
       "source": "/docs/guides/database/advanced-database-tasks/unique-constraints-and-indexes/postgresql",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/unique-constraints-and-indexes/sqlite",
       "destination": "/docs/concepts/components/prisma-schema/data-model#defining-a-unique-field"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys/mysql",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys/postgresql",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
+
     {
       "source": "/docs/guides/general-guides/database-workflows/foreign-keys/sqlite",
       "destination": "/docs/concepts/components/prisma-schema/relations#relational-databases"
     },
+
     {
       "source": "/docs/guides/prisma-guides/:any*",
       "destination": "/docs/guides/performance-and-optimization/:any*"
     },
+
     {
       "source": "/docs/mongodb",
       "destination": "/docs/concepts/database-connectors/mongodb"
     },
+
     {
       "source": "/docs/guides/database/developing-with-prisma-migrate/advanced-migrate-scenarios",
       "destination": "/docs/guides/database/developing-with-prisma-migrate/customizing-migrations"
     },
+
     {
       "source": "/docs/concepts/components/prisma-migrate/type-mapping",
       "destination": "/docs/concepts/components/prisma-migrate/supported-types-and-db-features"
     },
+
     {
       "source": "/docs/concepts/components/prisma-client/working-with-advanced-types",
       "destination": "/docs/concepts/components/prisma-client/working-with-fields"
     },
+
     {
       "source": "/docs/concepts/more/codemod",
       "destination": "/docs/guides/upgrade-guides/upgrading-versions/codemods"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/next-steps-typescript-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/next-steps-typescript-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/next-steps-node-postgres",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/next-steps-node-postgres"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/next-steps-typescript-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/next-steps-typescript-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/connect-your-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/using-prisma-migrate-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/install-prisma-client-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/install-prisma-client-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/querying-the-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/querying-the-database-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/start-from-scratch/next-steps-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/next-steps-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/connect-your-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/connect-your-database-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/introspection-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/introspection-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/install-prisma-client-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/install-prisma-client-node-mysql"
     },
+
     {
       "source": "/docs/getting-started/setup-prisma/add-to-existing-project/querying-the-database-node-mysql",
       "destination": "/docs/getting-started/setup-prisma/add-to-existing-project/relational-databases/querying-the-database-node-mysql"

From 41f86c1a8f3b0f75f9988c3050a9c22f5a463c8d Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Wed, 26 Apr 2023 08:16:10 +0200
Subject: [PATCH 04/14] chore: clean up reference & update links

---
 .../010-generating-prisma-client.mdx          |   2 +-
 .../100-components/02-prisma-client/index.mdx |   2 +-
 .../03-prisma-migrate/100-legacy-migrate.mdx  |   2 +-
 .../index.mdx => 05-prisma-cli.mdx}           |   0
 .../05-prisma-cli/01-installation.mdx         | 122 ------------------
 .../03-upgrading-the-prisma-layer.mdx         |   2 +-
 .../01-migrate-from-typeorm.mdx               |   2 +-
 .../02-migrate-from-sequelize.mdx             |   2 +-
 .../03-migrate-from-mongoose.mdx              |   4 +-
 .../200-command-reference.mdx                 |  45 ++++++-
 .../300-environment-variables-reference.mdx   |   2 +-
 11 files changed, 53 insertions(+), 132 deletions(-)
 rename content/200-concepts/100-components/{05-prisma-cli/index.mdx => 05-prisma-cli.mdx} (100%)
 delete mode 100644 content/200-concepts/100-components/05-prisma-cli/01-installation.mdx

diff --git a/content/200-concepts/100-components/02-prisma-client/000-working-with-prismaclient/010-generating-prisma-client.mdx b/content/200-concepts/100-components/02-prisma-client/000-working-with-prismaclient/010-generating-prisma-client.mdx
index 0e188036ea..33a1eb0c41 100644
--- a/content/200-concepts/100-components/02-prisma-client/000-working-with-prismaclient/010-generating-prisma-client.mdx
+++ b/content/200-concepts/100-components/02-prisma-client/000-working-with-prismaclient/010-generating-prisma-client.mdx
@@ -10,7 +10,7 @@ Prisma Client is an auto-generated database client that's tailored to your datab
 
 To generate and instantiate Prisma Client:
 
-1. Ensure that you have [Prisma CLI installed on your machine](/concepts/components/prisma-cli/installation).
+1. Ensure that you have [Prisma CLI installed on your machine](/reference/api-reference/command-reference#installation).
 
 1. Add the following `generator` definition to your Prisma schema:
 
diff --git a/content/200-concepts/100-components/02-prisma-client/index.mdx b/content/200-concepts/100-components/02-prisma-client/index.mdx
index b1b0134cf4..191c3726e3 100644
--- a/content/200-concepts/100-components/02-prisma-client/index.mdx
+++ b/content/200-concepts/100-components/02-prisma-client/index.mdx
@@ -57,7 +57,7 @@ model User {
 }
 ```
 
-Also make sure to [install the Prisma CLI](/concepts/components/prisma-cli/installation):
+Also make sure to [install the Prisma CLI](/reference/api-reference/command-reference#installation):
 
 ```
 npm install prisma --save-dev
diff --git a/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx b/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
index 5d4fa8e20f..bd4ca8b08b 100644
--- a/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
+++ b/content/200-concepts/100-components/03-prisma-migrate/100-legacy-migrate.mdx
@@ -10,7 +10,7 @@ hidePage: true
 
 > **Important!** This page documents legacy Prisma Migrate (Experimental) available in version 2.12.0 and earlier. [Prisma Migrate](.) is available in version [2.13.0](https://github.com/prisma/prisma/releases/tag/2.13.0) and Generally Available in [2.19.0](https://github.com/prisma/prisma/releases/tag/2.19.0).
 
-Legacy Prisma Migrate is a tool that lets you _change your database schema_, e.g. by creating new tables or adding columns to existing tables. These changes are called _schema migrations_. legacy Prisma Migrate is available as part of the [Prisma CLI](/concepts/components/prisma-cli/installation) via the `legacy Prisma Migrate` command.
+Legacy Prisma Migrate is a tool that lets you _change your database schema_, e.g. by creating new tables or adding columns to existing tables. These changes are called _schema migrations_. legacy Prisma Migrate is available as part of the [Prisma CLI](/reference/api-reference/command-reference#installation) via the `legacy Prisma Migrate` command.
 
 </TopBlock>
 
diff --git a/content/200-concepts/100-components/05-prisma-cli/index.mdx b/content/200-concepts/100-components/05-prisma-cli.mdx
similarity index 100%
rename from content/200-concepts/100-components/05-prisma-cli/index.mdx
rename to content/200-concepts/100-components/05-prisma-cli.mdx
diff --git a/content/200-concepts/100-components/05-prisma-cli/01-installation.mdx b/content/200-concepts/100-components/05-prisma-cli/01-installation.mdx
deleted file mode 100644
index 2259d9339d..0000000000
--- a/content/200-concepts/100-components/05-prisma-cli/01-installation.mdx
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: 'Installing the Prisma CLI'
-metaTitle: 'Prisma CLI Installation (Reference)'
-metaDescription: ''
----
-
-<TopBlock>
-
-The Prisma CLI is available as an [npm package](https://www.npmjs.com/prisma). We **recommend that you install the Prisma CLI locally** in your project's `package.json` to avoid version conflicts.
-
-See [Prisma CLI command reference](/reference/api-reference/command-reference) <span class="api"></span> for a complete list of commands.
-
-</TopBlock>
-
-## Local installation (recommended)
-
-The Prisma CLI is typically installed as a **development dependency**, that's why the `--save-dev` (npm) and `--dev` (Yarn) options are used in the commands below.
-
-### npm
-
-Install with [npm](https://www.npmjs.com/):
-
-```
-npm install prisma --save-dev
-```
-
-This should add `prisma` to the `devDependencies` in your `package.json`. You can then invoke the locally installed CLI with the **`prisma`** command prefixed with [`npx`](https://github.com/npm/npx#readme):
-
-```
-npx prisma
-```
-
-Here's an example for invoking the `generate` command:
-
-```
-npx prisma generate
-```
-
-### Yarn (1.19.2+)
-
-Install with [Yarn](https://yarnpkg.com/):
-
-```
-yarn add prisma --dev
-```
-
-This should add `prisma` to the `devDependencies` in your `package.json`. You can then invoke the locally installed CLI with the **`prisma`** command prefixed with `yarn`:
-
-```
-yarn prisma
-```
-
-Here's an example for invoking the `generate` command:
-
-```
-yarn prisma generate
-```
-
-<Admonition type="warning">
-
-We recommend that you keep **both** the `prisma` and `@prisma/client` packages in sync to avoid any unexpected errors or behaviors.
-
-</Admonition>
-
-## Global installation (not recommended)
-
-While it is recommended to [locally install](#local-installation-recommended) the Prisma CLI, you can also install it globally on your machine.
-
-> **Warning**: If you have several Prisma projects on your machine, a global installation can lead to version conflicts between these projects.
-
-### npm
-
-Install with npm:
-
-```
-npm install -g prisma
-```
-
-You can then invoke the globally installed CLI with the **`prisma`** command like so:
-
-```
-prisma
-```
-
-Here's an example for invoking the `generate` command:
-
-```
-prisma generate
-```
-
-### Yarn
-
-Install with Yarn:
-
-```
-yarn global add prisma
-```
-
-You can then invoke the globally installed CLI with the **`prisma`** command like so:
-
-```
-prisma
-```
-
-Here's an example for invoking the `generate` command:
-
-```
-prisma generate
-```
-
-## Using a HTTP proxy for the CLI
-
-Prisma CLI supports [custom HTTP proxies](https://github.com/prisma/prisma/issues/506). This is particularly relevant when being behind a corporate firewall.
-
-To activate the proxy, provide the environment variables `HTTP_PROXY` and/or `HTTPS_PROXY`. The behavior is very similar to how the [`npm` CLI handles this](https://docs.npmjs.com/misc/config#https-proxy).
-
-The following environment variables can be provided:
-
-- [`HTTP_PROXY`](/reference/api-reference/environment-variables-reference#http_proxy) <span class="api"></span> or `http_proxy`: Proxy URL for http traffic, for example `http://localhost:8080`
-- [`HTTPS_PROXY`](/reference/api-reference/environment-variables-reference#https_proxy) <span class="api"></span> or `https_proxy`: Proxy URL for https traffic, for example `https://localhost:8080`
-
-> To get a local proxy, you can also use the [`proxy`](https://www.npmjs.com/package/proxy) module.
diff --git a/content/300-guides/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer.mdx b/content/300-guides/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer.mdx
index e23fc2f381..6f0a8f193f 100644
--- a/content/300-guides/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer.mdx
+++ b/content/300-guides/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer.mdx
@@ -51,7 +51,7 @@ You can install the Prisma 2 CLI in your Node.js project as follows (be sure to
 npm install prisma --save-dev
 ```
 
-> **Note**: With Prisma 1, it was usually recommended to install the CLI globally. We now recommend to [install the Prisma CLI locally](/concepts/components/prisma-cli/installation#local-installation-recommended) to prevent version conflicts.
+> **Note**: With Prisma 1, it was usually recommended to install the CLI globally. We now recommend to [install the Prisma CLI locally](/reference/api-reference/command-reference#installation#local-installation-recommended) to prevent version conflicts.
 
 You can now use the local installation of the `prisma` CLI by prefixing it with `npx`:
 
diff --git a/content/300-guides/400-migrate-to-prisma/01-migrate-from-typeorm.mdx b/content/300-guides/400-migrate-to-prisma/01-migrate-from-typeorm.mdx
index 9080934bd5..b8e96dc084 100644
--- a/content/300-guides/400-migrate-to-prisma/01-migrate-from-typeorm.mdx
+++ b/content/300-guides/400-migrate-to-prisma/01-migrate-from-typeorm.mdx
@@ -240,7 +240,7 @@ As mentioned before, this guide is an extended variation of the TypeORM Express
 
 ## Step 1. Install the Prisma CLI
 
-The first step to adopt Prisma is to [install the Prisma CLI](/concepts/components/prisma-cli/installation#local-installation-recommended) in your project:
+The first step to adopt Prisma is to [install the Prisma CLI](/reference/api-reference/command-reference#installation#local-installation-recommended) in your project:
 
 ```terminal copy
 npm install prisma --save-dev
diff --git a/content/300-guides/400-migrate-to-prisma/02-migrate-from-sequelize.mdx b/content/300-guides/400-migrate-to-prisma/02-migrate-from-sequelize.mdx
index 6aca6908d8..4bd7123f98 100644
--- a/content/300-guides/400-migrate-to-prisma/02-migrate-from-sequelize.mdx
+++ b/content/300-guides/400-migrate-to-prisma/02-migrate-from-sequelize.mdx
@@ -172,7 +172,7 @@ In this guide, the route handlers are located in the `src/controllers` directory
 
 ## Step 1. Install the Prisma CLI
 
-The first step to adopt Prisma is to [install the Prisma CLI](/concepts/components/prisma-cli/installation#local-installation-recommended) in your project:
+The first step to adopt Prisma is to [install the Prisma CLI](/reference/api-reference/command-reference#installation#local-installation-recommended) in your project:
 
 ```terminal copy
 npm install prisma --save-dev
diff --git a/content/300-guides/400-migrate-to-prisma/03-migrate-from-mongoose.mdx b/content/300-guides/400-migrate-to-prisma/03-migrate-from-mongoose.mdx
index 8dfe43c44e..a8182a2bbc 100644
--- a/content/300-guides/400-migrate-to-prisma/03-migrate-from-mongoose.mdx
+++ b/content/300-guides/400-migrate-to-prisma/03-migrate-from-mongoose.mdx
@@ -16,7 +16,7 @@ You can learn how Prisma compares to Mongoose on the [Prisma vs Mongoose](/conce
 
 Note that the steps for migrating from Mongoose to Prisma are always the same, no matter what kind of application or API layer you're building:
 
-1. [Install the Prisma CLI](/concepts/components/prisma-cli/installation)
+1. [Install the Prisma CLI](/reference/api-reference/command-reference#installation)
 1. [Introspect your database](/concepts/components/introspection)
 1. [Install Prisma Client](/concepts/components/prisma-client#2-installation)
 1. Gradually replace your Mongoose queries with Prisma Client
@@ -147,7 +147,7 @@ Run `npm run seed` to populate your database with the sample data in the `./src/
 
 ## Step 1. Install the Prisma CLI
 
-The first step to adopt Prisma is to [install the Prisma CLI](/concepts/components/prisma-cli/installation#local-installation-recommended) in your project:
+The first step to adopt Prisma is to [install the Prisma CLI](/reference/api-reference/command-reference#installation#local-installation-recommended) in your project:
 
 ```terminal copy
 npm install prisma --save-dev
diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index faf05e942e..7d2d14de2a 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Commands'
+title: 'Prisma CLI reference'
 metaTitle: 'Prisma CLI Command Reference'
 metaDescription: 'This page gives an overview of all available Prisma CLI commands, explains their options and shows numerous usage examples.'
 tocDepth: 2
@@ -11,6 +11,36 @@ This document describes the Prisma CLI commands, arguments, and options.
 
 </TopBlock>
 
+## Installation
+
+The Prisma CLI is typically installed as a **development dependency**, that's why the `--save-dev` (npm) and `--dev` (Yarn) options are used in the commands below.
+
+<Admonition>
+
+We **recommend that you install the Prisma CLI locally** in your project's `package.json` to avoid version conflicts.
+
+</Admonition>
+
+### npm
+
+Install with [npm](https://www.npmjs.com/):
+
+```
+npm install prisma --save-dev
+```
+
+### Yarn
+
+```
+yarn add prisma --save-dev
+```
+
+### pnpm
+
+```
+pnpx install prisma --save-dev
+```
+
 ## Usage
 
 If you installed Prisma with a package manager, you need to prefix the `prisma` command with your package runner.
@@ -1321,3 +1351,16 @@ See [Seeding your database](/guides/migrate/seed-database) <span class="guide"><
 ```
 
 This is available from version 3.0.1 and later.
+
+## Using a HTTP proxy for the CLI
+
+Prisma CLI supports [custom HTTP proxies](https://github.com/prisma/prisma/issues/506). This is particularly relevant when being behind a corporate firewall.
+
+To activate the proxy, provide the environment variables `HTTP_PROXY` and/or `HTTPS_PROXY`. The behavior is very similar to how the [`npm` CLI handles this](https://docs.npmjs.com/misc/config#https-proxy).
+
+The following environment variables can be provided:
+
+- [`HTTP_PROXY`](/reference/api-reference/environment-variables-reference#http_proxy) <span class="api"></span> or `http_proxy`: Proxy URL for http traffic, for example `http://localhost:8080`
+- [`HTTPS_PROXY`](/reference/api-reference/environment-variables-reference#https_proxy) <span class="api"></span> or `https_proxy`: Proxy URL for https traffic, for example `https://localhost:8080`
+
+> To get a local proxy, you can also use the [`proxy`](https://www.npmjs.com/package/proxy) module.
diff --git a/content/400-reference/200-api-reference/300-environment-variables-reference.mdx b/content/400-reference/200-api-reference/300-environment-variables-reference.mdx
index 2b0ceb3608..cff68cac03 100644
--- a/content/400-reference/200-api-reference/300-environment-variables-reference.mdx
+++ b/content/400-reference/200-api-reference/300-environment-variables-reference.mdx
@@ -74,7 +74,7 @@ To configure `prisma generate` to [generate a Prisma Client for Data Proxy](/dat
 
 ## Proxy environment variables
 
-The Prisma CLI supports custom HTTP(S) proxies to download the Prisma engines. These can be helpful to use when working behind a corporate firewall. See [Using a HTTP proxy for the CLI](/concepts/components/prisma-cli/installation#using-a-http-proxy-for-the-cli) for more information.
+The Prisma CLI supports custom HTTP(S) proxies to download the Prisma engines. These can be helpful to use when working behind a corporate firewall. See [Using a HTTP proxy for the CLI](/reference/api-reference/command-reference#installation#using-a-http-proxy-for-the-cli) for more information.
 
 ### <inlinecode>NO_PROXY</inlinecode>
 

From eea2aca38e3324c47befd11fb5350a10cacc75f5 Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Wed, 26 Apr 2023 08:18:05 +0200
Subject: [PATCH 05/14] chore: update redirects

---
 vercel.json | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/vercel.json b/vercel.json
index f98a6eaafd..7290fe7d1d 100644
--- a/vercel.json
+++ b/vercel.json
@@ -1302,6 +1302,10 @@
     {
       "source": "/docs/guides/database/advanced-database-tasks",
       "destination": "/docs/guides/other/advanced-database-tasks"
+    },
+    {
+      "source": "/docs/concepts/components/prisma-cli/installation",
+      "destination": "/docs/reference/api-reference/command-reference#installation"
     }
   ]
 }

From 5b21f573d8d1aa4756c74f93052d42814edc1ad5 Mon Sep 17 00:00:00 2001
From: Alex Ruheni <33921841+ruheni@users.noreply.github.com>
Date: Thu, 27 Apr 2023 13:32:59 +0100
Subject: [PATCH 06/14] Update
 content/400-reference/200-api-reference/200-command-reference.mdx

Co-authored-by: Nikolas <nikolas.burk@gmail.com>
---
 .../400-reference/200-api-reference/200-command-reference.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index 7d2d14de2a..42a58a3823 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -17,7 +17,7 @@ The Prisma CLI is typically installed as a **development dependency**, that's wh
 
 <Admonition>
 
-We **recommend that you install the Prisma CLI locally** in your project's `package.json` to avoid version conflicts.
+We **recommend that you install the Prisma CLI locally** in your project's `package.json` to avoid version conflicts that can happen with a global installation.
 
 </Admonition>
 

From af2abc740e9cfa23e284463b889fb9d2f1910a61 Mon Sep 17 00:00:00 2001
From: Alex Ruheni <33921841+ruheni@users.noreply.github.com>
Date: Thu, 27 Apr 2023 13:34:26 +0100
Subject: [PATCH 07/14] Update
 content/400-reference/200-api-reference/200-command-reference.mdx

Co-authored-by: Nikolas <nikolas.burk@gmail.com>
---
 .../400-reference/200-api-reference/200-command-reference.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index 42a58a3823..dfeb44bda3 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -38,7 +38,7 @@ yarn add prisma --save-dev
 ### pnpm
 
 ```
-pnpx install prisma --save-dev
+pnpm install prisma --save-dev
 ```
 
 ## Usage

From 09817decbf0a202ac19780684eda27c903fc4f91 Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Thu, 27 Apr 2023 18:43:43 +0200
Subject: [PATCH 08/14] chore: link to package managers

---
 .../400-reference/200-api-reference/200-command-reference.mdx | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index dfeb44bda3..305d7b41d7 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -31,12 +31,16 @@ npm install prisma --save-dev
 
 ### Yarn
 
+Install with [yarn](https://yarnpkg.dev/):
+
 ```
 yarn add prisma --save-dev
 ```
 
 ### pnpm
 
+Install with [pnpm](https://pnpm.io/):
+
 ```
 pnpm install prisma --save-dev
 ```

From 6ca96a82f660dc1ce6be604b961e6c1a8aa6037a Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Thu, 27 Apr 2023 18:46:43 +0200
Subject: [PATCH 09/14] chore: add global installation instructions

---
 .../200-command-reference.mdx                 | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index 305d7b41d7..242fabe589 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -45,6 +45,35 @@ Install with [pnpm](https://pnpm.io/):
 pnpm install prisma --save-dev
 ```
 
+<details>
+<summary>Global installation (Not recommended)</summary>
+
+### npm
+
+Install with npm:
+
+```
+npm install -g prisma
+```
+
+### Yarn
+
+Install with Yarn:
+
+```
+yarn global add prisma
+```
+
+### pnpm
+
+Install with pnpm:
+
+```
+pnpm install prisma --global
+```
+
+</details>
+
 ## Usage
 
 If you installed Prisma with a package manager, you need to prefix the `prisma` command with your package runner.

From a142396417accceba901abb0b431eda57e3b9152 Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Thu, 27 Apr 2023 18:52:51 +0200
Subject: [PATCH 10/14] chore: rework HTTP proxy for CLI section

---
 .../200-api-reference/200-command-reference.mdx             | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index 242fabe589..1b7f7d821d 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -1389,11 +1389,7 @@ This is available from version 3.0.1 and later.
 
 Prisma CLI supports [custom HTTP proxies](https://github.com/prisma/prisma/issues/506). This is particularly relevant when being behind a corporate firewall.
 
-To activate the proxy, provide the environment variables `HTTP_PROXY` and/or `HTTPS_PROXY`. The behavior is very similar to how the [`npm` CLI handles this](https://docs.npmjs.com/misc/config#https-proxy).
-
-The following environment variables can be provided:
+To activate the proxy, provide either of the following environment variables:
 
 - [`HTTP_PROXY`](/reference/api-reference/environment-variables-reference#http_proxy) <span class="api"></span> or `http_proxy`: Proxy URL for http traffic, for example `http://localhost:8080`
 - [`HTTPS_PROXY`](/reference/api-reference/environment-variables-reference#https_proxy) <span class="api"></span> or `https_proxy`: Proxy URL for https traffic, for example `https://localhost:8080`
-
-> To get a local proxy, you can also use the [`proxy`](https://www.npmjs.com/package/proxy) module.

From 4bffa1b3f31e7f2d5367130e006df7e0d67857da Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Thu, 27 Apr 2023 18:54:06 +0200
Subject: [PATCH 11/14] chore: update wording

---
 .../400-reference/200-api-reference/200-command-reference.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index 1b7f7d821d..557f6a54ef 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -1389,7 +1389,7 @@ This is available from version 3.0.1 and later.
 
 Prisma CLI supports [custom HTTP proxies](https://github.com/prisma/prisma/issues/506). This is particularly relevant when being behind a corporate firewall.
 
-To activate the proxy, provide either of the following environment variables:
+To activate usage of the proxy, provide either of the following environment variables:
 
 - [`HTTP_PROXY`](/reference/api-reference/environment-variables-reference#http_proxy) <span class="api"></span> or `http_proxy`: Proxy URL for http traffic, for example `http://localhost:8080`
 - [`HTTPS_PROXY`](/reference/api-reference/environment-variables-reference#https_proxy) <span class="api"></span> or `https_proxy`: Proxy URL for https traffic, for example `https://localhost:8080`

From ca717d6988727d34ab218d14b1dc925790ea8a02 Mon Sep 17 00:00:00 2001
From: ruheni <aleruheni@outlook.com>
Date: Thu, 27 Apr 2023 18:55:20 +0200
Subject: [PATCH 12/14] chore: update wording

---
 .../400-reference/200-api-reference/200-command-reference.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index 557f6a54ef..43f9591692 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -76,7 +76,7 @@ pnpm install prisma --global
 
 ## Usage
 
-If you installed Prisma with a package manager, you need to prefix the `prisma` command with your package runner.
+If you installed Prisma as a development dependency, you need to prefix the `prisma` command with your package runner.
 
 ### npm
 

From 6db4a1e6423309731cedcc31c36fd57b933c2a1e Mon Sep 17 00:00:00 2001
From: Alex Ruheni <33921841+ruheni@users.noreply.github.com>
Date: Thu, 27 Apr 2023 19:23:02 +0200
Subject: [PATCH 13/14] chore: remove headings inside details

---
 .../200-api-reference/200-command-reference.mdx           | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/400-reference/200-api-reference/200-command-reference.mdx b/content/400-reference/200-api-reference/200-command-reference.mdx
index 43f9591692..a62ef8d763 100644
--- a/content/400-reference/200-api-reference/200-command-reference.mdx
+++ b/content/400-reference/200-api-reference/200-command-reference.mdx
@@ -13,7 +13,7 @@ This document describes the Prisma CLI commands, arguments, and options.
 
 ## Installation
 
-The Prisma CLI is typically installed as a **development dependency**, that's why the `--save-dev` (npm) and `--dev` (Yarn) options are used in the commands below.
+The Prisma CLI is typically installed locally as a **development dependency**, that's why the `--save-dev` (npm) and `--dev` (Yarn) options are used in the commands below.
 
 <Admonition>
 
@@ -48,7 +48,7 @@ pnpm install prisma --save-dev
 <details>
 <summary>Global installation (Not recommended)</summary>
 
-### npm
+- **npm**
 
 Install with npm:
 
@@ -56,7 +56,7 @@ Install with npm:
 npm install -g prisma
 ```
 
-### Yarn
+- **Yarn**
 
 Install with Yarn:
 
@@ -64,7 +64,7 @@ Install with Yarn:
 yarn global add prisma
 ```
 
-### pnpm
+- **pnpm**
 
 Install with pnpm:
 

From f396691283d72cd273761a1959220c130600d2f1 Mon Sep 17 00:00:00 2001
From: Jan Piotrowski <piotrowski+github@gmail.com>
Date: Thu, 27 Apr 2023 19:31:19 +0200
Subject: [PATCH 14/14] Fix generate-redirects.shfor special case where a page
 only looses the index.mdx

---
 .github/workflows/scripts/generate-redirects.sh | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/scripts/generate-redirects.sh b/.github/workflows/scripts/generate-redirects.sh
index 46ca459fef..990e734f66 100644
--- a/.github/workflows/scripts/generate-redirects.sh
+++ b/.github/workflows/scripts/generate-redirects.sh
@@ -30,14 +30,19 @@ do
         body="$body""\`\`\`%0A"
     fi
 
-    # name pieces
+    # name pieces (and replace `/index` from files (to get to a filename that would be equivalent))
     action=${values[0]}
-    path1=${values[1]}
-    path2=${values[3]}
+    path1=$(echo "${values[1]}" | sed -e 's#/index##g' )
+    path2=$(echo "${values[3]}" | sed -e 's#/index##g' )
+
+    # Skip if file names are identical (probably via `/index` replacement above)
+    if [[ "$path1" == "$path2" ]]; then
+        continue
+    fi
 
     # clean paths
-    path1_cleaned=$(echo "$path1" | sed -E 's:content/:/:g' | sed -E 's:/index.mdx::g' | sed -e 's/.mdx//g' | sed -E 's:/[0-9]+-:/:g' )
-    path2_cleaned=$(echo "$path2" | sed -E 's:content/:/:g' | sed -E 's:/index.mdx::g' | sed -e 's/.mdx//g' | sed -E 's:/[0-9]+-:/:g' )
+    path1_cleaned=$(echo "$path1" | sed -E 's:content/:/:g' | sed -e 's/.mdx//g' | sed -E 's:/[0-9]+-:/:g' )
+    path2_cleaned=$(echo "$path2" | sed -E 's:content/:/:g' | sed -e 's/.mdx//g' | sed -E 's:/[0-9]+-:/:g' )
     
     # special case for deletion
     if [[ "${values[0]}" == "D" ]]; then