docs(sentry-basics): Consolidate tutorials into one getting-started tutorial

docs/concepts/key-terms/dsn-explainer.mdx

@@ -68,4 +68,4 @@ For example, if you have a React frontend and an Express backend, whether they'r
 - Set up distributed tracing to follow requests across your frontend and backend
 - Assign responsibility to specific teams
 
-To learn more about setting up multiple projects for distributed tracing, see [Create Frontend and Backend Sentry Projects](/product/sentry-basics/distributed-tracing/create-new-project/). For general guidance on how many projects to create, see [How Many Projects Should I Create?](/organization/getting-started/#how-many-projects-should-i-create)
+To learn more about setting up multiple projects for distributed tracing, see [Create Frontend and Backend Sentry Projects](/product/sentry-basics/getting-started-tutorial/create-new-project/). For general guidance on how many projects to create, see [How Many Projects Should I Create?](/organization/getting-started/#how-many-projects-should-i-create)

docs/concepts/key-terms/tracing/distributed-tracing.mdx

@@ -74,7 +74,7 @@ Applications consist of interconnected components or services. For example, a mo
 
 Each component can be instrumented individually using a Sentry SDK to capture error data or crash reports, but this doesn't provide the full picture. Distributed tracing ties all the data together.
 
-Distributed tracing allows you to follow a request from the [frontend](/product/sentry-basics/integrate-frontend/) to the [backend](/product/sentry-basics/integrate-backend/) and back, pulling in data from any background tasks or notification jobs that request creates. This helps correlate Sentry error reports and gain insights into which services may negatively impact your application's performance.
+Distributed tracing allows you to follow a request from the [frontend](/product/sentry-basics/getting-started-tutorial/initialize-sentry-sdk-frontend/) to the [backend](/product/sentry-basics/getting-started-tutorial/initialize-sentry-sdk-backend/) and back, pulling in data from any background tasks or notification jobs that request creates. This helps correlate Sentry error reports and gain insights into which services may negatively impact your application's performance.
 
 ## Traces, Transactions, and Spans
 

docs/product/dashboards/sentry-dashboards/backend/queries.mdx

@@ -95,7 +95,7 @@ Query Sources are currently supported in Sentry's [Laravel](/platforms/php/guide
 
 </Alert>
 
-A query's source is the location in your application's code that triggered the query. Sentry automatically determines the query source by examining the [stack trace](/product/sentry-basics/integrate-frontend/upload-source-maps/) and attaches the source to the query data.
+A query's source is the location in your application's code that triggered the query. Sentry automatically determines the query source by examining the [stack trace](/product/sentry-basics/getting-started-tutorial/enable-readable-stack-traces/) and attaches the source to the query data.
 
 You can see the query's source underneath the query description on the **Query Details** dashboard, as shown in the image below. If you have a [source code management integration](/integrations/source-code-mgmt/) enabled, Sentry will also show a link to open the query's source in the relevant repository.
 

docs/product/explore/session-replay/mobile/index.mdx

@@ -29,7 +29,7 @@ Every replay has a detailed view that contains the embedded video player and ric
 
 The below list shows the breakdown of each component and why it’s valuable:
 
-- **Activity:** The **Activity** tab shows when key user interactions took place, specifically: user taps with the relevant component, navigations, when the user put the app in background or foreground, and [custom breadcrumbs](/product/sentry-basics/integrate-backend/configuration-options/#breadcrumbs) set by your organization. It also provides insight into the device of a given user session at particular timestamps:
+- **Activity:** The **Activity** tab shows when key user interactions took place, specifically: user taps with the relevant component, navigations, when the user put the app in background or foreground, and [custom breadcrumbs](/platforms/javascript/enriching-events/breadcrumbs/) set by your organization. It also provides insight into the device of a given user session at particular timestamps:
       - `device battery` (when battery level or charging status changes)
       - `orientation` (when the user rotates the device)
       - `connectivity` (when this status changes between wifi, cellular, and offline).

docs/product/explore/session-replay/replay-details.mdx

@@ -37,11 +37,11 @@ Sentry now provides **AI-powered replay summaries** that automatically analyze w
 The **Activity** tab shows when key user interactions took place during the replay. Entries are synced with the replay player and will auto-scroll as the video plays.
 
 **Both web and mobile replays include:**
-- **Custom Breadcrumbs:** Learn more about configuring [custom breadcrumbs](/product/sentry-basics/integrate-backend/configuration-options/#breadcrumbs)
+- **Custom Breadcrumbs:** Learn more about configuring [custom breadcrumbs](/platforms/javascript/enriching-events/breadcrumbs/)
 
 **Web-specific activity includes:**
 - **User Clicks:** including [rage clicks](/product/issues/issue-details/replay-issues/rage-clicks/) and [dead clicks](/product/issues/issue-details/replay-issues/rage-clicks/#detection-criteria)
-- **Navigations and Page Loads:** [Learn more about spans](/product/sentry-basics/distributed-tracing/)
+- **Navigations and Page Loads:** [Learn more about spans](/product/sentry-basics/getting-started-tutorial/)
 - **Web Vitals:** and an overall performance score [Learn more](/product/dashboards/sentry-dashboards/frontend/web-vitals/)
 
 **Mobile-specific activity includes:**

docs/product/index.mdx

@@ -18,7 +18,7 @@ Sentry's error monitoring capabilities make it possible to quickly get to the ro
 
 Sentry automatically captures unhandled exceptions (errors). It then groups similar errors into [issues](/product/issues/), making it possible to triage and manage them more efficiently.
 
-- If you're monitoring a web project, you can [**replay**](/product/explore/session-replay/) what the user experienced on your app and connect that error to the problematic line of code with [**source maps**](/product/sentry-basics/integrate-frontend/upload-source-maps/).
+- If you're monitoring a web project, you can [**replay**](/product/explore/session-replay/) what the user experienced on your app and connect that error to the problematic line of code with [**source maps**](/product/sentry-basics/getting-started-tutorial/enable-readable-stack-traces/).
 - If you set up Sentry for both your frontend and backend, you'll be able to use [**distributed tracing**](/product/sentry-basics/concepts/tracing/distributed-tracing/) to see the sequence of events (both frontend and backend) that led up to the event of interest.
 - Additionally, you can set up [**integrations**](/integrations/source-code-mgmt/) to link your source code so that Sentry can surface [**suspect commits**](/product/issues/suspect-commits/) and [**stack traces**](/integrations/source-code-mgmt/github/#stack-trace-linking) to show the problematic line of code, as well as [**suggest assignees**](/integrations/source-code-mgmt/github/#suspect-commits-and-suggested-assignees) for issues based on commit authors.
 

docs/product/projects/index.mdx

@@ -6,7 +6,7 @@ description: "View all the projects associated with teams that you're a member o
 
 A _Project_ represents your service or application in Sentry. For example, you might have separate projects for your API server and frontend client.
 
-When you first [create a project](/product/sentry-basics/integrate-frontend/create-new-project/), you also assign a team to it. All members of the assigned team have access to the project. Additional teams can be added in your project's [Project Teams](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/:projectId/teams/) settings.
+When you first [create a project](/product/sentry-basics/getting-started-tutorial/create-new-project/), you also assign a team to it. All members of the assigned team have access to the project. Additional teams can be added in your project's [Project Teams](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/:projectId/teams/) settings.
 
 You can create more projects to reflect your application landscape with finer granularity (for example, a separate project for each repo, mapping components and micro-services to the teams that own them). For most pages in Sentry, including **Issues** and **Discover**, the top-level filter bar defaults to showing information for your projects, so that you only see what's relevant to you and your team(s). How you set up your projects can go a long way in reducing noise and improving productivity. Learn more about best practices for setting up projects in our [account setup documentation](/organization/getting-started/#4-create-projects).