getsentry
diff --git a/‎docs/contributing/approach/sdk-docs/write-configuration.mdx‎
Lines changed: 16 additions & 5 deletions b/‎docs/contributing/approach/sdk-docs/write-configuration.mdx‎
Lines changed: 16 additions & 5 deletions
diff --git a/‎docs/contributing/pages/components.mdx‎
Lines changed: 25 additions & 10 deletions b/‎docs/contributing/pages/components.mdx‎
Lines changed: 25 additions & 10 deletions
@@ -28,18 +28,29 @@ This file is `options.mdx`. It explains all the configuration options.
 To develop content for this file:
 
 1. Create the `configuration/config-intro/` statement, which covers how options can be set.
-2. For individual options that the guide does NOT support, add the name of the guide to the `ConfigKey` statement for that option. This will prevent that option from displaying for this SDK. For example:
+2. Write option names in the platform's native casing:
+   - **camelCase** for JavaScript/TypeScript, Java, Kotlin, Dart/Flutter, Android, Apple
+   - **PascalCase** for .NET, Unity, Unreal, PowerShell
+   - **snake_case** for Python, PHP, Ruby, Go, Rust, Elixir, Native (C/C++), Godot
+3. For individual options that certain platform categories do NOT support, use `categoryNotSupported` in the `SdkOption` statement. For example:
 
-   `<ConfigKey name="debug" notSupported={["javascript.react"]}>`
+   `<SdkOption name="debug" type="boolean" defaultValue="false" categoryNotSupported={["browser"]}>`
 
-   Alternately, for individual options that the guide DOES support, add the name of the guide to `ConfigKey` statement for that option, which ensures the option displays. For example:
+   Alternately, for individual options that only certain platform categories DO support, use `categorySupported` in the `SdkOption` statement. For example:
 
-   `<ConfigKey name="send-default-pii" supported={["javascript.electron", "javascript.ember"]}>`
+   `<SdkOption name="sendDefaultPii" type="boolean" defaultValue="false" categorySupported={["server", "serverless"]}>`
 
-3. For a grouping of options that the guide DOES support, add the name of the guide to the `PlatformSection` statement for those options, which ensures the option displays. For example:
+4. For guide-specific filtering (less common), use `PlatformSection` to wrap options that only apply to specific guides. For example:
 
    `<PlatformSection supported={["javascript.react"]}>`
 
+5. Add metadata where applicable:
+   - `type` - the data type (e.g., `boolean`, `string`, `number`, `object`)
+   - `defaultValue` - the default value
+   - `envVar` - associated environment variable (if any)
+   - `availableSince` - SDK version when introduced (if known)
+6. Add a `<TableOfContents ignoreIds={["core-options"]} />` at the top of the available options section for better navigation.
+
 ### Releases & Health
 
 This file is `releases.mdx`. It explains how to configure the SDK to tell Sentry about releases. Provide a code sample for this SDK to set a release, then add the code sample to this directory:
 
@@ -255,30 +255,45 @@ function foo() {
 ```
 ````
 
-## ConfigKey
+## SdkOption
 
-Render a heading with a configuration key in the correctly cased format for a given platform.
+Render an SDK configuration option heading with a metadata table. Option names should be written in the platform's native casing (camelCase, PascalCase, or snake_case).
 
 <Alert>
 
-If content is specified, it will automatically hide the content when the given `platform` is not selected in context.
+If `categorySupported` is specified, it will automatically hide the option when the platform does not support it.
 
 </Alert>
 
 ```markdown {tabTitle:Example}
-<ConfigKey name="send-default-pii" notSupported={["javascript"]}>
+<SdkOption 
+  name="sampleRate" 
+  type="number" 
+  defaultValue="1.0"
+  envVar="SENTRY_SAMPLE_RATE">
 
-Description of send-default-pii
+The sample rate for error events, as a number between `0.0` and `1.0` (inclusive).
 
-</ConfigKey>
+</SdkOption>
 ```
 
 Attributes:
 
-- `name` (string)
-- `platform` (string) - defaults to the `platform` value from the page context
-- `supported` (string[])
-- `notSupported` (string[])
+- `name` (string) - **required** - the option name in the platform's native casing
+- `type` (string) - optional - data type (e.g., `boolean`, `string`, `number`)
+- `defaultValue` (string) - optional - default value for the option
+- `envVar` (string) - optional - associated environment variable
+- `availableSince` (string) - optional - SDK version when the option was introduced
+- `categorySupported` (string[]) - optional - platform categories that support this option (e.g., `["browser", "server"]`)
+- `categoryNotSupported` (string[]) - optional - platform categories that don't support this option
+
+**Platform-native casing guidelines:**
+
+- **camelCase**: JavaScript/TypeScript (all frameworks), Java, Kotlin, Dart/Flutter, Android, Apple (iOS/macOS)
+- **PascalCase**: .NET (all frameworks), Unity, Unreal, PowerShell
+- **snake_case**: Python, PHP, Ruby, Go, Rust, Elixir, Native (C/C++), Godot
+
+Use the `<PlatformIdentifier name="option-name" />` component to render option names with correct casing based on the platform's `case_style` setting.
 
 ## PageGrid