giseldo/neodataset huggingface dataset:
Update link for Always Iterating in Main Navigation

## Goal
We would like to update the link for Always Iterating in the main navigation which will improve the user experience as measured by session duration and time on page.


## Page(s)
Which page(s) are involved in this request?
* Main navigation -> Why GitLab -> Always Iterating

## 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?

- [ ] Change Always Iterating to link to https://about.gitlab.com/releases/categories/releases/

## 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
All instances of GitLab's DevOps lifecycle should be in the correct order

## Goal
We would like to have GitLab's DevOps lifecycle in the correct order which will improve consistency as measured by the correct representation of the DevOps lifecycle on our Marketing site.

## Page(s)
Which page(s) are involved in this request?
* Main Navigation -> Why GitLab? -> The DevOps Lifecycle
* Main Navigation -> Platform -> The DevOps Lifecycle
* Please check all instances on the Marketing site.

## 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?

- [ ] Update all instances of GitLab's DevOps Lifecycle to:
    1. Plan
    2. Create
    3. Verify
    4. Package
    5. Secure
    6. Release
    7. Configure
    8. Monitor
    9. Protect
    10. Manage

## 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: 2.0
Implement suggested results for top 5 search queries in Swiftype

## Goal
We would like to reorder our search results for our commonly searched terms which will improve our clickthrough rate. This is a small test to see if improving our search results for customer sought-out topics and content (ex: CI/CD, DevOps, etc) will keep users more engaged. 

## Background
From our [metrics](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/994#note_982711036), customers with a strong intention of making a search tend to navigate to a lot more pages than the average visit. Additionally, studies show how optimizing your internal search not only [improves usability](https://www.nngroup.com/articles/search-visible-and-simple/), but also significantly [increases conversion rates](https://econsultancy.com/is-site-search-less-important-for-niche-retailers/).

## Jobs To Be Done
* **Situation**: *When I am searching for a customer related topic (ex: CI/CD, DevOps, etc)*
* **Motivation**: *I want to see the most relevant information first*
* **Outcome**: *So I can quickly learn about how GitLab can solve my DevOps problem*

## Page(s)
Which page(s) are involved in this request?

Implementing suggested results for the following search qurtird: 
1. gitlab
1. docker
1. devops
1. careers
1. handbook
1. login 

[Excel sheet with re-ordering](https://docs.google.com/spreadsheets/d/10FILy6r0DV6j-QuED7XnNpUIlkFHXvAJ5LcPmtF85XE/edit#gid=0)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `@ctsang-ext` @lduggan 
- [ ] Consulted: @Tinaliseng @jhalloran 
- [ ] Informed: @fqureshi @laurenbarker 

## In scope
What is within scope of this request?

- [ ] Implement suggest results for 5 search queries in Swiftype
- [ ] Determining if we can edit the copy displayed for these results

## 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 / Content
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [x] UX Design
- [x] Engineering

Story points: 2.0
Add Side Navigation to pages with missing navigation

## Goal
With closing https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/677, we now have functional side navigation that we can add to existing high-value pages. This issue pertains to adding that to those specific pages. 

### 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?

- [ ] Enterprise page, small business page
## Out of scope
What is out of scope and not part of this iteration?

- [ ] Feature child pages
- [ ] Solution child pages (originally scoped, but layouts aren't standardized)


## 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: Get Started for Enterprise

## Goal
We would like to build a single template for our Get Started pages which will give users quick tutorials on how to get started using GitLab for Enterprise.

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/get-started/enterprise
* All Get Started pages will use the same template

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @miraclebanks 
- [ ] Consulted: @ctsang-ext @cblake 
- [ ] Informed: @fqureshi @laurenbarker 

## In scope
What is within scope of this request?

- [ ] Iterate on template
- [ ] Apply template to parent and child pages
- [ ]  Depreciate pages with duplicate content and set redircts
## 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: 1.0
ROI calculator - add legal disclaimer

## Goal
As per @rchachra - we should add a legal disclaimer in the ROI calculator. See note below.

> This page should have a disclaimer on it that the output is purely an estimate and subject to change based on various factors that went into the calculation. 

Proposed text: 
The results are purely an estimate and subject to change based on various factors that went into the calculation.

### 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)` https://about.gitlab.com/calculator/roi

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle` @supadhyaya 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Disclaimer in ROI calculator page
- [ ] 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
Bizible script shows twice in <head> in product

## Goal
After adding Bizible script to sign up pages and enabling it for gitlab.com, @dennischarukulvanich noticed that the `https://cdn.bizible.com/scripts/bizible.js` script was displaying twice in the `<head>`. 

![screen_shot_2022-06-17_at_11.58.22_am](/uploads/83ee020247ecf371773f915f48db7ed2/screen_shot_2022-06-17_at_11.58.22_am.png)

This issue is for further iterating on the original feature MR here to ensure the script only displays once. 

[Related slack thread in #digital-experience-team](https://gitlab.slack.com/archives/CN8AVSFEY/p1655491092242909)

## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/-/trials/new
* https://gitlab.com/-/trials/select
* https://gitlab.com/users/sign_up
* https://gitlab.com/-/trial_registrations/new
* https://gitlab.com/users/almost_there
* https://gitlab.com/users/sign_up/groups/new
* https://gitlab.com/users/sign_up/projects/new
* https://gitlab.com/users/sign_up/groups_projects/new
* https://gitlab.com/users/sign_up/welcome/trial_getting_started


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @degan @dennischarukulvanich 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?
- [ ] `gdk update` and fixing issues to enable local development
- [ ] MR to iterate on Bizible feature for GitLab
- [ ] Ensure change is enabled on production for 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 5.0
ENG: Refresh Update page

## Goal
We would like to update the /update/ page to match the card styles created on the /install/ page

### Jobs To Be Done
* **Situation**: *When ...*When a user goes from the Install page to the update page the styles are different*
* **Motivation**: *To have a consistent user experience*
* **Outcome**: *Clean up code*

## Page(s)
Which page(s) are involved in this request?
* [Update](https://about.gitlab.com/update/)
* [Install](https://about.gitlab.com/install)

## 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 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update styles/template

## Out of scope
What is out of scope and not part of this iteration?

- Updating Copy


## 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
Bug: Features LP - Pipeline security link points to a 404 page

### Describe the Bug

Clicking on `Pipelines security` from https://about.gitlab.com/features/?stage=verify leads to a [404 page](https://docs.gitlab.com/ee/user/project/new_ci_build_permissions_model.html). Unsure which docs page it should point to.

Also, should it read 'Pipeline security' without the plural 's'?

![Screen_Shot_2022-06-16_at_2.29.58_PM](/uploads/dc2792d5de0646d0935e8fd84c8e3ae3/Screen_Shot_2022-06-16_at_2.29.58_PM.png)

### What's my browser? 
Chrome

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/?stage=verify
* https://docs.gitlab.com/ee/user/project/new_ci_build_permissions_model.html

## 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
UX: Features landing page / UX research

## Goal
When making updates to the [Features page](https://about.gitlab.com/features/), I want to first do research so I can better understand what improvements are needed for a better user experience.

### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to easily find information about features that are relevant to my needs*
* **Outcome**: *To better understand if GitLab is the right solution for my problems*

## Page(s)
Which page(s) are involved in this request?
- [/features](https://about.gitlab.com/features/)

## Workfiles
[UX research doc](https://docs.google.com/document/d/1fHF4Hf5J-AxVYB_eb5vAC1MeaU72IqZQmcPDLufNR8U/edit?usp=sharing) - WIP
[See comment re: conversion goals](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1067#note_1016931422) 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted:  @jhalloran @ctsang-ext @dennischarukulvanich  
- [ ] Informed: @fqureshi 

## In scope
What is within scope of this request?

- [x] [Analytics report](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/941#note_970044291) - completed by @dennischarukulvanich 
- [ ] Review LogRocket Sessions
- [ ] Usability testing - MVC 3 vs MVC 4
- [x] [Stakeholder interviews](https://docs.google.com/document/d/18p_IC9q6iWD68lQ7hoMOGXixCVy0fbM_v9aEUYcIr-I/edit?usp=sharing)
- [x] Review [post-purchase survey](https://docs.google.com/presentation/d/1OQRID4vKwpeUAfgVYlDDrsv4whqSmb7R9Us_Q1EaiFY/edit?usp=sharing)


## 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
- [x] UX Design
- [ ] Engineering

Story points: 10.0
ENG: Features landing page / UX Updates / MVC 3

## Goal
We would like to update the UX on [/features](https://about.gitlab.com/features/) which will improve how potential customers learn about the Features that GitLab offers.

### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to review the features that are relevant to my needs*
* **Outcome**: *So I can make an informed purchasing decision.*


## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: `@dzalbo` `@cblake` @jhalloran 
- [ ] Informed: @justin.vetter @fqureshi 

## In scope
What is within scope of this request?

- [ ] Design updates as annotated in this [Figma file](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=971%3A4672)


## Out of scope
What is out of scope and not part of this iteration?

- content refresh


## 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: 5.0
ENG: Swap old logo from press page

## Goal
We would like to swap out the old Tanuki logo from the /press page

![CleanShot_2022-06-15_at_11.44.38](/uploads/695fd2212a81088c484760c7a1c1f0da/CleanShot_2022-06-15_at_11.44.38.jpg)

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[/press](https://about.gitlab.com/press/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jgarc 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Swap logo

## 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
CODEOWNERS iteration - Add /company

## Goal
We should ensure that CODEOWNERS for /company pages that have been migrated from [www-gtilab-com](https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/sites/uncategorized/source/company) to our [Buyer Experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/company) or communicate these permissions have been changed. 

Here is a [related slack thread](https://gitlab.slack.com/archives/C81PT2ALD/p1655183589470129) to CODEOWNERS for pages within the [/company](url) directory. 

### Jobs To Be Done
* **Situation**: *When anyone makes a change to a page within the /company URL, the proper people are notified to review the merge request.*
* **Motivation**: *We want to ensure owners of these pages have oversight changes.*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/company/
* https://about.gitlab.com/company/culture/all-remote/


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Determine appropriate people to be listed as code owners of company pages in the Buyer Experience repository
- [ ] Update CODEOWNERS in Buyer Experience with these people
- [ ] Communicate changes to GitLab if necessary 

## 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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Public Sector quote carousel previous button is facing the wrong direction

## Goal

The Previous button's chevron is facing the wrong way in the quote carousel, so it looks like there are two next buttons.

![image](/uploads/f863186260ee2c458865897d8ebd6b03/image.png)

## Page(s)
Which page(s) are involved in this request?
* `/solutions/public-sector` [link](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: 1.0
ENG: Case Study LP - Remove horizontal padding around the title

## Goal
We would like to remove the horizontal padding around the titles in the hero of the case study landing page which will improve readability as measured by click-through rates. 

### Describe the Bug
Large padding splits the title up over too many lines making it difficult to read and absorb.

This was a [community contribution](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/105962) for the blog that I agree with and would like to implement on the case study pages as well.

Here is a screenshot of the blog improvements: 

![Screen_Shot_2022-06-14_at_12.06.34_PM](/uploads/1a22a20ecb5f2d37b390d93ca698b4fa/Screen_Shot_2022-06-14_at_12.06.34_PM.png)

### What's my browser? 
- This change is for mobile only

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/customers/

## 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: Remove Parts Unlimited Case Study

## Goal
We would like to remove the [Parts Unlimited](https://about.gitlab.com/customers/parts_unlimited/) case study from the site

### Jobs To Be Done
* **Motivation**: This is a fictitious company and having it in our customers page makes us loose credibility

## Page(s)
Which page(s) are involved in this request?
* [Parts Unlimited](https://about.gitlab.com/customers/parts_unlimited/)

## 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: @FionaOKeeffe 

## In scope
What is within scope of this request?

- [ ] Remove Parts Unlimited case study

## 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: Tool tip icon cut off in Safari

## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?

### Describe the Bug
In Safari, the information tool tip icon is cut off. Can we remove the height of `.tooltip` to display the full icon?

![Screen_Shot_2022-06-14_at_9.36.31_AM](/uploads/f1c5f35e29b62907ba3ed1d130e38128/Screen_Shot_2022-06-14_at_9.36.31_AM.png)

### What's my browser? 
https://www.whatsmybrowser.org/b/GSXCV

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/

## 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