Merge branch 'update-links-following-migration' into 'main'

Update link following migration of acquisitions and use-cases

See merge request !1390

content/handbook/acquisitions/acquisition-process/_index.md

@@ -268,7 +268,7 @@ Each quarter the Corporate Development team defines a set of [three categories](
 Although we have our quarterly focus areas, we are open to discussing and potentially pursuing an opportunity outside of those focus areas. For us to look into an opportunity outside of our quarterly focus areas, it needs to satisfy one, or more, of the following criteria:
 1. Present an outsized revenue potential
 1. Serve as a strategic move (market dynamics etc.)
-1. Fit our [soft-landing framework](https://about.gitlab.com/handbook/acquisitions/#acquisition-approach)
+1. Fit our [soft-landing framework](/handbook/acquisitions/#acquisition-approach)
 
 Every opportunity we explore is constantly evaluated against our prioritization as well as our bandwidth (including active engagements).
 

content/handbook/alliances/_index.md

@@ -115,4 +115,4 @@ Alliance Partners may be eligible for NFR (not for resale) licenses to develop a
 
 **Acquisitions**
 
-If you are a Partner interested in inquiring about a potential acquisition of your company please visit our [acquisition handbook](https://about.gitlab.com/handbook/acquisitions/).
+If you are a Partner interested in inquiring about a potential acquisition of your company please visit our [acquisition handbook](/handbook/acquisitions/).

content/handbook/company/culture/all-remote/remote-compensation.md

@@ -39,7 +39,7 @@ Our co-founder and CEO Sid Sijbrandij discusses this in a blog post entitled "[W
 
 Particularly in comparison to companies in cities with high costs of living, such as London, San Francisco, Singapore, Sydney, etc., an all-remote company realizes [a notable set of advantages]({{< ref "compensation#why-we-pay-local-rates" >}}) by hiring brilliant minds in locales with lower costs of living.
 
-Funds that would be reserved for salaries — necessary to compete in hot labor markets — can be redirected to areas such as [research and development](https://about.gitlab.com/blog/2018/06/12/how-ux-research-impacts-product-decisions/) (R&D), [acquisitions](https://about.gitlab.com/handbook/acquisitions/), and [hiring more people](https://about.gitlab.com/jobs/).
+Funds that would be reserved for salaries — necessary to compete in hot labor markets — can be redirected to areas such as [research and development](https://about.gitlab.com/blog/2018/06/12/how-ux-research-impacts-product-decisions/) (R&D), [acquisitions](/handbook/acquisitions/), and [hiring more people](https://about.gitlab.com/jobs/).
 
 These additional investments can be made simply by lowering a company's overall spend on compensation, but only if a company is willing to hire in locales where a dollar goes farther than the [SF Benchmark](/handbook/total-rewards/compensation/compensation-calculator#sf-benchmark).
 

content/handbook/customer-success/_index.md

@@ -182,7 +182,7 @@ Customer Success team members maintain a [FAQ](https://about.gitlab.com/handbook
 - [EE Product Qualification Questions](https://about.gitlab.com/handbook/sales/qualification-questions/)
 - [GitLab Positioning](https://about.gitlab.com/handbook/positioning-faq/)
 - [FAQ from prospects](https://about.gitlab.com/handbook/sales/faq-from-prospects/)
-- [Client Use Cases](https://about.gitlab.com/handbook/use-cases/)
+- [Client Use Cases](/handbook/use-cases/)
 - [Proof of Value Guidelines](https://about.gitlab.com/handbook/customer-success/solutions-architects/tools-and-resources/pov)
 - [Account Planning Template for Large/Strategic Accounts](https://docs.google.com/presentation/d/1yQ6W7I30I4gW5Vi-TURIz8ZxnmL88uksCl0u9oyRrew/edit?ts=58b89146#slide=id.g1c9fcf1d5b_0_24))
 - [Sales Demo](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/demo/)

content/handbook/customer-success/csm/success-plans/questions-techniques.md

@@ -27,7 +27,7 @@ Asking open-ended questions is the most effective way to get clarity from the cu
 
 The most straightforward and open-ended approach to starting a conversation about stage adoption, growth, and strategic objectives is something to the effect of:
 
-> "So I know right now you're using [[use cases](https://about.gitlab.com/handbook/use-cases/) in use, such as SCM, CI, etc.] - where can we go from here to maximize your success and value?"
+> "So I know right now you're using [[use cases](/handbook/use-cases/) in use, such as SCM, CI, etc.] - where can we go from here to maximize your success and value?"
 
 This question creates an opening to explore driving additional value for the customer, with the customer leading.  From here, we can explore with the customer use cases or features they're interested in knowing more about, business problems they could solve using GitLab, or anything else related to GitLab or DevSecOps. This one question also sets you up for more targeted follow-ups.
 

content/handbook/customer-success/playbooks/cd-release.md

@@ -49,5 +49,5 @@ The following are recommended questions for discovering customer needs.
 
 ### Learning Resources
 
-- [Customer Use Case CD](https://about.gitlab.com/handbook/use-cases/#2-software-delivery-automation)
+- [Customer Use Case CD](/handbook/use-cases/#2-software-delivery-automation)
 - CS Skills Exchange: CD Deep Dive: coming soon

content/handbook/hiring/talent-acquisition-framework/acquisitions.md

@@ -15,7 +15,7 @@ An acquisition hire is any hire which was made as a direct result of acquisition
 
 1. Create a slack channel with #acq-talent-acquisition-(acquisition project name), add all relevant team members to the channel and provide specific details on the confidential nature of the acquisition.
 1. Notify the Talent Acquisition Manager/Lead of the need to process candidates as part of the acquisition at least 2 weeks before (where there are 3+ candidates) the final decision on the candidates needs to be made.
-1. Provide the details of the team they will be joining, the interview process if different from our [Standard Interview process]({{< ref "interviewing" >}}), the hiring manager an director responsible for the process. For engineering candidates joining the process is an abbreviated one to our standard one as described on our [acquisition process](https://about.gitlab.com/handbook/acquisitions/acquisition-process#early-diligence)
+1. Provide the details of the team they will be joining, the interview process if different from our [Standard Interview process]({{< ref "interviewing" >}}), the hiring manager an director responsible for the process. For engineering candidates joining the process is an abbreviated one to our standard one as described on our [acquisition process](/handbook/acquisitions/acquisition-process#early-diligence)
 1. Talent Acquisition Manager/Lead to gain a dummy [GHP ID](/handbook/finance/financial-planning-and-analysis/#headcount-and-the-talent-acquisition-single-source-of-truth)
 1. Talent Acquisition Manager/Lead will open a Requisition in Greenhouse that will house all the acquisition candidates.
 1. Talent Acquisition Manager will assign the Requisition to a Recruiter who will manage the Interview process.

content/handbook/leadership/mitigating-concerns.md

@@ -174,7 +174,7 @@ We can address this concern by:
 ### Technical debt ineffectively managed
 
 This is especially a problem if there are acquisitions of new technologies.
-We address this for acquired technology by having [acquired organizations](https://about.gitlab.com/handbook/acquisitions/) remake their functionality inside our [single application](/handbook/product/single-application/).
+We address this for acquired technology by having [acquired organizations](/handbook/acquisitions/) remake their functionality inside our [single application](/handbook/product/single-application/).
 
 Otherwise, we have a [clear and consistent prioritization framework across engineering](https://about.gitlab.com/handbook/engineering/development/principles/#prioritizing-technical-decisions) and [product](/handbook/product/product-processes/#how-we-prioritize-work) that helps ensure we are continuously making progress on the most important issues.
 
@@ -194,7 +194,7 @@ As we continue to grow and potentially acquire additional companies, we want to
 
 In order to address this concern:
 
-- Follow our [acquisition strategy](https://about.gitlab.com/handbook/acquisitions/#acquisition-strategy)
+- Follow our [acquisition strategy](/handbook/acquisitions/#acquisition-strategy)
 - For Engineering, the deciding factor is whether the senior-most technical stakeholder--who is not a founder--is on board or not. Because this person will either get the engineers on board or foment resistance.
 
 ### Inability to respond to technological change

content/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/asset_inventory.md

@@ -118,7 +118,7 @@ Accepted field descriptions are (fields in bold are required):
    date_published*:                    (month and year content first published. In iso-date format. eg 2020-05)
    last_changed                        (date the asset was last changed)
    gitlab_release:                     (major.minor GitLab release # the asset is built about/on. eg 12.10)
-   use_case*:                          (use case the asset focuses on. [Derived from customer use case page](https://about.gitlab.com/handbook/use-cases/). Acceptable values are:   )
+   use_case*:                          (use case the asset focuses on. [Derived from customer use case page](/handbook/use-cases/). Acceptable values are:   )
       - vcc
       - ci
       - cd

content/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/_index.md

@@ -12,7 +12,7 @@ title: Solutions Go-to-market
 
 Solutions are a product or suite or products and services that business purchase to solve business problems. They are typically categorized into 3 buckets that address
 
-1. Market segment requirements (e.g. DevOps platform solution). Ours are outlined below with more details [here](https://about.gitlab.com/handbook/use-cases/)
+1. Market segment requirements (e.g. DevOps platform solution). Ours are outlined below with more details [here](/handbook/use-cases/)
 1. Industries/verticals requirements (e.g. Pub Sec, High Tech, Retail)
 1. Business segment requirements (e.g. enterprise vs SMB)
 

content/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/data-science/_index.md

@@ -23,7 +23,7 @@ Common challenges in data science are described on the [Data Science with GitLab
 - Streamline testing and validation of work, making it much faster and more repeatable
 - Simplify infrastructure management and often across multiple cloud providers
 
-To be fleshed out as with [other usecases](https://about.gitlab.com/handbook/use-cases/).
+To be fleshed out as with [other usecases](/handbook/use-cases/).
 
 #### [Keywords and definitions](./keywords/)
 

content/handbook/marketing/developer-relations/technical-marketing/_index.md

@@ -37,7 +37,7 @@ You can find the content we create in the following places:
 To make a request of the Technical Marketing team please follow the [content request process](/handbook/marketing/developer-relations/content-request/) for the Developer Relations team. 
 
 ## Prioritizing work
-Our work is mainly driven and prioritized by the following Marketing defined [Core DevOps Solutions](https://about.gitlab.com/handbook/use-cases/) and can be tracked on the [Solutions Go-to-market](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/). Specifically, our deliverables contributing to this effort are sorted by priority below (subject to change).
+Our work is mainly driven and prioritized by the following Marketing defined [Core DevOps Solutions](/handbook/use-cases/) and can be tracked on the [Solutions Go-to-market](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/). Specifically, our deliverables contributing to this effort are sorted by priority below (subject to change).
 
 * Analyst Demos/Analyst Evaluations
 * Core Solutions Demos

content/handbook/marketing/plan-fy22.md

@@ -157,7 +157,7 @@ _The list below includes potential and recommended items to include in a GTM Mot
 
 ## Solution GTM Strategy
 
-The GTM Strategy doc includes the background market information to illustrates the context and personas experiencing a problem that attracts budget and describes how our solution meets that need. GTM strategy docs, also refered to as [Use Case GTM pages](https://about.gitlab.com/handbook/use-cases/), are kept in the handbook.
+The GTM Strategy doc includes the background market information to illustrates the context and personas experiencing a problem that attracts budget and describes how our solution meets that need. GTM strategy docs, also refered to as [Use Case GTM pages](/handbook/use-cases/), are kept in the handbook.
 
 ## GTM Motion Campaign
 {: #gtm-motion-campaign .gitlab-purple}

content/handbook/product/categories/_index.md

@@ -95,7 +95,7 @@ E.g Link the marketing page. If there's no marketing page, link to the docs. If
 
 #### Solutions
 
-[Solutions](https://about.gitlab.com/handbook/use-cases/) can consist of multiple categories and are typically used to align to a customer challenge (e.g. the need to reduce security and compliance risk) or to market segments defined by analysts such as Software Composition Analysis (SCA). Solutions are also often used to align to challenges unique to an industry vertical (e.g. financial services), or to a sales segment (e.g. SMB vs Enterprise).
+[Solutions](/handbook/use-cases/) can consist of multiple categories and are typically used to align to a customer challenge (e.g. the need to reduce security and compliance risk) or to market segments defined by analysts such as Software Composition Analysis (SCA). Solutions are also often used to align to challenges unique to an industry vertical (e.g. financial services), or to a sales segment (e.g. SMB vs Enterprise).
 
 Solutions typically represent a customer challenge, and we define how GitLab capabilities come together to meet that challenge, with business benefits of using our solution.
 

content/handbook/product/product-processes/_index.md

@@ -204,7 +204,7 @@ In order to support [findability](/handbook/values/#findability) and to clearly
 Some **internal** methods for communication include:
 
 - Sharing the updates various product-based Slack channels such as: `#product`, `#s_`, `#g_`, or `#f_` Slack channels
-- Cross-posting changes in direction or categories into #customer-success and if they impact [use cases](https://about.gitlab.com/handbook/use-cases/) tag `@cs-leadership` for awareness
+- Cross-posting changes in direction or categories into #customer-success and if they impact [use cases](/handbook/use-cases/) tag `@cs-leadership` for awareness
 - Recording a quick video and sharing with Customer Success that discusses direction updates. Use sync meetings [as needed](/handbook/company/culture/all-remote/asynchronous/#when-to-start-synchronous-first) to facilitate efficient communication.
 - [Collaborate with the Field Communications team](https://about.gitlab.com/handbook/sales/field-communications/#field-communications-playbook) to determine if a larger internal communications plan/approach is necessary for the Field (Sales, Customer Success, Channel & Alliances) team.
 - Aggregating and sharing highlights of monthly direction page updates at the Section-level across the organization

content/handbook/sales/_index.md

@@ -36,7 +36,7 @@ description: "The GitLab Field team includes multiple functions: Enterprise Sale
 | **Field Operations Teams and Resources** | **Customer Success Resources** | **Helpful Sales Handbook Tips** | **Sales Resources Outside of the Sales Handbook** |
 |  ------ | ------ | ------ | ------ |
 | [Field Operations](https://about.gitlab.com/handbook/sales/field-operations/) | [Customer Success Groups](https://about.gitlab.com/handbook/customer-success/#customer-success-groups) | [FAQ from Prospects](https://about.gitlab.com/handbook/sales/faq-from-prospects/) |[Resellers Handbook](https://about.gitlab.com/handbook/resellers/) |
-| [Sales Operations](https://about.gitlab.com/handbook/sales/field-operations/sales-operations/) | [How to Engage a Solutions Architect](https://about.gitlab.com/handbook/customer-success/solutions-architects#when-and-how-to-engage-a-solutions-architect) | [Client Use Cases](https://about.gitlab.com/handbook/use-cases/) | [Customer Reference Sheet](https://docs.google.com/a/gitlab.com/spreadsheets/d/1Off9pVkc2krT90TyOEevmr4ZtTEmutMj8dLgCnIbhRs/edit?usp=sharing) |
+| [Sales Operations](https://about.gitlab.com/handbook/sales/field-operations/sales-operations/) | [How to Engage a Solutions Architect](https://about.gitlab.com/handbook/customer-success/solutions-architects#when-and-how-to-engage-a-solutions-architect) | [Client Use Cases](/handbook/use-cases/) | [Customer Reference Sheet](https://docs.google.com/a/gitlab.com/spreadsheets/d/1Off9pVkc2krT90TyOEevmr4ZtTEmutMj8dLgCnIbhRs/edit?usp=sharing) |
 | [Deal Desk](https://about.gitlab.com/handbook/sales/field-operations/sales-operations/deal-desk/) | [Account Planning Template for Large Accounts](https://docs.google.com/presentation/d/1yQ6W7I30I4gW5Vi-TURIz8ZxnmL88uksCl0u9oyRrew/edit?ts=58b89146#slide=id.g1c9fcf1d5b_0_24) | [Dealing with Security Questions From Prospects](/handbook/security/#security-questionnaires-for-customers) | [Customer Reference Case Study Dynamic Board](https://gitlab.com/gitlab-com/marketing/strategic-marketing/customer-reference-content/case-study-content/-/boards/1804878?scope=all&utf8=%E2%9C%93&) |
 | [Field Enablement](https://about.gitlab.com/handbook/sales/field-operations/field-enablement/) | [How to Engage a CSM/CSE](https://about.gitlab.com/handbook/customer-success/pre-sales-post-sales-transition/) | [How to conduct an executive meeting](https://www.youtube.com/watch?v=PSGMyoEFuMY&feature=youtu.be) | [GitLab Support Handbook](/handbook/support/) |
 | [Sales Strategy](https://about.gitlab.com/handbook/sales/field-operations/sales-strategy/) |  | [CEO Preferences when speaking w/ prospects/customers](/handbook/ceo/) | |

content/handbook/sales/command-of-the-message/metrics.md

@@ -44,7 +44,7 @@ Below is just one example of how you could leverage Nico's approach to open the
 
 Are any of these true for your organization?”
 
-Another critical way to embrace your role as a trusted advisor is to become and stay intimately familiar with the specific problems that GitLab helps to solve. Watch the below video and master your knowledge of [GitLab's customer use cases](https://about.gitlab.com/handbook/use-cases/).
+Another critical way to embrace your role as a trusted advisor is to become and stay intimately familiar with the specific problems that GitLab helps to solve. Watch the below video and master your knowledge of [GitLab's customer use cases](/handbook/use-cases/).
 
 <figure class="video_container">
   <iframe src="https://www.youtube.com/embed/4wZQ_oxOcRs" frameborder="0" allowfullscreen="true"> </iframe>

content/handbook/sales/prospecting.md

@@ -60,7 +60,7 @@ Work with your [Sales Development team member](/handbook/marketing/sales-develop
 Work with your Sales Development team member to:
 - Decide which format of approach is best (email, linkedin, phone), and what your cadence will be:
 - Customize the [Prospecting Sequences for AEs](https://docs.google.com/document/d/1ksEGBsDVjQGkSeq8ESKf9Jdy-N7wREq_stnLutJBPTo/edit#heading=h.ufep756p4z4j) template or create your own.
-- Organize the [qualifying questions](https://about.gitlab.com/handbook/sales/qualification-questions/) and [customer use cases](https://about.gitlab.com/handbook/use-cases/) that might be relevant.
+- Organize the [qualifying questions](https://about.gitlab.com/handbook/sales/qualification-questions/) and [customer use cases](/handbook/use-cases/) that might be relevant.
 - **Practice your elevator pitch.** Both you and your SD teammate need to practice your pitches together to make sure you’re aligned on what you want the customer or prospect to hear. Really work on your tone of voice. You know you’re ready if you can easily tweak it based on who you’re talking to and what’s relevant to them.
 
 **Work with partners:** Work with your Channel Account Manager (CAM), talk to your peers, or use the [Partner Directory](https://partners.gitlab.com/English/directory/) to identify if there is a partner that supports specific accounts and can provide insight into target contacts or stakeholders.
@@ -134,7 +134,7 @@ Holding hurts our prospective customers because while they’re sitting there, t
 
 - [Sales discovery and qualifying questions handbook page](https://about.gitlab.com/handbook/sales/qualification-questions/)
 - [Effective discovery handbook page](https://about.gitlab.com/handbook/sales/playbook/discovery/)
-- [Most common customer use cases handbook page](https://about.gitlab.com/handbook/use-cases/)
+- [Most common customer use cases handbook page](/handbook/use-cases/)
 
 #### Training
 

content/handbook/sales/sales-operating-procedures/facilitate-the-opportunity.md

@@ -103,7 +103,7 @@ Your job is to call out the specific key pain points and show the customer how t
 
 The next component of the pitch deck is showing how GitLab can help. This will require you to understand the customer’s specific use case. You discovery calls should have provided much of the data to define the problem, but going further you must do the following:
 
-- Research [Customer Use Cases](https://about.gitlab.com/handbook/use-cases/)
+- Research [Customer Use Cases](/handbook/use-cases/)
 - Align the customer’s pain point to a typical customer use case
 - Explain what Gitlab does in relation to the associated customer use case
 

content/handbook/sales/training/_index.md

@@ -90,14 +90,14 @@ GitLab field team members must understand how various elements of the GitLab por
 | What is GitLab's product strategy?  | - [GitLab Dedicated](https://gitlab.highspot.com/items/6478cd2f94e64c47fe04e6f5)  (Jun 2023, 30 minutes) <br> - [Automated Software Delivery (AutoSD) Integrated Campaign](https://youtu.be/Eq-DdOGkAlk) (Aug 2022, 21 minutes) <br> - [Positioning & Selling GitLab.com](https://youtu.be/mCqC6btgQBc) (June 2022, 26 minutes) <br> - [15.0 Release](https://youtu.be/gGMJZo40CjE) (May 2022, 18 minutes) <br> - [GitLab acquires Opstrace](https://youtu.be/l1HWrdUJdjs) (Dec 2021, 20 minutes) <br> - [Breaking Changes in 14.0 - AMA with Product & Customer Success](https://youtu.be/k-wvJtL_NeM) (Jun 2021, 30 minutes) <br> - [Positioning Verify & Product Vision](https://youtu.be/zKmD4i80tdg) (Mar 2021, 30 minutes) <br> - [GitLab Direction](https://about.gitlab.com/direction/) <br> - [Advantages of a single application](/handbook/product/single-application/) <br> - GitLab Sales Kickoff 2021 Product Keynote: A Winning Product for Peak Performance ([slides](https://docs.google.com/presentation/d/1NunKRuZBnDcZi0k_N5-NQBvdy5X5ZaV4a1Qf7w126qs/edit?usp=sharing)) ([video](https://gitlab.edcast.com/insights/ECL-a4010292-8e12-435f-a971-b3a6f3a121c7)) (Feb 2021, 88 minutes) |
 | What are GitLab's product tiers? | - [GitLab Tiers](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/tiers/) <br> - [Why GitLab Ultimate?](/pricing/ultimate/) <br> - [Why GitLab Premium?](/pricing/premium/) <br> - [Feature comparison](/pricing/feature-comparison/) <br> - [The Journey to Ultimate](https://youtu.be/d3tkGHBFaRM) (Nov 2021, 48 minutes) <br> - [How to upgrade your customer to a higher tier](https://www.youtube.com/watch?v=8ZpU7PZzFyY) (Jul 2019, 26 minutes) <br> - [Discovery Questions for Selling GitLab Ultimate and GitLab Premium](https://about.gitlab.com/handbook/sales/qualification-questions/#questions-for-selling-gitlab-premium-and-ultimate) <br> - [Seven Ways GitLab Premium will Accelerate Customer Development](https://www.youtube.com/watch?v=aHUNPmzzusg&feature=youtu.be) (July 2020, 40 minutes) |
 | How is GitLab priced? | - [Pricing page](/pricing/) <br> - [Pricing model](/handbook/company/pricing/) in the Handbook |
-| What are the GitLab customer use cases (solutions)? | - Check out the [Customer Use Cases Handbook page](https://about.gitlab.com/handbook/use-cases/) <br> - [Use Case Driven Go To Market (GTM)](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/) |
+| What are the GitLab customer use cases (solutions)? | - Check out the [Customer Use Cases Handbook page](/handbook/use-cases/) <br> - [Use Case Driven Go To Market (GTM)](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/) |
 | Where may I learn about the Version Control & Collaboration use case / solution (formerly Source Code Management (SCM))? | - Check out the [Version Control & Collaboration Handbook page](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/version-control-collaboration/) <br> - [The GitLab Journey & The SCM Use Case](https://www.youtube.com/watch?v=GN891Bqc6QY) (Mar 2020, 27 minutes) |
 | Where may I learn about the Continuous Integration (CI) customer use case / solution? | - Check out the [Continuous Integration (CI) Handbook page](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/ci/) <br> - [The GitLab Journey & The CI Use Case](https://www.youtube.com/watch?v=JoeaTYIH5lI) (Mar 2020, 30 minutes) <br> - [Forrester Wave Cloud CI Report: What It Means to GitLab Sales, Customers & Prospects](https://youtu.be/q6YXIvHZuDU) (Oct 2019, 32 minutes) <br> - Complete the Continuous Integration Customer Use Case learning path in [Level Up](https://levelup.gitlab.com/access/saml/login/internal-team-members?returnTo=https://levelup.gitlab.com/learn/course/continuous-integration-customer-use-case) (internal only). <br> - Just want to take the knowledge check quiz? [Click Here](https://forms.gle/SYcjEptqKyfohUHx7) |
 | Where may I learn about the DevSecOps customer use case / solution (aka Shift Left Security)? |  - Check out the [DevSecOps Handbook page](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/devsecops/) <br> - Complete the DevSecOps Customer Use Case learning path in [Level Up](https://levelup.gitlab.com/access/saml/login/internal-team-members?returnTo=https://levelup.gitlab.com/learn/course/devsecops-customer-use-case) (internal only) <br> - Just want to take the knowledge check quiz? [Click Here](https://forms.gle/hkta3uDUpki52BGD8) |
 | Where may I learn about the DevOps Platform customer use case / solution? | - Check out the [DevOps Platform Handbook page](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/devops-platform/) <br> - [GitLab AutoDevOps Run Click-Through Demo](https://www.youtube.com/watch?v=V_6bR0Kjju8) (Apr 2019, 21 minutes) <br> - Complete the DevOps Platform Customer Use Case learning path in [Level Up](https://levelup.gitlab.com/access/saml/login/internal-team-members?returnTo=https://levelup.gitlab.com/learn/course/devops-platform-customer-use-case) (internal only). |
 | Where may I learn about the GitOps customer use case / solution? | - Check out the [GitOps Handbook page](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/gitops/) <br> - Watch [The GitLab Journey & the GitOps Use Case](https://youtu.be/Ap14indu2-w) (July 2020, 30 minutes)  |
 | Where may I learn about the Agile Planning customer use case / solution? | - Check out the [Agile Planning website page](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/usecase-gtm/agile/) (Handbook page coming soon) <br> - [Agile Project & Portfolio Management on GitLab Click-Through Demo](https://www.youtube.com/watch?v=Eo8pFoE6DjU) (Jun 2019, 30 minutes) |
-| Are additional customer use cases / solutions being considered and/or developed? | - Yes, check out the [Customer Use Cases Handbook page](https://about.gitlab.com/handbook/use-cases/) for the latest and greatest information |
+| Are additional customer use cases / solutions being considered and/or developed? | - Yes, check out the [Customer Use Cases Handbook page](/handbook/use-cases/) for the latest and greatest information |
 | What about services? | - [Positioning Professional Services](https://youtu.be/vFr86T4MFCE) (Apr 2023, 29 minutes) <br> - Professional services, available through GitLab or partners, help to optimize your organization's adoption of GitLab, continue to leverage the tools your teams use every day, facilitate your transition to GitLab, and deliver hands-on training to accelerate your team’s adoption <br> - [Q1 FY23 Professional Services Update](https://youtu.be/_UUhi2A2Biw) (Mar 2022, 25 minutes) <br> - [GitLab Value Stream Assesments](https://youtu.be/jfM3AG6dBFY) (Feb 2022, 29 minutes) <br> - [Services to Accelerate Customer Adoption](https://about.gitlab.com/handbook/customer-success/professional-services-engineering/sales-enablement/) <br> - [How to engage Professional Services to help you sell and scope](https://about.gitlab.com/handbook/customer-success/professional-services-engineering/working-with/) <br> - [Professional Services Full Catalog](/services/catalog/) <br> - [The Value of Professional Services: A CFOs Perspective](https://youtu.be/arF-6BBRAxU) (Aug 2020, 29 minutes) <br> - [Professional Services Offerings & Positioning](https://www.youtube.com/watch?v=_04S2JhVZ5A) (Apr 2020, 29 minutes) <br> - [Selling Services to Accelerate Customer Adoption](https://youtu.be/ngTI5-1cQK4) (Oct 2019, 28 minutes) |
 | What about GitLab security? | - [Solution Selling: Compliance](https://youtu.be/sGSZlxGciiE) (Apr 2022, 29 minutes) <br> - [Product Stage Direction - Secure](https://about.gitlab.com/direction/secure/) <br> - From SCM and CI to Security: Paths to Ultimate ([slides](https://docs.google.com/presentation/d/1VTCfKcAZ4NS2xQu8C-fA6pugCdvUbb0MfQhimLiAGak/) from GitLab Sales Kickoff 2020) <br> - [How GitLab Helps Customers Achieve Compliance](https://youtu.be/MRaCKYDXmuI) (May 2020, 26 minutes) <br> - [Forrester Software Composition Analysis (SCA) Wave & Security Q&A](https://www.youtube.com/watch?v=FIfZCg02G3o) (Apr 2019, 30 minutes) <br>- [GitLab SOC2 Security Compliance](/handbook/security/security-assurance/security-compliance/certifications.html) |
 | What about GitLab testing capabilities? | - [Pipeline Security Direction Handbook pages](/handbook/product/categories/#pipeline-security-group) <br> - [Verify:Pipeline Security Category Vision and Positioning](https://youtu.be/Zisa9Qfh8v8) (Sep 2021, 26 minutes) |