docs: remove /docs from absolute Markdown links (#37132)

As indicated by https://docusaurus.io/docs/markdown-features/links, absolute file paths that are relaive to the site directory (i.e. `/npm-packages/docs/`) are not recommended, and it is recommended instead to use paths that are relative to the content root (`/npm-packages/docs/docs/`) instead.

I tested manually that links still work with this change.

GitOrigin-RevId: fd1738e467b4f7fc075fc9a1525e8db77da73ca8

Author: Nicolapps

npm-packages/docs/docs/ai.mdx

@@ -57,6 +57,5 @@ using rigorous evals. You can help by
 
 ## Convex MCP Server
 
-[Setup the Convex MCP server](/docs/ai/convex-mcp-server.mdx) to give your AI
-coding agent access to your Convex deployment to query and optimize your
-project.
+[Setup the Convex MCP server](/ai/convex-mcp-server.mdx) to give your AI coding
+agent access to your Convex deployment to query and optimize your project.

npm-packages/docs/docs/ai/convex-mcp-server.mdx

@@ -17,8 +17,8 @@ Add the following command to your MCP servers configuration:
 
 See editor specific instructions:
 
-- [Cursor](/docs/ai/using-cursor.mdx#setup-the-convex-mcp-server)
-- [Windsurf](/docs/ai/using-windsurf.mdx#setup-the-convex-mcp-server)
+- [Cursor](/ai/using-cursor.mdx#setup-the-convex-mcp-server)
+- [Windsurf](/ai/using-windsurf.mdx#setup-the-convex-mcp-server)
 
 ## Available Tools
 

npm-packages/docs/docs/ai/using-cursor.mdx

@@ -30,9 +30,9 @@ using rigorous evals. You can help by
 ## Setup the Convex MCP Server
 
 The Convex CLI comes with a
-[Convex Model Context Protocol](/docs/ai/convex-mcp-server.mdx) (MCP) server
-built in. The Convex MCP server gives your AI coding agent access to the your
-Convex deployment to query and optimize your project.
+[Convex Model Context Protocol](/ai/convex-mcp-server.mdx) (MCP) server built
+in. The Convex MCP server gives your AI coding agent access to the your Convex
+deployment to query and optimize your project.
 
 To get started with Cursor, open "Cursor Settings > MCP", click on "Add new
 global MCP server", and add a "convex" section to "mcpServers" in the `mcp.json`

npm-packages/docs/docs/ai/using-windsurf.mdx

@@ -23,9 +23,9 @@ using rigorous evals. You can help by
 ## Setup the Convex MCP Server
 
 The Convex CLI comes with a
-[Convex Model Context Protocol](/docs/ai/convex-mcp-server.mdx) (MCP) server
-built in. The Convex MCP server gives your AI coding agent access to the your
-Convex deployment to query and optimize your project.
+[Convex Model Context Protocol](/ai/convex-mcp-server.mdx) (MCP) server built
+in. The Convex MCP server gives your AI coding agent access to the your Convex
+deployment to query and optimize your project.
 
 To get started with Windsurf, open "Windsurf Settings > Cascade > Model Context
 Protocol (MCP) Servers", click on "Add Server", click "Add custom server", and

npm-packages/docs/docs/auth.mdx

@@ -21,23 +21,23 @@ most comprehensive authentication solutions. Integrating another service
 provides a ton of functionality like passkeys, two-factor auth, spam protection,
 and more on top of the authentication basics.
 
-- [Clerk](/docs/auth/clerk.mdx) is newer and has better Next.js and React Native
+- [Clerk](/auth/clerk.mdx) is newer and has better Next.js and React Native
   support
-- [Auth0](/docs/auth/auth0.mdx) is more established with more bells and whistles
-- [Custom Auth Integration](/docs/auth/advanced/custom-auth.mdx) allow any
-  OpenID Connect-compatible identity provider to be used for authentication
+- [Auth0](/auth/auth0.mdx) is more established with more bells and whistles
+- [Custom Auth Integration](/auth/advanced/custom-auth.mdx) allow any OpenID
+  Connect-compatible identity provider to be used for authentication
 
 After you integrate one of these, learn more about accessing authentication
-information in [Functions](/docs/auth/functions-auth.mdx) and storing user
-information in the [Database](/docs/auth/database-auth.mdx).
+information in [Functions](/auth/functions-auth.mdx) and storing user
+information in the [Database](/auth/database-auth.mdx).
 
 ## Convex Auth
 
 For client-side React and React Native mobile apps you can implement auth
-directly in Convex with the [Convex Auth](/docs/auth/convex-auth.mdx) library.
-This [npm package](https://github.com/get-convex/convex-auth) runs on your
-Convex deployment and helps you build a custom sign-up/sign-in flow via social
-identity providers, one-time email or SMS access codes, or via passwords.
+directly in Convex with the [Convex Auth](/auth/convex-auth.mdx) library. This
+[npm package](https://github.com/get-convex/convex-auth) runs on your Convex
+deployment and helps you build a custom sign-up/sign-in flow via social identity
+providers, one-time email or SMS access codes, or via passwords.
 
 Convex Auth is in beta (it isn't complete and may change in
 backward-incompatible ways) and doesn't provide as many features as third party
@@ -51,7 +51,7 @@ experimental support please [give it a try](https://labs.convex.dev/auth)!
 
 ## Debugging
 
-If you run into issues consult the [Debugging](/docs/auth/debug.mdx) guide.
+If you run into issues consult the [Debugging](/auth/debug.mdx) guide.
 
 ## Service Authentication
 

npm-packages/docs/docs/auth/advanced/custom-auth.mdx

@@ -5,7 +5,7 @@ sidebar_position: 3
 ---
 
 **Note: This is an advanced feature!** We recommend sticking with the
-[supported third-party authentication providers](/docs/auth.mdx).
+[supported third-party authentication providers](/auth.mdx).
 
 Convex can be integrated with any identity provider supporting the
 [OpenID Connect](https://openid.net/connect/) protocol. At minimum this means
@@ -15,12 +15,12 @@ exposes the corresponding
 [JWKS](https://auth0.com/docs/secure/tokens/json-web-tokens/json-web-key-sets).
 The ID token is passed from the client to your Convex backend which ensures that
 the token is valid and enables you to query the user information embedded in the
-token, as described in [Auth in Functions](/docs/auth/functions-auth.mdx).
+token, as described in [Auth in Functions](/auth/functions-auth.mdx).
 
 ## Server-side integration
 
-Just like with [Clerk](/docs/auth/clerk.mdx) and [Auth0](/docs/auth/auth0.mdx),
-the backend needs to be aware of the domain of the Issuer and your application's
+Just like with [Clerk](/auth/clerk.mdx) and [Auth0](/auth/auth0.mdx), the
+backend needs to be aware of the domain of the Issuer and your application's
 specific applicationID for a given identity provider.
 
 Add these to your `convex/auth.config.js` file:
@@ -42,8 +42,8 @@ export default {
 
 The [`ConvexProviderWithAuth`](/api/modules/react#ConvexProviderWithAuth)
 component provides a convenient abstraction for building an auth integration
-similar to the ones Convex provides for [Clerk](/docs/auth/clerk.mdx) and
-[Auth0](/docs/auth/auth0.mdx).
+similar to the ones Convex provides for [Clerk](/auth/clerk.mdx) and
+[Auth0](/auth/auth0.mdx).
 
 In the following example we build an integration with an imaginary "ProviderX",
 whose React integration includes `AuthProviderXReactProvider` and
@@ -113,11 +113,11 @@ utilities for checking the authentication state: the
 [`AuthLoading`](/api/modules/react#authloading) helper components.
 
 See
-[Logged-in and logged-out views](/docs/auth/clerk.mdx#logged-in-and-logged-out-views)
+[Logged-in and logged-out views](/auth/clerk.mdx#logged-in-and-logged-out-views)
 for examples of using these.
 
 ### Debugging
 
-See [Debugging Authentication](/docs/auth/debug.mdx).
+See [Debugging Authentication](/auth/debug.mdx).
 
 <StackPosts query="authentication" />

npm-packages/docs/docs/auth/advanced/custom-jwt.mdx

@@ -5,7 +5,7 @@ sidebar_position: 4
 ---
 
 **Note: This is an advanced feature!** We recommend sticking with the
-[supported third-party authentication providers](/docs/auth.mdx).
+[supported third-party authentication providers](/auth.mdx).
 
 If your custom auth provider implements the OIDC protocol, it's easiest to
 configure it as a [Custom OIDC Provider](/auth/advanced/custom-auth). However,

npm-packages/docs/docs/auth/auth0.mdx

@@ -24,7 +24,7 @@ If you're using Next.js see the
 ## Get started
 
 This guide assumes you already have a working React app with Convex. If not
-follow the [Convex React Quickstart](/docs/quickstart/react.mdx) first. Then:
+follow the [Convex React Quickstart](/quickstart/react.mdx) first. Then:
 
 <StepByStep>
   <Step title="Follow the Auth0 React quickstart">
@@ -184,12 +184,11 @@ export default function Badge() {
 
 ## User information in functions
 
-See [Auth in Functions](/docs/auth/functions-auth.mdx) to learn about how to
-access information about the authenticated user in your queries, mutations and
-actions.
+See [Auth in Functions](/auth/functions-auth.mdx) to learn about how to access
+information about the authenticated user in your queries, mutations and actions.
 
-See [Storing Users in the Convex Database](/docs/auth/database-auth.mdx) to
-learn about how to store user information in the Convex database.
+See [Storing Users in the Convex Database](/auth/database-auth.mdx) to learn
+about how to store user information in the Convex database.
 
 ## Configuring dev and prod tenants
 
@@ -241,8 +240,8 @@ Now switch to the new configuration by running `npx convex deploy`.
 To configure your client you can use environment variables as well. The exact
 name of the environment variables and the way to refer to them depends on each
 client platform (Vite vs Next.js etc.), refer to our corresponding
-[Quickstart](/docs/quickstarts.mdx) or the relevant documentation for the
-platform you're using.
+[Quickstart](/quickstarts.mdx) or the relevant documentation for the platform
+you're using.
 
 Change the props to `Auth0Provider` to take in environment variables:
 
@@ -258,8 +257,8 @@ Change the props to `Auth0Provider` to take in environment variables:
 Use the `.env.local` or `.env` file to configure your client when running
 locally. The name of the environment variables file depends on each client
 platform (Vite vs Next.js etc.), refer to our corresponding
-[Quickstart](/docs/quickstarts.mdx) or the relevant documentation for the
-platform you're using:
+[Quickstart](/quickstarts.mdx) or the relevant documentation for the platform
+you're using:
 
 ```py title=".env.local"
 VITE_AUTH0_DOMAIN="your-domain.us.auth0.com"
@@ -269,7 +268,7 @@ VITE_AUTH0_CLIENT_ID="yourclientid"
 **Production configuration**
 
 Set the environment variables in your production environment depending on your
-hosting platform. See [Hosting](/docs/production/hosting/hosting.mdx).
+hosting platform. See [Hosting](/production/hosting/hosting.mdx).
 
 ## Debugging authentication
 
@@ -283,7 +282,7 @@ contains a list of configured authentication providers. You must run
 configuration to your backend.
 
 For more thorough debugging steps, see
-[Debugging Authentication](/docs/auth/debug.mdx).
+[Debugging Authentication](/auth/debug.mdx).
 
 ## Under the hood
 

npm-packages/docs/docs/auth/clerk.mdx

@@ -34,7 +34,7 @@ See the following sections for the Clerk SDK that you're using:
 [React with Convex and Clerk](https://github.com/get-convex/template-react-vite-clerk)
 
 This guide assumes you already have a working React app with Convex. If not
-follow the [Convex React Quickstart](/docs/quickstart/react.mdx) first. Then:
+follow the [Convex React Quickstart](/quickstart/react.mdx) first. Then:
 
 <StepByStep>
   <Step title="Sign up for Clerk">
@@ -195,7 +195,7 @@ follow the [Convex React Quickstart](/docs/quickstart/react.mdx) first. Then:
 [Next.js with Convex and Clerk](https://github.com/get-convex/template-nextjs-clerk)
 
 This guide assumes you already have a working Next.js app with Convex. If not
-follow the [Convex Next.js Quickstart](/docs/quickstart/nextjs.mdx) first. Then:
+follow the [Convex Next.js Quickstart](/quickstart/nextjs.mdx) first. Then:
 
 <StepByStep>
   <Step title="Sign up for Clerk">
@@ -438,19 +438,18 @@ follow the [Convex Next.js Quickstart](/docs/quickstart/nextjs.mdx) first. Then:
 [Tanstack Start with Convex and Clerk](https://github.com/get-convex/templates/tree/main/template-tanstack-start)
 
 See the
-[Tanstack Start with Clerk guide](/docs/client/react/tanstack-start/clerk.mdx)
-for more information.
+[Tanstack Start with Clerk guide](/client/react/tanstack-start/clerk.mdx) for
+more information.
 
 ## Next steps
 
 ### Accessing user information in functions
 
-See [Auth in Functions](/docs/auth/functions-auth.mdx) to learn about how to
-access information about the authenticated user in your queries, mutations and
-actions.
+See [Auth in Functions](/auth/functions-auth.mdx) to learn about how to access
+information about the authenticated user in your queries, mutations and actions.
 
-See [Storing Users in the Convex Database](/docs/auth/database-auth.mdx) to
-learn about how to store user information in the Convex database.
+See [Storing Users in the Convex Database](/auth/database-auth.mdx) to learn
+about how to store user information in the Convex database.
 
 ### Accessing user information client-side
 
@@ -571,7 +570,7 @@ configured authentication providers. You must run `npx convex dev` or
 your backend.
 
 For more thorough debugging steps, see
-[Debugging Authentication](/docs/auth/debug.mdx).
+[Debugging Authentication](/auth/debug.mdx).
 
 ## Under the hood
 

npm-packages/docs/docs/auth/database-auth.mdx

@@ -17,16 +17,16 @@ import WebhookMessages from "!!raw-loader!@site/../demos/users-and-clerk-webhook
 import WebhookHook from "!!raw-loader!@site/../demos/users-and-clerk-webhooks/src/useCurrentUser.ts";
 import WebhookClient from "!!raw-loader!@site/../demos/users-and-clerk-webhooks/src/App.tsx";
 
-_If you're using [Convex Auth](/docs/auth/convex-auth.mdx) the user information
-is already stored in your database. There's nothing else you need to implement._
+_If you're using [Convex Auth](/auth/convex-auth.mdx) the user information is
+already stored in your database. There's nothing else you need to implement._
 
 You might want to store user information directly in your Convex database, for
 the following reasons:
 
 - Your functions need information about other users, not just about the
   currently logged-in user
 - Your functions need access to information other than the fields available in
-  the [Open ID Connect JWT](/docs/auth/functions-auth.mdx)
+  the [Open ID Connect JWT](/auth/functions-auth.mdx)
 
 There are two ways you can choose from for storing user information in your
 database (but only the second one allows storing information not contained in
@@ -46,8 +46,8 @@ the JWT):
 ### (optional) Users table schema
 
 You can define a `"users"` table, optionally with an
-[index](/docs/database/reading-data/indexes/indexes.md) for efficient looking up
-the users in the database.
+[index](/database/reading-data/indexes/indexes.md) for efficient looking up the
+users in the database.
 
 In the examples below we will use the `tokenIdentifier` from the
 `ctx.auth.getUserIdentity()` to identify the user, but you could use the
@@ -139,8 +139,8 @@ Set _Endpoint URL_ to
 `https://<your deployment name>.convex.site/clerk-users-webhook` (note the
 domain ends in **`.site`**, not `.cloud`). You can see your deployment name in
 the `.env.local` file in your project directory, or on your Convex dashboard as
-part of the [Deployment URL](/docs/dashboard/deployments/settings.md). For
-example, the endpoint URL could be:
+part of the [Deployment URL](/dashboard/deployments/settings.md). For example,
+the endpoint URL could be:
 `https://happy-horse-123.convex.site/clerk-users-webhook`.
 
 In _Message Filtering_, select **user** for all user events (scroll down or use
@@ -156,8 +156,8 @@ UI), it should start with `whsec_`. Set it as the value of the
 ### (optional) Users table schema
 
 You can define a `"users"` table, optionally with an
-[index](/docs/database/reading-data/indexes/indexes.md) for efficient looking up
-the users in the database.
+[index](/database/reading-data/indexes/indexes.md) for efficient looking up the
+users in the database.
 
 In the examples below we will use the `subject` from the
 `ctx.auth.getUserIdentity()` to identify the user, which should be set to the

npm-packages/docs/docs/auth/debug.mdx

@@ -24,14 +24,14 @@ To handle this, you can either:
 
 1. Use the `Authenticated` component from `convex/react` to wrap the component
    that includes the `useQuery` call (see the last two steps in the
-   [Clerk guide](/docs/auth/clerk.mdx#get-started))
+   [Clerk guide](/auth/clerk.mdx#get-started))
 2. Or return `null` or some other "sentinel" value from the query and handle it
    on the client
 
 If you are using `fetchQuery` for
-[Next.js Server Rendering](/docs/client/react/nextjs/nextjs-server-rendering.mdx),
+[Next.js Server Rendering](/client/react/nextjs/nextjs-server-rendering.mdx),
 make sure you are explicitly passing in a JWT token as documented
-[here](/docs/client/react/nextjs/nextjs-server-rendering.mdx#server-side-authentication).
+[here](/client/react/nextjs/nextjs-server-rendering.mdx#server-side-authentication).
 
 If this hasn't helped, follow the steps below to resolve your issue.
 
@@ -107,9 +107,9 @@ backend, is to inspect the traffic between them.
      </p>
 
    - For HTTP based clients (`ConvexHTTPClient` and the
-     [HTTP API](/docs/http-api/index.md)), select `Fetch/XHR` as the type of
-     traffic. You should see an individual network request for each function
-     call, with an `Authorization` header with value `Bearer ` followed by the
+     [HTTP API](/http-api/index.md)), select `Fetch/XHR` as the type of traffic.
+     You should see an individual network request for each function call, with
+     an `Authorization` header with value `Bearer ` followed by the
      authentication token.
 
      <p style={{ textAlign: "center" }}>

npm-packages/docs/docs/auth/functions-auth.mdx

@@ -12,10 +12,9 @@ import Fetch from "!!raw-loader!@site/../private-demos/snippets/src/httpAuthCall
 _If you're using Convex Auth, see the
 [authorization doc](https://labs.convex.dev/auth/authz#use-authentication-state-in-backend-functions)._
 
-Within a Convex [function](/docs/functions.mdx), you can access information
-about the currently logged-in user by using the
-[`auth`](/api/interfaces/server.Auth) property of the
-[`QueryCtx`](/api/interfaces/server.GenericQueryCtx),
+Within a Convex [function](/functions.mdx), you can access information about the
+currently logged-in user by using the [`auth`](/api/interfaces/server.Auth)
+property of the [`QueryCtx`](/api/interfaces/server.GenericQueryCtx),
 [`MutationCtx`](/api/interfaces/server.GenericMutationCtx), or
 [`ActionCtx`](/api/modules/server#actionctx) object: