giseldo/neodataset huggingface dataset:
UX: Add TeamOps section to About page

## Goal
We would like to add a section on TeamOps to the About page

#### Jobs To Be Done
* **Situation**: *When prospects want to learn more about GitLab as a company.*
* **Motivation**: *We want to feature the TeamOps page.*
* **Outcome**: *So we can provide provide awareness to the initiative.*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [X]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - section to feature the TeamOps page

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [X] Yes: How many people are clicking on the CTA?
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[About](gitlab.com/about)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @KristinaWeis @Tinaliseng @jhalloran @fqureshi @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering

Story points: 2.0
ENG: Solutions child page template SEO improvements

## Goal

We would like to make improvements to the /solutions child template which will improve engagement and conversion as measured by metrics.

## Page(s)

Which page(s) are involved in this request?

* https://about.gitlab.com/enterprise/
* https://about.gitlab.com/small-business/
* https://about.gitlab.com/solutions/public-sector/
* https://about.gitlab.com/solutions/continuous-software-security-assurance/
* https://about.gitlab.com/solutions/delivery-automation/

## DCI

[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

* [ ] DRI: 
* [ ] Consulted: @Tinaliseng `@ncregan` @justin.vetter 
* [ ] Informed: @fqureshi 

## Working Files
[Suggested worksheet doc for each URL](https://docs.google.com/document/d/1KF5OMF8UR_3Ulv9yRSKLjOgemu6ZZTNewbzYuBKK02s/edit?usp=sharing)

### Scope

* [ ] Use document to update and optimize solutions child template

### Not in scope
- [ ] Update content, add descriptions, optimize javascript

## Requirements

What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

* [ ] Copy writing
* [ ] Illustration
* [ ] Custom Graphics
* [ ] Research
* [ ] Data / Analytics
* [ ] UX Design
* [x] Engineering

Story points: 2.0
ENG: Security & Compliance LP | Lightning strike

## Goal
We would like to create a `Security & Compliance` landing page that will increase customer trust and confidence as measured by engagement.



## Workfiles


* [Figma mock](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=0%3A1)

### Extra workingfiles
* [Content wireframe](https://docs.google.com/document/d/1UU_TWbY9TWRYCUE2T5jLHXp-uzCWkxPaxg--RP51vb4/edit)
  * [Dev Sec Ops page content wireframe](https://docs.google.com/document/d/1UU_TWbY9TWRYCUE2T5jLHXp-uzCWkxPaxg--RP51vb4/edit#)
* [JTBD wireframe](https://www.figma.com/file/vwWJNCcnRQtlOmhDkXm3bW/Security-%26-Compliance?node-id=1%3A10)

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: `Lightening strike priority`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to launch the Security & Compliance LP`


**What analytics / data will we need to set-up?**
- [x] Yes: `Standard DEX analytics will need to be added`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[Security & Compliance](https://about.gitlab.com/solutions/security-and-compliance)` *new page*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Security & Compliance LP
- [ ] Deliverable 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 4.0
UX: Security & Compliance Lightning strike: Software Supply chain security refresh

## Goal
We would like to update the [Software Supply chain security](https://about.gitlab.com/solutions/supply-chain/) landing page to support our Security & Compliance lightning strike.

### Project notes
Pasted from https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/6521#web-page-updates-chandler-saumya-jennifer

## Workfiles

- [Software supply chain security content wireframe](https://docs.google.com/document/d/1QpfhcnwhkaZvpjid7mwOpg_fw6l6FXeITF7ATMQEs1g/edit)
- [Figma file](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=157%3A5204)

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/supply-chain/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @supadhyaya @chandlergibb 
- [ ] Informed: @justin.vetter @fqureshi 

## In scope
What is within scope of this request?

- [ ] [Content wireframe](https://docs.google.com/document/d/1PDs1M2REEzsykFPxOgCK6cEy_ssaCTXWltNMTIsIs0U/edit?usp=sharing) @chandlergibb 
- [ ] Figma mock @Tinaliseng 
- [ ] Engineer (separate issue to come)

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 3.0
Hero Component in Common Folder

## Goal
Create a reusable hero component in common folder. We currently do not have one and have been reusing the BySolutions Hero

#### Jobs To Be Done
* **Situation**: *Whenever we need to create a new page or update a template we are using the BySolutions Hero*
* **Motivation**: *Creating a Common hero will improve development time, help track our components and prevent duplicate components in the future*
* **Outcome**: *A top level hero component*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - `When the new component is created`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* All pages(now and in the future) requiring the new infinity hero

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@miraclebanks``@mduque-ext`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 2.0
ENG: Remove LaunchDarkly test PricingBorders

## Goal
We would like to push the pricing borders live by removing the LaunchDarkly code from the pricing page.

#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: `This needs to be completed before we can run our next test on the pricing page`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `Remove LaunchDarkly code and push variant code only`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* `[Pricing](https://about.gitlab.com/pricing)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @meganfilo 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove LaunchDarkly code
- [ ] Only show have pricing border variant live

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
ENG: Bug Mobile Menu Pricing link

## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?

### Describe the Bug
In the mobile menu when you click the actual word "pricing" it 404s, but when you click the white space to the right it takes you to the correct page.  It looks like there is some weird rendering issue in the HTML. 

![CleanShot_2022-10-04_at_15.28.49](/uploads/1d10f6a0312f51a2646e1c19e928eeff/CleanShot_2022-10-04_at_15.28.49.jpg)

### What's my browser? 
Share your browser infromation from https://www.whatsmybrowser.org/ 

Mobile chrome

## Page(s)
Which page(s) are involved in this request?
* Mobile Menu

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Add 'TeamOps' in the 'Learn' navigation

## Goal
We would like to drive more visitors to the teamops page.

#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 2.0
ENG: Fix render blocking for Google fonts

## Goal
We would like to increase our core web vital scores.  One of the line items that is hurting our scores is how Google fonts is loaded.

![CleanShot_2022-10-04_at_10.23.26](/uploads/f0c22811b237a6bf3b39a9270e6a8e02/CleanShot_2022-10-04_at_10.23.26.jpg)


#### Jobs To Be Done
* **Situation**: *When the DOM loads google fonts is blocking page render lowering our core vital score*
* **Motivation**: *We want to update to fix our core vital scores*
* **Outcome**: *So we can show increased core vital score*

#### Please provide more information related to this request
Here are two articles talking about how to resolve this issue
- https://dieppa.co.uk/2020/10/21/eliminate-render-blocking-resources-google-fonts/
- https://www.tutorialjinni.com/eliminate-render-blocking-google-fonts.html

We will need to test to see if we are seeing major font popping with these options, and weigh the benefit of this change.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - Lower Web Core Vital score

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* All

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ndubord 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Change how google fonts is loaded into BE
- [ ] Deliverable 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Regression: Support Template

## Goal
There are reports of the Support page not loading properly. This is issues is for defining those issues and resolving them.


### Describe the Bug
- 1350px wide the menu jumps to the left and the scroll gets wonky
- On page load, nothing is displayed in the body, this resolves after 2 seconds and then content displays
- @theo.dp please describe your bug here

### What's my browser? 
Share your browser information from https://www.whatsmybrowser.org/ 


## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 4.0
[Design] Free Trial Sign-Up Screen re-design

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [X]  Yes: Request from Ashley
- [ ]  No

### Workfiles
* [Figma file](https://www.figma.com/file/DkrMqoi7TStumwGfG19Rt1/Form-A%2FB-test---Ultimate-Free-Trial-Form-refresh?node-id=3%3A773)
* [Figma prototype](uhttps://www.figma.com/proto/DkrMqoi7TStumwGfG19Rt1/Form-A%2FB-test---Ultimate-Free-Trial-Form-refresh?page-id=0%3A1&node-id=3%3A773&viewport=-500%2C665%2C0.41&scaling=min-zoom)

## Page(s)
Which page(s) are involved in this request?
* [Free Trial Sign Up](https://gitlab.com/-/trials/new)
* Only update the logged out version of this page 
![image](/uploads/2bc86acbf81f19334ce30fff8c3a1f46/image.png)

And use this screen as a starting point
![image](/uploads/d01c9497b9bb4e2c35fa77e935b044a8/image.png)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @s_awezec @fqureshi @justin.vetter @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove 'Skip Trial' link 
- [ ] Remove or change illustration 

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering

Story points: 1.0
MVC1: Changes to Nav

## Goal
We would like to make changes to the Nav as an MVC 1 iteration

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [X]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [X]  Yes `@akramer` 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**


**How do we measure success?**
 - Increased or stagnant clicks to Solutions pages

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No

## Page(s)
Which page(s) are involved in this request?
* [Homepage](about.gitlab.com)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [X] DRI: @mpreuss22 
- [X] Consulted: @ctsang-ext @Tinaliseng @fqureshi @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Move Solutions under Platform 

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering

Story points: 4.0
ENG: Topic Page Template / Add Side Nav

## Goal
We would like to add the multi-level side navigation to the Topic pages which will decrease exit rates as measured by metrics.

## Design
- [Slippers Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=9327%3A16896)

![Screen_Shot_2022-09-28_at_9.18.59_AM](/uploads/45da370cd57a7ed0bef694c3d03d4232/Screen_Shot_2022-09-28_at_9.18.59_AM.png)


Relates to:
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1327

## Page(s)
Which page(s) are involved in this request?
* (List top topic pages for MVC 1 - TODO: @ncregan  )

## Scope
- [ ] List of pages and links - TODO @ncregan 
- [ ] Apply the [multi-level side nav](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148) TODO `DEX ENG`

## RCI
- Responsible:
- Consulted: @ncregan @Tinaliseng @dennischarukulvanich 
- Informed: @ndubord @justin.vetter 

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 3.0