hack to be able to test redirects (#5512)

Co-authored-by: Nikolas Burk <[email protected]>

content/200-orm/050-overview/300-prisma-in-your-stack/01-rest.md

@@ -8,7 +8,7 @@ metaDescription: 'This page gives an overview of the most important things when
 
 When building REST APIs, Prisma Client can be used inside your _route controllers_ to send databases queries.
 
-![REST APIs with Prisma Client](../prisma-rest-apis.png)
+![REST APIs with Prisma Client](../100-introduction/prisma-rest-apis.png)
 
 </TopBlock>
 

content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx

@@ -61,7 +61,7 @@ In reality, not all Data Mapper ORMs adhere to this pattern strictly. For exampl
 
 Given the following `User` table in the database:
 
-![user-table](../user-table.png)
+![user-table](../100-introduction/user-table.png)
 
 This is what the corresponding entity class would look like:
 
@@ -265,7 +265,7 @@ Here's a break down of the example above:
 
 The `User` / `Post` relation can be visualized with the following diagram:
 
-![1-n relation between User and Post](../user-post-relation-1-n.png)
+![1-n relation between User and Post](../100-introduction/user-post-relation-1-n.png)
 
 At a Prisma level, the `User` / `Post` relation is made up of:
 

content/200-orm/100-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdx

@@ -7,7 +7,7 @@ tocDepth: 2
 
 <TopBlock>
 
-Composite IDs and compound unique constraints can be defined in your Prisma schema using the [`@@id`](/reference/api-reference/prisma-schema-reference#id-1)  and [`@@unique`](/reference/api-reference/prisma-schema-reference#unique-1)  attributes.
+Composite IDs and compound unique constraints can be defined in your Prisma schema using the [`@@id`](/reference/api-reference/prisma-schema-reference#id-1) and [`@@unique`](/reference/api-reference/prisma-schema-reference#unique-1) attributes.
 
 <Admonition type="warning">
 
@@ -101,7 +101,7 @@ const like = await prisma.like.findUnique({
 
 <Admonition type="info">
 
-Note composite ID and compound unique constraint keys are only available as filter options for _unique_ queries such as `findUnique` and `findUniqueOrThrow`. See the [section](/concepts/components/prisma-client/working-with-fields/working-with-composite-ids/#where-you-can-use-compound-ids-and-unique-identifiers) above for a list of places these fields may be used.
+Note composite ID and compound unique constraint keys are only available as filter options for _unique_ queries such as `findUnique` and `findUniqueOrThrow`. See the [section](/concepts/components/prisma-client/working-with-fields/working-with-composite-ids-and-constraints#where-you-can-use-compound-ids-and-unique-identifiers) above for a list of places these fields may be used.
 
 </Admonition>
 

content/200-orm/100-prisma-client/300-client-extensions/150-type-utilities.mdx

@@ -12,7 +12,7 @@ Several type utilities exist within Prisma Client that can assist in the creatio
 
 ## Type Utilities
 
-[Prisma Client type utilities](/concepts/components/prisma-client/advanced-type-safety/) are utilities available within your application and Prisma Client extensions and provide useful ways of constructing safe and extendable types for your extension.
+[Prisma Client type utilities](/concepts/components/prisma-client/advanced-type-safety) are utilities available within your application and Prisma Client extensions and provide useful ways of constructing safe and extendable types for your extension.
 
 The type utilities available are:
 

content/200-orm/100-prisma-client/500-deployment/600-deploy-migrations-from-a-local-environment.mdx

@@ -51,4 +51,4 @@ The pipeline should handle deployment to staging and production environments, an
 
 When you add Prisma Migrate to an **existing database**, you must [baseline](/orm/prisma-migrate/workflows/baselining) the production database. Baselining is performed **once**, and can be done from a local instance.
 
-![](../../doc-images/baseline-production-from-local.png)
+![](../../../doc-images/baseline-production-from-local.png)

content/200-orm/200-prisma-migrate/200-understanding-prisma-migrate/010-mental-model.mdx

@@ -171,7 +171,7 @@ Under the hood, the `migrate deploy` command:
 1. Applies pending migrations
 1. Updates `_prisma_migrations` table with the new migrations
 
-![](../../../300-guides/025-migrate/100-developing-with-prisma-migrate/deploy-db.png)
+![](/orm/prisma-migrate/workflows/deploy-db.png)
 
 The command should be run in an automated CI/ CD environment, for example GitHub Actions.
 

content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer.mdx

@@ -406,7 +406,7 @@ npx prisma db pull
 
 Here's a graphical illustration for what happens when `db pull` is invoked:
 
-![Introspect your database with Prisma](../../../doc-images/prisma-db-pull-generate-schema.png)
+![Introspect your database with Prisma](../../../../doc-images/prisma-db-pull-generate-schema.png)
 
 For the above Prisma 1 datamodel, this results in the following Prisma 2 schema (note that the models have been reordered to match the initial order of the Prisma 1 datamodel):
 

content/400-pulse/100-what-is-pulse.mdx

@@ -10,7 +10,7 @@ toc: true
 
 [Pulse](https://www.prisma.io/data-platform/pulse) is a managed [change data capture (CDC)](https://en.wikipedia.org/wiki/Change_data_capture) service that captures change events from your database and delivers them instantly to your applications. With Pulse, you can quickly build real-time applications in a type-safe manner using [Prisma Client](/orm/prisma-client).
 
-![Pulse usage diagram.](../../doc-images/data-platform/platform/pulse/diagram.png)
+![Pulse usage diagram.](../doc-images/data-platform/platform/pulse//diagram.png)
 
 <Admonition type="warning">
 

content/400-pulse/300-concepts.mdx

@@ -12,7 +12,7 @@ toc: true
 
 [Change data capture (CDC)](https://en.wikipedia.org/wiki/Change_data_capture) is a technique used to track and capture changes in a database enabling real-time updates. It allows applications to be informed about the modifications in the database, ensuring data consistency between multiple applications.
 
-![Pulse diagram.](../../doc-images/data-platform/platform/pulse/diagram.png)
+![Pulse usage diagram.](../doc-images/data-platform/platform/pulse//diagram.png)
 
 ## Logical replication