giseldo/neodataset huggingface dataset:
[ENG] Homepage | Remove Launch Darkly code from hero

## Goal
We would like to remove the LaunchDarkly code around the hero and deploy the variant hero subcopy

#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal is to remove LaunchDarkly code from hero in preparation for next AB test`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* `[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: @justin.vetter @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove LD code
- [ ] Deploy Variant subcopy

## 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
UX: Security & Compliance Lightning strike: Compliance page - refresh

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

Story points: 3.0
ENG: Topic page template / Related content tab UI update

### Describe the Bug
Tabs titles are too close to the active state underline


<details><summary>Current</summary>![Screen_Shot_2022-10-14_at_10.23.36_AM](/uploads/965cf9723741f5736a94c3e3dd07aaa3/Screen_Shot_2022-10-14_at_10.23.36_AM.png)

</details>

Todo:

1. 16px of space between the copy and the underline
2. Reduce active underline to 24px on each side. 

![Screen_Shot_2022-10-14_at_10.27.58_AM](/uploads/2cd9cf268f8d40dc8ba067dadee7761c/Screen_Shot_2022-10-14_at_10.27.58_AM.png)


## Page(s)
Which page(s) are involved in this request?
* All instances on /topics
* Example: https://about.gitlab.com/topics/devops/

## 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
Navigation: Change "Customer Case Studies" to "Customer Success Stories"

## Goal
We would like to Change "Customer Case Studies" to "Customer Success Stories" in the main navigation which will improve traffic to this section of the site as measured by CTA clicks and visits to the page.


#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [x]  Yes `@dsteer` 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

## Page(s)
Which page(s) are involved in this request?
* `Main Navigation`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@mpreuss22` 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Change "Customer Case Studies" to "Customer Success Stories"

## 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
Remove DevOps Stages section from homepage

## Goal
We would like to remove the DevOps Stages section of the homepage which will improve our product marketing messaging as measured by homepage engagement metrics.


#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [x]  Yes `@dsteer`  
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* `[Homepage](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: `@mpreuss22`  
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove this section of the homepage
- [ ] ![Screen_Shot_2022-10-13_at_2.40.17_PM](/uploads/9e2d31c7a1110a386f012e8e1ce9a020/Screen_Shot_2022-10-13_at_2.40.17_PM.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
ENG: Solutions / Software Supply chain security - refresh

## Goal
We would like to update the [Software Supply chain security](https://about.gitlab.com/solutions/supply-chain/) landing page to support our [Security & Compliance lightning strike](https://gitlab.com/groups/gitlab-com/marketing/-/epics/3271).

## Workfiles

- [Content doc](https://docs.google.com/document/d/1QpfhcnwhkaZvpjid7mwOpg_fw6l6FXeITF7ATMQEs1g/edit)
- [Figma file](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=157%3A5204)

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/supply-chain/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI:  
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: @justin.vetter @fqureshi 

## In scope
What is within scope of this request?

- [ ] Update the existing [Software Supply Chain Security](https://about.gitlab.com/solutions/supply-chain/) 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
- [ ] UX Design
- [x] Engineering

Story points: 3.0
ENG: Solutions / Change 'Take GitLab for a Spin' copy

## Goal
I would like to iterate on the line `Take GitLab for a Spin` which will improve clicks as measured by metrics.

This section has the lowest engagement on the page ([source](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1375#note_1118351358)) so we would like to test an alternative line of copy. I hypothesize that 'Take GitLab for a Spin' is both too vague and too aggressive. I would like to replace the line with `Try Ultimate for Free` which is a more clear and more succinct call to action.

<details><summary>Current</summary>
![Screen_Shot_2022-10-12_at_3.14.20_PM](/uploads/5c5f0471e3af93d69fc8218a9a84fa35/Screen_Shot_2022-10-12_at_3.14.20_PM.png)
</details>

<details><summary>Updated</summary>
![Screen_Shot_2022-10-12_at_3.14.04_PM](/uploads/af737cc463d58218fa1cacee548b96b6/Screen_Shot_2022-10-12_at_3.14.04_PM.png)
</details>

### Technical details
The current <NextStep/> component uses a universal yml file for all of the content across the site.  We will need to modify the component to look for data coming from the page yml file and have a fallback to use the current universal yml file. 

## Page(s)
Which page(s) are involved in this request?
1. All /solution child pages 
1. https://about.gitlab.com/solutions

## In scope
What is within scope of this request?

- [ ] Modify the current <NextStep> component to accept page data with a fall back to use the current universal yml file
- [ ] Replace ~~Take GitLab for a Spin~~ with `Try Ultimate for Free` on /solutions and /solution child pages

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @dennischarukulvanich 
- [ ] Informed: @justin.vetter 


## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 3.0
[ENG]: Bug Features page | Text breaking out of container

### Describe the Bug
There is a visual bug where the text is breaking out of the card container on the features page.

<details><summary>Screen Shot</summary>
![CleanShot_2022-10-12_at_14.50.32](/uploads/56e4f2eb5fe1440857d835111b40f87b/CleanShot_2022-10-12_at_14.50.32.jpg)
</details>

### What's my browser? 
Share your browser infromation from https://www.whatsmybrowser.org/ 

## Page(s)
Which page(s) are involved in this request?
* `[Features](https://about.gitlab.com/features)`

## 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: 1.0
[ENG] : Pricing Page | Salient bullet design update

## Goal
We would like to revisit how the salient bullet points are displayed as the list for premium and ultimate appear to be the same length.

<details><summary>Screen Shots</summary>
Before salient bullet point change: 
![Screen_Shot_2022-09-28_at_12.22.11_PM](/uploads/af13fe7bad2051366733d89de0eb3879/Screen_Shot_2022-09-28_at_12.22.11_PM.png)

After salient bullet point change: 
![Screen_Shot_2022-09-28_at_12.14.47_PM](/uploads/398dc0536f4bbcd7f295e0a12b2a6496/Screen_Shot_2022-09-28_at_12.14.47_PM.png)
</details>

### _We do not want this to go live until AB tests are complete on the Pricing page_

#### Jobs To Be Done
* **Situation**: When users are reviewing the different plans on the pricing page 
* **Motivation**: We want to display how much more a user is getting with the ultimate tier 
* **Outcome**: So we can help users differentiate the different tiers 

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [X]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [X]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - The ultimate salient bullet points should look longer than the premium 

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No

## Page(s)
Which page(s) are involved in this request?
* [Pricing Page](https://about.gitlab.com/pricing/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] [Figma designs](https://www.figma.com/file/uwtK7pFI6KRHeQBL8Pk8RP/Pricing---tier-updates?node-id=476%3A16571)

## 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
Bug: Incorrect logo on blog post

## Goal
Somehow our very new logo appears on this blog post from 2015: https://about.gitlab.com/blog/2015/07/03/our-new-logo/ 

Let's find the old svg re-upload it somewhere new and then update the blog post to point to that new image location.

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Updating old blog post to reference the correct 2015 logo`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `Blog post displays correct logo from 2015`

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/blog/2015/07/03/our-new-logo/ 

## 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?

- [ ] Find the old logo file
- [ ] Update the blog post to point to correct old logo

## 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
Create sprint changelog

## Goal
We would like to create a changelog that is autogenerated at the end of every iteration. We will use add at the bottom of each executive iteration update to direct people to if they'd like to dig deeper.

#### Jobs To Be Done
* **Situation**: *When a iteration is completed, all the items completed are added to changelog.*
* **Motivation**: *We want to create a efficient way to communicate the work completed by the Digital Experience team.*
* **Outcome**: *So we can ensure transparency.*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [x]  Yes @mpreuss22 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - `Changelog exists`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* Changelog for about.gitlab.com - only Buyer Experience 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create changelog for the Buyer Experience repository
- [ ] Automate changelog to generate at end of iteration cadence 
- [ ] Documentation in the handbook
- [ ] Developer docs in repo, /docs  

## 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
Create new 'About GitLab' template

## Goal
We would like to update create a new template for the [About GitLab](https://about.gitlab.com/company/) page.


### Jobs To Be Done
* **Situation**: *When prospects want to learn more about GitLab as a company.*
* **Motivation**: *We want to ensure the information on the page is current, accurate, and in line with our messaging.*
* **Outcome**: *So we can provide them with the correct information and provide awareness.*

## Page(s)
Which page(s) are involved in this request?
* `[About GitLab](https://about.gitlab.com/company/)`

## 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?

- [ ] Code template from [Design](https://www.figma.com/file/pigc5p3VIgMlp7IopvdFoM/About?node-id=0%3A1): Updating the design to align with our latest 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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 6.0
Update Translated URL Structure  and hreflang-tagging handbook

## Goal
We would like to ensure the information under Translated URL Structure, hreflang-tagging, and list of localized websites is still accurate (or even relevant)?


#### URLS
* https://about.gitlab.com/handbook/marketing/localization/#translated-url-structure
* https://about.gitlab.com/handbook/marketing/localization/#hreflang-tagging
* https://about.gitlab.com/handbook/marketing/localization/#list-of-localized-websites

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: `we are implementing a GDN POC with Smartling, and need to determine what localized sites allready exists and technology around them`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [x]  Yes @laurenbarker 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `Update the handbook with accurate information`

**How do we measure success?**
 - `Handbook is updated and list of localized sites is accurate`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @lduggan 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Figure out the history of the handbook page
- [ ] Determine if the information is relevant
- [ ] update the handbook

## 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
- [ ] Engineering

Story points: 1.0