getsentry · antonpirker · Nov 16, 2024 · Nov 7, 2024 · Nov 7, 2024 · Nov 8, 2024
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -13,7 +13,7 @@ repos:
       - id: detect-private-key
         exclude: |
           (?x)^(
-              develop-docs/application/config.mdx|
+              develop-docs/architecture/config.mdx|
               develop-docs/integrations/github.mdx|
               develop-docs/self-hosted/sso.mdx
           )$

diff --git a/develop-docs/backend/api/basics.mdx → develop-docs/api-server/api/basics.mdx b/develop-docs/backend/api/basics.mdx → develop-docs/api-server/api/basics.mdx
diff --git a/develop-docs/backend/api/checklist.mdx → develop-docs/api-server/api/checklist.mdx b/develop-docs/backend/api/checklist.mdx → develop-docs/api-server/api/checklist.mdx
diff --git a/develop-docs/backend/api/concepts.mdx → develop-docs/api-server/api/concepts.mdx b/develop-docs/backend/api/concepts.mdx → develop-docs/api-server/api/concepts.mdx
diff --git a/develop-docs/backend/api/design.mdx → develop-docs/api-server/api/design.mdx b/develop-docs/backend/api/design.mdx → develop-docs/api-server/api/design.mdx
diff --git a/develop-docs/backend/api/index.mdx → develop-docs/api-server/api/index.mdx b/develop-docs/backend/api/index.mdx → develop-docs/api-server/api/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: API Development
-sidebar_order: 1
+sidebar_order: 20
 ---
 
 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/public.mdx → develop-docs/api-server/api/public.mdx b/develop-docs/backend/api/public.mdx → develop-docs/api-server/api/public.mdx
diff --git a/develop-docs/backend/api/serializers.mdx → develop-docs/api-server/api/serializers.mdx b/develop-docs/backend/api/serializers.mdx → develop-docs/api-server/api/serializers.mdx
diff --git a/develop-docs/backend/ab-testing/index.mdx → .../application-domains/ab-testing/index.mdx b/develop-docs/backend/ab-testing/index.mdx → .../application-domains/ab-testing/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: A/B Tests with Amplitude
-sidebar_order: 190
+sidebar_order: 50
 ---
 
 ## Why AB testing?

diff --git a/develop-docs/backend/queue.mdx → ...plication-domains/aynchronous-workers.mdx b/develop-docs/backend/queue.mdx → ...plication-domains/aynchronous-workers.mdx
@@ -1,6 +1,6 @@
 ---
 title: Asynchronous Workers
-sidebar_order: 100
+sidebar_order: 70
 ---
 
 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/...ns/img/post-deploy-pipeline-materials.png → ...ns/img/post-deploy-pipeline-materials.png b/...ns/img/post-deploy-pipeline-materials.png → ...ns/img/post-deploy-pipeline-materials.png
diff --git a/...rations/img/post-deploy-pipeline-tile.png → ...rations/img/post-deploy-pipeline-tile.png b/...rations/img/post-deploy-pipeline-tile.png → ...rations/img/post-deploy-pipeline-tile.png
diff --git a/...ns/img/post-deploy-pipeline-variables.png → ...ns/img/post-deploy-pipeline-variables.png b/...ns/img/post-deploy-pipeline-variables.png → ...ns/img/post-deploy-pipeline-variables.png
diff --git a/...ocs/backend/database-migrations/index.mdx → ...ion-domains/database-migrations/index.mdx b/...ocs/backend/database-migrations/index.mdx → ...ion-domains/database-migrations/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: Database Migrations
-sidebar_order: 30
+sidebar_order: 20
 ---
 
 Django migrations are how we handle changes to the database in Sentry.

diff --git a/develop-docs/backend/digests.mdx → ...pi-server/application-domains/digests.mdx b/develop-docs/backend/digests.mdx → ...pi-server/application-domains/digests.mdx
@@ -1,6 +1,6 @@
 ---
 title: Notification Digests
-sidebar_order: 140
+sidebar_order: 130
 ---
 
 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 → .../api-server/application-domains/email.mdx b/develop-docs/backend/email.mdx → .../api-server/application-domains/email.mdx
@@ -1,6 +1,6 @@
 ---
 title: Email
-sidebar_order: 110
+sidebar_order: 150
 ---
 
 Sentry provides support for both outbound, and incoming email.

diff --git a/...p-docs/backend/feature-flags/flagpole.mdx → ...cation-domains/feature-flags/flagpole.mdx b/...p-docs/backend/feature-flags/flagpole.mdx → ...cation-domains/feature-flags/flagpole.mdx
diff --git a/develop-docs/backend/feature-flags/index.mdx → ...plication-domains/feature-flags/index.mdx b/develop-docs/backend/feature-flags/index.mdx → ...plication-domains/feature-flags/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Feature Flags'
-sidebar_order: 40
+sidebar_order: 30
 ---
 
 Feature flags are declared in Sentry's codebase (look for `SENTRY_FEATURES` in

diff --git a/...feature-flags/options-backed-features.mdx → ...feature-flags/options-backed-features.mdx b/...feature-flags/options-backed-features.mdx → ...feature-flags/options-backed-features.mdx
diff --git a/develop-docs/backend/grouping.mdx → ...i-server/application-domains/grouping.mdx b/develop-docs/backend/grouping.mdx → ...i-server/application-domains/grouping.mdx
@@ -1,6 +1,6 @@
 ---
 title: Grouping
-sidebar_order: 60
+sidebar_order: 100
 ---
 
 Sentry has an extensive grouping system ([public documentation](https://docs.sentry.io/product/sentry-basics/grouping-and-fingerprints/))

diff --git a/develop-docs/api-server/application-domains/index.mdx b/develop-docs/api-server/application-domains/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Application Domains
+sidebar_order: 40
+---
+
+<PageGrid />
diff --git a/develop-docs/backend/kafka.mdx → .../api-server/application-domains/kafka.mdx b/develop-docs/backend/kafka.mdx → .../api-server/application-domains/kafka.mdx
@@ -1,6 +1,6 @@
 ---
 title: Kafka consumers
-sidebar_order: 110
+sidebar_order: 60
 ---
 
 ## Creating a new consumer in Sentry

diff --git a/develop-docs/backend/metrics.mdx → ...pi-server/application-domains/metrics.mdx b/develop-docs/backend/metrics.mdx → ...pi-server/application-domains/metrics.mdx
@@ -1,6 +1,6 @@
 ---
 title: Metrics
-sidebar_order: 120
+sidebar_order: 180
 ---
 
 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 → ...-server/application-domains/nodestore.mdx b/develop-docs/backend/nodestore.mdx → ...-server/application-domains/nodestore.mdx
@@ -1,6 +1,6 @@
 ---
 title: Node Storage
-sidebar_order: 130
+sidebar_order: 120
 ---
 
 Sentry provides an abstraction called ‘nodestore’ which is used for storing key/value blobs.

diff --git a/develop-docs/backend/options/index.mdx → ...pi-server/application-domains/options.mdx b/develop-docs/backend/options/index.mdx → ...pi-server/application-domains/options.mdx
@@ -1,6 +1,6 @@
 ---
 title: Options
-sidebar_order: 50
+sidebar_order: 10
 ---
 
 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 → ...i-server/application-domains/outboxes.mdx b/develop-docs/backend/outboxes.mdx → ...i-server/application-domains/outboxes.mdx
@@ -1,6 +1,6 @@
 ---
 title: Outboxes
-sidebar_order: 70
+sidebar_order: 110
 ---
 
 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 → ...-server/application-domains/pii/index.mdx b/develop-docs/backend/pii/index.mdx → ...-server/application-domains/pii/index.mdx
diff --git a/develop-docs/backend/pii/methods.mdx → ...erver/application-domains/pii/methods.mdx b/develop-docs/backend/pii/methods.mdx → ...erver/application-domains/pii/methods.mdx
diff --git a/develop-docs/backend/pii/selectors.mdx → ...ver/application-domains/pii/selectors.mdx b/develop-docs/backend/pii/selectors.mdx → ...ver/application-domains/pii/selectors.mdx
diff --git a/develop-docs/backend/pii/types.mdx → ...-server/application-domains/pii/types.mdx b/develop-docs/backend/pii/types.mdx → ...-server/application-domains/pii/types.mdx
diff --git a/develop-docs/backend/quotas.mdx → ...api-server/application-domains/quotas.mdx b/develop-docs/backend/quotas.mdx → ...api-server/application-domains/quotas.mdx
@@ -1,6 +1,6 @@
 ---
 title: Quotas
-sidebar_order: 150
+sidebar_order: 160
 ---
 
 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/.../backend/transaction-clustering/index.mdx → ...-domains/transaction-clustering/index.mdx b/.../backend/transaction-clustering/index.mdx → ...-domains/transaction-clustering/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: Clustering URL Transactions
-sidebar_order: 60
+sidebar_order: 90
 ---
 
 Sentry attempts to scrub high-cardinality identifiers from URL transactions

diff --git a/...backend/transaction-clustering/merged.png → ...domains/transaction-clustering/merged.png b/...backend/transaction-clustering/merged.png → ...domains/transaction-clustering/merged.png
diff --git a/...lustering/transaction-clustering-arch.png → ...lustering/transaction-clustering-arch.png b/...lustering/transaction-clustering-arch.png → ...lustering/transaction-clustering-arch.png
diff --git a/...lustering/transaction-clustering-arch.svg → ...lustering/transaction-clustering-arch.svg b/...lustering/transaction-clustering-arch.svg → ...lustering/transaction-clustering-arch.svg
diff --git a/...s/backend/transaction-clustering/tree.png → ...n-domains/transaction-clustering/tree.png b/...s/backend/transaction-clustering/tree.png → ...n-domains/transaction-clustering/tree.png
diff --git a/...ransaction-clustering/unparameterized.png → ...ransaction-clustering/unparameterized.png b/...ransaction-clustering/unparameterized.png → ...ransaction-clustering/unparameterized.png
diff --git a/develop-docs/backend/translations.mdx → ...rver/application-domains/translations.mdx b/develop-docs/backend/translations.mdx → ...rver/application-domains/translations.mdx
@@ -1,6 +1,6 @@
 ---
 title: Translations
-sidebar_order: 180
+sidebar_order: 40
 ---
 
 We use [**Transifex**](https://www.transifex.com/getsentry/sentry) to translate Sentry.

diff --git a/develop-docs/backend/tsdb.mdx → ...s/api-server/application-domains/tsdb.mdx b/develop-docs/backend/tsdb.mdx → ...s/api-server/application-domains/tsdb.mdx
@@ -1,6 +1,6 @@
 ---
 title: Time-series Storage
-sidebar_order: 160
+sidebar_order: 140
 ---
 
 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/backend/buffers.mdx → ...ver/application-domains/write-buffers.mdx b/develop-docs/backend/buffers.mdx → ...ver/application-domains/write-buffers.mdx
@@ -1,6 +1,6 @@
 ---
 title: Write Buffers
-sidebar_order: 170
+sidebar_order: 80
 ---
 
 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/api-server/index.mdx b/develop-docs/api-server/index.mdx
@@ -0,0 +1,8 @@
+---
+title: API Server
+sidebar_order: 50
+---
+
+The monolith powering Sentry. The backend of our application.
+
+<PageGrid />
diff --git a/...nd/issue-platform/img/issueProperties.jpg → ...er/issue-platform/img/issueProperties.jpg b/...nd/issue-platform/img/issueProperties.jpg → ...er/issue-platform/img/issueProperties.jpg
diff --git a/...lop-docs/backend/issue-platform/index.mdx → ...-docs/api-server/issue-platform/index.mdx b/...lop-docs/backend/issue-platform/index.mdx → ...-docs/api-server/issue-platform/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: Issue Platform
-sidebar_order: 80
+sidebar_order: 30
 ---
 
 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/...g/issuePlatformAdminDetectionSettings.png → ...g/issuePlatformAdminDetectionSettings.png b/...g/issuePlatformAdminDetectionSettings.png → ...g/issuePlatformAdminDetectionSettings.png
diff --git a/...issuePlatformCustomerDetectorSettings.png → ...issuePlatformCustomerDetectorSettings.png b/...issuePlatformCustomerDetectorSettings.png → ...issuePlatformCustomerDetectorSettings.png
diff --git a/...PlatformDbonMainThreadDetectorSetting.png → ...PlatformDbonMainThreadDetectorSetting.png b/...PlatformDbonMainThreadDetectorSetting.png → ...PlatformDbonMainThreadDetectorSetting.png
diff --git a/...ors/img/issuePlatformFingerprinting01.png → ...ors/img/issuePlatformFingerprinting01.png b/...ors/img/issuePlatformFingerprinting01.png → ...ors/img/issuePlatformFingerprinting01.png
diff --git a/...ors/img/issuePlatformFingerprinting02.png → ...ors/img/issuePlatformFingerprinting02.png b/...ors/img/issuePlatformFingerprinting02.png → ...ors/img/issuePlatformFingerprinting02.png
diff --git a/...ors/img/issuePlatformFingerprinting03.png → ...ors/img/issuePlatformFingerprinting03.png b/...ors/img/issuePlatformFingerprinting03.png → ...ors/img/issuePlatformFingerprinting03.png
diff --git a/...ackend/issue-platform-detectors/index.mdx → ...ssue-platform/writing-detectors/index.mdx b/...ackend/issue-platform-detectors/index.mdx → ...ssue-platform/writing-detectors/index.mdx
@@ -1,6 +1,6 @@
 ---
-title: Issue Platform - Writing Detectors
-sidebar_order: 90
+title: Writing Detectors
+sidebar_order: 10
 ---
 
 Issue detectors identify application issues by examining one or more datasets collected by Sentry, and report detected issue occurrences via the <Link to="/backend/issue-platform/">Issue Platform</Link>. Detectors must fingerprint issues accurately and provide actionable information to developers.

diff --git a/develop-docs/application/config.mdx → develop-docs/architecture/config.mdx b/develop-docs/application/config.mdx → develop-docs/architecture/config.mdx
@@ -1,6 +1,6 @@
 ---
 title: Configuration
-sidebar_order: 60
+sidebar_order: 30
 ---
 
 This document describes configuration available to the Sentry server itself.

diff --git a/...ication/dynamic-sampling/architecture.mdx → ...tecture/dynamic-sampling/architecture.mdx b/...ication/dynamic-sampling/architecture.mdx → ...tecture/dynamic-sampling/architecture.mdx
diff --git a/.../dynamic-sampling/fidelity-and-biases.mdx → .../dynamic-sampling/fidelity-and-biases.mdx b/.../dynamic-sampling/fidelity-and-biases.mdx → .../dynamic-sampling/fidelity-and-biases.mdx
diff --git a/.../dynamic-sampling/images/architecture.png → .../dynamic-sampling/images/architecture.png b/.../dynamic-sampling/images/architecture.png → .../dynamic-sampling/images/architecture.png
diff --git a/...tion/dynamic-sampling/images/biasesUI.png → ...ture/dynamic-sampling/images/biasesUI.png b/...tion/dynamic-sampling/images/biasesUI.png → ...ture/dynamic-sampling/images/biasesUI.png
diff --git a/...n/dynamic-sampling/images/celeryTasks.png → ...e/dynamic-sampling/images/celeryTasks.png b/...n/dynamic-sampling/images/celeryTasks.png → ...e/dynamic-sampling/images/celeryTasks.png
diff --git a/...pling/images/clientAndDynamicSampling.png → ...pling/images/clientAndDynamicSampling.png b/...pling/images/clientAndDynamicSampling.png → ...pling/images/clientAndDynamicSampling.png
diff --git a/...on/dynamic-sampling/images/dsOverview.png → ...re/dynamic-sampling/images/dsOverview.png b/...on/dynamic-sampling/images/dsOverview.png → ...re/dynamic-sampling/images/dsOverview.png
diff --git a/...sampling/images/fidelityAndPriorities.png → ...sampling/images/fidelityAndPriorities.png b/...sampling/images/fidelityAndPriorities.png → ...sampling/images/fidelityAndPriorities.png
diff --git a/...c-sampling/images/redisBoostedRelease.png → ...c-sampling/images/redisBoostedRelease.png b/...c-sampling/images/redisBoostedRelease.png → ...c-sampling/images/redisBoostedRelease.png
diff --git a/...sampling/images/sampleRateAndAdoption.png → ...sampling/images/sampleRateAndAdoption.png b/...sampling/images/sampleRateAndAdoption.png → ...sampling/images/sampleRateAndAdoption.png
diff --git a/...on/dynamic-sampling/images/sequencing.png → ...re/dynamic-sampling/images/sequencing.png b/...on/dynamic-sampling/images/sequencing.png → ...re/dynamic-sampling/images/sequencing.png
diff --git a/...dynamic-sampling/images/traceSampling.png → ...dynamic-sampling/images/traceSampling.png b/...dynamic-sampling/images/traceSampling.png → ...dynamic-sampling/images/traceSampling.png
diff --git a/...cs/application/dynamic-sampling/index.mdx → ...s/architecture/dynamic-sampling/index.mdx b/...cs/application/dynamic-sampling/index.mdx → ...s/architecture/dynamic-sampling/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: Dynamic Sampling
 description: Dynamic Sampling is a feature of the ingestion pipeline that allows Sentry to automatically adjust the amount of data retained based on the value of the data.
-sidebar_order: 10
+sidebar_order: 50
 ---
 
 From all the data received by the SDKs, Sentry is able to extract low-granularity information through metrics, while Dynamic Sampling makes the decision of whether to keep or drop data.

diff --git a/...application/dynamic-sampling/outcomes.mdx → ...rchitecture/dynamic-sampling/outcomes.mdx b/...application/dynamic-sampling/outcomes.mdx → ...rchitecture/dynamic-sampling/outcomes.mdx
diff --git a/...tion/dynamic-sampling/the-big-picture.mdx → ...ture/dynamic-sampling/the-big-picture.mdx b/...tion/dynamic-sampling/the-big-picture.mdx → ...ture/dynamic-sampling/the-big-picture.mdx
diff --git a/...ocs/application/feedback-architecture.mdx → ...cs/architecture/feedback-architecture.mdx b/...ocs/application/feedback-architecture.mdx → ...cs/architecture/feedback-architecture.mdx
@@ -1,6 +1,6 @@
 ---
 title: User Feedback Architecture
-sidebar_order: 20
+sidebar_order: 60
 ---
 
 **The goal of this doc is to give engineers an in-depth understanding of User Feedback's backend.**

diff --git a/develop-docs/application/index.mdx → develop-docs/architecture/index.mdx b/develop-docs/application/index.mdx → develop-docs/architecture/index.mdx
@@ -1,5 +1,5 @@
 ---
-title: Application
+title: Architecture
 sidebar_order: 30
 ---
 

diff --git a/develop-docs/application/control-silo.mdx → .../multi-region-deployment/control-silo.mdx b/develop-docs/application/control-silo.mdx → .../multi-region-deployment/control-silo.mdx
@@ -1,6 +1,6 @@
 ---
 title: Control Silo
-sidebar_order: 30
+sidebar_order: 10
 ---
 
 Within the Control Silo are features that allow us to provide backwards compatibility for both customer API usage, and integrations

diff --git a/.../application/cross-region-replication.mdx → ...n-deployment/cross-region-replication.mdx b/.../application/cross-region-replication.mdx → ...n-deployment/cross-region-replication.mdx
@@ -1,6 +1,6 @@
 ---
 title: Cross Region Replication
-sidebar_order: 40
+sidebar_order: 20
 ---
 
 Our data-model includes many relations between users and the objects they create or interact with. Eventually users are deleted, and they need to be detached from the records they created, or those records need to be destroyed. Before sentry became a multi-region application, we relied on a mixture of Django callbacks, and postgres constraints to cascade deletions. However, in a multi-region state we arent't able to rely on these anymore as Users are in [Control Silo](/architecture/#silo-modes) and many of the objects they interact with are in the various Region Silos.

diff --git a/...lop-docs/application/cross-region-rpc.mdx → ...ti-region-deployment/cross-region-rpc.mdx b/...lop-docs/application/cross-region-rpc.mdx → ...ti-region-deployment/cross-region-rpc.mdx
@@ -1,6 +1,6 @@
 ---
 title: Cross Region RPC
-sidebar_order: 50
+sidebar_order: 30
 ---
 
 When Sentry is deployed in a multi-region deployment (like sentry.io) there are many scenarios and workflows where a region silo requires information that is stored in Control Silo. Similarly there are flows where Control Silo operations need to read or mutate state stored in regions.

diff --git a/develop-docs/architecture/multi-region-deployment/index.mdx b/develop-docs/architecture/multi-region-deployment/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Multi-Region Deployment
+sidebar_order: 40
+---
+
+<PageGrid />
diff --git a/develop-docs/application/architecture.mdx → develop-docs/architecture/overview.mdx b/develop-docs/application/architecture.mdx → develop-docs/architecture/overview.mdx
@@ -1,6 +1,6 @@
 ---
-title: Architecture
-sidebar_order: 1
+title: Overview
+sidebar_order: 10
 ---
 
 ## High level overview

diff --git a/...-docs/application/sentry-vs-getsentry.mdx → ...docs/architecture/sentry-vs-getsentry.mdx b/...-docs/application/sentry-vs-getsentry.mdx → ...docs/architecture/sentry-vs-getsentry.mdx
@@ -1,6 +1,6 @@
 ---
 title: sentry vs. getsentry
-sidebar_order: 70
+sidebar_order: 20
 ---
 
 You'll find numerous references to both `sentry` and `getsentry` in our documentation. Both are [Django](https://www.djangoproject.com/) apps, but `sentry` [is open](https://github.com/getsentry/sentry) and `getsentry` is closed. What's in which?

diff --git a/develop-docs/backend/index.mdx b/develop-docs/backend/index.mdx
diff --git a/develop-docs/development/analytics.mdx → .../development-infrastructure/analytics.mdx b/develop-docs/development/analytics.mdx → .../development-infrastructure/analytics.mdx
@@ -1,7 +1,7 @@
 ---
 title: Analytics
 description: This guide steps you through instrumenting your code with Sentry's 3rd-party analytics infrastructure.
-sidebar_order: 100
+sidebar_order: 90
 ---
 
 

diff --git a/develop-docs/backend/development-server.mdx → ...astructure/backend-development-server.mdx b/develop-docs/backend/development-server.mdx → ...astructure/backend-development-server.mdx
@@ -1,6 +1,6 @@
 ---
 title: Backend Development Server
-sidebar_order: 10
+sidebar_order: 20
 ---
 
 (*see also: [Frontend Development Server](/frontend/development-server/)*)
@@ -30,4 +30,3 @@ This will do literally nothing except bring up the web workers. You are now resp
 Use `sentry run --help` to see what you might be missing by not running devserver.
 
 To run the development server with ngrok, see [Developing with Ngrok](/development/ngrok/).
-
diff --git a/...cs/development/continuous-integration.mdx → ...infrastructure/continuous-integration.mdx b/...cs/development/continuous-integration.mdx → ...infrastructure/continuous-integration.mdx
@@ -1,7 +1,7 @@
 ---
 title: Continuous Integration
 description: Sentry uses a variety of continuous integration services to help ensure we don't accidentally break the application.
-sidebar_order: 60
+sidebar_order: 80
 ---
 
 ## Deployments

diff --git a/develop-docs/development/devservices.mdx → ...evelopment-infrastructure/devservices.mdx b/develop-docs/development/devservices.mdx → ...evelopment-infrastructure/devservices.mdx
@@ -1,6 +1,6 @@
 ---
 title: Service Manager (devservices)
-sidebar_order: 80
+sidebar_order: 40
 ---
 
 Sentry provides an abstraction to Docker to run required services within development called `devservices`.

diff --git a/...op-docs/development/environment/index.mdx → ...ment-infrastructure/environment/index.mdx b/...op-docs/development/environment/index.mdx → ...ment-infrastructure/environment/index.mdx
diff --git a/...op-docs/development/environment/ports.mdx → ...ment-infrastructure/environment/ports.mdx b/...op-docs/development/environment/ports.mdx → ...ment-infrastructure/environment/ports.mdx
diff --git a/...ironment/pycharm/img/AddConfiguration.png → ...ironment/pycharm/img/AddConfiguration.png b/...ironment/pycharm/img/AddConfiguration.png → ...ironment/pycharm/img/AddConfiguration.png
diff --git a/...nt/pycharm/img/AddPytestConfiguration.png → ...nt/pycharm/img/AddPytestConfiguration.png b/...nt/pycharm/img/AddPytestConfiguration.png → ...nt/pycharm/img/AddPytestConfiguration.png
diff --git a/...onment/pycharm/img/DevserverLeetSetup.png → ...onment/pycharm/img/DevserverLeetSetup.png b/...onment/pycharm/img/DevserverLeetSetup.png → ...onment/pycharm/img/DevserverLeetSetup.png
diff --git a/.../pycharm/img/DevserverTroubleshooting.png → .../pycharm/img/DevserverTroubleshooting.png b/.../pycharm/img/DevserverTroubleshooting.png → .../pycharm/img/DevserverTroubleshooting.png
diff --git a/...ironment/pycharm/img/PyCharmGetsentry.png → ...ironment/pycharm/img/PyCharmGetsentry.png b/...ironment/pycharm/img/PyCharmGetsentry.png → ...ironment/pycharm/img/PyCharmGetsentry.png
diff --git a/...ment/pycharm/img/PyCharmPyInterpreter.png → ...ment/pycharm/img/PyCharmPyInterpreter.png b/...ment/pycharm/img/PyCharmPyInterpreter.png → ...ment/pycharm/img/PyCharmPyInterpreter.png
diff --git a/...nt/pycharm/img/PycharmRunConfigEnvVar.png → ...nt/pycharm/img/PycharmRunConfigEnvVar.png b/...nt/pycharm/img/PycharmRunConfigEnvVar.png → ...nt/pycharm/img/PycharmRunConfigEnvVar.png
diff --git a/...development/environment/pycharm/index.mdx → ...rastructure/environment/pycharm/index.mdx b/...development/environment/pycharm/index.mdx → ...rastructure/environment/pycharm/index.mdx
diff --git a/develop-docs/development/environment/u2f.mdx → ...opment-infrastructure/environment/u2f.mdx b/develop-docs/development/environment/u2f.mdx → ...opment-infrastructure/environment/u2f.mdx
diff --git a/develop-docs/frontend/development-server.mdx → ...structure/frontend-development-server.mdx b/develop-docs/frontend/development-server.mdx → ...structure/frontend-development-server.mdx
@@ -1,6 +1,6 @@
 ---
 title: Frontend Development Server
-sidebar_order: 1
+sidebar_order: 30
 ---
 
 (*see also: [Backend Development Server](/backend/development-server/)*)

diff --git a/develop-docs/development-infrastructure/index.mdx b/develop-docs/development-infrastructure/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Development Infrastructure
+sidebar_order: 40
+---
+
+<PageGrid />
diff --git a/develop-docs/development/ngrok.mdx → ...docs/development-infrastructure/ngrok.mdx b/develop-docs/development/ngrok.mdx → ...docs/development-infrastructure/ngrok.mdx
diff --git a/develop-docs/backend/python-dependencies.mdx → ...nt-infrastructure/python-dependencies.mdx b/develop-docs/backend/python-dependencies.mdx → ...nt-infrastructure/python-dependencies.mdx
@@ -1,6 +1,6 @@
 ---
 title: Python Dependencies
-sidebar_order: 20
+sidebar_order: 100
 ---
 
 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/development/testing.mdx → ...cs/development-infrastructure/testing.mdx b/develop-docs/development/testing.mdx → ...cs/development-infrastructure/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: 50
+sidebar_order: 60
 ---
 
 ## Getting Setup

diff --git a/develop-docs/development/workflow.mdx → ...s/development-infrastructure/workflow.mdx b/develop-docs/development/workflow.mdx → ...s/development-infrastructure/workflow.mdx
@@ -1,6 +1,6 @@
 ---
 title: Workflow
-sidebar_order: 40
+sidebar_order: 50
 ---
 
 You may also be interested in <Link to="/application/sentry-vs-getsentry/">sentry vs. getsentry</Link>.

diff --git a/develop-docs/development/code-review.mdx → ...ocs/engineering-practices/code-review.mdx b/develop-docs/development/code-review.mdx → ...ocs/engineering-practices/code-review.mdx
diff --git a/develop-docs/development/commit-messages.mdx → ...engineering-practices/commit-messages.mdx b/develop-docs/development/commit-messages.mdx → ...engineering-practices/commit-messages.mdx
diff --git a/develop-docs/development/documentation.mdx → ...s/engineering-practices/documentation.mdx b/develop-docs/development/documentation.mdx → ...s/engineering-practices/documentation.mdx
diff --git a/develop-docs/development/index.mdx → develop-docs/engineering-practices/index.mdx b/develop-docs/development/index.mdx → develop-docs/engineering-practices/index.mdx
@@ -1,5 +1,5 @@
 ---
-title: Development
+title: Engineering Practices
 sidebar_order: 20
 ---
 

diff --git a/develop-docs/development/rust.mdx → develop-docs/engineering-practices/rust.mdx b/develop-docs/development/rust.mdx → develop-docs/engineering-practices/rust.mdx
@@ -1,7 +1,7 @@
 ---
 title: Rust Development
 description: This is a document that contains a bunch of useful resources for getting started with Rust and adhering to our coding principles.
-sidebar_order: 90
+sidebar_order: 40
 ---
 
 ## Getting Started

diff --git a/develop-docs/frontend/index.mdx b/develop-docs/frontend/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: Frontend Handbook
-sidebar_order: 40
+sidebar_order: 60
 ---
 
 This guide covers how we write frontend code at Sentry, and is specifically focussed on the [Sentry](https://github.com/getsentry/sentry) and [Getsentry](https://github.com/getsentry/getsentry) codebases. It assumes you are using the eslint rules outlined by [eslint-config-sentry](https://github.com/getsentry/eslint-config-sentry); hence code style enforced by these linting rules will not be discussed here.

diff --git a/develop-docs/relay/index.mdx → develop-docs/ingestion/index.mdx b/develop-docs/relay/index.mdx → develop-docs/ingestion/index.mdx
@@ -1,12 +1,13 @@
 ---
-title: Relay Development
-sidebar_order: 70
+title: Ingestion
+sidebar_order: 90
 ---
 
-Relay is a service for event filtering, rate-limiting and processing. It can act as:
+Ingestion is done by [Sentry Relay](https://github.com/getsentry/relay). Relay is a service for event filtering, rate-limiting and processing.
+
+It can act as:
 
 * the store endpoint for your Sentry installation. See [Relay developer
   documentation](https://getsentry.github.io/relay/relay/).
 * an additional middle layer between your application and Sentry. See [Relay product
   documentation](https://docs.sentry.io/product/relay/).
-
diff --git a/...p-docs/relay/projectconfig-versioning.mdx → ...cs/ingestion/projectconfig-versioning.mdx b/...p-docs/relay/projectconfig-versioning.mdx → ...cs/ingestion/projectconfig-versioning.mdx
diff --git a/...ocs/relay/transaction-span-ratelimits.mdx → ...ingestion/transaction-span-ratelimits.mdx b/...ocs/relay/transaction-span-ratelimits.mdx → ...ingestion/transaction-span-ratelimits.mdx