Merge branch 'fix-links-10' into 'main'

Fix broken links See merge request !9575

Merge branch 'fix-links-10' into 'main'
1910fb2b · Cynthia "Arty" Ng · 10dbeffb · 455376ee · 1910fb2b · 1910fb2b
Commit 1910fb2b authored 4 months ago by Cynthia "Arty" Ng
--- a/content/handbook/customer-success/csm/cadence-calls.md
+++ b/content/handbook/customer-success/csm/cadence-calls.md
@@ -157,7 +157,7 @@ At the end of each customer call any changes to customer health should be reflec
 ### Best Practices for Note-Taking

 - Write down your *agenda* (including questions you want to ask) in advance. This way you can quickly add your notes for the specific context.
- If you're comfortable in writing in [Markdown format](/handbook/markdown-guide/), use it to quickly structure your notes in real time.
+- If you're comfortable in writing in [Markdown format](https://handbook.gitlab.com/docs/markdown-guide/), use it to quickly structure your notes in real time.
 - Allow yourself time directly after the call to clean up your notes. Avoid scheduling back-to-back meetings.
 - Practice slowing down call conversations. Stopping the dialog for a few seconds to say "let me write that down" tells the customer what they said is important to you.
 - Ask your SAE/AE/SA to take notes with you. After the meeting combine and add detail.

--- a/content/handbook/customer-success/csm/csm-development.md
+++ b/content/handbook/customer-success/csm/csm-development.md
@@ -139,7 +139,7 @@ As CSMs have positioned themselves to be more strategic and reach Director, VP,

 #### Markdown

- [Handbook Markdown Guide](/handbook/markdown-guide/)
+- [Handbook Markdown Guide](https://handbook.gitlab.com/docs/markdown-guide/)
 - [GitLab Flavored Markdown (GLFM)](https://docs.gitlab.com/ee/user/markdown.html)
 - [Handbook Style Guide](/handbook/about/style-guide/)
 - [Markdown Tutorial](https://about.gitlab.com/blog/2018/08/17/gitlab-markdown-tutorial/)

--- a/content/handbook/customer-success/csm/escalations/_index.md
+++ b/content/handbook/customer-success/csm/escalations/_index.md
@@ -234,6 +234,6 @@ Occasionally, customers will require a product leader to act as a stable counter

 ## Related Links

- [Support Engineering Page](/handbook/support/) and [Support Engineering Escalation Procedures](/handbook/support/workflows/working-with-issues.html)
+- [Support Engineering Page](/handbook/support/) and [Support Engineering Escalation Procedures](/handbook/support/workflows/working-with-issues/)
 - [Product Escalation Issue Template](https://gitlab.com/gitlab-com/Product/issues/new?issuable_template=Product-Support-Request) to request Product Team support for roadmap / future needs, prioritization of enhancements and/or issues and troubleshooting of customer issues.
 - [Customer Health Assessment and Account Triaging](/handbook/customer-success/csm/health-score-triage/)
--- a/content/handbook/customer-success/csm/gainsight/_index.md
+++ b/content/handbook/customer-success/csm/gainsight/_index.md
@@ -87,7 +87,7 @@ The table below represents the steps a CSM would typically take in Gainsight. Pl

 #### Technical Documentation

- [Gainsight Technical Documentation](/handbook/sales/field-operations/customer-success-operations/gainsight/gainsight-gtm.html)
+- [Gainsight Technical Documentation](/handbook/sales/field-operations/customer-success-operations/gainsight/gainsight-gtm/)
 - [Gainsight Administration](/handbook/sales/field-operations/customer-success-operations/gainsight/)
 - [SalesForce and Zendesk Sync](/handbook/customer-success/csm/gainsight/#salesforce-and-zendesk-syncing)


--- a/content/handbook/customer-success/csm/risk-mitigation/_index.md
+++ b/content/handbook/customer-success/csm/risk-mitigation/_index.md
@@ -144,7 +144,7 @@ Once we know the risk and done some discovery into that risk, we have some optio

 #### Customer not using CI

- Offer an [Advanced CI/CD workshop](/handbook/customer-success/workshops/ci-workshop.html) if they have difficulty in building pipelines.
+- Offer an [Advanced CI/CD workshop](/handbook/customer-success/workshops/ci-workshop/) if they have difficulty in building pipelines.
 - Work with the GitLab team to build CI/CD templates for certain jobs and pipelines to make it easier for users to adopt CI.
 - If it is a migration problem, work with the customer on tutorials to do a migration
  - Try to identify teams who are willing to work with you on their pipeline

--- a/content/handbook/customer-success/csm/segment/cse/content/_index.md
+++ b/content/handbook/customer-success/csm/segment/cse/content/_index.md
@@ -107,7 +107,7 @@ The following sections provide an overview of all content assets, and links to f

 ### Environments/Infrastructure to support Demonstrating Content

- **Build Your Own -** Self service public cloud infrastructure/tooling/environments. Individual AWS account or GCP project access documented in the [Sandbox Cloud Realm](/handbook/infrastructure-standards/realms/sandbox) handbook pages and accessed through [gitlabsandbox.cloud](https://gitlabsandbox.cloud).
+- **Build Your Own -** Self service public cloud infrastructure/tooling/environments. Individual AWS account or GCP project access documented in the [Sandbox Cloud Realm](/handbook/company/infrastructure-standards/realms/sandbox) handbook pages and accessed through [gitlabsandbox.cloud](https://gitlabsandbox.cloud).
  - *Use Cases:*
    - *Competitor analysis/demonstration/exploration*
    - *Personal runner/fleet demonstration/exploration*
@@ -131,7 +131,7 @@ The following sections provide an overview of all content assets, and links to f
 | Title                                                        | Group         | Last updated | YouTube |
 | ------------------------------------------------------------ | ------------- | ------------ | ------- |
 | [Holistic Approach to Securing the Development Lifecycle](https://drive.google.com/file/d/11-mPw0aNXcazOMVVVvxEo97meQz1TYMW/view?usp=drive_link) | Secure        | 2023-10-13   | https://youtu.be/WWA7z2WtFvM  |
-| [Git Basics](https://drive.google.com/file/d/17BvOGiXmWNLYm3MXmIqZ6kAkC0b4cow7/view?usp=drive_link) | Create        | 2023-10-13   | https://youtu.be/WMWoi6for1M | 
+| [Git Basics](https://drive.google.com/file/d/17BvOGiXmWNLYm3MXmIqZ6kAkC0b4cow7/view?usp=drive_link) | Create        | 2023-10-13   | https://youtu.be/WMWoi6for1M |
 | [Intro to GitLab](https://drive.google.com/file/d/14vWu6oCIcWwrkNtcZw_pioC8K3c2hNEt/view?usp=drive_link) | All           | 2023-12-07   | https://youtu.be/E1tKfOPKMA8 |
 | [Intro to CI/CD](https://drive.google.com/file/d/1V3sH4rTQSMzFfwZpzZgmi9wZJq8vSoMm/view?usp=drive_link) | Verify        | 2023-10-13   | https://youtu.be/bE2YXhAVBeE |
 | [Advanced CI/CD](https://drive.google.com/file/d/1GlGg0Q7p7gsAGGWgZ1vj82NZmap7PX3w/view?usp=drive_link) | Verify        | 2023-10-23   | https://youtu.be/9VTGW1pCTC8 |

--- a/content/handbook/customer-success/csm/segment/cse/cse-operating-rhythm.md
+++ b/content/handbook/customer-success/csm/segment/cse/cse-operating-rhythm.md
@@ -73,7 +73,7 @@ The upcoming month's hands-on labs are added to an issue in the [Customer Succes
 1. Fill in the form to the best of your knowledge.
 1. Click `Submit Request`.

-This will result in an Issue being created on the [Demo Architect - Workshop Management Board](https://gitlab.com/gitlab-com/customer-success/demo-engineering/workshop-library/demo-engineering-workshop-issues/-/boards/7697518?label_name[]=DA%20Workshop%20Request) which will be picked up by the Demo Architecture team. 
+This will result in an Issue being created on the [Demo Architect - Workshop Management Board](https://gitlab.com/gitlab-com/customer-success/demo-engineering/workshop-library/demo-engineering-workshop-issues/-/boards/7697518?label_name[]=DA%20Workshop%20Request) which will be picked up by the Demo Architecture team.

 A pair of invitation codes, one for production and one for testing will be generated and shared in a comment on the issue. The Demo Architecture team will assign DRIs ownership of the session (Top level group) and verify invitation codes and associated runners are operational.

@@ -168,7 +168,7 @@ Escalations ought to be used sparingly and only for the larger accounts in our s

 There are two types of escalations: support escalations and account escalations.

-1. Support escalations are for existing tickets causing a very high business impact for the customer and is raising their temperature very high. The escalation process can bring attention to the issue and raise its priority within support. Following the defined process for a support ticket escalation noted on [the Support ticket attention requests page](/handbook/support/internal-support/support-ticket-attention-requests.html#submitting-a-support-ticket-attention-request-star--starring-a-ticket) is sufficient.
+1. Support escalations are for existing tickets causing a very high business impact for the customer and is raising their temperature very high. The escalation process can bring attention to the issue and raise its priority within support. Following the defined process for a support ticket escalation noted on [the Support ticket attention requests page](/handbook/support/internal-support/support-ticket-attention-requests/#submitting-a-support-ticket-attention-request-star--starring-a-ticket) is sufficient.
 1. Account escalations may or may not relate to a support ticket. It could be relevant to an open issue for a product bug or a feature request. It's useful when the customer communicates a highly-impactful problem relevant to, for example an open issue that is blocking a critical use case and causing them to evaluate other vendors for non-GitLab solutions and is thus posing a churn or contraction risk for GitLab.

 ### Meeting Workflow
@@ -233,19 +233,19 @@ If a customer has additional questions after receiving the follow-up email, the
 **Important Notes**:

 - If the topic the customer wants to address is a new topic, a new request shall be opened to clearly distinguish the different topics/requests. We also consider anything that comes up after more than 4 weeks a new request.
- Rule of thumb: We don't want to exceed more than 3 follow ups about the same topic. 
+- Rule of thumb: We don't want to exceed more than 3 follow ups about the same topic.
 - Please do not reopen requests from the previous quarter, even if it's related to the previous topic, it may result in uninteded consequences in regards to our metrics.

 If the customer comes back with additional questions to the AE or RM, please feel free to redirect them to the CSE who had the call previously with the customer.

 ## CSE Useful Link Signpost

-QBR : [Template](https://docs.google.com/presentation/d/1YlEpP81DlZd5rSqKKlxZclHY8ZDT6U1y342QFVt4qhA/edit?usp=sharing) / [CSE Cases Dashboard](https://gitlab.gainsightcloud.com/v1/ui/dashboard#/d7283d4f-4314-4bb8-a3f2-13b32a532ad7) /  [CSE Manager Dashboard](https://gitlab.gainsightcloud.com/v1/ui/dashboard#/b6c9482d-e9b8-4167-951e-f67b908cdf37)  
-**INITIATIVES** : [All Initiatives](https://gitlab.com/gitlab-com/customer-success/customer-success-engineering/scale-cse/-/issues/?sort=created_date&state=opened&label_name%5B%5D=CSE%20Initiative&first_page_size=100) / [Initiatives Needs Help](https://gitlab.com/gitlab-com/customer-success/customer-success-engineering/scale-cse/-/issues/?sort=created_date&state=opened&label_name%5B%5D=CSE%20Initiative%3A%3ANeeds%20Help&first_page_size=100) / [Comments assigned to me](https://drive.google.com/drive/u/1/search?q=followup:actionitems) / [Initiatives Board](https://gitlab.com/gitlab-com/customer-success/customer-success-engineering/scale-cse/-/boards/7715232?label_name[]=CSE%20Initiative)  
-**SIGNPOST** : [Find Product Slack Channels](/handbook/product/categories/features/) / [CS Tools](https://gitlab.com/gitlab-com/cs-tools/gitlab-cs-tools) / [Version Metrics](https://version.gitlab.com/users/sign_in) / [Metrics Dictionary Sheet](https://docs.google.com/spreadsheets/d/1EhSXqx6YXcpqHg2TpS0ZN5Rk_d2hhrTPrW5FTbmuZjw/edit?gid=0#gid=0) + [Tool](https://metrics.gitlab.com/)   
-**1:MANY** : [Adoption Labs Master Decks](https://drive.google.com/drive/u/1/folders/1h-I2J_J4MlgBmjfwxpdGiyVM0vIVW9vY) /  [Webinar Master Recordings](https://drive.google.com/drive/u/1/folders/1x0_7J30cTpfbRXjrXgG_2XOIARLusNt3) / [Webinars Youtube](https://www.youtube.com/playlist?list=PL05JrBw4t0Kpczt4pRtyF147Uvn2bGGvq) / [Scale Webinars Dashboard](https://gitlab.gainsightcloud.com/v1/ui/dashboard#/7b7c1229-e510-490f-9dbe-5c082b4e1c30)  
-**COACH** : [CI Product Coach playbook](https://docs.google.com/document/d/1qUu2JGe9c_KGMaC67z1R5li_5IVFKdyuz2xdFnic97U/edit) / [CI Coach Report](https://docs.google.com/document/d/1LUtRu5EiPES9g9EORrk6poZ6t6Grj1Wqd19CbYepHGM/edit?usp=sharing) / [Security Coach Playbook](https://docs.google.com/document/d/1e1-Ib6lDR61QigylGLmAEWMePorauCWdg2Kb3v4jYLM) / [Pipeline Parser](https://gitlab.com/ci-product-coach-pipeline-parser/pipeline-parser-2-0) / [Security Coach Common Topics & Recommendations](https://docs.google.com/document/d/1li025fruN2shzQr5tVE5Ss0wVnXcIzOMGe9V6aqeuJ4/edit#heading=h.ndg2qmc91wtx)  
+QBR : [Template](https://docs.google.com/presentation/d/1YlEpP81DlZd5rSqKKlxZclHY8ZDT6U1y342QFVt4qhA/edit?usp=sharing) / [CSE Cases Dashboard](https://gitlab.gainsightcloud.com/v1/ui/dashboard#/d7283d4f-4314-4bb8-a3f2-13b32a532ad7) /  [CSE Manager Dashboard](https://gitlab.gainsightcloud.com/v1/ui/dashboard#/b6c9482d-e9b8-4167-951e-f67b908cdf37)
+**INITIATIVES** : [All Initiatives](https://gitlab.com/gitlab-com/customer-success/customer-success-engineering/scale-cse/-/issues/?sort=created_date&state=opened&label_name%5B%5D=CSE%20Initiative&first_page_size=100) / [Initiatives Needs Help](https://gitlab.com/gitlab-com/customer-success/customer-success-engineering/scale-cse/-/issues/?sort=created_date&state=opened&label_name%5B%5D=CSE%20Initiative%3A%3ANeeds%20Help&first_page_size=100) / [Comments assigned to me](https://drive.google.com/drive/u/1/search?q=followup:actionitems) / [Initiatives Board](https://gitlab.com/gitlab-com/customer-success/customer-success-engineering/scale-cse/-/boards/7715232?label_name[]=CSE%20Initiative)
+**SIGNPOST** : [Find Product Slack Channels](/handbook/product/categories/features/) / [CS Tools](https://gitlab.com/gitlab-com/cs-tools/gitlab-cs-tools) / [Version Metrics](https://version.gitlab.com/users/sign_in) / [Metrics Dictionary Sheet](https://docs.google.com/spreadsheets/d/1EhSXqx6YXcpqHg2TpS0ZN5Rk_d2hhrTPrW5FTbmuZjw/edit?gid=0#gid=0) + [Tool](https://metrics.gitlab.com/)
+**1:MANY** : [Adoption Labs Master Decks](https://drive.google.com/drive/u/1/folders/1h-I2J_J4MlgBmjfwxpdGiyVM0vIVW9vY) /  [Webinar Master Recordings](https://drive.google.com/drive/u/1/folders/1x0_7J30cTpfbRXjrXgG_2XOIARLusNt3) / [Webinars Youtube](https://www.youtube.com/playlist?list=PL05JrBw4t0Kpczt4pRtyF147Uvn2bGGvq) / [Scale Webinars Dashboard](https://gitlab.gainsightcloud.com/v1/ui/dashboard#/7b7c1229-e510-490f-9dbe-5c082b4e1c30)
+**COACH** : [CI Product Coach playbook](https://docs.google.com/document/d/1qUu2JGe9c_KGMaC67z1R5li_5IVFKdyuz2xdFnic97U/edit) / [CI Coach Report](https://docs.google.com/document/d/1LUtRu5EiPES9g9EORrk6poZ6t6Grj1Wqd19CbYepHGM/edit?usp=sharing) / [Security Coach Playbook](https://docs.google.com/document/d/1e1-Ib6lDR61QigylGLmAEWMePorauCWdg2Kb3v4jYLM) / [Pipeline Parser](https://gitlab.com/ci-product-coach-pipeline-parser/pipeline-parser-2-0) / [Security Coach Common Topics & Recommendations](https://docs.google.com/document/d/1li025fruN2shzQr5tVE5Ss0wVnXcIzOMGe9V6aqeuJ4/edit#heading=h.ndg2qmc91wtx)
 **DEMO** : [Demo Cloud](https://gitlabdemo.cloud/login) / [Shared Demo Systems Doc](/handbook/customer-success/demo-systems/#access-shared-omnibus-instances) / [Sandbox Cloud](https://gitlabsandbox.cloud/login) / [CS Shared Demo Space](https://gitlab.com/gitlab-learn-labs/webinars)
-**TRAINING** : [DevSecOps Bootcamp Nana](https://techworld-with-nana.teachable.com/courses/enrolled/2186952) / [New CSE Learning Path](https://university.gitlab.com/learn/learning-path/scale-customer-success-engineer-cse-onboarding)  
-**USEFUL APPS** : [Rectangle](https://rectangleapp.com/) / [Amphetamine](https://apps.apple.com/us/app/amphetamine/id937984704?mt=12)  
-**CSE Lunch & Learn Recordings** : [Recordings](https://drive.google.com/drive/folders/1lXYzA4QSFEtR1zr0n7Nby7OYMrUYoVw4) 
+**TRAINING** : [DevSecOps Bootcamp Nana](https://techworld-with-nana.teachable.com/courses/enrolled/2186952) / [New CSE Learning Path](https://university.gitlab.com/learn/learning-path/scale-customer-success-engineer-cse-onboarding)
+**USEFUL APPS** : [Rectangle](https://rectangleapp.com/) / [Amphetamine](https://apps.apple.com/us/app/amphetamine/id937984704?mt=12)
+**CSE Lunch & Learn Recordings** : [Recordings](https://drive.google.com/drive/folders/1lXYzA4QSFEtR1zr0n7Nby7OYMrUYoVw4)
--- a/content/handbook/customer-success/csm/services/_index.md
+++ b/content/handbook/customer-success/csm/services/_index.md
@@ -58,5 +58,5 @@ There are various services a Customer Success Manager will provide to ensure tha
  - Review the [Upgrade Assistance page](https://about.gitlab.com/support/scheduling-upgrade-assistance/) with customers during upgrade planning to ensure a plan is in place (including a rollback strategy) and Support have enough time to review the plan
 - [Infrastructure upgrade coordination](/handbook/customer-success/csm/services/infrastructure-upgrade/) -  CSMs may provide high-level guidance but the technical implementation should ideally be provided by Professional Services via [Dedicated Implementation Services](/services/implementation/enterprise/)
 - Launch best practices
- Review and submit [Support Ticket Attention Requests](/handbook/support/internal-support/support-ticket-attention-requests.html)
+- Review and submit [Support Ticket Attention Requests](/handbook/support/internal-support/support-ticket-attention-requests/)
 - Monitor SaaS based customer experience by adding them to the [Marquee Accounts alerts](https://gitlab.com/gitlab-com/gl-infra/marquee-account-alerts) project
--- a/content/handbook/customer-success/csm/support.md
+++ b/content/handbook/customer-success/csm/support.md
@@ -12,7 +12,7 @@ Define the process for how the CSM interacts with the systems and processes desi

 ## Establishing Customers in Support Systems

-During the onboarding process, the CSM will ensure that customers are correctly established in the support system. GitLab manages support requests through a system called [Zendesk](/handbook/support/workflows/zendesk-instances.html). GitLab has [integrated the GitLab instance of Salesforce with Zendesk](/handbook/support/workflows/zendesk_organizations_and_users_overview/) to facilitate the establishment of users in Zendesk. The integration synchronizes account-level data so that the Zendesk ticket has accurate information on the customers' purchase of products that include support.
+During the onboarding process, the CSM will ensure that customers are correctly established in the support system. GitLab manages support requests through a system called [Zendesk](/handbook/support/workflows/zendesk-instances/). GitLab has [integrated the GitLab instance of Salesforce with Zendesk](/handbook/support/workflows/zendesk_organizations_and_users_overview/) to facilitate the establishment of users in Zendesk. The integration synchronizes account-level data so that the Zendesk ticket has accurate information on the customers' purchase of products that include support.

 Though automation exists, the CSM must still ensure customers take additional steps to fully establish their personnel in Zendesk. Specifically, the CSM must work with the customer to establish specific Zendesk users under the Zendesk Account so that tickets submitted by the customer's personnel are guided by the GitLab support team's [Service Level Agreements (SLAs)](https://about.gitlab.com/support/#gitlab-support-service-levels).

@@ -100,7 +100,7 @@ In the email notifying CSMs of new tickets, the included Zendesk ticket link cur

 ## Provide Customer Feedback on Support Tickets

-Sometimes CSMs receive feedback on a support ticket from a customer via email. This feedback can be positive or negative. You can feed back that information to the support management team by following the instructions under points 3 and 4 in the [Sources of feedback](/handbook/support/workflows/how-to-respond-to-feedback.html#sources-of-feedback) section of the Support Satisfaction (SSAT) workflow documentation. The SSAT Reviewing Manager will pick up and action the feedback.
+Sometimes CSMs receive feedback on a support ticket from a customer via email. This feedback can be positive or negative. You can feed back that information to the support management team by following the instructions under points 3 and 4 in the [Sources of feedback](/handbook/support/workflows/how-to-respond-to-feedback/#sources-of-feedback) section of the Support Satisfaction (SSAT) workflow documentation. The SSAT Reviewing Manager will pick up and action the feedback.

 As described at that link, support already collects feedback via an automatic email survey and a mid-ticket feedback link. It can be helpful to remind customers about these options from time to time. You'll still see the feedback when reviewing a customer's support tickets prior to cadence calls.


--- a/content/handbook/customer-success/csm/workshops.md
+++ b/content/handbook/customer-success/csm/workshops.md
@@ -45,13 +45,13 @@ The following are already developed, have been given to multiple customers and a
 - **WebIDE and Markdown** *(for anyone looking to make changes to code or Pages)* - Covers what you can do with the built-in GitLab WebIDE to make changes to code, files, Pages directly from the GitLab web UI, as well as tips & tricks you can do with GitLab markdown in issues, merge requests, epics, Pages, etc.
 - **Git Basics** *(for those who want to contribute on their local machine)* - Focuses on the command line interface into GitLab that a developer may need to pull/push code to/from the GitLab server
 - **CI/CD Basics** *(for those who want to learn about automated build/test/deploy pipelines)* - Covers the basics of how to set up a pipeline to build, test, and deploy your code
- [**Advanced CI/CD**](/handbook/customer-success/workshops/ci-workshop.html) *(for those interested in learning more about CI/CD)* - Requires basic CI/CD knowledge and covers advanced topics such as includes/extends, rules, child pipelines, and more (specific content will be curated)
+- [**Advanced CI/CD**](/handbook/customer-success/workshops/ci-workshop/) *(for those interested in learning more about CI/CD)* - Requires basic CI/CD knowledge and covers advanced topics such as includes/extends, rules, child pipelines, and more (specific content will be curated)
 - [**GitLab Security and Compliance**](/handbook/customer-success/workshops/secure/) *(for security, developers, managers, and PMs)* - Covers an overview of the security features including how developers see the scan results in the merge request and how security teams can review the results in the Security Dashboard
 - [**DevSecOps Adoption Path**](https://gitlab.highspot.com/items/636013fdcba3439c837f10d7?lfrm=ssrp.1#1) *(for security & developers)* - A prescriptive and curated route to adopting GitLab Secure scanners to get the most ROI as quickly as possible with Secure. This is a great workshop for customers who are struggling with Secure adoption or are just beginning their journey on Ultimate and using GitLab Secure.
 - **GitLab as a PM tool** *(for PMs, scrum masters, team leads, developers)* - Focuses on organization and use of epics, sub-epics, roadmaps, issues, labels, milestones, and boards
 - **Issue, labels, and boards** *(for those interested in learning more about GitLab PM)* - Covers more tips & tricks on issues, labels, and boards and is good follow-on after the PM session
 - **DevOps Metrics with GitLab** *(for managers, PMs, team leads)* - Goes over what the DORA4 metrics are, why it is useful to track them, and what is available in GitLab
- [**Innersourcing with GitLab**](/handbook/customer-success/workshops/innersource-workshop.html) *(for teams interested in starting code-sharing initiatives internally)* - Goes over what is innersourcing, why it is useful, and what are the key things needed for success, followed by how to get started in GitLab
+- [**Innersourcing with GitLab**](/handbook/customer-success/workshops/innersource-workshop/) *(for teams interested in starting code-sharing initiatives internally)* - Goes over what is innersourcing, why it is useful, and what are the key things needed for success, followed by how to get started in GitLab
 - **GitOps with GitLab** *(for teams looking to use GitLab for Infrastructure as Code)* - Goes over what is GitOps, how it is more than just Infrastructure as Code, what are the benefits, and how to get started with GitLab
 - **GitLab Administration** *(for GitLab Admins of self-managed instances)* - Goes over GitLab components and architecture, installs, upgrades, admin area of the UI, common CLI commands, and back-ups
 - **Permissions & Access with GitLab** *(for GitLab Admins of self-managed instances)* - Goes over permission access at the Group, Subgroup, Project, and Member levels, and discusses how to effectively tie access in with supported authentication protocols for on and offboarding
@@ -69,7 +69,7 @@ If you are interested in a session that doesn't exist yet, but you're not able o

 CSMs should offer sessions early during onboarding, and whenever working on a stage enablement. If the customer wants a session on a topic we do not already have slides for, request more time to prepare, and then work with the Customer Success team to help pull together some slides for the session. Then the newly created session can be added to the list of existing sessions available to other CSMs.

-It is recommended to invite another GitLab team member to the session to help with notes, audience management (including obtaining screenshots of audience participants), and Q&A. This helper could be the Solutions Architect or Account Executive for the account, or it could be a fellow CSM. 
+It is recommended to invite another GitLab team member to the session to help with notes, audience management (including obtaining screenshots of audience participants), and Q&A. This helper could be the Solutions Architect or Account Executive for the account, or it could be a fellow CSM.

 Consider the typical length of the session when scheduling. It is recommended to coordinate with your champion on the following information:

@@ -112,7 +112,7 @@ Similar to taking notes in a cadence call, it is useful to add to your running n
 ### Best Practices for Note-Taking & Planning

 - Write down your *agenda* (including questions you want to ask). This way you can quickly add your notes for the specific context.
- If you're comfortable writing in [Markdown format](/handbook/markdown-guide/), use it to quickly structure your notes in real time.
+- If you're comfortable writing in [Markdown format](https://handbook.gitlab.com/docs/markdown-guide/), use it to quickly structure your notes in real time.
 - Allow yourself time directly after the call to clean up your notes. Avoid scheduling back-to-back meetings.
 - Practice slowing down call conversations. Stopping the dialog for a few seconds to say "let me write that down" tells the customer what they said is important to you.
 - Ask your SAE/AE/SA to take notes with you. After the meeting combine and add detail.

--- a/content/handbook/customer-success/demo-systems/_index.md
+++ b/content/handbook/customer-success/demo-systems/_index.md
@@ -143,7 +143,7 @@ Historically, there has not been a consistent set of demo data. Each of our Solu

 See the handbook page for [Demo Readiness](/handbook/solutions-architects/demonstrations/#demo-readiness) and [Existing Demonstrations](/handbook/solutions-architects/demonstrations/#existing-demonstrations) to get started.

-Please see the <a href="https://gitlab.com/gitlab-com/customer-success/solutions-architecture-leaders/sa-initiatives/-/issues">Solutions Architecture Initiatives issue tracker</a> for more information on the crowd sourced OKRs that are in progress and the development of our [Communities of Practice](/handbook/customer-success/initiatives/communities-of-practice.html).
+Please see the <a href="https://gitlab.com/gitlab-com/customer-success/solutions-architecture-leaders/sa-initiatives/-/issues">Solutions Architecture Initiatives issue tracker</a> for more information on the crowd sourced OKRs that are in progress and the development of our [Communities of Practice](/handbook/customer-success/initiatives/communities-of-practice/).

 ## Projects and Code Repositories

@@ -197,7 +197,7 @@ The Demo Systems v1 repositories can be found in [gitlab.com/gitlab-com/customer
 ### Handbook Links for Related Infrastructure

 - [GitLab Sandbox Cloud](/handbook/company/infrastructure-standards/realms/sandbox/)
- [GitLab Infrastructure Standards](/handbook/infrastructure-standards/)
+- [GitLab Infrastructure Standards](/handbook/company/infrastructure-standards/)
 - [GitLab Infrastructure Standards - Labels and Tags](/handbook/company/infrastructure-standards/labels-tags/)
 - [Demo Systems Kubernetes Architecture Docs](/handbook/customer-success/demo-systems/infrastructure/kubernetes/)
 - [Demo Systems Network Architecture and Subnet Docs](/handbook/customer-success/demo-systems/infrastructure/networking/)

--- a/content/handbook/customer-success/education-enablement.md
+++ b/content/handbook/customer-success/education-enablement.md
@@ -361,6 +361,6 @@ If you want to share an answer in a direct message you'll need to create a group
 - [Field Enablement Handbook Page](/handbook/sales/field-operations/field-enablement/)
 - [Field Accreditation Handbook Page](/handbook/sales/training/field-certification/)
 - [Sales Training](/handbook/sales/training/)
- [Communities of Practice](/handbook/customer-success/initiatives/communities-of-practice.html)
+- [Communities of Practice](/handbook/customer-success/initiatives/communities-of-practice/)
 - [Learn at GitLab](https://about.gitlab.com/learn/)
 - [GitLab Releases](https://about.gitlab.com/releases/)
--- a/content/handbook/customer-success/playbooks/_index.md
+++ b/content/handbook/customer-success/playbooks/_index.md
@@ -61,9 +61,9 @@ The following playbooks are aligned to our [customer adoption journey](/handbook
 | Usage Data Enablement                                           | Manual           | Lifecycle       | [Service Ping FAQ](/handbook/customer-success/csm/service-ping-faq/)                                               |
 | Agile Enablement Stage Adoption                                 | Manual           | Objective       |                                                              |
 | Agile Expansion Stage Enablement                                | Manual           | Objective       |                                                              |
-| CD Enablement Stage Adoption                                    | Manual           | Objective       | [Continuous Delivery/Release](/handbook/customer-success/playbooks/cd-release.html)                                  |
+| CD Enablement Stage Adoption                                    | Manual           | Objective       | [Continuous Delivery/Release](/handbook/customer-success/playbooks/cd-release/)                                  |
 | CD Expansion Stage Adoption                                     | Manual           | Objective       |                                                              |
-| CI Enablement Stage Adoption                                    | Manual           | Objective       | [Continuous Integration/Verify](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/ci/) <br> [CSM CI Workshop](/handbook/customer-success/playbooks/ci-verify.html)               |
+| CI Enablement Stage Adoption                                    | Manual           | Objective       | [Continuous Integration/Verify](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/ci/) <br> [CSM CI Workshop](/handbook/customer-success/playbooks/ci-verify/)               |
 | CI Expansion Stage Adoption                                     | Manual           | Objective       |                                                              |
 | Configure Enablement Stage Adoption                             | Manual           | Objective       |                                                              |
 | Configure Expansion Stage Adoption                              | Manual           | Objective       |                                                              |

--- a/content/handbook/customer-success/product-usage-data/use-case-adoption/index.md
+++ b/content/handbook/customer-success/product-usage-data/use-case-adoption/index.md
@@ -130,7 +130,7 @@ Due to equal weighting and Gainsight's defined scoring ranges, two (2) of the th
 ## Limitations

 1. Some customers have been given an exception for sending usage data.
-   1. [Cloud licensing and the support exemption process explained](/handbook/support/license-and-renewals/workflows/self-managed/cloud-licensing.html)
+   1. [Cloud licensing and the support exemption process explained](/handbook/support/license-and-renewals/workflows/self-managed/cloud-licensing/)
   1. [INTERNAL - Customer Availability, Eligibility & Opt-Out](https://internal.gitlab.com/handbook/product/fulfillment/cloudlicensing/cloud-licensing/#customer-availability-eligibility--opt-out)
   1. [Cloud Licensing Adoption Dashboard](https://10az.online.tableau.com/#/site/gitlab/views/WIPCloudLicensingPOC/CloudLicensingAdoption?:iid=1)
   1. **Resolution**: Exceptions are considered valid reasons for a customer to not be sending data. However, we have made more exceptions than planned and will be working on enablement on removing exceptions at time of renewal wherever possible.

--- a/content/handbook/customer-success/professional-services-engineering/education-services/fg-gitlabcicd.md
+++ b/content/handbook/customer-success/professional-services-engineering/education-services/fg-gitlabcicd.md
@@ -11,7 +11,7 @@ description: "This Facilitator Guide is intended to walk you through all importa

 1. Instructor Slides: Follow the link in your instructor kit provided by your organization from within the EdCast Marketplace.
 2. Hands On Lab Environment: Use these [GitLab Template Projects VM Builds](https://gitlab.com/gitlab-com/customer-success/professional-services-group/partner-training-template-projects/gitlab-cicd-hands-on-demo)
-3. [Hands On Guide](/handbook/customer-success/professional-services-engineering/education-services/gitlabcicdhandson.html)
+3. [Hands On Guide](/handbook/customer-success/professional-services-engineering/education-services/gitlabcicdhandson/)
 4. [Remote Sessions Tips and Tricks](/handbook/customer-success/professional-services-engineering/remote-training-tips/)

 ### For GitLab Team Members and Contractors
@@ -23,7 +23,7 @@ description: "This Facilitator Guide is intended to walk you through all importa
   - Save  your copy in the applicable [client folder](https://drive.google.com/drive/u/0/folders/1ozPKiAlUzbKwpkscaYVTp9PVoi9hWm4U)

 2. Hands On Lab Environment: Use the sample projects located in the GitLab Demo Cloud
-3. [Hands On Guide](/handbook/customer-success/professional-services-engineering/education-services/gitlabcicdhandson.html)
+3. [Hands On Guide](/handbook/customer-success/professional-services-engineering/education-services/gitlabcicdhandson/)
 4. [Remote Sessions Tips and Tricks](/handbook/customer-success/professional-services-engineering/remote-training-tips/)

 ## Things to do Ahead
@@ -37,7 +37,7 @@ description: "This Facilitator Guide is intended to walk you through all importa
   2. Test each hands-on activity in the lab environment
 3. Websites to have up prior to class:
    1. [Related GitLab Docs pages](https://docs.gitlab.com/ee/ci/)
-    2. [Hands on Guide](/handbook/customer-success/professional-services-engineering/education-services/gitlabcicdhandson.html)
+    2. [Hands on Guide](/handbook/customer-success/professional-services-engineering/education-services/gitlabcicdhandson/)
    3. Lab environments
 4. Slide Check
    1. Make sure you can access the slides with presenter notes

--- a/content/handbook/customer-success/professional-services-engineering/processes/professional-services-delivery-methodology/gitlab-best-practices/_index.md
+++ b/content/handbook/customer-success/professional-services-engineering/processes/professional-services-delivery-methodology/gitlab-best-practices/_index.md
@@ -124,7 +124,7 @@ Scenarios in which the final approver might not merge an MR:

 If any of these scenarios occurs, an MR author may merge their own MR if it has all required approvals and they have merge rights to the repository. This is also in line with the GitLab [bias for action](../../../../../values/_index.md#operate-with-a-bias-for-action) value.

-This policy is in place to satisfy the CHG-04 control of the GitLab [Change Management Controls](/handbook/security/change-management-policy.html).
+This policy is in place to satisfy the CHG-04 control of the GitLab [Change Management Controls](/handbook/security/change-management-policy/).

 To implement this policy in gitlab-org/gitlab, we have enabled the following settings to ensure MRs get an approval from a top-level CODEOWNERS maintainer:


--- a/content/handbook/customer-success/professional-services-engineering/workflows/internal/15minute-standup.md
+++ b/content/handbook/customer-success/professional-services-engineering/workflows/internal/15minute-standup.md
@@ -3,4 +3,4 @@ title: 15-minute Standup
 category: Internal
 ---

-See [Standing Calls](/handbook/customer-success/professional-services-engineering/workflows/project_execution/calls.html)
+See [Standing Calls](/handbook/customer-success/professional-services-engineering/workflows/project_execution/calls/)
--- a/content/handbook/customer-success/professional-services-engineering/workflows/process.md
+++ b/content/handbook/customer-success/professional-services-engineering/workflows/process.md
@@ -7,21 +7,21 @@ title: Process
 ## Project Process

 1. **Manager, Professional Services**: Once an SOW has been approved and moved for **Closed Won**, assign a Professional Services Engineer.
-1. **Manager, Professional Services**: Send [welcome e-mail](/handbook/customer-success/professional-services-engineering/workflows/project_execution/welcome-email.html)
+1. **Manager, Professional Services**: Send [welcome e-mail](/handbook/customer-success/professional-services-engineering/workflows/project_execution/welcome-email/)
 1. **Professional Services Engineer**: Begins project with processes defined here.

-   - [Kick-off](/handbook/customer-success/professional-services-engineering/workflows/project_execution/kick-off.html)
-   - Intake for [AWS](/handbook/customer-success/professional-services-engineering/workflows/intake/aws.html) or [on-prem](/handbook/customer-success/professional-services-engineering/workflows/intake/on-prem.html)
-   - [On-going project calls (external)](/handbook/customer-success/professional-services-engineering/workflows/project_execution/calls.html)
+   - [Kick-off](/handbook/customer-success/professional-services-engineering/workflows/project_execution/kick-off/)
+   - Intake for [AWS](/handbook/customer-success/professional-services-engineering/workflows/intake/aws/) or [on-prem](/handbook/customer-success/professional-services-engineering/workflows/intake/on-prem/)
+   - [On-going project calls (external)](/handbook/customer-success/professional-services-engineering/workflows/project_execution/calls/)
   - [On-going internal project updates](/handbook/customer-success/professional-services-engineering/workflows/internal/15minute-standup.html)
   - [Change request when required for scope changes](https://docs.google.com/document/d/1aBKeyui9qCt9YoVtZg-Z7XRkNpomTa-H3KRPBLnt6TQ/edit?usp=sharing)
-   - [Project Summary](/handbook/customer-success/professional-services-engineering/workflows/project_execution/project-summary.html)
+   - [Project Summary](/handbook/customer-success/professional-services-engineering/workflows/project_execution/project-summary/)

-1. **Professional Services Engineer**: Starts [financial wrap-up](/handbook/customer-success/professional-services-engineering/workflows/internal/financial-wrapup.html) process.
-1. **Manager, Professional Services**: Schedule [blameless post-mortem](/handbook/customer-success/professional-services-engineering/workflows/internal/root-cause-analysis.html)
+1. **Professional Services Engineer**: Starts [financial wrap-up](/handbook/customer-success/professional-services-engineering/workflows/internal/financial-wrapup/) process.
+1. **Manager, Professional Services**: Schedule [blameless post-mortem](/handbook/customer-success/professional-services-engineering/workflows/internal/root-cause-analysis/)

 ## Quote to Sign-off Process

 This is an overview of the entire process for a services engagement from discovery of the customer's needs to the sign-off from the customer.

-See [Professional Services Business Operations](/handbook/customer-success/professional-services-engineering/workflows/internal/biz-ops.html)
+See [Professional Services Business Operations](/handbook/customer-success/professional-services-engineering/workflows/internal/biz-ops/)
--- a/content/handbook/engineering/_index.md
+++ b/content/handbook/engineering/_index.md
@@ -49,13 +49,13 @@ Work in the 40% time budget should be coordinated and prioritized by the Enginee
 Some of the above examples for the 40% time budget can help in forming a long-term technical roadmap for your group, and determine how best to prioritize your technical work to support overall business goals. In addition to the examples above:

 - Ask yourself these questions
-  - What are your most frequent sources of delays? (Could be long-standing tech debt you have to work past while developing, could be lack of reviewers for your domain, could be external to your team like with pipeline duration) 
+  - What are your most frequent sources of delays? (Could be long-standing tech debt you have to work past while developing, could be lack of reviewers for your domain, could be external to your team like with pipeline duration)
  - Do you have any consistently similar bugs or security issues that come in due to a certain area?
  - Has your team been talking about potentially refactoring any areas?
  - Is your team struggling with certain processes?
  - Have you had recent incidents that allude to a larger problem?
  - Are you getting frequent requests for help in some area?
-  - Is your team frequently missing their deliverable commitments? What would help? 
+  - Is your team frequently missing their deliverable commitments? What would help?
  - Does your area have performance (slow endpoints, inconsistent responses, intermittent errors) or scalability (the feature or area as-is will not scale) concerns?
  - Where do you see the biggest instability? Have you talked to operations and support about feedback for  your area?
  - Do you have application or rate limits in the right places?
@@ -67,13 +67,13 @@ Some of the above examples for the 40% time budget can help in forming a long-te
  - Do you have adequate telemetry , logging, monitoring of your features?
  - Do you have adequate error handling and error codes that allows fast and easy diagnostics?
 - Gather data like this
-  - Master:Broken issues 
+  - Master:Broken issues
  - ~"severity::1" and ~"severity::2"  bugs
  - Missed-Slo issues
  - Flaky test issues
  - ~"type::maintenance" issues
 - Think about the future state of your product
-  - Where do you want your product to be this time next year? 
+  - Where do you want your product to be this time next year?
  - What are the technical requirements to achieve that?
  - What are technical topics that would benefit from research/POCs?
  - What would make it easier for you to achieve that if it was no longer a factor?
@@ -178,7 +178,7 @@ There are five departments within the Engineering Division:

 ### GitLab in Production

- [Workflow Diagram](/handbook/engineering/workflow/related-workflows.html)
+- [Workflow Diagram](/handbook/engineering/workflow/related-workflows/)
 - [Error Budgets](/handbook/engineering/error-budgets/)
 - [Performance of GitLab](/handbook/engineering/performance/)
 - [Monitoring of GitLab.com](/handbook/engineering/monitoring/)
@@ -211,7 +211,7 @@ To maintain high availability, Engineering runs a weekly SaaS Availability stand

 Each week the Infrastructure team reports on incidents and key metrics. Updating these items at the top of the
 [Engineering Allocation Meeting Agenda](https://docs.google.com/document/d/1Zk3qgbn8iDyJRq0i5C5LPBgEopY6o1tpYEKfdNfA9Bg/edit#heading=h.5t67v3au7sd4)
-is the responsibility of the Engineering Manager for the [General Squad](/handbook/engineering/infrastructure/team/reliability/#general-squad) in Reliability.
+is the responsibility of the Engineering Manager for the [General Squad](/handbook/engineering/infrastructure/team/) in Reliability.

 1. Incident Review
   - Include any [S1 incidents](https://gitlab.com/gitlab-com/gl-infra/production/-/issues/?sort=created_date&state=all&label_name%5B%5D=incident&label_name%5B%5D=severity%3A%3A1&first_page_size=100) that have occurred since the previous meeting.

--- a/content/handbook/engineering/automation.md
+++ b/content/handbook/engineering/automation.md
@@ -15,7 +15,7 @@ Automations for the `gitlab-org` group and projects under it can be split into t
 * Automation via API within a project: a [project access token](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens) is sufficient.
 * Automation via API within a group: a [group access token](https://docs.gitlab.com/ee/user/group/settings/group_access_tokens.html) is sufficient.

-These guidelines ensure consistency for Engineering automation using approved secure patterns aligned with [least privileged access principle](/handbook/security/access-management-policy.html#least-privilege-reviews-for-access-requests).
+These guidelines ensure consistency for Engineering automation using approved secure patterns aligned with [least privileged access principle](/handbook/security/access-management-policy/#least-privilege-reviews-for-access-requests).

 ### Merge request automation guidelines