giseldo/neodataset huggingface dataset:
ENG: Why Premium/Ultimate | Update <title> and H1

## Goal
We would like to add the GitLab name into the page title to help with organic search

<title>Why GitLab Premium?</title>
<title>Why GitLab Ultimate?</title>

### Jobs To Be Done
* **Situation**: *When a user searches GitLab tiers adding our name into the results helps brand*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can increase organic search traffic*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/premium/
* https://about.gitlab.com/pricing/ultimate/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @jhalloran @fqureshi `@ncregan` 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update Title of the two pages
- [ ] 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: Features | Update meta description

## Goal
We would like to update the Meta description for the page to _Learn about the various features of GitLab Premium, Ultimate, and Free, including issue tracking, time tracking, reporting, file locking, and more._


### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [Features](https://about.gitlab.com/features)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter `@ncregan` 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Updating meta description
- [ ] 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: Feature Comparison | Update buy links

## Goal
At the top of the Feature Comparison page we would like to update the links (Free trial, Buy premium, Buy Ultimate)

- **Free Trial:** -> https://gitlab.com/-/trials/new?glm_content=default-saas-trial&glm_source=about.gitlab.com&_gl=1*nh1qyb*_ga*MzY4MDQ0NjU4LjE2NTIxMjM0Mjk.*_ga_ENFH3X7M5Y*MTY2MDc1MzIyOS4yMi4xLjE2NjA3NTg1OTAuMC4wLjA.
- **Buy Premium** -> https://gitlab.com/-/subscriptions/new?plan_id=2c92a00d76f0d5060176f2fb0a5029ff&test=capabilities
- **Buy Ultimate** -> https://gitlab.com/-/subscriptions/new?plan_id=2c92a0ff76f0d5250176f2f8c86f305a&test=capabilities



### Jobs To Be Done
* **Situation**: *When a user clicks any of the top links on the page they are taken to the home page*
* **Motivation**: *We want to make sure we continue the correct flow for trial or purchase*
* **Outcome**: *So we can direct potential signups to the correct page*

## Page(s)
Which page(s) are involved in this request?
* [Feature Comparison](https://about.gitlab.com/pricing/feature-comparison/)

## 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?

- [ ] Update all 3 links in the header
- [ ] 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
Google Analytics Tracking: SaaS Trial Event

## Goal

Review the new SaaS Trial flow here: https://docs.google.com/presentation/d/1K-fwk3n_mqN_JDfGGXWMETfIWLPhRoWsEdmV7yJDD-M/

Add the Google Tag Manager JS and OneTrust (if not already included) to the new "About Your Company" page: 
**gitlab.com/users/sign_up/company/new**

Paste this code as high in the `<head>` of the page as possible:
```
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NJXWQL');</script>
<!-- End Google Tag Manager -->
```

Additionally, paste this code immediately after the opening `<body>` tag:
```
<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-NJXWQL"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->
```


Fire the following dataLayer event upon a successful form submission after the "Continue" button click. The `aboutYourCompanyType` should be dynamic. If the user is part of the Free Account flow, they will have an additional toggle field "Gitlab Ultimate Trial". If the user is part of the SaaS flow, the field should not be there, so the variable value should be `ultimate_trial`. 
```
dataLayer.push({
  'event':'aboutYourCompanyFormSubmit',
  'aboutYourCompanyType':'[ultimate_trial or free_account]'
});
```


## Page(s)
Which page(s) are involved in this request?
* gitlab.com/users/sign_up/company/new

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dennischarukulvanich @tywilliams 
- [ ] Consulted: @s_awezec 
- [ ] Informed: @mpreuss22 @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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 4.0
ENG: Integrate Launchdarkly component with the dataLayer

## Goal
Note from Dennis: 

https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/14#note_1050161026

## 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: `@jgarc`
- [ ] Consulted: `Dennis`
- [ ] 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
Add All Resources link and update page

## Goal
We would like to add a link to "[All resources](https://about.gitlab.com/resources/)" and update the page with the latest branding.

### Jobs To Be Done
* **Situation**: *When a website visitor is looking for GitLab resources*
* **Motivation**: *We want to have the newest assets/webcasts accessible \*
* **Outcome**: *So we can drive registrations/downloads from website visitors*

## Page(s)
Which page(s) are involved in this request?
* `[All Resources Page](https://about.gitlab.com/resources/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @Tinaliseng @jhalloran
- [ ] Informed: @fqureshi @laurenbarker 

## 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
- [X] UX Design
- [ ] Engineering

Story points: 2.0
Eng: Replace minimal footer with version from navigation repo

## Goal
Currently some pages (such as the solutions page) use the minimal footer. We should remove the hardcoded footer in BEx, and replace any instances with the minimal footer in the navigation repository. 

Example of implementing our minimal header [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/831).

Story points: 1.0
ENG: Resolve Feature Flag evaluation with experiments

## Goal
Background can be found in this [support ticket](https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/e6d657282472fe1252bdcb1e592caef5/We_are_using_Launchdarkly_w...___LaunchDarkly.pdf)

I'll be honest. I'm still unclear on what a percentage rollout is compared to an experiment. 

## 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: Implement Launchdarkly with Custom Events

## Goal

According to this [support ticket](https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/852679b3678d1a281b31d99956848d78/Hello__We_are_using_Launchd...___LaunchDarkly.pdf), we need to make sure our metrics are set up as custom events within LaunchDarkly. 

> If you are changing the URL upon click, you would have to use a custom conversion (Such as if
you were submitting a form that redirects to a new page, etc.).

> If your click metric triggers a page redirect, then the redirect is happening before the click
event can be sent back to LaunchDarkly.

> Click metrics are unfortunately not very robust; I would suggest recreating the metric as a
custom conversion metric instead:
https://docs.launchdarkly.com/home/experimentation/metrics/custom-conversion.

> This way, you have greater control and can call track when you need to and flush immediately
right after to ensure that the metric event is captured prior to redirect.

Hypothesis: The behavior that I have when using click events is that clicking on said targets will result in incrementing the unique visitors by 1.  

## 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: Debug URL parameters hidden class

## Goal
Discovered in this MR: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/897

`.hidden` class doesn't update when passing URL parameters to pages with a LaunchDarkly component. Checking the props within the LaunchDarkly components shows us the value of the `loading` data value is correct. This makes me believe that the component is not showing this change in value within the UI.

comment with Megan: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/897#note_1058902114

## 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
Inconsistent Text size on the Footer

## Goal
In the footer, we would like to change the text size of "Cookie Preferences" to match the size of the other text.

### Describe the Bug
![image](/uploads/b0263173c9a292d92ed3286be2046be2/image.png)

### What's my browser? 
https://www.whatsmybrowser.org/b/GU0G1

## Page(s)
Which page(s) are involved in this request?
* All pages

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering

Story points: 2.0
Docs Subdomain - Update Google Tag Manager ID

## Goal
The current Google Tag Manager account ID on the docs subdomain is set to `GTM-WZCXKT5` - no one can access this GTM account because it was created by a former employee on their personal work email address. There is an issue within the Google Analytics page URL data where `/index.html` needs to be included in order to match the correlated `index.md` file (analyzed by the technical content writers). Related GitLab [issue here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1214#note_1064405619). 

In order to affix `/index.html`, we'll need to first update the Google Tag Manager ID from `GTM-WZCXKT5` to `GTM-NJXWQL` on docs.gitlab.com, that way we can configure a new GA tags on a GTM account we have access to. 

### Instructions

- Revise the existing GTM code in the `<head>` by switching the ID from `GTM-WZCXKT5` to `GTM-NJXWQL` (<https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/content/assets/javascripts/google_tagmanager.js>):

  ```js
  (function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
  new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
  j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
  'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
  })(window,document,'script','dataLayer','GTM-NJXWQL');
  ```

- Additionally, update the ID in GTM `<body>` tag (<https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/layouts/gtm.html>):

  ```html
  <!-- Google Tag Manager (noscript) -->
  <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-NJXWQL"
  height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
  <!-- End Google Tag Manager (noscript) -->
  ```


## Page(s)
Which page(s) are involved in this request?
* All docs.gitlab.com pages

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @sselhorn @sarahgerman @axil @marcel.amirault @susantacker
- [ ] Informed: @justin.vetter @laurenbarker @mpreuss22 


## 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
Release: Launch Qualtrics survey on Help Topics page

## Goal
We would like to learn more about the Get Help page to find opportunities for improvement by implementing a Qualtrics survey that was completed as part of this issue. 

**What the survey is for**<br>
To determine what users are expecting to find on the [Help Topics](https://about.gitlab.com/get-help/) page.

**Who the survey is to be completed by**<br>
Everyone who comes to the Help Topics page

**How the survey delivered to user**<br>
Immediately on arrival of the Help Topics page using a notification in the corner of the page like [this](https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/791#note_651041011) but with updated branding.

**What URL and platform the survey is hosted on**<br>
[Qualtrics ](https://gitlab.fra1.qualtrics.com/jfe/form/SV_brobq0o5o2Fdtu6)

**How long the survey is open**<br>
Open until we get 200 responses.

![Screen_Shot_2021-08-13_at_14.18.24](/uploads/c718e6a9e840da6edc70c450ead168d8/Screen_Shot_2021-08-13_at_14.18.24.png)

### Jobs To Be Done
* **Situation**: *When a user visits the get help page, a notification displays in the corner for the survey*
* **Motivation**: *We want to gather data on what users are looking for when the arrive on the get help page*
* **Outcome**: *So we can improve our get help page*

## Page(s)
Which page(s) are involved in this request?
* `https://about.gitlab.com/get-help/`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @ctsang-ext 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create notification for survey on Get Help Page, linking out to [this survey](https://gitlab.fra1.qualtrics.com/jfe/form/SV_brobq0o5o2Fdtu6)
- [ ] Answer in thread: Is it also possible to gather what page each person is at before they get to the Get Help 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: 2.0
ENG: Solutions Landing page MVC 1

## Goal
We would like to update [/solutions](https://about.gitlab.com/solutions/) which will improve user experience as measured by metrics.

## Page(s)
Which page(s) are involved in this request?
* [/solutions](https://about.gitlab.com/solutions/)

## Workfiles

* [On-going agenda](https://docs.google.com/document/d/1EWheKycnvlBzDSSE3h5RO9h_GPI7R_3uio7MpJ4rohU/edit?usp=sharing)
* [Figma design](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=2144%3A11815)
* [Copy Deck](https://docs.google.com/document/d/1EP8tAlmI7QX1YfnE4J2lPYN29UNf__SLXOHdZjtgrQw/edit?usp=sharing)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: `@ncregan` @KristinaWeis @andrewrhickey @chandlergibb 
- [ ] Informed: @justin.vetter 

## In scope
What is within scope of this request?

- [ ] Landing page

## Out of scope
What is out of scope and not part of this iteration?

- Single landing page for each theme/grouping for this iteration

## 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: 10.0
Place full navigation on pricing page

## Goal
We would like to remove the minimized navigation component from the pricing page and use the full navigation instead. 

### Jobs To Be Done
* **Situation**: *When a user visits the pricing page*
* **Motivation**: *We want to display the full navigation component in the header*
* **Outcome**: *So we can provide users with a full navigation experience*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Switch 'minimized-navigation' for default layout on pages/pricing/index.vue`
- [ ] Test pricing page to ensure no regressions
- [ ] Fix all regressions due to nav swap before deploying to prod
- [ ] Deploy and and monitor slack channels
- [ ] Create issue for capturing feedback if needed

## 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: Spike Personalization Foundation | Detect if a user is logged into the product from marketing site

## Goal
start on spike work to evaluate our options for detecting when a user is logged into the product from the marketing site. 

### Jobs To Be Done
* **Situation**: *When a user is logged into the product we are able to detect it on about.gitlab.com*
* **Motivation**: *So we can personalize content for users*
* **Outcome**: *Drive users to better content*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @tywilliams 
- [ ] Consulted: @justin.vetter @laurenbarker 
- [ ] Informed: @ndubord @fqureshi 

## In scope
What is within scope of this request?

- [ ] Spike Research on personalization possibilities
- [ ] Integrate with the product so we can create new issues to personalize BE site

## Out of scope
What is out of scope and not part of this iteration?

- Full integration of personalization
- 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: 10.0