Improve onboarding options (#10390)

Author: stephanie-anderson

docs/platforms/dotnet/config.yml

@@ -1,8 +1,10 @@
 ---
 title: .NET
 sdk: sentry.dotnet
-caseStyle: snake_case
+caseStyle: PascalCase
 supportLevel: production
+aliases:
+  - C#
 ---
 
 On this page, we get you up and running with Sentry's .NET SDK, automatically reporting errors and exceptions in your application.

docs/platforms/dotnet/index.mdx

@@ -27,7 +27,7 @@ To set up Sentry for a Google Cloud Function:
 
 <SignInNote />
 
-```javascript {tabTitle:Http functions}
+```javascript {tabTitle:Http functions} {"onboardingOptions": {"performance": "5-9"}}
 const Sentry = require("@sentry/google-cloud-serverless");
 
 Sentry.init({
@@ -44,7 +44,7 @@ exports.helloHttp = Sentry.wrapHttpFunction((req, res) => {
 });
 ```
 
-```javascript {tabTitle:Background functions}
+```javascript {tabTitle:Background functions} {"onboardingOptions": {"performance": "5"}}
 const Sentry = require("@sentry/google-cloud-serverless");
 
 Sentry.init({
@@ -59,7 +59,7 @@ exports.helloEvents = Sentry.wrapEventFunction(
 );
 ```
 
-```javascript {tabTitle:CloudEvent functions}
+```javascript {tabTitle:CloudEvent functions} {"onboardingOptions": {"performance": "5"}}
 const Sentry = require("@sentry/google-cloud-serverless");
 
 Sentry.init({

docs/platforms/javascript/guides/gcp-functions/index.mdx

@@ -6,7 +6,11 @@ description: "Learn how to set up the SDK manually."
 
 If you can't (or prefer not to) run the [automatic setup](/platforms/javascript/guides/remix/#install), you can follow the instructions below to configure your application.
 
-## Installation
+## Install
+
+<OnboardingOptionButtons
+  options={["error-monitoring", "performance", "profiling", "session-replay"]}
+/>
 
 Get started by installing the Sentry Remix SDK:
 
@@ -22,7 +26,7 @@ yarn add @sentry/remix
 pnpm add @sentry/remix
 ```
 
-## Configuration
+## Configure
 
 To use this SDK, initialize Sentry in your Remix entry points for both the client and server.
 
@@ -34,7 +38,7 @@ The two configuration types are mostly the same, except that some configuration
 
 ### Client-side Configuration
 
-```typescript {tabTitle:Client} {filename: entry.client.tsx}
+```typescript {tabTitle:Client} {filename: entry.client.tsx} {"onboardingOptions": {"performance": "8-12,16-23", "session-replay": "13-14,24-28"}}
 import { useLocation, useMatches } from "@remix-run/react";
 import * as Sentry from "@sentry/remix";
 import { useEffect } from "react";
@@ -68,7 +72,7 @@ Sentry.init({
 
 ### Server-side Configuration
 
-```typescript {tabTitle:Server} {filename: entry.server.tsx}
+```typescript {tabTitle:Server} {filename: entry.server.tsx} {"onboardingOptions": {"performance": "5-9"}}
 import * as Sentry from "@sentry/remix";
 
 Sentry.init({

docs/platforms/javascript/guides/remix/manual-setup.mdx

@@ -6,7 +6,7 @@ description: "Learn how to set up the SDK manually."
 
 If you can't (or prefer not to) run the <PlatformLink to="/#install">automatic setup</PlatformLink>, you can follow the instructions below to configure the Sentry SvelteKit SDK in your application. This guide is also useful to adjust the pre-set configuration if you used the installation wizard for automatic setup.
 
-## Installation
+## Install
 
 ```bash {tabTitle:npm}
 npm install --save @sentry/sveltekit
@@ -22,7 +22,9 @@ pnpm add @sentry/sveltekit
 
 If you're updating your Sentry SDK to the latest version, check out our [migration guide](https://github.com/getsentry/sentry-javascript/blob/master/MIGRATION.md) to learn more about breaking changes.
 
-## Client-side Setup
+## Configure
+
+### Client-side Setup
 
 1. If you don't already have a [client hooks](https://kit.svelte.dev/docs/hooks#shared-hooks) file, create a new one in `src/hooks.client.(js|ts)`.
 
@@ -88,7 +90,7 @@ export const handleError = Sentry.handleErrorWithSentry(myErrorHandler);
 // export const handleError = handleErrorWithSentry();
 ```
 
-## Server-side Setup
+### Server-side Setup
 
 1. If you don't already have a [server hooks](https://kit.svelte.dev/docs/hooks#server-hooks) file, create a new one in `src/hooks.server.(js|ts)`.
 
@@ -157,7 +159,7 @@ export const handle = Sentry.sentryHandle();
 // export const handle = sequence(Sentry.sentryHandle(), yourHandler());
 ```
 
-## Vite Setup
+### Vite Setup
 
 Add the `sentrySvelteKit` plugins to your `vite.config.(js|ts)` file so the Sentry SDK can apply build-time features.
 Make sure that it is added _before_ the sveltekit plugin:
@@ -187,7 +189,7 @@ The `sentrySvelteKit()` function adds Vite plugins to your Vite config to:
 - Automatically upload source maps to Sentry
 - Automatically instrument `load` functions for tracing
 
-## Configure Source Maps Upload
+### Configure Source Maps Upload
 
 By default, `sentrySvelteKit()` will add an instance of the [Sentry Vite Plugin](https://www.npmjs.com/package/@sentry/vite-plugin), to upload source maps for both server and client builds. This means that when you run a production build (`npm run build`), source maps will be generated and uploaded to Sentry, so that you get readable stack traces in your Sentry issues.
 
@@ -255,7 +257,7 @@ export default {
 
 Using the `sourceMapsUploadOptions` object is useful if the default source maps upload doesn't work out of the box, for instance, if you have a customized build setup or if you're using the SDK with a SvelteKit adapter other than the [supported adapters](../#compatibility).
 
-### Overriding SvelteKit Adapter detection
+#### Overriding SvelteKit Adapter detection
 
 By default, `sentrySvelteKit` will try to detect your SvelteKit adapter to configure source maps upload correctly.
 If you're not using one of the [supported adapters](../#compatibility) or the wrong one is detected, you can override the adapter detection by passing the `adapter` option to `sentrySvelteKit`:
@@ -290,7 +292,7 @@ export default {
 };
 ```
 
-### Disable Source Maps Upload
+#### Disable Source Maps Upload
 
 You can disable automatic source maps upload in your Vite config:
 
@@ -326,7 +328,7 @@ export default {
 
 If you disable automatic source maps upload, you must explicitly set a `release` value in your `Sentry.init()` configs. You can also skip the `sentry-cli` configuration step below.
 
-## Configure Auto-Instrumentation
+### Configure Auto-Instrumentation
 
 The SDK primarily uses [SvelteKit's hooks](https://kit.svelte.dev/docs/hooks) to collect error and performance data. However, SvelteKit doesn't yet offer a hook for universal or server-only `load` function calls. Therefore, the SDK uses a Vite plugin to auto-instrument `load` functions so that you don't have to add a Sentry wrapper to each function manually.
 
@@ -339,7 +341,7 @@ If you have custom Sentry code in these files, you'll have to [manually](#instru
 
 </Note>
 
-### Customize Auto-instrumentation
+#### Customize Auto-instrumentation
 
 By passing the `autoInstrument` option to `sentrySvelteKit` you can disable auto-instrumentation entirely, or customize which `load` functions should be instrumented:
 
@@ -379,7 +381,7 @@ export default {
 };
 ```
 
-### Disable Auto-instrumentation
+#### Disable Auto-instrumentation
 
 If you set the `autoInstrument` option to `false`, the SDK won't auto-instrument any `load` functions. You can still [manually instrument](#instrument-load-functions-manually) specific `load` functions.
 
@@ -413,11 +415,11 @@ export default {
 };
 ```
 
-### Instrument `load` Functions Manually
+#### Instrument `load` Functions Manually
 
 If you don't want to use auto-instrumentation, you can also manually instrument specific `load` functions with the SDK's `load` function wrappers.
 
-#### Universal `load` Functions
+##### Universal `load` Functions
 
 Use the `wrapLoadWithSentry` function to wrap universal `load` functions declared in `+page.(js|ts)` or `+layout.(js|ts)`
 
@@ -441,7 +443,7 @@ export const load = wrapLoadWithSentry(({ fetch }) => {
 });
 ```
 
-#### Server-only `load` Functions
+##### Server-only `load` Functions
 
 Or use the `wrapServerLoadWithSentry` function to wrap server-only `load` functions declared in `+page.server.(js|ts)` or `+layout.server.(js|ts)`
 
@@ -465,7 +467,7 @@ export const load = wrapServerLoadWithSentry(({ event }) => {
 });
 ```
 
-### Configure Client-side `fetch` Instrumentation
+#### Configure Client-side `fetch` Instrumentation
 
 <Note>
 
@@ -499,7 +501,7 @@ const config = {
 };
 ```
 
-#### Disable Client-side `fetch` Proxy Script
+##### Disable Client-side `fetch` Proxy Script
 
 If you do not want to inject the script responsible for instrumenting client-side `load` calls, you can disable injection by passing `injectFetchProxyScript: false` to `sentryHandle`:
 

docs/platforms/javascript/guides/sveltekit/manual-setup.mdx

@@ -9,19 +9,19 @@ categories:
 
 Sentry's Wasm integration enhances the Browser SDK, and allows it to provide more detailed debug information not only for the error itself, but also for the entire module it was executed from. It includes things like Debug IDs, Debug Files, Code IDs, Code Files and memory addresses.
 
-### Install
+## Install
 
 Install `@sentry/browser` and `@sentry/wasm` using `yarn` or `npm`:
 
-```bash {tabTitle:npm}
-npm install --save @sentry/browser @sentry/wasm
-```
-
 ```bash {tabTitle:Yarn}
 yarn add @sentry/browser @sentry/wasm
 ```
 
-and afterwards use it like this:
+```bash {tabTitle:npm}
+npm install --save @sentry/browser @sentry/wasm
+```
+
+## Configure
 
 <SignInNote />
 
@@ -31,22 +31,26 @@ import { wasmIntegration } from "@sentry/wasm";
 
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
-  integrations: [wasmIntegration()],
+  integrations: [
+    wasmIntegration()
+  ],
 });
+```
 
-// Now, whenever any code from WebAssembly module will throw an error,
-// it'll get captured and it'll contain all the necessary information.
+## Verify
 
+Now, whenever any code from WebAssembly module will throw an error, it'll get captured, and it'll contain all the necessary information.
+
+```javascript
 function executeInternalWasmStuff() {
   throw new Error("whoops");
 }
 
 const { instance } = await WebAssembly.instantiateStreaming(
-  fetch("very-complex-module.wasm"),
-  {
+  fetch("very-complex-module.wasm"), {
     env: {
       external_func: executeInternalWasmStuff,
-    },
+    }
   }
 );
 

docs/platforms/javascript/guides/wasm/index.mdx

@@ -54,7 +54,7 @@ services:
         tags: { name: monolog.processor, handler: sentry }
 ```
 
-## Test the implementation
+## Verify
 
 To test that both logger error and exception are correctly sent to sentry.io, you can create the following controller:
 

docs/platforms/php/guides/symfony/index.mdx

@@ -1,6 +1,7 @@
 ---
 title: Set Up Metrics
 description: "Learn how to measure the data points you care about by configuring Metrics in your Symfony app."
+sidebar_order: 5500
 ---
 
 <Include name="feature-stage-beta-metrics.mdx" />

docs/platforms/php/guides/symfony/metrics/index.mdx

@@ -3,28 +3,23 @@ title: PHP
 sdk: sentry.php
 caseStyle: snake_case
 supportLevel: production
-description: PHP (or Hypertext Preprocessor) is an open source, general-purpose scripting language that's well-suited for web development. It can be embedded into HTML. 
+description: PHP (or Hypertext Preprocessor) is an open source, general-purpose scripting language that's well-suited for web development. It can be embedded into HTML.
 ---
 
-
-On this page, we get you up and running with Sentry's PHP SDK, automatically reporting errors and exceptions in your application.
+On this page, we get you up and running with Sentry's PHP SDK, automatically reporting errors and exceptions in your application. The SDK provides support for PHP 7.2 or later. If you're using a previous version of the PHP SDK, you can access the <Link rel="nofollow" to="/platforms/php/legacy-sdk/">legacy SDK documentation</Link>.
 
 <Note>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
 </Note>
 
-Using a framework? Check out the other SDKs we support in the left-hand dropdown.
-
 <GuideGrid platform="php" />
 
-## Configure the PHP SDK
-
-The below Sentry PHP SDK provides support for PHP 7.2 or later. If you're using a previous version of the PHP SDK, you can access the <Link rel="nofollow" to="/platforms/php/legacy-sdk/">legacy SDK documentation</Link>.
-
 Sentry captures data by using an SDK within your application’s runtime. Our SDKs are platform-specific and allow Sentry to have a deep understanding of how your application works.
 
+## Install
+
 <OnboardingOptionButtons
   options={[
     'error-monitoring',
@@ -33,9 +28,6 @@ Sentry captures data by using an SDK within your application’s runtime. Our SD
   ]}
 />
 
-## Install
-In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). To enable tracing and/or profiling, click the corresponding checkmarks to get the code snippets.
-
 Install the SDK using [Composer](https://getcomposer.org/).
 
 ```bash