Moving performance enablement pages

.gitlab/CODEOWNERS

@@ -233,7 +233,6 @@
 /content/handbook/engineering/infrastructure/test-platform/ @ghosh-abhinaba @kkolpakova @ksvoboda @sabrinafarmer @vincywilson
 /content/handbook/engineering/infrastructure/test-platform/onboarding/ @ghosh-abhinaba @kkolpakova @ksvoboda @vincywilson
 /content/handbook/engineering/infrastructure/test-platform/quad-planning/ @ghosh-abhinaba @kkolpakova @ksvoboda @vincywilson
-/content/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/ @ksvoboda
 /content/handbook/engineering/infrastructure/test-platform/test-engineering-team/ @kkolpakova
 /content/handbook/engineering/quality/engineering-analytics.md @sabrinafarmer @lmai1
 

content/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/_index.md → content/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/_index.md

@@ -124,7 +124,7 @@ Anything that would be assigned a weight of 8 or larger should be broken down.
 
 ## Test Platform process across product sections
 
-Overall we follow the same process as [defined](../#how-we-work) in our Test Platform handbook across all groups in Core Platform and SaaS Platform
+Overall we follow the same process as [defined](/handbook/engineering/infrastructure/test-platform/#how-we-work) in our Test Platform handbook across all groups in Core Platform and SaaS Platform
 except for a few exceptions curated to fit the needs of specific groups.
 
-* [Test Platform in Distribution group](/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/distribution/)
+* [Test Platform in Distribution group](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/distribution/)

content/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/distribution.md → content/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/distribution.md

@@ -38,8 +38,8 @@ to run GitLab QA locally for development.
     - If Allure report is available: Click on report link -> Product defects -> Select failed spec -> click Failure issues. [Demo](https://youtu.be/_0dM6KLdCpw?t=234)
     - Some specs might have multiple QA failure issues with different stack trace. In such case, compare failed stack trace from the job with the ones listed in the issues.
 1. If an issue with the same error is not found
-    - Continue to debug the QA failure [following the guide](/handbook/engineering/infrastructure/test-platform/debugging-qa-test-failures/#investigate-the-root-cause)
-    - Reach out to the Test Platform sub-department - [on-call DRI](/handbook/engineering/infrastructure/test-platform/oncall-rotation/#schedule) or [Distribution SET](/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/#team-members)
+    - Continue to debug the QA failure [following the guide](/handbook/engineering/infrastructure/test-platform/pipeline-triage/#investigate-the-root-cause)
+    - Reach out to the Test Platform sub-department - [on-call DRI](/handbook/engineering/infrastructure/test-platform/oncall-rotation/#schedule) or [Distribution SET](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/#team-members)
 
 ### Bug Prioritization
 

content/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/performance.md → content/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/performance.md

@@ -116,7 +116,7 @@ Load testing in the cloud presents a number of challenges:
 
 #### System Level Load Testing
 
-We currently conduct load testing using [GPT](../performance-and-scalability#performance-tool) and [GBPT](../performance-and-scalability#browser-performance-tool). This testing is predominately run against our [Reference Architectures](../performance-and-scalability/#reference-architectures), but can be run against a live environment, but caution should be applied when running against [shared enviornments](../performance-and-scalability#no-shared-environments-usage).
+We currently conduct load testing using [GPT](/handbook/engineering/infrastructure/test-platform/performance-and-scalability/#performance-tool) and [GBPT](/handbook/engineering/infrastructure/test-platform/performance-and-scalability/#browser-performance-tool). This testing is predominately run against our [Reference Architectures](/handbook/engineering/infrastructure/test-platform/performance-and-scalability//#reference-architectures), but can be run against a live environment, but caution should be applied when running against [shared enviornments](/handbook/engineering/infrastructure/test-platform/performance-and-scalability/#no-shared-environments-usage).
 
 #### Component Level Load Testing
 
@@ -157,7 +157,7 @@ We can run load tests on specific sub components. This can be a subsystem (like
 | [Profiling page](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/profiling.md?ref_type=heads) | Documentation on approaches to do profiling on GitLab |
 | [Performance Bar](https://docs.gitlab.com/ee/administration/monitoring/performance/performance_bar.html) | Performance Bar that can be used in a running GitLab instance to see metrics |
 | [Performance Guidelines](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/performance.md?ref_type=heads) | Our docs page on performance guidelines |
-| [Cells Performance Testing](../../cells/cells_test_strategy/#performance-testing) | Cells performance test strategy handbook page |
+| [Cells Performance Testing](/handbook/engineering/infrastructure/cells/cells_test_strategy/#performance-testing) | Cells performance test strategy handbook page |
 | [Metrics Catalog](https://gitlab.com/gitlab-com/runbooks/-/tree/master/metrics-catalog?ref_type=heads) | home for our SLA/SLO/SLI definitions |
 | [Cells Performance Dashboard](https://dashboards.gitlab.net/d/cells-main/cells3a-cells-performance?orgId=1&from=now-6h%2Fm&to=now%2Fm&timezone=utc&var-PROMETHEUS_DS=mimir-gitlab-ops&var-environment=gprd) | First pass at creating an Observability Performance Dashboard in Grafana |
 | [Platform Triage Dashboard](https://dashboards.gitlab.net/d/general-triage/general3a-platform-triage?orgId=1&from=now-6h%2Fm&to=now%2Fm&timezone=utc&var-PROMETHEUS_DS=mimir-gitlab-gprd&var-environment=gprd&var-stage=main) | the home page dashboard for our grafana, a common starting point for investigating performance in our Observability |

content/handbook/engineering/infrastructure/_index.md

@@ -106,8 +106,8 @@ flowchart LR
     D --> Switchboard
     click Switchboard "/handbook/engineering/infrastructure/team/gitlab-dedicated/switchboard/"
 
-    TP --> SMP[Self-Managed Platform]
-    click SMP "/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/"
+    TP --> PE[Performance Enablement]
+    click PE "/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/"
     TP --> TE[Test Engineering]
     click TE "/handbook/engineering/infrastructure/test-platform/test-engineering-team/"
     TP --> TTI[Test and Tools Infrastructure]

content/handbook/engineering/infrastructure/core-platform/systems/distribution/_index.md

@@ -345,7 +345,7 @@ The following important areas of the GitLab Handbook impact how we work and are
 - [How to follow our Product Principles](/handbook/product/product-principles/#how-we-follow-our-principles)
 - [Principles of our company strategy](/handbook/company/strategy/#principles)
 - [Effective & Responsible Communication Guidelines](/handbook/communication/#effective--responsible-communication-guidelines)
-- [Test Platform in Distribution group](/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/distribution/)
+- [Test Platform in Distribution group](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/distribution/)
 
 ## Work/life harmony
 

content/handbook/engineering/infrastructure/engineering-productivity/issue-triage.md

@@ -80,9 +80,9 @@ Once you've determined a severity for an issue add a note that explains in summa
 | Type of `~"type::bug"` | `~"severity::1"`: Blocker | `~"severity::2"`: Critical | `~"severity::3"`: Major  | `~"severity::4"`: Low | Triage DRI |
 |----------------|--------------------------|---------------------------|-------------------------|----------------------|------------|
 | General bugs   | Broken feature with no workaround or any data-loss. | Broken feature with an unacceptably complex workaround. | Broken feature with a workaround. | Functionality is inconvenient. | [SET](/handbook/engineering/quality/#individual-contributors), [QEM](/handbook/engineering/quality/#management-team), or [EM](/handbook/engineering/management/) for that product group. |
-| `~"bug::performance"` Response time <br> (API/Web/Git)[^1] | Above 9000ms to timing out | Between 2000ms and 9000ms | Between 1000ms and 2000ms | Between 200ms and 1000ms | [Enablement Quality Engineering team](/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/) |
-| `~"bug::performance"` Browser Rendering <br> ([LCP](https://web.dev/lcp/))[^2] | Above 9000ms to timing out | Between 4000ms and 9000ms | Between 3000ms and 4000ms | Between 3000ms and 2500ms | [Enablement Quality Engineering team](/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/) |
-| `~"bug::performance"` Browser Rendering <br> ([TBT](https://web.dev/tbt/))[^2] | Above 9000ms to timing out | Between 2000ms and 9000ms | Between 1000ms and 2000ms | Between 300ms and 1000ms | [Enablement Quality Engineering team](/handbook/engineering/infrastructure/test-platform/self-managed-platform-team/) |
+| `~"bug::performance"` Response time <br> (API/Web/Git)[^1] | Above 9000ms to timing out | Between 2000ms and 9000ms | Between 1000ms and 2000ms | Between 200ms and 1000ms | [Enablement Quality Engineering team](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/) |
+| `~"bug::performance"` Browser Rendering <br> ([LCP](https://web.dev/lcp/))[^2] | Above 9000ms to timing out | Between 4000ms and 9000ms | Between 3000ms and 4000ms | Between 3000ms and 2500ms | [Enablement Quality Engineering team](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/) |
+| `~"bug::performance"` Browser Rendering <br> ([TBT](https://web.dev/tbt/))[^2] | Above 9000ms to timing out | Between 2000ms and 9000ms | Between 1000ms and 2000ms | Between 300ms and 1000ms | [Enablement Quality Engineering team](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/) |
 | `~bug::ux` User experience problem [&sup3;](#ux) | "I can't figure this out." Users are blocked and/or likely to make risky errors due to poor usability, and are likely to ask for support. | "I can figure out why this is happening, but it's really painful to solve." Users are significantly delayed by the available workaround. | "This still works, but I have to make small changes to my process." Users are self sufficient in completing the task with the workaround, but may be somewhat delayed. |  "There is a small inconvenience or inconsistency." Usability isn't ideal or there is a small cosmetic issue. | [Product Designers](/handbook/product/ux/product-design/) of that Product group |
 | `~"bug::availability"` of GitLab SaaS | See [Availability section](#availability) | See [Availability section](#availability) | See [Availability section](#availability) | See [Availability section](#availability) | |
 | `~"bug::vulnerability"` Security Vulnerability | See [Vulnerability Remediation SLAs](/handbook/security/product-security/vulnerability-management/sla/) | See [Vulnerability Remediation SLAs](/handbook/security/product-security/vulnerability-management/sla/) | See [Vulnerability Remediation SLAs](/handbook/security/product-security/vulnerability-management/sla/) | See [Vulnerability Remediation SLAs](/handbook/security/product-security/vulnerability-management/sla/) | AppSec team |

content/handbook/engineering/infrastructure/test-platform/_index.md

@@ -157,12 +157,12 @@ Infrastructure Department structure is documented [here](/handbook/engineering/i
 ```mermaid
 graph TD
     A[Test Platform sub-department]
-    A --> B(Self-Managed Platform team)
+    A --> B(Performance Enablement)
     A --> C(Test Engineering team)
     A --> D(Test and Tools Infrastructure team)
 
     click A "/handbook/engineering/infrastructure/test-platform"
-    click B "/handbook/engineering/infrastructure/test-platform/self-managed-platform-team"
+    click B "/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement"
     click C "/handbook/engineering/infrastructure/test-platform/test-engineering-team"
     click D "/handbook/engineering/infrastructure/test-platform/test-and-tools-infrastructure-team"
 ```
@@ -174,7 +174,7 @@ Feel free to reach out to us by opening an issue on the [Quality Team Tasks proj
 | Team                           | GitLab.com handle  | Slack channel | Slack handle |
 | ------------------------------ | ------------------ | ------------- | ------------ |
 | Test Platform            | [`@gl-quality/tp-sub-dept`](https://gitlab.com/gl-quality/tp-sub-dept) | [#test-platform](https://gitlab.slack.com/archives/C3JJET4Q6) | None |
-| [Self-Managed Platform team](self-managed-platform-team) | [`@gl-quality/tp-self-managed-platform`](https://gitlab.com/gl-quality/tp-self-managed-platform) | [#self-managed-platform-team](https://gitlab.slack.com/archives/CTP7N0PM4) | `@self-managed-platform` |
+| [Self-Managed Platform team](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement) | [`@gl-quality/tp-self-managed-platform`](https://gitlab.com/gl-quality/tp-self-managed-platform) | [#self-managed-platform-team](https://gitlab.slack.com/archives/CTP7N0PM4) | `@self-managed-platform` |
 | [Test Engineering team](test-engineering-team) | [`@gl-quality/tp-test-engineering`](https://gitlab.com/gl-quality/tp-test-engineering) | [#test-engineering-team](https://gitlab.slack.com/archives/C064M4S0FU5) |`@test-engineering-team` |
 | [Test and Tools Infrastructure team](test-and-tools-infrastructure-team)     | [`@gl-quality/tp-test-tools-infrastructure`](https://gitlab.com/gl-quality/tp-test-tools-infrastructure)  |  [`#test-tools-infrastructure-team`](https://gitlab.slack.com/archives/C064M4D2V37)  | `@test-tools-infrastructure` |
 
@@ -186,7 +186,7 @@ Feel free to reach out to us by opening an issue on the [Quality Team Tasks proj
 
 ### Individual contributors
 
-The following people are members of the [Self-Managed Platform team](self-managed-platform-team):
+The following people are members of the [Self-Managed Platform team](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement):
 
 {{< team-by-manager-slug "ksvoboda" >}}
 

content/handbook/engineering/infrastructure/test-platform/dashboards.md

@@ -19,10 +19,10 @@ description: "This handbook page serves as a central repository for all our Test
 |                         | [Test Economy](https://10az.online.tableau.com/#/site/gitlab/views/DRAFTTestEconomyMetrics/TestEconomyMetricsDashboard?:iid=3)                                                                                                                                                                                                                                                                                   | Insights into the cost-effectiveness of testing processes.                          | [Test and Tools Infrastructure](test-and-tools-infrastructure-team)                                                |
 |                         | [Test Infra Availability (E2E Test)](https://dashboards.gitlab.net/d/ci-runners-main/ci-runners3a-overview?orgId=1&var-PROMETHEUS_DS=mimir-gitlab-gprd&var-environment=gprd&var-stage=main&var-shard=qa-runners&from=now-24h&to=now&viewPanel=2211350843) | Dashboard indicating the current availability of E2E test infrastructure.           | [Test and Tools Infrastructure](test-and-tools-infrastructure-team)                                                |
 | Test Contribution       | [Developer Contribution To E2E Tests](https://10az.online.tableau.com/#/site/gitlab/views/TestPlatformDeveloperContributionDashboard/TestPlatformDeveloperContributionDashboard?:iid=2)                                                                                                                                                                                                                          | Tracking developer engagement and contributions to E2E tests.                       | [Test Engineering](test-engineering-team) <br> [Test and Tools Infrastructure](test-and-tools-infrastructure-team) |
-| Performance Testing     | [GPT Results](https://gitlab.com/gitlab-org/quality/performance/-/wikis/home)                                                                                                                                                                                                                                                                                                                                    | GitLab Performance Tool test results from automated reference environment pipelines | [Self-Managed Platform](self-managed-platform-team)                                                                |
-| Self-Managed Excellence | [Reference Architectures](https://10az.online.tableau.com/#/site/gitlab/views/DRAFTSelf-ManagedExcellenceMetrics/ReferenceArchitectures)                                                                                                                                                                                                                                                                         | Reference Architecture issues created and closed per request type                   | [Self-Managed Platform](self-managed-platform-team)                                                                |
-|                         | [GitLab Environment Toolkit](https://10az.online.tableau.com/#/site/gitlab/views/DRAFTSelf-ManagedExcellenceMetrics/GitlabEnvironmentToolkit)                                                                                                                                                                                                                                                                    | GitLab Environment Toolkit merge requests and issues per type                       | [Self-Managed Platform](self-managed-platform-team)                                                                |
-|                         | [GitLab Performance Tool](https://10az.online.tableau.com/#/site/gitlab/views/DRAFTSelf-ManagedExcellenceMetrics/GitlabPerformanceTool)                                                                                                                                                                                                                                                                          | GitLab Performance Tool merge requests and issues per type                          | [Self-Managed Platform](self-managed-platform-team)                                                                |
+| Performance Testing     | [GPT Results](https://gitlab.com/gitlab-org/quality/performance/-/wikis/home)                                                                                                                                                                                                                                                                                                                                    | GitLab Performance Tool test results from automated reference environment pipelines | [Self-Managed Platform](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement)                                                                |
+| Self-Managed Excellence | [Reference Architectures](https://10az.online.tableau.com/#/site/gitlab/views/DRAFTSelf-ManagedExcellenceMetrics/ReferenceArchitectures)                                                                                                                                                                                                                                                                         | Reference Architecture issues created and closed per request type                   | [Self-Managed Platform](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement)                                                                |
+|                         | [GitLab Environment Toolkit](https://10az.online.tableau.com/#/site/gitlab/views/DRAFTSelf-ManagedExcellenceMetrics/GitlabEnvironmentToolkit)                                                                                                                                                                                                                                                                    | GitLab Environment Toolkit merge requests and issues per type                       | [Self-Managed Platform](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement)                                                                |
+|                         | [GitLab Performance Tool](https://10az.online.tableau.com/#/site/gitlab/views/DRAFTSelf-ManagedExcellenceMetrics/GitlabPerformanceTool)                                                                                                                                                                                                                                                                          | GitLab Performance Tool merge requests and issues per type                          | [Self-Managed Platform](/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement)                                                                |
 | Bug Tracking            | [Customer Bugs](https://10az.online.tableau.com/#/site/gitlab/views/OpenBugAgeOBA/CustomerBugsDashboard?:iid=1)                                                                                                                                                                                                                                                                                                  | Dynamic tracking of Customer bugs                                                   | [Test Engineering](test-engineering-team)                                                                          |
 |                         | [Bug Prioritization](https://10az.online.tableau.com/#/site/gitlab/views/OpenBugAgeOBA/BugPrioritizationDashboard?:iid=1)                                                                                                                                                                                                                                                                                        | Bug prioritization based on burndown trends                                         | [Test Engineering](test-engineering-team)                                                                          |
 | Operational Excellence| [Team Operational Trends](https://10az.online.tableau.com/t/gitlab/views/TeamProductivityMetricsforTTI/DashboardwithDocumentation/8c6fdf45-8ebb-4858-95a4-df9f9ef94d34/fb1e8aca-b0fb-45af-ad2b-0463ef51b491) | This dashboard is designed to give us a deeper understanding of Test Platform sub-department's operational effectiveness over time | [Test and Tools Infrastructure](test-and-tools-infrastructure-team) |