fix(docs): Remove hard-coded domains from URLs where applicable across all documentation

docs/cli/dif.mdx

@@ -91,7 +91,7 @@ sentry-cli debug-files upload --include-sources /path/to/files...
 This feature is supported by build tools that produce debug information files
 supported by Sentry such as DWARF and PDB. This applies to languages such
 as C/C++/C#/Swift/Rust/Zig/etc.
-For Java/Kotlin and other JVM languages, use one of the plugins: [Maven](https://docs.sentry.io/platforms/java/maven/) or [Gradle](https://docs.sentry.io/platforms/java/gradle/).
+For Java/Kotlin and other JVM languages, use one of the plugins: [Maven](/platforms/java/maven/) or [Gradle](/platforms/java/gradle/).
 
 </Alert>
 

docs/concepts/data-management/event-grouping/index.mdx

@@ -57,7 +57,7 @@ Grouping falls back to messages if the stack trace, `type`, and `value` are not
 
 In addition to fingerprint-based grouping, Sentry uses AI to further improve issue grouping accuracy. This system helps identify semantically similar errors that might have different fingerprints due to minor code variations. The AI grouping system works alongside traditional fingerprinting - it only attempts to group new issues and will never split up issues that were grouped by fingerprint.
 
-This system will not apply to any events that have fully custom fingerprints (either set via SDK or [fingerprint rules](https://docs.sentry.io/product/issues/grouping-and-fingerprints/#fingerprint-rules)). However, events with fingerprints containing `{{ default }}` will use AI grouping to calculate the `{{ default }}` portion of the fingerprint.
+This system will not apply to any events that have fully custom fingerprints (either set via SDK or [fingerprint rules](/product/issues/grouping-and-fingerprints/#fingerprint-rules)). However, events with fingerprints containing `{{ default }}` will use AI grouping to calculate the `{{ default }}` portion of the fingerprint.
 
 When Sentry's default fingerprinting algorithm generates a new hash, it automatically sends the error data to [Seer](https://github.com/getsentry/seer), our AI/ML service. That error data includes the message and in-app stack frames (including those configured with stack trace rules), or all frames when no in-app frames are present.
 

docs/concepts/data-management/filtering/index.mdx

@@ -112,7 +112,7 @@ Once applied, you can track the filtered events (numbers and cause) using the gr
 
 ## Logs Filtering
 
-Inbound data filters have partial support for [Logs](https://docs.sentry.io/product/explore/logs/). Only a subset of the available inbound filters apply to Logs.
+Inbound data filters have partial support for [Logs](/product/explore/logs/). Only a subset of the available inbound filters apply to Logs.
 
 The following inbound filters **do** apply to Logs:
 

docs/concepts/otlp/index.mdx

@@ -10,8 +10,8 @@ keywords: ["otlp", "otel", "opentelemetry"]
 Sentry can ingest [OpenTelemetry](https://opentelemetry.io) traces directly via the  [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/). If you have an existing OpenTelemetry trace instrumentation, you can configure your OpenTelemetry exporter to send traces to Sentry directly. Sentry's OTLP ingestion endpoint is currently in development, and has a few known limitations:
 
 - Span events are not supported. All span events are dropped during ingestion.
-- Span links are partially supported. We ingest and display span links, but they cannot be searched, filtered, or aggregated. Links are are shown in the [Trace View](https://docs.sentry.io/concepts/key-terms/tracing/trace-view/).
-- Array attributes are partially supported. We ingest and display array attributes, but they cannot be searched, filtered, or aggregated. Array attributes are shown in the [Trace View](https://docs.sentry.io/concepts/key-terms/tracing/trace-view/).
+- Span links are partially supported. We ingest and display span links, but they cannot be searched, filtered, or aggregated. Links are are shown in the [Trace View](/concepts/key-terms/tracing/trace-view/).
+- Array attributes are partially supported. We ingest and display array attributes, but they cannot be searched, filtered, or aggregated. Array attributes are shown in the [Trace View](/concepts/key-terms/tracing/trace-view/).
 - Sentry does not support ingesting OTLP metrics or OTLP logs.
 
 The easiest way to configure an OpenTelemetry exporter is with environment variables. You'll need to configure the trace endpoint URL, as well as the authentication headers. Set these variables on the server where your application is running.

docs/concepts/search/searchable-properties/session-replay.mdx

@@ -102,7 +102,7 @@ The `title` of an element that was clicked. For example, `Save this comment` wou
 
 ### `count_dead_clicks`
 
-The number of [dead clicks](https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds) within a replay.
+The number of [dead clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds) within a replay.
 
 - **Type:** number
 
@@ -114,7 +114,7 @@ The number of errors within a replay.
 
 ### `count_rage_clicks`
 
-The number of [rage clicks](<https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>) within a replay.
+The number of [rage clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>) within a replay.
 
 - **Type:** number
 
@@ -138,7 +138,7 @@ The number of URLs that the user visited during a replay recording.
 
 ### `dead.selector`
 
-Similar to the `click.selector` search property, but only queries on [dead clicks](https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
+Similar to the `click.selector` search property, but only queries on [dead clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
 
 - **Type:** string
 
@@ -228,7 +228,7 @@ The id of the project.
 
 ### `rage.selector`
 
-Similar to the `click.selector` search property, but only queries on [rage clicks](<https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
+Similar to the `click.selector` search property, but only queries on [rage clicks](</product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
 
 - **Type:** string
 

docs/contributing/approach/sdk-docs/write-quick-start.mdx

@@ -90,7 +90,7 @@ Use this template for your manual setup guides. Keep your instructions concise a
 
 We recommend you base your guide on a similar existing SDK page, such as:
 
-- [Next.js quick start guide manual setup](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/)
+- [Next.js quick start guide manual setup](/platforms/javascript/guides/nextjs/manual-setup/)
 
 **Minimal structure:**
 

docs/organization/integrations/deployment/expo/index.mdx

@@ -49,5 +49,5 @@ To see your Sentry Issues and Replays in Expo dashboard, you'll first need to en
   npx @sentry/wizard@latest -i reactNative
   ```
 
-  For more details on using Sentry with Expo, refer to the [Sentry documentation](https://docs.sentry.io/platforms/react-native/) for React Native applications.
+  For more details on using Sentry with Expo, refer to the [Sentry documentation](/platforms/react-native/) for React Native applications.
 </Alert>

docs/organization/integrations/integration-platform/webhooks/issues.mdx

@@ -56,7 +56,7 @@ A status can mean multiple things, so substatus gives more details about the sta
 * `ignoreWindow`: Used with `ignoreCount` indicating the number of minutes that `ignoreCount` occurences will be ignored
 * `ignoreUserCount`: Maximun number of users who are affected by an archived issue before it gets escalated
 * `ignoreUserWindow`: Used with `ignoreUserCount` indicating the number of minutes that `ignoreUserCount` affected users will be ignored 
-* `ignoreDuration`: The duration (in minutes) that an archived issue should be ignored before it gets escalated. Increase in the number of users affected or the number of occurences will not escalate before this duration has passed unless there is a spike. To learn more about how this works, see [Escalating Issues Algorithm](https://docs.sentry.io/product/issues/states-triage/escalating-issues/).
+* `ignoreDuration`: The duration (in minutes) that an archived issue should be ignored before it gets escalated. Increase in the number of users affected or the number of occurences will not escalate before this duration has passed unless there is a spike. To learn more about how this works, see [Escalating Issues Algorithm](/product/issues/states-triage/escalating-issues/).
 
 ```json
 {

docs/platforms/android/configuration/shared-environments.mdx

@@ -6,7 +6,7 @@ sidebar_order: 2000
 
 <Alert>
 
-Using the Sentry SDK within another SDK is [discouraged](https://docs.sentry.io/platforms/). This can lead to unexpected behaviour and potential data leakage. If you need to use Sentry within another SDK, please follow the best practices outlined below.
+Using the Sentry SDK within another SDK is [discouraged](/platforms/). This can lead to unexpected behaviour and potential data leakage. If you need to use Sentry within another SDK, please follow the best practices outlined below.
 
 </Alert>
 

docs/platforms/apple/common/install/swift-package-manager.mdx

@@ -14,7 +14,7 @@ You will then be prompted to choose one of the options `Sentry`, `Sentry-Dynamic
 
 - `Sentry` is the static framework, which is the recommended option if you prefer a fast app start time.
 - `Sentry-Dynamic` is the dynamic framework.
-- `SentrySwiftUI` is used to track performance of SwiftUI views, see more information in the [docs](https://docs.sentry.io/platforms/apple/guides/ios/tracing/instrumentation/swiftui-instrumentation/).
+- `SentrySwiftUI` is used to track performance of SwiftUI views, see more information in the [docs](/platforms/apple/guides/ios/tracing/instrumentation/swiftui-instrumentation/).
 
 <Alert>
   Xcode allows you to choose many options, but you should choose only one of the

docs/platforms/dart/guides/flutter/migration.mdx

@@ -81,7 +81,7 @@ During `SentryFlutter.init` the SDK will inject the CDN script into the HTML's h
 This change allows us to utilize existing SDK functionality such as native JS Errors, add new features such as release health and makes it easier to develop features such as debug ids in the future.
 
 If you initialize the native SDKs separately with `options.autoInitializeNativeSdk = false` you will also need to add the Sentry Browser Javascript SDK to your website's HTML head.
-[Read this guide](https://docs.sentry.io/platforms/javascript/install/loader/#cdn) on how to install the SDK into your application via CDN bundles.
+[Read this guide](/platforms/javascript/install/loader/#cdn) on how to install the SDK into your application via CDN bundles.
 
 ### Drift Integration
 

docs/platforms/dotnet/common/configuration/msbuild.mdx

@@ -176,7 +176,7 @@ Sentry will try to determine the release version automatically by checking the f
 
 <ConfigKey name="SentrySetCommits">
 
-Enable `SentrySetCommits` to automatically [associate commits with the release](https://docs.sentry.io/cli/releases/#commit-integration).
+Enable `SentrySetCommits` to automatically [associate commits with the release](/cli/releases/#commit-integration).
 
 </ConfigKey>
 

docs/platforms/dotnet/common/crons/hangfire/index.mdx

@@ -4,7 +4,7 @@ description: "Learn more about how to monitor your Hangfire jobs."
 sidebar_order: 5001
 ---
 
-The .NET SDK provides an integration with [Hangfire](https://www.hangfire.io/) to monitor your jobs by automatically [creating check-ins for them](https://docs.sentry.io/product/crons/job-monitoring/). The SDK relies on job filters that are set up when you call `UseSentry`. For example:
+The .NET SDK provides an integration with [Hangfire](https://www.hangfire.io/) to monitor your jobs by automatically [creating check-ins for them](/product/crons/job-monitoring/). The SDK relies on job filters that are set up when you call `UseSentry`. For example:
 
 ```csharp
 using Hangfire;

docs/platforms/dotnet/common/data-management/data-collected.mdx

@@ -36,7 +36,7 @@ To enable sending the user's IP address, set the option `SendDefaultPii = true`
 
 Even if enabled, whether you're able to send the user's IP address or not, will depend on the integrations you enable in Sentry's SDK. Most integrations won't set the user's IP address at all.
 
-You can [prevent Sentry from storing IP Addresses](https://docs.sentry.io/platforms/native/enriching-events/identify-user/#ip_address) either by configuring this in the "Security & Privacy" settings of your Sentry project or using [server-side data scrubbing](https://docs.sentry.io/security-legal-pii/scrubbing/server-side-scrubbing/).
+You can [prevent Sentry from storing IP Addresses](/platforms/native/enriching-events/identify-user/#ip_address) either by configuring this in the "Security & Privacy" settings of your Sentry project or using [server-side data scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/).
 
 ## Request URL
 

docs/platforms/godot/configuration/stack-traces.mdx

@@ -114,7 +114,7 @@ If you need to `Export with Debug`, you can compile a debug template using the `
 
 ## Uploading Debug Symbols
 
-In order to get readable stack traces in Sentry, you also need to upload your debug symbols. The easiest way to do it is by using [Sentry CLI](https://docs.sentry.io/cli/). This tool allows you to upload the necessary debug information, making the stack traces useful for debugging.
+In order to get readable stack traces in Sentry, you also need to upload your debug symbols. The easiest way to do it is by using [Sentry CLI](/cli/). This tool allows you to upload the necessary debug information, making the stack traces useful for debugging.
 
 <Expandable title="Installing Sentry CLI">
 

docs/platforms/java/common/integrations/reactor.mdx

@@ -107,6 +107,6 @@ tx.finish()
 
 For more complex use cases, you can also use `SentryReactorUtils.withSentryForkedRoots` to fork the root scopes or `SentryReactorUtils.withSentryScopes` to wrap the operation in arbitrary scopes.
 
-For more information on scopes and scope forking, please consult our [scopes documentation](https://docs.sentry.io/platforms/java/enriching-events/scopes).
+For more information on scopes and scope forking, please consult our [scopes documentation](/platforms/java/enriching-events/scopes).
 
 You can also consult our GitHub repository for practical examples on how to use our Reactor integration with Spring WebFlux with [Spring Boot 2](https://github.com/getsentry/sentry-java/tree/main/sentry-samples/sentry-samples-spring-boot-webflux) and [Spring Boot 3](https://github.com/getsentry/sentry-java/tree/main/sentry-samples/sentry-samples-spring-boot-webflux-jakarta).

docs/platforms/javascript/common/best-practices/shared-environments.mdx

@@ -27,7 +27,7 @@ keywords:
 
 <Alert>
 
-We recommend using JavaScript SDK `8.x` and above when using the SDK with shared environments. Check out our [migration docs](https://docs.sentry.io/platforms/javascript/migration/) to upgrade from an older SDK version to `8.x` and above.
+We recommend using JavaScript SDK `8.x` and above when using the SDK with shared environments. Check out our [migration docs](/platforms/javascript/migration/) to upgrade from an older SDK version to `8.x` and above.
 
 </Alert>
 

docs/platforms/javascript/common/configuration/filtering.mdx

@@ -106,7 +106,7 @@ If you choose a mode to only apply tags, the tags can then be used in Sentry to
 
 <Alert>
 
-The `thirdPartyErrorFilterIntegration` will not work with the [Sentry Loader Script or CDN Bundles](https://docs.sentry.io/platforms/javascript/install/loader/).
+The `thirdPartyErrorFilterIntegration` will not work with the [Sentry Loader Script or CDN Bundles](/platforms/javascript/install/loader/).
 This is the case because the Sentry Loader Script and CDN Bundles are detected as "third party" by the integration. This makes it apply the chosen behavior to almost all events, since the Sentry SDK wraps many browser-native APIs.
 
 </Alert>

docs/platforms/javascript/common/data-management/data-collected/index.mdx

@@ -162,5 +162,5 @@ By default, the Sentry SDK sends information about the device and runtime to Sen
 
   At the time of a native crash, the stack of each thread is collected and sent to Sentry as part of the Minidump snapshot. This information is sent to Sentry by default, but dropped after processing the event in the backend.
 
-  These files are not stored by default, but you can [enable Minidump Storage](https://docs.sentry.io/platforms/native/guides/minidumps/enriching-events/attachments/#store-minidumps-as-attachments) in the Sentry organization or project settings.
+  These files are not stored by default, but you can [enable Minidump Storage](/platforms/native/guides/minidumps/enriching-events/attachments/#store-minidumps-as-attachments) in the Sentry organization or project settings.
 </PlatformSection>