rework nav for ruby (#15591)

coolguyzone · Alex Krawiec · philprime · commit 281afa8f7b35 · 2025-11-28T09:32:39.000+01:00
## DESCRIBE YOUR PR See changes on https://sentry-docs-git-feat-ruby-docs-nav-standardized.sentry.dev/platforms/ruby/ and all ruby platforms Sidebar Sections Added 'Features' section with organized feature pages Added 'Configuration' section Both sections now have proper headers and grouping Features Section (sidebar_section: features) Order: Capturing Errors → Logs → Tracing → Profiling → Crons Renamed 'Usage' to 'Capturing Errors' (matching JS) Added 'new' tag to Logs Added 'beta' tag to Metrics Reordered all features for consistency Configuration Section (sidebar_section: configuration) Order: Enriching Events → Extended Configuration → Integrations → Data Management → Security Policy Reporting → Migration Guide → Troubleshooting Follows the pattern established in #15440 <img width="321" height="744" alt="Screenshot 2025-11-21 at 2 48 07 PM" src="https://github.com/user-attachments/assets/238cc32d-0a70-4121-bb96-1aebb167dd53" /> ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.):  - [ ] Other deadline:  - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE  Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) --------- Co-authored-by: Alex Krawiec <alex.krawiec@R7J1Y747QQ.local>
diff --git a/docs/platforms/ruby/common/configuration/environments.mdx b/docs/platforms/ruby/common/configuration/environments.mdx
@@ -1,7 +1,8 @@
 ---
 title: Environments
-sidebar_order: 30
 description: "Learn how to configure your SDK to tell Sentry about your environments."
+sidebar_order: 30
+sidebar_section: configuration
 ---
 
 Environments tell you where an error occurred, whether that's in your production system, your staging server, or elsewhere.
diff --git a/docs/platforms/ruby/common/configuration/filtering.mdx b/docs/platforms/ruby/common/configuration/filtering.mdx
@@ -1,7 +1,8 @@
 ---
 title: Filtering
-sidebar_order: 60
 description: "Learn more about how to configure your SDK to filter events reported to Sentry."
+sidebar_order: 60
+sidebar_section: configuration
 ---
 
 When you add Sentry to your app, you get a lot of valuable information about errors and performance. And lots of information is good -- as long as it's the right information, at a reasonable volume.
diff --git a/docs/platforms/ruby/common/configuration/index.mdx b/docs/platforms/ruby/common/configuration/index.mdx
@@ -1,7 +1,9 @@
 ---
-title: Configuration
-description: "Additional configuration options for the SDK."
-sidebar_order: 5
+title: Extended Configuration
+sidebar_title: Extended Configuration
+description: "Learn about additional configuration options for the Ruby SDK."
+sidebar_order: 13
+sidebar_section: configuration
 ---
 
 <PageGrid />
diff --git a/docs/platforms/ruby/common/configuration/integration_options.mdx b/docs/platforms/ruby/common/configuration/integration_options.mdx
@@ -1,7 +1,8 @@
 ---
 title: Integration Options
-sidebar_order: 200
 description: "Learn about configuring integrations."
+sidebar_order: 200
+sidebar_section: configuration
 ---
 
 ## sentry-rails
diff --git a/docs/platforms/ruby/common/configuration/options.mdx b/docs/platforms/ruby/common/configuration/options.mdx
@@ -2,6 +2,7 @@
 title: Options
 description: "Learn more about how the SDK can be configured via options. These are being passed to the init function and therefore set when the SDK is first initialized."
 sidebar_order: 1
+sidebar_section: configuration
 ---
 
 <PlatformContent includePath="configuration/config-intro" />
diff --git a/docs/platforms/ruby/common/configuration/releases.mdx b/docs/platforms/ruby/common/configuration/releases.mdx
@@ -1,7 +1,8 @@
 ---
 title: Releases & Health
-sidebar_order: 40
 description: "Learn how to configure your SDK to tell Sentry about your releases."
+sidebar_order: 40
+sidebar_section: configuration
 ---
 
 A release is a version of your code that is deployed to an <PlatformLink to="/configuration/environments/">environment</PlatformLink>. When you give Sentry information about your releases, you can:
diff --git a/docs/platforms/ruby/common/configuration/sampling.mdx b/docs/platforms/ruby/common/configuration/sampling.mdx
@@ -1,6 +1,7 @@
 ---
 title: Sampling
 description: "Learn how to configure the volume of error and transaction events sent to Sentry."
+sidebar_section: configuration
 sidebar_order: 50
 ---
 
diff --git a/docs/platforms/ruby/common/crons/index.mdx b/docs/platforms/ruby/common/crons/index.mdx
@@ -2,7 +2,8 @@
 title: Set Up Crons
 sidebar_title: Crons
 description: "Sentry Crons allows you to monitor the uptime and performance of any scheduled, recurring job in your application."
-sidebar_order: 5750
+sidebar_order: 9
+sidebar_section: features
 ---
 
 Once implemented, it'll allow you to get alerts and metrics to help you solve errors, detect timeouts, and prevent disruptions to your service.
diff --git a/docs/platforms/ruby/common/data-management/index.mdx b/docs/platforms/ruby/common/data-management/index.mdx
@@ -1,7 +1,8 @@
 ---
 title: Data Management
-sidebar_order: 2500
 description: Manage your events by pre-filtering, scrubbing sensitive information, and forwarding them to other systems.
+sidebar_order: 15
+sidebar_section: configuration
 ---
 
 <PageGrid />
diff --git a/docs/platforms/ruby/common/enriching-events/index.mdx b/docs/platforms/ruby/common/enriching-events/index.mdx
@@ -1,7 +1,8 @@
 ---
 title: Enriching Events
 description: Enrich events with additional context to make debugging simpler.
-sidebar_order: 2300
+sidebar_order: 12
+sidebar_section: configuration
 ---
 
 <PageGrid />
diff --git a/docs/platforms/ruby/common/integrations/index.mdx b/docs/platforms/ruby/common/integrations/index.mdx
@@ -1,7 +1,8 @@
 ---
 title: Integrations
 description: "Sentry provides additional integrations designed to change configuration or add instrumentation to your application."
-sidebar_order: 40
+sidebar_order: 14
+sidebar_section: configuration
 ---
 
 The Sentry SDK uses integrations to hook into the functionality of popular frameworks and libraries to automatically instrument your application and give you the best data out of the box.
diff --git a/docs/platforms/ruby/common/migration.mdx b/docs/platforms/ruby/common/migration.mdx
@@ -1,7 +1,8 @@
 ---
 title: Migration Guide
-sidebar_order: 8000
 description: "Learn about how to migrate from the deprecated sentry-raven SDK."
+sidebar_order: 17
+sidebar_section: configuration
 ---
 
 ## Table of Content
diff --git a/docs/platforms/ruby/common/profiling/index.mdx b/docs/platforms/ruby/common/profiling/index.mdx
@@ -2,7 +2,8 @@
 title: Set Up Profiling
 sidebar_title: Profiling
 description: "Learn how to enable profiling in your app if it is not already set up."
-sidebar_order: 5000
+sidebar_order: 8
+sidebar_section: features
 ---
 
 <PlatformContent includePath="profiling/index/preface" />
diff --git a/docs/platforms/ruby/common/security-policy-reporting/index.mdx b/docs/platforms/ruby/common/security-policy-reporting/index.mdx
@@ -1,8 +1,9 @@
 ---
 title: Set Up Security Policy Reporting
 sidebar_title: Security Policy Reporting
-sidebar_order: 7500
 description: "Learn how Sentry can help manage Content-Security-Policy violations and reports here."
+sidebar_order: 16
+sidebar_section: configuration
 ---
 
 <Include name="platforms/security-policy-reporting/content.mdx" />
diff --git a/docs/platforms/ruby/common/tracing/index.mdx b/docs/platforms/ruby/common/tracing/index.mdx
@@ -2,7 +2,8 @@
 title: Set Up Tracing
 sidebar_title: Tracing
 description: "Learn how to enable tracing in your app and discover valuable performance insights of your application."
-sidebar_order: 4000
+sidebar_order: 6
+sidebar_section: features
 ---
 
 With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
diff --git a/docs/platforms/ruby/common/troubleshooting.mdx b/docs/platforms/ruby/common/troubleshooting.mdx
@@ -1,7 +1,8 @@
 ---
 title: Troubleshooting
 description: "Learn how to troubleshoot your SDK setup."
-sidebar_order: 9000
+sidebar_order: 18
+sidebar_section: configuration
 ---
 
 ## General
diff --git a/docs/platforms/ruby/common/usage/index.mdx b/docs/platforms/ruby/common/usage/index.mdx
@@ -1,7 +1,9 @@
 ---
-title: Usage
+title: Capturing Errors
+sidebar_title: Capturing Errors
 description: "Use the SDK to manually capture errors and other events."
-sidebar_order: 10
+sidebar_order: 3
+sidebar_section: features
 ---
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
diff --git a/docs/platforms/ruby/common/user-feedback/index.mdx b/docs/platforms/ruby/common/user-feedback/index.mdx
@@ -2,7 +2,8 @@
 title: Set Up User Feedback
 sidebar_title: User Feedback
 description: "Learn more about collecting user feedback when an event occurs. Sentry pairs the feedback with the original event, giving you additional insight into issues."
-sidebar_order: 6000
+sidebar_order: 10
+sidebar_section: features
 ---
 
 When a user experiences an error, Sentry provides the ability to collect additional feedback. You can collect feedback according to the method supported by the SDK.
diff --git a/docs/platforms/ruby/guides/rails/logs/index.mdx b/docs/platforms/ruby/guides/rails/logs/index.mdx
@@ -2,7 +2,9 @@
 title: Set Up Logs
 sidebar_title: Logs
 description: "Structured logs allow you to send, view and query logs sent from your Rails applications within Sentry."
-sidebar_order: 5600
+sidebar_order: 4
+sidebar_section: features
+new: true
 ---
 
 With Sentry Structured Logs, you can send text-based log information from your Rails applications to Sentry. Once in Sentry, these logs can be viewed alongside relevant errors, searched by text-string, or searched using their individual attributes.
diff --git a/docs/platforms/ruby/logs/index.mdx b/docs/platforms/ruby/logs/index.mdx
@@ -2,7 +2,9 @@
 title: Set Up Logs
 sidebar_title: Logs
 description: "Structured logs allow you to send, view and query logs sent from your applications within Sentry."
-sidebar_order: 5755
+sidebar_order: 4
+sidebar_section: features
+new: true
 ---
 
 With Sentry Structured Logs, you can send text-based log information from your applications to Sentry. Once in Sentry, these logs can be viewed alongside relevant errors, searched by text-string, or searched using their individual attributes.
