giseldo/neodataset huggingface dataset:
Remove Commit Virtual from Commit website

## Goal
We would like to have the Virtual registration section removed from the Commit website as it's being delayed til February 2023. Mentions of Virtual for speakers should also be removed. 

### Jobs To Be Done
* **Situation**: *When users visit the Commit website*
* **Motivation**: *We want to promote only the NY and London events at this time*
* **Outcome**: *So we can encourage registration for the in-person events instead of Virtual*

## Page(s)
Which page(s) are involved in this request?
* [Commit](https://about.gitlab.com/events/commit/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @meganfilo 
- [ ] Consulted: ` @jhalloran  @khartline `
- [ ] 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: 1.0
Typography Adjustment - Support Template

## Goal
The typography on the main support page seems "off" compared to [the Figma template](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=388%3A12778). Some things I've noticed are: 

| Section | Figma | https://about.gitlab.com/support/ | Screen Shot | Style |
|---------|-------|-----------------------------------|-------------|-------------|
| [Test in priorty support table](https://about.gitlab.com/support/#priority-support) | font size: 16px | font size: 20px | ![Screen_Shot_2022-08-09_at_10.33.15_AM](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/612518b1cc680dd6ca9018f9349210ae/Screen_Shot_2022-08-09_at_10.33.15_AM.png) | Body 2 | 
| All bulleted text | font size: 16px, line-height: 24px , text-indent: 16px | font size: 20px, line-height: 24px, no text indent | ![Screen_Shot_2022-08-09_at_10.35.04_AM](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/06ed51d092f1d2ec7332dfa8426acfa1/Screen_Shot_2022-08-09_at_10.35.04_AM.png) | Lists |
| More Help @ bottom | ![image](/uploads/fcb3130c5a0245828f47e7a1c5436efd/image.png) | duplicated text at font-size: 16px, line-height: 24px | ![Screen_Shot_2022-08-09_at_10.39.14_AM](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/17c1d2b27b718f9442527f4eb21f4998/Screen_Shot_2022-08-09_at_10.39.14_AM.png) | None, please remove smaller text |


make sure we are following the grid, per comment above:

| In production | In design |
| ------ | ------ |
| ![image](/uploads/baa8f2dbe85e4888dcfbfd87440363cf/image.png) | ![image](/uploads/4a3ded715cb93079b43a232e5408ae92/image.png) |


### What's my browser?  
https://www.whatsmybrowser.org/b/M528L

## 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
- [x] UX Design
- [x] Engineering

Story points: 3.0
ENG: /features - Implement side nav

## Goal
Implement side navigation to all /features pages that have been updated with the most recent template.

## Page(s)
Which page(s) are involved in this request?
* [Continuous Integration](https://about.gitlab.com/features/continuous-integration/)

## 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: /solutions - Implement side nav

## Goal
Implement side navigation to all /solution pages that have been updated with the most recent template.

## Page(s)
Which page(s) are involved in this request?
* [Automated Delivery](https://about.gitlab.com/solutions/delivery-automation/)
* [Continuous Software Security Assurance](https://about.gitlab.com/solutions/continuous-software-security-assurance/)
* [Public Sector](https://about.gitlab.com/solutions/public-sector/)

## 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
ENG: Results by Type - Blog, Handbook, All

## Goal
We would like add a feature to our search results that enables users to view results by type.

We want to let users know how many results exist in the Blog, Handbook, Everything, and enable them to view just those results. 

![Screen_Shot_2022-08-02_at_8.56.40_AM](/uploads/9ff57896dc7fafb71c0636d2ae53525e/Screen_Shot_2022-08-02_at_8.56.40_AM.png)

### Jobs To Be Done
* **Situation**: *A user can sort results by type that is powered by Swiftype site search API.*
* **Motivation**: *We want to lower bounce rate, increased pages per session, and increased time on site.*
* **Outcome**: *So we can increase engagement.*

## Page(s)
Which page(s) are involved in this request?
* The search bar in the navigation


## 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?

- [ ] Add sort by type (Blog, Handbook, Everything) feature
- [ ] Ship to about.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: 4.0
ENG: Sort Results

## Goal
We would like add a feature to our search results that enables users to sort results.

This issue is for implementing the "Sort by" component at the top of the full panel layover.

[Figma Design](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=137%3A1387)
![Screen_Shot_2022-08-02_at_8.51.59_AM](/uploads/b25bed38030e129afaefc197320b20e3/Screen_Shot_2022-08-02_at_8.51.59_AM.png)

### Jobs To Be Done
* **Situation**: *A user can sort results that is powered by the Swiftype site search API.*
* **Motivation**: *We want to lower bounce rate, increased pages per session, and increased time on site.*
* **Outcome**: *So we can increase engagement.*

## Page(s)
Which page(s) are involved in this request?
* The search bar in the navigation


## 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?

- [ ] Add sort by feature
- [ ] Ship to about.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: 4.0
ENG: Results and Pagination

## Goal
We would like to implement a new search design template and apply it to the search experience launched from the header of about.gitlab.com.

This issue is for implementing the full panel lay over with results and pagination.

[Figma Design](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=137%3A1387)


![Screen_Shot_2022-08-02_at_8.48.56_AM](/uploads/e9cef1e76b22e848cca6afa3d0960a77/Screen_Shot_2022-08-02_at_8.48.56_AM.png)
### Jobs To Be Done
* **Situation**: *When a user clicks on the search icon in the header, they get the new template design that is powered by the Swiftype site search API.*
* **Motivation**: *We want to lower bounce rate, increased pages per session, and increased time on site.*
* **Outcome**: *So we can increase engagement.*

## Page(s)
Which page(s) are involved in this request?
* The search bar in the navigation

## 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 new search template with results and pagination
- [ ] Stretch goal to display the icon and result type
- [ ] Ship to about.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: 4.0
Commit Registration Page: Add Speakers

https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1070#note_1046593435

> We would like to add additional speakers to the featured speakers section of the website.
>
> The three people we would like to add are:
> 
> * Fernando Diaz - Senior Technical Marketing Manager ([Fernando's GitLab Profile](https://gitlab.com/fjdiaz))
> * Francis Ofungwu - Global Field CISO ([Francis' GitLab Profile](https://gitlab.com/fofungwu))
> * William Arias - Senior Technical Marketing Manager ([William's GitLab Profile](https://gitlab.com/warias))
> 
> [Here is a link to the headshots](https://drive.google.com/drive/folders/1MpT8pY2kUgVm38UzOL3BGARFXm_cqlcq)


## Scope of changes
- [ ] Add speakers to content file
- [ ] Adjust speakers section UI if necessary
- [ ] Update NY address

Story points: 2.0
ENG: Pricing | Add contact sales link to Ultimate tier card

## Goal
We would like to add an additional contact sales link to the Ultimate tier card which will improve how customers can buy GitLab as measured by increased Enterprise sales.

### Jobs To Be Done

* **Situation**: *When an Enterprise customer visits our pricing page...*
* **Motivation**: *We want to offer them their preferred method of buying GitLab ...*
* **Outcome**: *So we can finalize their purchase.*

## Page(s)

Which page(s) are involved in this request?

* [Pricing](https://about.gitlab.com/pricing/)
* [Figma designs](https://www.figma.com/file/uwtK7pFI6KRHeQBL8Pk8RP/Pricing---tier-updates?node-id=35%3A7705)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @jhalloran @justin.vetter `@fqureshi` 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add contact sales link to ultimate card
- [ ] 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: Homepage | remove/hide See what's coming in GitLab 15 and beyond pill

## Goal
We would like to remove/hide the `See what's coming in GitLab 15 and beyond →` pill from the homepage header section. We will replace the link with a new pill link in the future.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [homepage](https://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: @fqureshi @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove the pill link
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Changing the link
- 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: Content update Commit Landing page

## Goal
We would like to add the location venue information for two of the events.  We would also like to swap out the image for the virtual event.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [Commit](https://about.gitlab.com/events/commit/)
* [Figma](https://www.figma.com/file/zxa7DLEbZrkeh0YJozVOqb/Event-Templates-%2F-Commit-2022?node-id=2150%3A8170)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @jhalloran @fqureshi @justin.vetter 
- [ ] Informed: `@khartline`

## In scope
What is within scope of this request?

- [ ] Add links to a Google map address for New York City and London venues
- [ ] Update FAQ section with venue information `When and where` in the [FAQ Doc](https://docs.google.com/document/d/1w_MysOiyfDRW5DFi3NUx1cTCuN3VNBJWwPmZilRdxhE/edit#heading=h.5xovaeihi7p0)
- [ ] Swap thumbnail image for Virtual event

## 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
[Phase 2] Automate the synchronization of features.yml into Buyer Experience

## Goal
We would like to synchronize feature.yml in both the www repository and the buyer experience repository.

**How?**

_This is just a rough idea, I haven't looked into it much_

Create a step in the www-gitlab-com pipeline that either uses gitlab-api GET, gitlab pages, or whatever else to host features.yml. Then in Buyer Experience write a script/another step in the build to curl the file down.

Story points: 6.0
ENG: Update pricing faq

## Goal
The FAQ section on the pricing page is getting out of sync, there have been changes, like this one: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/107569#note_1040516722

That hasn't been copied over.

## Page(s)
Which page(s) are involved in this request?
* [Pricing](https://about.gitlab.com/pricing) FAQ section
* [Changes to be mirrored](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/107569/diffs#note_1040516722)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter
- [ ] Informed: `@m_taylor` 

## In scope
What is within scope of this request?

- [ ] Update FAQ section
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Integrate legacy pricing_faq.yml to current page
- 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
Re-add deprecated localized pages

## Goal
As per this slack [thread](https://gitlab.slack.com/archives/CN8AVSFEY/p1658752802724089), add back the following pages that were removed in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/971):

- https://about.gitlab.com/fr-fr/pourquoi/integration-continue-pour-construire-et-tester-plus-rapidement/
- https://about.gitlab.com/de-de/warum/nutze-continuous-integration-fuer-schnelleres-bauen-und-testen/

### 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: 1.0
ENG: Icons on ROI calculator page are showing up very small and filled in rather than outlined

## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?

### Describe the Bug
What is the bug?

Icons on ROI calculator page are showing up very small and filled in rather than outlined

### What's my browser? 
Share your browser information from https://www.whatsmybrowser.org/ 

[https://www.whatsmybrowser.org/b/OFL7U](https://www.whatsmybrowser.org/b/OFL7U)

## Page(s)
Which page(s) are involved in this request?
* [ROI Calculator](https://about.gitlab.com/calculator/roi/)

| Live | Figma |
| ------ | ------ |
| ![Screen_Shot_2022-07-27_at_15.03.49](/uploads/c00808213794a5a91f730d1db21ad826/Screen_Shot_2022-07-27_at_15.03.49.png) | ![Screen_Shot_2022-07-27_at_15.13.00](/uploads/6d35df1000cfda9dcce626e51857d3dd/Screen_Shot_2022-07-27_at_15.13.00.png) |



## 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
Migrate Commit page SVGs to Slippers

With a tight due date, I was unable to add the new SVG icons we are using on the new Commit page to Slippers. 
As part of this issue I will:

- [x] Add icons to Slippers
- [ ] Once Slippers version is bumped in Buyer Experience, swap out the hardcoded icons for the SlpIcon alternative

Story points: 2.0
Plan: Support Services page (Exploration and Research)

## Goal
We would like to learn more about the Support Services page to find opportunities for improvement

### Jobs To Be Done
TBD

## Page(s)
Which page(s) are involved in this request?
- [Support Services](https://about.gitlab.com/services/#contactform) 
- [Figma](https://www.figma.com/file/2zmj9hb6MBH40d6NMZm8Jw/Professional-Services?node-id=26%3A3)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @Tinaliseng, @jhalloran, @dennischarukulvanich 
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?

- [ ] Exploration + Next steps for design and/or research

## 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
- [x] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 6.0
Define requirements to consume Swiftype API

## Goal
We would like to define requirements for about.gitlab.com to consume the Swiftype API. This will enable us to customize the search experience and execute on the parent OKR of this issue. 

### Jobs To Be Done
* **Situation**: *We are using a javascript snippet from Swiftype to enable search functionality, as documented in the [quick start guide here](https://swiftype.com/documentation/site-search/crawler-quick-start). This limits our ability to customize the experience.*
* **Motivation**: *We want to implement the [Swiftype site search API](https://swiftype.com/documentation/site-search/overview) to programmatically alter how our 
  * pages are crawled
  * documents are indexed
  * searches are completed
  * analytics are generated
  * and more!
* **Outcome**: *To do this, we need to define requirements to implement the site search API on about.gitlab.com.*

## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com - search that exists in the header
* https://swiftype.com/documentation/site-search/overview 

## 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?

- [ ] Investigate the Swiftype search API
- [ ] Create a feature branch or sandbox environment that uses the search type api
- [ ] Define requirements to implement Swiftype search API on primary header search on a about.gitlab.com
- [ ] Create issue to implement Swiftype search API

## Out of scope
What is out of scope and not part of this iteration?

- This issue is not for implementing the api, is purely exploratory and to define the requirements.

## 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