giseldo/neodataset huggingface dataset:
GA4: gtag learn.gitlab.com

## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.

Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US

Place the default `gtag` script *before* the Google Tag Manager and OneTrust scripts across all **learn.gitlab.com** pages. 

Gtag script logic: By default, deny cookie storage for users from the EU, UK, Peru, and Russia; grant cookie storage for all other geolocation. Later on, Google Consent Mode will be enabled on OneTrust, which will dynamically update the values to "denied" or "granted" based on the user's preference. 

```
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}

  gtag('consent', 'default', {
    'analytics_storage': 'granted',
    'ad_storage': 'granted',
    'functionality_storage': 'granted',
    'wait_for_update': 500
  });

  gtag('consent', 'default', {
    'analytics_storage': 'denied',
    'ad_storage': 'denied',
    'functionality_storage': 'denied',
    'region': ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'IS', 'LI', 'NO', 'GB', 'PE', 'RU'],
    'wait_for_update': 500
  });
</script>

<!-- 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-XXXXXX');</script>
<!-- End Google Tag Manager -->

<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js"  type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```


## Page(s)
Which page(s) are involved in this request?
* All learn.gitlab.com pages 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker @justin.vetter 
- [ ] Consulted: @dennischarukulvanich 
- [ ] Informed: @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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
GA4: gtag about.gitlab.com

## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.

Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US

Place the default `gtag` script *before* the Google Tag Manager and OneTrust scripts across all **about.gitlab.com** pages. 

Gtag script logic: By default, deny cookie storage for users from the EU, UK, Peru, and Russia; grant cookie storage for all other geolocation. Later on, Google Consent Mode will be enabled on OneTrust, which will dynamically update the values to "denied" or "granted" based on the user's preference. 

```
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}

  gtag('consent', 'default', {
    'analytics_storage': 'granted',
    'ad_storage': 'granted',
    'functionality_storage': 'granted',
    'wait_for_update': 500
  });

  gtag('consent', 'default', {
    'analytics_storage': 'denied',
    'ad_storage': 'denied',
    'functionality_storage': 'denied',
    'region': ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'IS', 'LI', 'NO', 'GB', 'PE', 'RU'],
    'wait_for_update': 500
  });
</script>

<!-- 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-XXXXXX');</script>
<!-- End Google Tag Manager -->

<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js"  type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```


## Page(s)
Which page(s) are involved in this request?
* All about.gitlab.com pages 
*  @dennischarukulvanich to verify that GA4 is running properly on about.gitlab.com

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker @justin.vetter 
- [ ] Consulted: @dennischarukulvanich 
- [ ] Informed: @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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 4.0
GA4: gtag docs.gitlab.com

## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.

Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US

Place the default `gtag` script *before* the Google Tag Manager and OneTrust scripts across **docs.gitlab.com** pages.

Gtag script logic: By default, deny cookie storage for users from the EU, UK, Peru, and Russia; grant cookie storage for all other geolocation. Later on, Google Consent Mode will be enabled on OneTrust, which will dynamically update the values to "denied" or "granted" based on the user's preference. 

```
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}

  gtag('consent', 'default', {
    'analytics_storage': 'granted',
    'ad_storage': 'granted',
    'functionality_storage': 'granted',
    'wait_for_update': 500
  });

  gtag('consent', 'default', {
    'analytics_storage': 'denied',
    'ad_storage': 'denied',
    'functionality_storage': 'denied',
    'region': ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'IS', 'LI', 'NO', 'GB', 'PE', 'RU'],
    'wait_for_update': 500
  });
</script>

<!-- 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 -->

<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js"  type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```

## 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: @laurenbarker @justin.vetter 
- [ ] Consulted: @dennischarukulvanich 
- [ ] Informed: @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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
ENG: Implement Slipper Icons in BE

## Goal
We would like to remove all icons from the Buyer Experience repository and use the slipper icon component added as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/42). 

### Jobs To Be Done
* **Situation**: *When we use an icon in the Buyer Experience repository we are using a Slippers UI component and not added the icon svg/png/image directly to the project*
* **Motivation**: *We want to improve the performance of our code*
* **Outcome**: *So we can be consistent with our icons across the marketing site*

## Page(s)
Which page(s) are involved in this request?
* All pages built by the Buyer Experience repository

## 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?

- [ ] Pulling in a new Slippers package to the Buyer Experience project
- [ ] Updating all instances of an icon to a Slippers vue component
- [ ] QA every component that includes the new vue icon component
- [ ] QA every page that includes these components

## Out of scope
What is out of scope and not part of this iteration?

- www-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: 2.0
Customize Swiftype css to be on brand

## Goal
We would like to iterate on custom css to style our Swifttype search bar and results to be on brand.

### Jobs To Be Done
* **Situation**: *When the search bar is used, the colors and fonts are on brand*
* **Motivation**: *We want to be consistent with our branding on the marketing site*
* **Outcome**: *So we can increase engagement*

## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Customize the css https://swiftype.com/documentation/site-search/tutorials/custom_styles#custom_css
- [x] Implement on the Buyer Experience repository
- [ ] Implement on the www-gitlab-com repository

## 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
/customers/ change filter to ALL

## Goal
Change filters on the /customers/ page to AND instead of ANY.

## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ndubord 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: @FionaOKeeffe 

## In scope
What is within scope of this request?
- [ ] Change filters to work as follows: Company size and Industry and Region

## 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:
- [ ] Engineering

Story points: 2.0
Accessibility Updates: Pricing Page Modal

## Goal
The 'buy now modal 'Get started/Buy GitLab Premium/Buy GitLab Ultimate' modal is currently not accessible. 

There is no way to use a keyboard to focus or navigate on the modal once it's opened. A screenreader will not prompt the user that the modal is opened / closed.

The modal close/exit button should have appropriate labels that will allow a screenreader to tell the user that the modal will closed once the button is clicked.

## Page(s)
Which page(s) are involved in this request?
* `[Pricing](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: 

- [x] Engineering

Story points: 2.0
Updating Resource page banner report


The current banner highlighted report on https://about.gitlab.com/resources/ is the DevSecOps 2020 report ( Screenshot below). 

![Screenshot_2022-05-10_at_5.29.35_PM](/uploads/0b0c0faba44d8eba8f2d0be954a5847a/Screenshot_2022-05-10_at_5.29.35_PM.png)

Since this is a 2 year old report, and we have a more recent version, can we swap this out for the [2021 DSO survey results](https://about.gitlab.com/developer-survey/)? 

@cblake has confirmed [here](https://gitlab.com/gitlab-com/marketing/demand-generation/campaigns/-/issues/2371#note_948126826) that we should consider this swap if there are no other concerns.


















<!-- Please leave the label below on this issue -->

Story points: 1.0
ENG: Swiftype API Consumption

## Goal
We would like to consume the Swiftype API in our search experience.

This will enable us to create the search experience designed here: [Figma Design](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=137%3A1387)

### Jobs To Be Done
* **Situation**: *We enable the Navigation repository to consume the Swiftype API*
* **Motivation**: *We want to build custom search experience*
* **Outcome**: *So we can increase engagement.*

## Page(s)
Which page(s) are involved in this request?
* Navigation repository

## 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?

- [ ] Enable the Swiftype API in the Navigation repository

## 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
Follow up from Pricing Page Screen Reader Testing - Engineering updates

Fix critical items within the Pricing page that failed criteria on this sheet: https://docs.google.com/spreadsheets/d/1GrfrpWAf39NOt2GMxYwKnE8_JnAaxK9G7dE2ha98eo8/edit#gid=0

**Scope:**
- Tooltips
- Table
- Addons
- FAQ Accordion

Story points: 2.0
Pricing Page - Screen Reader Testing

Review the Pricing page with the [WCAG A/AA guideline sheet](https://docs.google.com/spreadsheets/d/1GrfrpWAf39NOt2GMxYwKnE8_JnAaxK9G7dE2ha98eo8/edit#gid=0) and test with a screen reader.

Create issues, if necessary, for any remaining failed criterion.

Story points: 1.0
ENG: Remove quote section from customers page

## Goal
We would like to remove the quote section from the customers page as the content is repetitive. 

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpenagos-ext 
- [ ] Consulted: @justin.vetter  
- [ ] Informed: @FionaOKeeffe 

## 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: Fix Leding/spacing in Customers hero

## Goal
On the Customers page in the hero when you click on "Drupal Association" the spacing for the stats is not right.

![chrome_QCSy1i8xbJ](/uploads/09ad574078ce5f4f0be2bdfc7b4ef84c/chrome_QCSy1i8xbJ.png)

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: Fix the spacing

## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Record process of signing up for a Free Trial from pricing page

## Goal
We would like to create a screen recording of the process required to sign up for a Free Trial of GitLab.

### Jobs To Be Done
* **Situation**: *When a user clicks on any free trial button on the marketing site.*
* **Motivation**: *We want to have a screen recording of the entire process to complete that action.*
* **Outcome**: *So we can verify what the process is and potential improvements.*

## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com -> free trial button

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: @gherrera-ext 
- [x] Consulted: @laurenbarker 
- [x] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Upload this screen recording to our [GitLab Unfiltered channel](https://about.gitlab.com/handbook/marketing/marketing-operations/youtube/#uploading-conversations-to-youtube). There's a direct link to the YouTube upload page in #6. Or send video to @laurenbarker  
- [x] Post a link to this video in our #digital-experience-team slack channel
- [x] Post a link to this video in this issue

## 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: 2.0
Remove webcasts page and move events page in the navigation

## Goal
We would like to remove the [Webcasts](https://about.gitlab.com/webcast/) page and replace "Webcasts" in the `Learn` navigation with [Events](https://about.gitlab.com/events/) which is currently listed under `People`.

We stopped updating the webcasts page months ago in favor of keeping the events page up to date with both webcasts and live events.

### Jobs To Be Done
* **Situation**: *When ...* a person is looking for live or virtual events
* **Motivation**: *We want to ...* have a single location to view all upcoming events
* **Outcome**: *So we can ...* make it easier for a person to find what they are looking for.

## Page(s)
Which page(s) are involved in this request?
* [Webcasts](https://about.gitlab.com/webcast/)
* [Events](https://about.gitlab.com/events/)

Updated navigation - Remove webcasts, replace with Events
![image](/uploads/0c26af454b66a5bc1125231706e20a58/image.png)

Remove events from the `People` section
![image](/uploads/e90611da876e311bd4fd1fc22a954cd7/image.png)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: `@jgragnola`
- [x] Consulted: `@lblanchard`
- [x] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove Webcasts page from the navigation of `Learn` section
- [ ] Move Events page from the `People` section of the navigation to the `Learn` section

## 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
DISCOVERY: Improving the 404 experience for about.gitlab.com

## Goal
We would like to increase engagement on about.gitlab.com by improving the 404 page. 

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/404/

### Jobs To Be Done

* **Situation**: *When want to gather input from our team members on what they think a great 404 page experience is for about.gitlab.com*
* **Motivation**: *We want to be transparent and collaborate on the new 404 experience for about.gitlab.com*
* **Outcome**: *So we can live our GitLab CREDIT values and increase engagement on the marketing site.*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted:`@mpreuss22` 
- [ ] Informed: `Everyone`

Story points: 2.0
DISCOVERY: Improving the search experience for about.gitlab.com

## Goal
We would like to improve the search experience of the marketing website.

### Jobs To Be Done
* **Situation**: *When a using our search experience on about.gitlab.com, the user finds what they are looking for OR something related and helpful to their search.*
* **Motivation**: *We want to lower the bounce rate, increase pages viewed per session, and increase time on site.*
* **Outcome**: *So we can increase engagement.*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/search/
* Search bar in primary navigation

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: `@mpreuss22 `
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Gather feedback from team on good search experiences
- [ ] Update handbook documentation with our current search tool and architecture

## 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: 2.0