fix broken links

Author: AmanVarshney01

src/components/GettingStarted/index.tsx

@@ -82,6 +82,36 @@ export const PrismaPostgres = ({ color, height, width }: any) => (
   </svg>
 );
 
+export const Plus = ({ color, width, height }: any) => (
+  <svg
+    xmlns="http://www.w3.org/2000/svg"
+    height={height ? height : "16"}
+    width={width ? width : "14"}
+    viewBox="0 0 448 512"
+    style={{ marginRight: `4px`, transform: `translateY(2px)` }}
+  >
+    <path
+      fill={color ? color : "currentColor"}
+      d="M256 80c0-17.7-14.3-32-32-32s-32 14.3-32 32V224H48c-17.7 0-32 14.3-32 32s14.3 32 32 32H192V432c0 17.7 14.3 32 32 32s32-14.3 32-32V288H400c17.7 0 32-14.3 32-32s-14.3-32-32-32H256V80z"
+    />
+  </svg>
+);
+
+export const Plug = ({ color, width, height }: any) => (
+  <svg
+    xmlns="http://www.w3.org/2000/svg"
+    height={height ? height : "16"}
+    width={width ? width : "14"}
+    viewBox="0 0 384 512"
+    style={{ marginRight: `4px`, transform: `translateY(2px)` }}
+  >
+    <path
+      fill={color ? color : "currentColor"}
+      d="M96 0C78.3 0 64 14.3 64 32v96h64V32c0-17.7-14.3-32-32-32zM288 0c-17.7 0-32 14.3-32 32v96h64V32c0-17.7-14.3-32-32-32zM32 160c-17.7 0-32 14.3-32 32s14.3 32 32 32v32c0 77.4 55 142 128 156.8V480c0 17.7 14.3 32 32 32s32-14.3 32-32V412.8C297 398 352 333.4 352 256V224c17.7 0 32-14.3 32-32s-14.3-32-32-32H32z"
+    />
+  </svg>
+);
+
 export const BorderBoxWrapper = ({ children, ...props }) => (
   <div {...props} className={styles.borderBox}>
     {children}
@@ -123,6 +153,21 @@ export const LinkCard = ({ icon, title, desc, link, highlight }: any) => {
   );
 };
 
+export const QuickstartLinkCard = ({ title, highlight, link, children }: any) => {
+  return (
+    <Link
+      to={link}
+      className={clsx(styles.linkCardWrapper, highlight && styles.linkCardHighlight)}
+      style={highlight ? { borderColor: highlight } : {}}
+    >
+      <div className={styles.title}>
+        <h6>{title}</h6>
+      </div>
+      <div>{children}</div>
+    </Link>
+  );
+};
+
 export const Tab = ({ children, ...props }) => (
   <div {...props} className={styles.tab}>
     {children}

versioned_docs/version-6.0.0/200-orm/050-overview/500-databases/600-mongodb.mdx

@@ -309,7 +309,7 @@ console.log(findNulls)
 
 This is because `name: null` is checking for equality, and a non-existing field isn't equal to `null`.
 
-To include missing fields as well, use the [`isSet` filter](/orm/reference/prisma-client-reference#isset) to explicitly search for fields which are either `null` or not set. This will return both records:
+To include missing fields as well, use the [`isSet` filter](/6.0/orm/reference/prisma-client-reference#isset) to explicitly search for fields which are either `null` or not set. This will return both records:
 
 <CodeWithResult expanded={true}>
 

versioned_docs/version-6.0.0/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx

@@ -15,7 +15,7 @@ datasource db {
 
 A Prisma schema can only have _one_ data source. However, you can:
 
-- [Programmatically override a data source `url` when creating your `PrismaClient`](/orm/reference/prisma-client-reference#programmatically-override-a-datasource-url)
+- [Programmatically override a data source `url` when creating your `PrismaClient`](/6.0/orm/reference/prisma-client-reference#programmatically-override-a-datasource-url)
 - [Specify a different URL for Prisma Migrate's shadow database if you are working with cloud-hosted development databases](/orm/prisma-migrate/understanding-prisma-migrate/shadow-database#cloud-hosted-shadow-databases-must-be-created-manually)
 
 > **Note**: Multiple provider support was removed in 2.22.0. Please see [Deprecation of provider array notation](https://github.com/prisma/prisma/issues/3834) for more information.

versioned_docs/version-6.0.0/200-orm/100-prisma-schema/20-data-model/10-models.mdx

@@ -1164,20 +1164,20 @@ Refer to the [relations documentation](/orm/prisma-schema/data-model/relations)
 
 Every model in the data model definition will result in a number of CRUD queries in the generated [Prisma Client API](/orm/prisma-client):
 
-- [`findMany()`](/orm/reference/prisma-client-reference#findmany)
-- [`findFirst()`](/orm/reference/prisma-client-reference#findfirst)
-- [`findFirstOrThrow()`](/orm/reference/prisma-client-reference#findfirstorthrow)
-- [`findUnique()`](/orm/reference/prisma-client-reference#findunique)
-- [`findUniqueOrThrow()`](/orm/reference/prisma-client-reference#finduniqueorthrow)
-- [`create()`](/orm/reference/prisma-client-reference#create)
-- [`update()`](/orm/reference/prisma-client-reference#update)
-- [`upsert()`](/orm/reference/prisma-client-reference#upsert)
-- [`delete()`](/orm/reference/prisma-client-reference#delete)
-- [`createMany()`](/orm/reference/prisma-client-reference#createmany)
-- [`createManyAndReturn()`](/orm/reference/prisma-client-reference#createmanyandreturn)
-- [`updateMany()`](/orm/reference/prisma-client-reference#updatemany)
-- [`updateManyAndReturn()`](/orm/reference/prisma-client-reference#updatemanyandreturn)
-- [`deleteMany()`](/orm/reference/prisma-client-reference#deletemany)
+- [`findMany()`](/6.0/orm/reference/prisma-client-reference#findmany)
+- [`findFirst()`](/6.0/orm/reference/prisma-client-reference#findfirst)
+- [`findFirstOrThrow()`](/6.0/orm/reference/prisma-client-reference#findfirstorthrow)
+- [`findUnique()`](/6.0/orm/reference/prisma-client-reference#findunique)
+- [`findUniqueOrThrow()`](/6.0/orm/reference/prisma-client-reference#finduniqueorthrow)
+- [`create()`](/6.0/orm/reference/prisma-client-reference#create)
+- [`update()`](/6.0/orm/reference/prisma-client-reference#update)
+- [`upsert()`](/6.0/orm/reference/prisma-client-reference#upsert)
+- [`delete()`](/6.0/orm/reference/prisma-client-reference#delete)
+- [`createMany()`](/6.0/orm/reference/prisma-client-reference#createmany)
+- [`createManyAndReturn()`](/6.0/orm/reference/prisma-client-reference#createmanyandreturn)
+- [`updateMany()`](/6.0/orm/reference/prisma-client-reference#updatemany)
+- [`updateManyAndReturn()`](/6.0/orm/reference/prisma-client-reference#updatemanyandreturn)
+- [`deleteMany()`](/6.0/orm/reference/prisma-client-reference#deletemany)
 
 The operations are accessible via a generated property on the Prisma Client instance. By default the name of the property is the lowercase form of the model name, e.g. `user` for a `User` model or `post` for a `Post` model.
 
@@ -1196,7 +1196,7 @@ const allUsers = await prisma.user.findMany()
 
 Prisma Client also generates **type definitions** that reflect your model structures. These are part of the generated [`@prisma/client`](/orm/prisma-client/setup-and-configuration/generating-prisma-client#the-prismaclient-npm-package) node module.
 
-When using TypeScript, these type definitions ensure that all your database queries are entirely type safe and validated at compile-time (even partial queries using [`select`](/orm/reference/prisma-client-reference#select) or [`include`](/orm/reference/prisma-client-reference#include) ).
+When using TypeScript, these type definitions ensure that all your database queries are entirely type safe and validated at compile-time (even partial queries using [`select`](/6.0/orm/reference/prisma-client-reference#select) or [`include`](/6.0/orm/reference/prisma-client-reference#include) ).
 
 Even when using plain JavaScript, the type definitions are still included in the `@prisma/client` node module, enabling features like [IntelliSense](https://code.visualstudio.com/docs/editor/intellisense)/autocompletion in your editor.
 

versioned_docs/version-6.0.0/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx

@@ -215,7 +215,7 @@ const updateAuthor = await prisma.user.update({
 })
 ```
 
-In the underlying database, this query uses a [nested `connect` query](/orm/reference/prisma-client-reference#connect) to link the post with an `id` of 4 to the user with an `id` of 20. The query does this with the following steps:
+In the underlying database, this query uses a [nested `connect` query](/6.0/orm/reference/prisma-client-reference#connect) to link the post with an `id` of 4 to the user with an `id` of 20. The query does this with the following steps:
 
 - The query first looks for the user with an `id` of `20`.
 - The query then sets the `authorID` foreign key to `20`. This links the post with an `id` of `4` to the user with an `id` of `20`.

versioned_docs/version-6.0.0/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx

@@ -157,7 +157,7 @@ const users = await prisma.user.findMany()
 
 <Admonition type="info">
 
-All Prisma Client methods return an instance of [`PrismaPromise`](/orm/reference/prisma-client-reference#prismapromise-behavior) which only executes when you call `await` or `.then()` or `.catch()`.
+All Prisma Client methods return an instance of [`PrismaPromise`](/6.0/orm/reference/prisma-client-reference#prismapromise-behavior) which only executes when you call `await` or `.then()` or `.catch()`.
 
 </Admonition>
 

versioned_docs/version-6.0.0/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx

@@ -120,7 +120,7 @@ import { PrismaClient } from './generated/client'
 :::note 
 
 
-For improved compatibility with ECMAScript modules (ESM) and to ensure consistent behaviour of Prisma ORM across different Node.js runtimes, you can also use the newer [`prisma-client`](/orm/prisma-schema/overview/generators#prisma-client) generator. This generator is specifically designed to handle common challenges with module resolution and runtime variations, providing a smoother integration experience and less friction with bundlers.
+For improved compatibility with ECMAScript modules (ESM) and to ensure consistent behaviour of Prisma ORM across different Node.js runtimes, you can also use the newer [`prisma-client`](/6.0/orm/prisma-schema/overview/generators#prisma-client) generator. This generator is specifically designed to handle common challenges with module resolution and runtime variations, providing a smoother integration experience and less friction with bundlers.
 
 :::
 

versioned_docs/version-6.0.0/200-orm/200-prisma-client/000-setup-and-configuration/015-instantiate-prisma-client.mdx

@@ -33,7 +33,7 @@ const prisma = new PrismaClient()
 
 :::tip
 
-You can further customize `PrismaClient` with [constructor parameters](/orm/reference/prisma-client-reference#prismaclient) — for example, set [logging levels](/orm/prisma-client/observability-and-logging/logging), [transaction options](/orm/prisma-client/queries/transactions#transaction-options) or customize [error formatting](/orm/prisma-client/setup-and-configuration/error-formatting).
+You can further customize `PrismaClient` with [constructor parameters](/6.0/orm/reference/prisma-client-reference#prismaclient) — for example, set [logging levels](/orm/prisma-client/observability-and-logging/logging), [transaction options](/orm/prisma-client/queries/transactions#transaction-options) or customize [error formatting](/orm/prisma-client/setup-and-configuration/error-formatting).
 
 :::
 

versioned_docs/version-6.0.0/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/100-connection-management.mdx

@@ -9,8 +9,8 @@ tocDepth: 3
 
 `PrismaClient` connects and disconnects from your data source using the following two methods:
 
-- [`$connect()`](/orm/reference/prisma-client-reference#connect-1)
-- [`$disconnect()`](/orm/reference/prisma-client-reference#disconnect-1)
+- [`$connect()`](/6.0/orm/reference/prisma-client-reference#connect-1)
+- [`$disconnect()`](/6.0/orm/reference/prisma-client-reference#disconnect-1)
 
 In most cases, you **do not need to explicitly call these methods**. `PrismaClient` automatically connects when you run your first query, creates a [connection pool](/orm/prisma-client/setup-and-configuration/databases-connections/connection-pool), and disconnects when the Node.js process ends.
 
@@ -29,7 +29,7 @@ See the [connection management guide](/orm/prisma-client/setup-and-configuration
 
 ## `$connect()`
 
-It is not necessary to call [`$connect()`](/orm/reference/prisma-client-reference#connect-1) thanks to the _lazy connect_ behavior: The `PrismaClient` instance connects lazily when the first request is made to the API (`$connect()` is called for you under the hood).
+It is not necessary to call [`$connect()`](/6.0/orm/reference/prisma-client-reference#connect-1) thanks to the _lazy connect_ behavior: The `PrismaClient` instance connects lazily when the first request is made to the API (`$connect()` is called for you under the hood).
 
 ### Calling `$connect()` explicitly
 
@@ -44,7 +44,7 @@ await prisma.$connect()
 
 ## `$disconnect()`
 
-When you call [`$disconnect()`](/orm/reference/prisma-client-reference#disconnect-1) , Prisma Client:
+When you call [`$disconnect()`](/6.0/orm/reference/prisma-client-reference#disconnect-1) , Prisma Client:
 
 1. Runs the [`beforeExit` hook](#exit-hooks)
 2. Ends the Query Engine child process and closes all connections

versioned_docs/version-6.0.0/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx

@@ -88,7 +88,7 @@ datasource db {
 
 The number of connections Prisma Client uses can be viewed using [logging](/orm/prisma-client/observability-and-logging/logging) and [metrics](/orm/prisma-client/observability-and-logging/metrics).
 
-Using the `info` [logging level](/orm/reference/prisma-client-reference#log-levels), you can log the number of connections in a connection pool that are opened when Prisma Client is instantiated.
+Using the `info` [logging level](/6.0/orm/reference/prisma-client-reference#log-levels), you can log the number of connections in a connection pool that are opened when Prisma Client is instantiated.
 
 For example, consider the following Prisma Client instance and invocation: