add index page to use-cases (#2105)

* change underscores to dashes * update links to use hyphens * update file name + links to use hyphens * create use cases index page * squash! Prettier * fix link Co-authored-by: marybelzer <[email protected]>
sourcegraph · Feb 1, 2022 · 9b84056 · 9b84056
1 parent 92667e5
commit 9b84056
Show file tree

Hide file tree

Showing 14 changed files with 28 additions and 12 deletions.
diff --git a/content/departments/ce/index.md b/content/departments/ce/index.md
@@ -37,4 +37,4 @@ You can reach us at the #ce channel or @ce on Slack. Customer Engineering repres
 ### Customer Use Cases
 
 - [Use cases](../../strategy-goals/strategy/index.md#use-cases)
-- [How to work with use cases](../../strategy-goals/strategy/working_with_use_cases.md)
+- [How to work with use cases](../../strategy-goals/strategy/working-with-use-cases.md)
diff --git a/content/departments/marketing/index.md b/content/departments/marketing/index.md
@@ -75,7 +75,7 @@ The table below breaks down the capabilities of each team within Marketing. Once
 - [Marketing roles - open positions](https://sourcegraph.com/careers)
 
 - [Use cases](../../strategy-goals/strategy/index.md#use-cases)
-- [How to work with use cases](../../strategy-goals/strategy/working_with_use_cases.md)
+- [How to work with use cases](../../strategy-goals/strategy/working-with-use-cases.md)
 - [Process docs](process/index.md)
 - [Marketing Rapid Response Process](marketing_rapid_response_process/index.md)
 

diff --git a/content/departments/product-engineering/engineering/index.md b/content/departments/product-engineering/engineering/index.md
@@ -34,7 +34,7 @@
   - [Career development framework](career-development/framework.md)
   - [Talent review process](career-development/talent-review-process.md)
 - [Use cases](../../../strategy-goals/strategy/index.md#use-cases)
-- [How to work with use cases](../../../strategy-goals/strategy/working_with_use_cases.md)
+- [How to work with use cases](../../../strategy-goals/strategy/working-with-use-cases.md)
 
 Welcome to Engineering!
 

diff --git a/content/departments/product-engineering/product/index.md b/content/departments/product-engineering/product/index.md
@@ -70,5 +70,5 @@ There are various problems, feature areas, or initiatives related to Product (wh
 - [Key accounts deck](https://docs.google.com/presentation/d/18hw513mX3ssA9isQdGdnmrt5-BIN4TRMpjkSaodTEuw/edit#slide=id.gf03521df2b_0_0) (internal only)
 - [Product Gaps Dashboard](https://sourcegraph2020.lightning.force.com/lightning/r/Report/00O3t000006WZklEAG/view) (internal only)
 - [Use cases](../../../strategy-goals/strategy/index.md#use-cases)
-- [How to work with use cases](../../../strategy-goals/strategy/working_with_use_cases.md)
+- [How to work with use cases](../../../strategy-goals/strategy/working-with-use-cases.md)
 - [Product team tools](tools/index.md)
diff --git a/content/departments/product-engineering/strategy-goals/index.md b/content/departments/product-engineering/strategy-goals/index.md
@@ -4,7 +4,7 @@ Our FY23 strategy is broken down in what we're planning to do, and why.
 
 ## Why
 
-Sourcegraph today addresses many of the critical challenges that modern software teams face, such as accelerating [onboarding](https://about.sourcegraph.com/case-studies/convoy-improved-on-boarding) and [developer velocity](https://about.sourcegraph.com/case-studies/indeed-accelerates-development-velocity/), [incident response](../../../strategy-goals/strategy/use_cases/incident_response.md), [fixing security vulnerabilities](https://about.sourcegraph.com/case-studies/cloudflare-accelerates-debugging-and-improves-security/), [code reuse](https://about.sourcegraph.com/case-studies/cern-reduces-technical-debt/), and [monitoring code health](https://about.sourcegraph.com/case-studies/quantcast-large-scale-refactoring/).
+Sourcegraph today addresses many of the critical challenges that modern software teams face, such as accelerating [onboarding](https://about.sourcegraph.com/case-studies/convoy-improved-on-boarding) and [developer velocity](https://about.sourcegraph.com/case-studies/indeed-accelerates-development-velocity/), [incident response](../../../strategy-goals/strategy/use-cases/incident-response.md), [fixing security vulnerabilities](https://about.sourcegraph.com/case-studies/cloudflare-accelerates-debugging-and-improves-security/), [code reuse](https://about.sourcegraph.com/case-studies/cern-reduces-technical-debt/), and [monitoring code health](https://about.sourcegraph.com/case-studies/quantcast-large-scale-refactoring/).
 
 Many of our current customers bought into our core capabilities (searching and navigating code, understanding code context, and automating large-scale changes) because they understood how to leverage them to address these use cases. But connecting these capabilities to use cases requires a leap of understanding: our product does not currently have first-class user flows built around these use cases. This friction can hamper further expansion and engagement.
 

diff --git a/content/departments/sales/index.md b/content/departments/sales/index.md
@@ -17,7 +17,7 @@ The Sales team represents us and our values to customers, bringing back dollars
 - [Engaging with Legal](process/saleslegal.md)
 - [Engaging with Security](process/salessecurity.md)
 - [Use cases](../../strategy-goals/strategy/index.md#use-cases)
-- [How to work with use cases](../../strategy-goals/strategy/working_with_use_cases.md)
+- [How to work with use cases](../../strategy-goals/strategy/working-with-use-cases.md)
 - [Process docs](process/index.md)
 
 ## Pipeline, data, and models

diff --git a/content/strategy-goals/strategy/index.md b/content/strategy-goals/strategy/index.md
@@ -29,18 +29,18 @@ Our [values](../../company-info-and-process/values/index.md) are the principles
 
 We have identified five key use cases for our universal code search platform:
 
-1. [Developer onboarding](use_cases/dev-onboarding.md)
-1. [Code reuse](use_cases/code_reuse.md)
-1. [Code health](use_cases/code_health.md)
-1. [Fixing security vulnerabilities](use_cases/fixing_security_vulnerabilities.md)
-1. [Incident Response](use_cases/incident_response.md)
+1. [Developer onboarding](use-cases/dev-onboarding.md)
+1. [Code reuse](use-cases/code-reuse.md)
+1. [Code health](use-cases/code-health.md)
+1. [Fixing security vulnerabilities](use-cases/fixing-security-vulnerabilities.md)
+1. [Incident Response](use-cases/incident-response.md)
 
 There are also several related resources:
 
 - [Use cases slide (internal only)](https://docs.google.com/presentation/d/1XIZFqOxB9ZVEeswOzLWgLaOxK-K9SAn94juo2_cpRnY/edit#slide=id.g1074ab41e5e_2_0)
 - [FY23 use cases in detail (internal only)](https://docs.google.com/document/d/1k7w-sgK3T4B_kLi9wuEIvvMdRp4hPd0YtsUt0UpwvsU/edit#heading=h.t4fumzvh3saz)
 - [Productboard use case index (internal only)](https://sourcegraph.productboard.com/feature-board/3957049-fy23-use-cases)
-- How we [work with use cases](working_with_use_cases.md)
+- How we [work with use cases](working-with-use-cases.md)
 
 ### Principles
 

diff --git a/...y-goals/strategy/use_cases/code_health.md → ...y-goals/strategy/use-cases/code-health.md b/...y-goals/strategy/use_cases/code_health.md → ...y-goals/strategy/use-cases/code-health.md
diff --git a/...gy-goals/strategy/use_cases/code_reuse.md → ...gy-goals/strategy/use-cases/code-reuse.md b/...gy-goals/strategy/use_cases/code_reuse.md → ...gy-goals/strategy/use-cases/code-reuse.md
diff --git a/...oals/strategy/use_cases/dev-onboarding.md → ...oals/strategy/use-cases/dev-onboarding.md b/...oals/strategy/use_cases/dev-onboarding.md → ...oals/strategy/use-cases/dev-onboarding.md
diff --git a/..._cases/fixing_security_vulnerabilities.md → ...-cases/fixing-security-vulnerabilities.md b/..._cases/fixing_security_vulnerabilities.md → ...-cases/fixing-security-vulnerabilities.md
diff --git a/...s/strategy/use_cases/incident_response.md → ...s/strategy/use-cases/incident-response.md b/...s/strategy/use_cases/incident_response.md → ...s/strategy/use-cases/incident-response.md
diff --git a/content/strategy-goals/strategy/use-cases/index.md b/content/strategy-goals/strategy/use-cases/index.md
@@ -0,0 +1,16 @@
+### Use cases
+
+We have identified five key use cases for our universal code search platform:
+
+1. [Developer onboarding](dev-onboarding.md)
+2. [Code reuse](code-reuse.md)
+3. [Code health](code-health.md)
+4. [Fixing security vulnerabilities](fixing-security-vulnerabilities.md)
+5. [Incident Response](incident-response.md)
+
+There are also several related resources:
+
+- [Use cases slide (internal only)](https://docs.google.com/presentation/d/1XIZFqOxB9ZVEeswOzLWgLaOxK-K9SAn94juo2_cpRnY/edit#slide=id.g1074ab41e5e_2_0)
+- [FY23 use cases in detail (internal only)](https://docs.google.com/document/d/1k7w-sgK3T4B_kLi9wuEIvvMdRp4hPd0YtsUt0UpwvsU/edit#heading=h.t4fumzvh3saz)
+- [Productboard use case index (internal only)](https://sourcegraph.productboard.com/feature-board/3957049-fy23-use-cases)
+- How we [work with use cases](../working-with-use-cases.md)
diff --git a/...-goals/strategy/working_with_use_cases.md → ...-goals/strategy/working-with-use-cases.md b/...-goals/strategy/working_with_use_cases.md → ...-goals/strategy/working-with-use-cases.md
-Original file line number
+Diff line change
@@ Expand Up @@
     ## Why
-    Sourcegraph today addresses many of the critical challenges that modern software teams face, such as accelerating [onboarding](https://about.sourcegraph.com/case-studies/convoy-improved-on-boarding) and [developer velocity](https://about.sourcegraph.com/case-studies/indeed-accelerates-development-velocity/), [incident response](../../../strategy-goals/strategy/use_cases/incident_response.md), [fixing security vulnerabilities](https://about.sourcegraph.com/case-studies/cloudflare-accelerates-debugging-and-improves-security/), [code reuse](https://about.sourcegraph.com/case-studies/cern-reduces-technical-debt/), and [monitoring code health](https://about.sourcegraph.com/case-studies/quantcast-large-scale-refactoring/).
+    Sourcegraph today addresses many of the critical challenges that modern software teams face, such as accelerating [onboarding](https://about.sourcegraph.com/case-studies/convoy-improved-on-boarding) and [developer velocity](https://about.sourcegraph.com/case-studies/indeed-accelerates-development-velocity/), [incident response](../../../strategy-goals/strategy/use-cases/incident-response.md), [fixing security vulnerabilities](https://about.sourcegraph.com/case-studies/cloudflare-accelerates-debugging-and-improves-security/), [code reuse](https://about.sourcegraph.com/case-studies/cern-reduces-technical-debt/), and [monitoring code health](https://about.sourcegraph.com/case-studies/quantcast-large-scale-refactoring/).
     Many of our current customers bought into our core capabilities (searching and navigating code, understanding code context, and automating large-scale changes) because they understood how to leverage them to address these use cases. But connecting these capabilities to use cases requires a leap of understanding: our product does not currently have first-class user flows built around these use cases. This friction can hamper further expansion and engagement.
@@ Expand Down @@