Revise sidebar ordering and cleanup files that were duplicated

markstory · markstory · commit 14fe58db05cf · 2024-10-18T17:31:30.000-07:00
diff --git a/develop-docs/application/config.mdx b/develop-docs/application/config.mdx
@@ -1,5 +1,6 @@
 ---
 title: Configuration
+sidebar_order: 60
 ---
 
 This document describes configuration available to the Sentry server itself.
diff --git a/develop-docs/backend/ab-testing/index.mdx b/develop-docs/backend/ab-testing/index.mdx
@@ -1,5 +1,6 @@
 ---
 title: A/B Tests with Amplitude
+sidebar_order: 190
 ---
 
 ## Why AB testing?
diff --git a/develop-docs/backend/api/design.mdx b/develop-docs/backend/api/design.mdx
@@ -2,6 +2,7 @@
 title: Designing a New API
 sidebar_order: 2
 ---
+
 [Django REST framework](https://www.django-rest-framework.org/)(DRF) is a powerful and flexible toolkit
 for building Web APIs. Sentry APIs are built using DRF. Here are some considerations to make when designing APIs at Sentry.
 
diff --git a/develop-docs/backend/api/index.mdx b/develop-docs/backend/api/index.mdx
@@ -1,5 +1,6 @@
 ---
 title: API Development
+sidebar_order: 1
 ---
 
 As a developer-facing company it's critical for us to have simple, intuitive, and consistent APIs that our users can call from their dev environment to accomplish key tasks without going to the UI. If you're creating or editing an endpoint, this doc will help you achieve Sentry standards.
diff --git a/develop-docs/backend/api/serializers.mdx b/develop-docs/backend/api/serializers.mdx
@@ -1,5 +1,6 @@
 ---
 title: Serializers
+sidebar_order: 10
 ---
 
 Serializers are used to take complex python models and translate them into json. Serializers can also be used to deserialize json back to the python models after validating the incoming data.
diff --git a/develop-docs/backend/buffers.mdx b/develop-docs/backend/buffers.mdx
@@ -1,5 +1,6 @@
 ---
 title: Write Buffers
+sidebar_order: 170
 ---
 
 Sentry manages database row contention by buffering writes and flushing bulk changes to the database over a period of time. This is extremely helpful if you have high concurrency, especially if they’re frequently the same event.
diff --git a/develop-docs/backend/development-server.mdx b/develop-docs/backend/development-server.mdx
@@ -1,5 +1,6 @@
 ---
 title: Backend Development Server
+sidebar_order: 10
 ---
 
 (*see also: [Frontend Development Server](/frontend/development-server/)*)
diff --git a/develop-docs/backend/digests.mdx b/develop-docs/backend/digests.mdx
@@ -1,5 +1,6 @@
 ---
 title: Notification Digests
+sidebar_order: 140
 ---
 
 Sentry provides a service that will collect notifications as they occur and schedule them for delivery as aggregated “digest” notifications.
diff --git a/develop-docs/backend/email.mdx b/develop-docs/backend/email.mdx
@@ -1,5 +1,6 @@
 ---
 title: Email
+sidebar_order: 110
 ---
 
 Sentry provides support for both outbound, and incoming email.
diff --git a/develop-docs/backend/feature-flags/index.mdx b/develop-docs/backend/feature-flags/index.mdx
@@ -1,5 +1,6 @@
 ---
 title: 'Feature Flags'
+sidebar_order: 40
 ---
 
 Feature flags are declared in Sentry's codebase (look for `SENTRY_FEATURES` in
diff --git a/develop-docs/backend/grouping.mdx b/develop-docs/backend/grouping.mdx
@@ -1,5 +1,6 @@
 ---
 title: Grouping
+sidebar_order: 60
 ---
 
 Sentry has an extensive grouping system ([public documentation](https://docs.sentry.io/product/sentry-basics/grouping-and-fingerprints/))
diff --git a/develop-docs/backend/issue-platform-detectors/index.mdx b/develop-docs/backend/issue-platform-detectors/index.mdx
@@ -1,5 +1,6 @@
 ---
 title: Issue Platform - Writing Detectors
+sidebar_order: 90
 ---
 
 Issue detectors identify application issues by examining one or more datasets collected by Sentry, and report detected issue occurrences via the <Link to="/issue-platform/">Issue Platform</Link>. Detectors must fingerprint issues accurately and provide actionable information to developers.
diff --git a/develop-docs/backend/issue-platform/index.mdx b/develop-docs/backend/issue-platform/index.mdx
@@ -1,5 +1,6 @@
 ---
 title: Issue Platform
+sidebar_order: 80
 ---
 
 The Issue Platform allows developers to create new issue types from arbitrary data sources. If you have data about something that you want to track via an issue, you can build it on the issue platform. For example, building profiling issues on the issue platform allowed us to turn things like “JSON decoding on the main thread” into their own issue types.
diff --git a/develop-docs/backend/kafka.mdx b/develop-docs/backend/kafka.mdx
@@ -1,5 +1,6 @@
 ---
 title: Kafka consumers
+sidebar_order: 110
 ---
 
 ## Creating a new consumer in Sentry
diff --git a/develop-docs/backend/metrics.mdx b/develop-docs/backend/metrics.mdx
@@ -1,5 +1,6 @@
 ---
 title: Metrics
+sidebar_order: 120
 ---
 
 Sentry provides an abstraction called ‘metrics’ which is used for internal monitoring, generally timings and various counters.
diff --git a/develop-docs/backend/nodestore.mdx b/develop-docs/backend/nodestore.mdx
@@ -1,5 +1,6 @@
 ---
 title: Node Storage
+sidebar_order: 130
 ---
 
 Sentry provides an abstraction called ‘nodestore’ which is used for storing key/value blobs.
diff --git a/develop-docs/backend/options/index.mdx b/develop-docs/backend/options/index.mdx
@@ -1,5 +1,6 @@
 ---
 title: Options
+sidebar_order: 50
 ---
 
 Options are a way to store generic system-wide configuration. They serve a similar purpose to configuration files, but they are backed by a database, so it's possible to change them at runtime without a deploy. Options are stored in the database and cached, so they are performant and reliable. This makes options well-suited for rates, quotas, and limits.
diff --git a/develop-docs/backend/outboxes.mdx b/develop-docs/backend/outboxes.mdx
@@ -1,5 +1,6 @@
 ---
 title: Outboxes
+sidebar_order: 70
 ---
 
 Outboxes are database backed deferred units of work that drive a large portion of our system's eventual consistency workflows. They were designed with a couple of key features in mind:
diff --git a/develop-docs/backend/pii/index.mdx b/develop-docs/backend/pii/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: PII and Data Scrubbing
 description: This document describes a configuration format that we would like to hide from the user eventually. The only reason this page still exists is, because currently Relay accepts this format in alternative to regular data scrubbing settings.
-sidebar_order: 40
+sidebar_order: 170
 ---
 
 The following document explores the syntax and semantics of the configuration
diff --git a/develop-docs/backend/python-dependencies.mdx b/develop-docs/backend/python-dependencies.mdx
@@ -1,6 +1,6 @@
 ---
 title: Python Dependencies
-sidebar_order: 9000
+sidebar_order: 20
 ---
 
 Unlike our frontend JavaScript story, where we're generally very happy pulling in dependencies, we're much more conservative on
diff --git a/develop-docs/backend/queue.mdx b/develop-docs/backend/queue.mdx
@@ -1,5 +1,6 @@
 ---
 title: Asynchronous Workers
+sidebar_order: 100
 ---
 
 Sentry comes with a built-in queue to process tasks in a more asynchronous fashion. For example when an event comes in instead of writing it to the database immediately, it sends a job to the queue so that the request can be returned right away, and the background workers handle actually saving that data.
diff --git a/develop-docs/backend/quotas.mdx b/develop-docs/backend/quotas.mdx
@@ -1,5 +1,6 @@
 ---
 title: Quotas
+sidebar_order: 150
 ---
 
 With the way Sentry works you may find yourself in a situation where you’ll see too much inbound traffic without a good way to drop excess messages. There’s a few solutions to this, and you’ll likely want to employ them all if you are faced with this problem.
diff --git a/develop-docs/backend/translations.mdx b/develop-docs/backend/translations.mdx
@@ -1,6 +1,6 @@
 ---
 title: Translations
-sidebar_order: 90
+sidebar_order: 180
 ---
 
 We use [**Transifex**](https://www.transifex.com/getsentry/sentry) to translate Sentry.
diff --git a/develop-docs/backend/tsdb.mdx b/develop-docs/backend/tsdb.mdx
@@ -1,5 +1,6 @@
 ---
 title: Time-series Storage
+sidebar_order: 160
 ---
 
 Sentry provides a service to store time-series data. Primarily this is used to display aggregate information for events and projects, as well as calculating (in real-time) the rates of events.
diff --git a/develop-docs/development/testing.mdx b/develop-docs/development/testing.mdx
@@ -1,7 +1,7 @@
 ---
 title: Testing Tips
 description: We run several kinds of tests at Sentry as part of our CI process. This section aims to document some of the sentry specific helpers and give guidelines on what kinds of tests you should consider including when building new features.
-sidebar_order: 20
+sidebar_order: 50
 ---
 
 ## Getting Setup
@@ -146,10 +146,10 @@ To create test models, modify the `Meta` of your test model, and assign the mode
 ```python
 class MyTestModel(models.Model):
     ... # some fields
-    
+
     class Meta:
         app_label = "fixtures"
-        
+
 ```
 
 ### External Services
