giseldo/neodataset huggingface dataset:
ROI Calculator tests

## Goal
Add Jest to the Buyer Experience project and write Jest tests for the new ROI calculator. These tests will give us peace of mind when there are calculator updates that the calculations are still correct.

## Page(s)
Which page(s) are involved in this request?
* `/calculator/roi`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @tywilliams 
- [ ] Informed: `Everyone`


## In scope
- [ ] Add Jest testing to our Buyer Experience repository
- [ ] Add Jest tests for functions within the `/lib/roiCalculate.js` file
- [ ] Ensure all tests are passing

Story points: 4.0
Site Search with Multiple Domains - add gitlab.com

## Goal
Users who mistaken the marketing site's search feature for the product search feature. These includes searches for namespace, group, or project names.

Our current search provide has the ability to set-up [Site Search with multiple domains](https://swiftype.com/documentation/site-search/guides/multiple-domains). 

Let's add the gitlab.com domain to our site search. 

Related https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/994#note_982711036

### Jobs To Be Done
* **Situation**: *When a user searches for a namespace, group, or project names it returns a result.*
* **Motivation**: *We want to reduce the number of searches with no action taken.*
* **Outcome**: *So we can increase site search from 1% to 3.4%.*

## Page(s)
Which page(s) are involved in this request?
* Swfittype and every page with search

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @dennischarukulvanich 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add gitlab.com to Swfitype search configuration
- [ ] Monitor search analytics

## Out of scope
What is out of scope and not part of this iteration?

- Editing the search design

## 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
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Banner - Privacy Policy Updated

## Goal
We would like to place a banner on the marketing site that notifies users of our updated Privacy Policy.

[Slack Thread](https://gitlab.slack.com/archives/C62ERFCFM/p1654821112375479)

Banner text:
`We've updated our Privacy Policy.  Please click [here - link] to learn more about how we process your personal data`

Related https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/102770 

### Jobs To Be Done
* **Situation**: *When a user visits our marketing site they see a banner of the privacy policy update.*
* **Motivation**: *We want to be transparent about this update to our privacy policy.*
* **Outcome**: *So we can notify users.*

## Page(s)
Which page(s) are involved in this request?
- Every page on about.gitlab.com

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @mpreuss22 @emccrann @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] MR to [navigation repository](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation) with banner
- [ ] Push update to NPM package
- [ ] MR Pull update into [www-gitlab-com](https://gitlab.com/gitlab-com/www-gitlab-com)
- [ ] MR Pull update into [Buyer Experience](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience)

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1

## 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
- [x] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 3.0
Regression in slp-tooltip within free trial page

https://gitlab.slack.com/archives/CN8AVSFEY/p1654633608430129

> the small “SaaS” label on the tab here: https://about.gitlab.com/free-trial/ is that by design?

## Page(s)
Which page(s) are involved in this request?
* [Free trial page](https://about.gitlab.com/free-trial/)

![Screen_Shot_2022-06-08_at_11.17.57_AM](/uploads/9c75750a7526fd48c10d5d2ad05cb6a1/Screen_Shot_2022-06-08_at_11.17.57_AM.png)

## 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: Clean up removal of ten-oh-announcement from www template

## Goal
With the updated home page we would like to clean up the www repo by cleaning up templates.  In [this](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/105499#note_972755555) MR @brhea tried to remove the template and all references but the pipeline failed.  

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* template: includes/home/ten-oh-announcement
* Unused www homepage & template

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @tywilliams 
- [ ] Consulted: @brhea 
- [ ] 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: 1.0
ENG: Release Post template - Brand refresh

## Goal
We would like to update the release post template to be better inlined with our refreshed brand.  This is similar to the blog refresh where we need to make sure the styles work for previous posts as well.   

All changes with this issue should revolve around the styles and theme of the template. 

Slack thread [here](https://gitlab.slack.com/archives/CN8AVSFEY/p1652798710579189)

### Jobs To Be Done
* **Situation**: Our release template theme is not on brand
* **Motivation**: We want to have this before the June 22nd release
* **Outcome**: When someone goes to our release page the brand matches our new brand refresh

## Page(s)
Which page(s) are involved in this request?
* [Release post example](https://about.gitlab.com/releases/2022/04/22/gitlab-14-10-released/)
* [Figma file](https://www.figma.com/file/JzLrT0korZQuRmnCv7md4K/Release-template?node-id=2%3A53)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @jhalloran @amittner @justin.vetter @ndubord 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update styles related to the GitLab release post


## Out of scope
What is out of scope and not part of this iteration?

- Modifying the markup of the template
- 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: 8.0
Deprecate 12 Solution pages

## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.

|  Solutions Pages to Deprecate                                                    |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/solutions/apm/                                                        |
| https://about.gitlab.com/solutions/developer-platform/                                         |
| https://about.gitlab.com/solutions/no-ticket-provisioning/                                     |
| https://about.gitlab.com/solutions/ops-insights/                                               |
| https://about.gitlab.com/solutions/program-management/                                         |
| https://about.gitlab.com/solutions/public-sector/secure-software/                              |
| https://about.gitlab.com/solutions/public-sector/speed-to-mission/                             |
| https://about.gitlab.com/solutions/reference-architectures/gitlab-reference-architectures.html |
| https://about.gitlab.com/solutions/release-controls/                                           |
| https://about.gitlab.com/solutions/security-risk-mitigation/                                   |
| https://about.gitlab.com/solutions/self-managed-reliability/                                   |
| https://about.gitlab.com/solutions/simplify-devops/                                            |

These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet. 

Related https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/703
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [x] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed

## 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
Deprecate 4 Service and 5 Snapshot pages

## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.

|  Pages to Deprecate                                                    |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/services/implementation/enterprise/ |
| https://about.gitlab.com/services/innersourcing/             |
| https://about.gitlab.com/services/pse-certifications/        |
| https://about.gitlab.com/services/specialized/               |
| https://about.gitlab.com/snapshots/                          |
| https://about.gitlab.com/snapshots/agile-management/         |
| https://about.gitlab.com/snapshots/continuous-delivery/      |
| https://about.gitlab.com/snapshots/continuous-integration/   |
| https://about.gitlab.com/snapshots/security/                 |

These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet. 

### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed

## 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
Deprecate 5 Learn pages

## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.

|  Pages to Deprecate                                                    |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/learn/classification/    |
| https://about.gitlab.com/learn/registration/      |
| https://about.gitlab.com/learn/registration/paid/ |
| https://about.gitlab.com/learn/use-case/          |
| https://about.gitlab.com/learn/use-case/public/   |

These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet. 

### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed

## 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
Deprecate 7 Events pages

## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.

|  Pages to Deprecate                                                    |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/de-de/warum/nutze-continuous-integration-fuer-schnelleres-bauen-und-testen    |
| https://about.gitlab.com/events/commit/2020/      |
| https://about.gitlab.com/events/commit/speakers/ |
| https://about.gitlab.com/events/hacktoberfest-21/  |
| https://about.gitlab.com/events/kubecon-amsterdam/ |
| https://about.gitlab.com/events/kubecon-na/        |
| https://about.gitlab.com/fr-fr/pourquoi/integration-continue-pour-construire-et-tester-plus-rapidement/ | 

These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet. 

### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed

## 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
ENG: Support Child Pages

## Goal
We would like to redesign the support pages which will give users a place to self-help.

## Page(s)
This requires the following:

1. A new design for the [main page](https://www.figma.com/proto/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?page-id=388%3A12778&node-id=388%3A12869&viewport=6507%2C1774%2C0.66&scaling=min-zoom&starting-point-node-id=388%3A12869). We'll be using this [copy deck](https://docs.google.com/document/d/14QciHeozCNpNg_hAjXhO9J5I5jf6BXS1lx8OO-YYMKY/edit#) for final copy.

2. Reformatting of individual pages. With the new design, we will be breaking out the existing long page into individual pages. For the individual pages, reformat them using [this design](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=388%3A13106) as a template/guide.

List of individual pages: 
- [Customer Satisfaction](https://about.gitlab.com/support/customer-satisfaction/)
- [Support Definitions](https://about.gitlab.com/support/definitions/)
- [Managing Support Contacts](https://about.gitlab.com/support/managing-support-contacts/)
- [General Support Practices](https://about.gitlab.com/support/general-policies/)
- [GitLab Policies](https://about.gitlab.com/support/gitlab-com-policies/)
- [Providing Large Files](https://about.gitlab.com/support/providing-large-files/)
- [Scheduling Upgrade Assistance](https://about.gitlab.com/support/scheduling-upgrade-assistance/)
- [Sensitive Information](https://about.gitlab.com/support/sensitive-information/)
- [Statement of Support](https://about.gitlab.com/support/statement-of-support/)
- [US Federal Support](https://about.gitlab.com/support/us-federal-support/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @ctsang-ext @jcolyer 
- [ ] Informed: @fqureshi @laurenbarker 

## In scope
What is within scope of this request?

- [ ] Build template 
- [ ] Apply template to parent and child pages

## Design
- [Figma file](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=368%3A3068)

## Out of scope
What is out of scope and not part of this iteration?

- Side anchor nav is being addressed in this issue https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148

## 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: 10.0
ENG: Why Gitlab scroll | Animation

## Goal
We would like to iterate on the scroll animation for the Why GitLab page

![CleanShot_2022-06-02_at_11.25.39](/uploads/6e3e15da59819a6178bdc83d4123297a/CleanShot_2022-06-02_at_11.25.39.gif)

[Frame.io link](https://app.frame.io/reviews/6e6f4cb3-6a37-46b0-9d2e-d0d9e3e137e1/8c09dbda-d19e-4f81-a6c1-d6cd4f1da271)

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [Why GitLab](https://about.gitlab.com/why-gitlab/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `Engineer` & @jhalloran (for general design support)
- [ ] Consulted: @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Scroll animation for the One Dev Ops Infinity Loop

## Out of scope
What is out of scope and not part of this iteration?

- Any other animations on the page

## 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
- [x] Engineering

Story points: 8.0
ENG: Hero image mask | Animation

## Goal
We would like to create a mask-style animation for the page load in the hero.

![CleanShot_2022-06-02_at_11.03.24](/uploads/4728e9dfd9b54739c65f3a6441d4eb72/CleanShot_2022-06-02_at_11.03.24.gif)

[Figma link](https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26734)

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* Pages with circle hero component ex. [Enterprise](https://about.gitlab.com/enterprise/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] CSS/JS to create mask animation

## 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: 3.0