giseldo/neodataset huggingface dataset:
ENG: Update press kit with new assets

## Goal
We would like to update the press kit with the new brand assets.

### Jobs To Be Done
* **Situation**: *When a user accesses the press kit they get updates assets*
* **Motivation**: *We want to align with our 4/27 launch*
* **Outcome**: *So we can by consistent with our brand*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/press/press-kit/
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/press/press-kit/index.html.haml
 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update the existing press kit page in the www-gitlab-com repository with new brand assets

## Out of scope
What is out of scope and not part of this iteration?

- Migrating anything for the press kit to the buyer experience repo

## 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
Turn off OneTrust in review app

OneTrust is taking up to 12 seconds to load and then fail to load on the review apps for Buyer Experience.

My hypothesis is that's because OneTrust is not configured to work in our review environments, which means it takes a long time to try and connect to the OneTrust server, never gets what it needs, and ends up bailing out. 

I don't think we need OneTrust in review apps. I would prefer to have it to emulate prod environment, but if it's not configured for this at the moment, I'd rather just disable it in review apps so we don't artificially slow down those pages. 

Fortunately, this is not an issue that makes its way to production, because OneTrust is correctly configured for `about.gitlab.com`, so this is a pretty low priority thing. I just want to clean it up before a lot of folks are walking through the refresh branch and wondering why it's so slow. 

Once I remove it, I will triple-check that it's still loading in production, where we absolutely need to have it.

Story points: 1.0
ENG: Ensure all existing topic pages have new coat of paint

## Goal
We would like to review all existing topic pages and ensure they have the fresh quote of paint - fonts, colors, and logo.

## Page(s)
Which page(s) are involved in this request?
* All topic pages that exist in the Buyer Experience repository - https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/topics

## 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`

## 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
ENG: Ensure all existing solutions pages have new coat of paint

## Goal
We would like to ensure all existing solution pages have the fresh coat of paint

## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/topics

## In scope
What is within scope of this request?

- [ ] Make sure all existing solution pages have the fresh coat of paint 

## 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
UX: Review Solutions by Industry

## Goal
We would like to X which will improve Y as measured by Z.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## 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

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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: Create new resource component - Solutions

## Goal
We would like to build the new resources component. 

## Page(s)
Which page(s) are involved in this request?
* https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11

## 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
UX: Review Solutions by Solutions/ Use Case

DRAFT

## Goal
We would like to X which will improve Y as measured by Z.

- [Refresh Branch](https://refresh.about.gitlab-review.app/)

## Page(s)
Which page(s) are involved in this request?
* 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

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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
UX: Review Solutions by Company Size

DRAFT

## Goal
We would like to X which will improve Y as measured by Z.

- [Refresh Branch](https://refresh.about.gitlab-review.app/)

## 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

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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: Apply new hero to all Solutions

## Goal
We would like to apply the new hero to all existing Solutions pages.

[Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A1765)

### Jobs To Be Done
* **Situation**: *When a user lands on any existing solutions page*
* **Motivation**: *The hero is skinned to the new template*
* **Outcome**: *So we can ensure an existing experience*

## Page(s)
Which page(s) are involved in this request?
* /solutions/*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Apply new hero to all existing solutions pages



## 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
UX: Resources - Learn page

## Goal
We would like to update the Learn page, which will improve findability and brand recognition, as measured by reduced drop off.

### Jobs To Be Done
* **Situation**: *When a customer visits the Learn page ...*
* **Motivation**: *they want to easily find and consume content that will help them improve...*
* **Outcome**: *so they can grow with GitLab as a product.*

## Page(s)
Which page(s) are involved in this request?
* [Learn page](https://about.gitlab.com/learn/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update UX as needed
- [ ] Skin in new brand refresh designs

## Out of scope
What is out of scope and not part of this iteration?

- TBD

## 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: 6.0
UX: Review Solutions navigation experience

## Goal
We would like to review the experience of navigating to all items under "solutions" from the primary nav.

- [Refresh Branch](https://refresh.about.gitlab-review.app/)

## 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

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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: Solutions by Sector - Education

## Goal
We would like to apply this template from Jam3 to our Education solutions page.

## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/education/
* [Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A1765)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Apply the new template to the education page

## Out of scope
What is out of scope and not part of this iteration?

- www-gitlab-com

## 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: Create Show Case component

## Goal
We would like to create a reusable case studies component as designed here: https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=7200%3A13980

This will include updating the current place holder component (`by-solution-features`) used on the Delivery Automation solutions page. 


### Jobs To Be Done
* **Situation**: *When we want to use the case studies component for a solutions page it is available*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Build a reusable case studies component for solutions pages

## 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
ENG Create Side Nav component - Solutions

## Goal
We would like to build a reusable side nav component as designed here: https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT?node-id=1117:6720#176945666 



### Jobs To Be Done
* **Situation**: *Create this component so it's available to apply to a solutions page that uses the new template*
* **Motivation**: *We want to move fast*
* **Outcome**: *So we can migrate a couple solutions pages to the new template*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jgarc
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create the component in the refresh branch

## Out of scope
What is out of scope and not part of this iteration?

- Applying it to any page - We'll need a solutions page in the full template to use. 

## 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: Create ValueProp component - Solutions

## Goal
We would like to have a ValueProp component in the refresh branch with new styles that can be reused in our Solutions pages.

[Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=6963%3A13367)

![Screen_Shot_2022-04-18_at_2.39.13_PM](/uploads/d103260785f7d2e3601ffe2661c131a3/Screen_Shot_2022-04-18_at_2.39.13_PM.png)

## Page(s)
Which page(s) are involved in this request?
* Public Sector
* Delivery Automation
* Future solutions pages

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [X] Consulted: `@laurenbarker`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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
ENG: Create Benefits component - Solutions

## Goal
We would like to have a Benefits component in the refresh branch with new styles that can be reused in our Solutions pages.

Apply this component to the Delivery Automation and Public Sector solutions pages in the **refresh branch**. 
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/refresh/content/solutions/delivery-automation.yml
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/refresh/content/solutions/public-sector.yml

Figma Resources:
- Here is the [full Figma ](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11)file for those pages. 
- Here is the [Slippers Foundation Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11) for this component

![Screen_Shot_2022-04-18_at_2.36.38_PM](/uploads/0f4abd491c46c06e98688ceb86165932/Screen_Shot_2022-04-18_at_2.36.38_PM.png)

## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/delivery-automation/
* https://refresh.about.gitlab-review.app/solutions/public-sector/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [X] Consulted: `@laurenbarker`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- www-gitlab=com work

## 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: pricing page SaaS/SM Modal.

## Goal
We would like to update the pricing modal in the refresh branch to align with new designs.

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpenagos-ext 
- [ ] Consulted: 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update modal to align with [Figma design](https://www.figma.com/file/4CkayJDu97uNEWBOlgABwE/Pricing-Refresh-2022-04-01?node-id=220%3A5757)

## 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
Why GitLab: Case Studies

[Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)

This was started as part of #623 but the design been changed to match the Homepage case studies section.

** Note: Save the existing Case Studies component code, as we may need to reuse it in the future

With that said, we can probably steal the Homepage case studies code (or use the component entirely if it fits our needs!).

Update case_studies content in why.yml if needed.

Story points: 2.0
Why GitLab: Section w/three cards

[Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)

### Scope
- Add content to Why.yml
- Create card component (doesn't look like this has been created yet)
- Add the header, See more link, and three cards to Why page (feel free to create a separate component for the whole section!)

Story points: 4.0
Why GitLab: Accordion / Company Logo section

We should copy some of the code from our accordion or faq component for this.

[Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)

### Scope
- Add content Why.yml
- Create component and add to Why page
- Ensure analytics tags are added. See the [comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/638#note_903425202) in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/638) for more information.

Story points: 8.0
Why Gitlab: Slider component

This is the same as the component being built in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/588). We can find a way to collaborate, or if the team working on this component doesn't get to it before we do, we can start it!

[Figma file](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)

Story points: 8.0
ENG & SEO: URL structure for solutions content neighborhood

## Goal
We would like to define the URL structure for the solutions content neighborhood.

### Jobs To Be Done
* **Situation**: *When build out the solutions content neighborhood *
* **Motivation**: *We want to know the URL structure *
* **Outcome**: *So we can organize our routes, templates, and data efficiently.*

## Page(s)
Which page(s) are involved in this request?
* Buyer Experience repository`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @jhalloran @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] URL structure of solutions by solution
- [ ] URL structure of solutions by industry
- [ ] URL structure of solutions by department
- [ ] URL structure of solutions by technology
- [ ] URL structure of solutions by company size
- [ ] URL structure of solutions by technology

## Out of scope
What is out of scope and not part of this iteration?

- Building anything

## 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
- [x] Data / Analytics
- [x] UX Design
- [x] Engineering

Story points: 1.0
Free Trial page is not available in review apps

The Free Trial page is not reachable in review apps due to too many redirects. Lets fix that. 

The following discussion from !349 should be addressed:

- [ ] @dennischarukulvanich started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/349#note_901750085):  (+3 comments)

Story points: 1.0