giseldo/neodataset huggingface dataset:
Update Buyer Experience components with header tags so pages are rendering header content semantically

## Goal
Looking through pages built in our Buyer Experience repo, there are discrepancies in the way we are using heading tags. There are some pages that do not have any h2 tags (they go from h1 to h3) or are completely missing h1 tags. Let's audit what we have and make changes where necessary.

### Jobs To Be Done
* **Situation**: *When someone visits a page built in our Buyer Experience repo*
* **Motivation**: *We want to present header tags correctly / semantically*
* **Outcome**: *So we can improve accessibility and search engine crawling on these pages*

## Examples
Which page(s) are involved in this request?
* [Demo](https://about.gitlab.com/demo/) - no h1
* [Solutions](https://about.gitlab.com/solutions/) - jumping from h1 to h3 tags

## In Scope
-  HTML tag updates

## Not in scope
-  CSS updates

## 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
Safari Cross site scripting console errors

## Goal
Investigate if there's an easy solution to prevent console errors from external vendors in safari (screenshot attached)![Screen_Shot_2022-01-24_at_4.52.19_PM](/uploads/eaab8d361a319d9a535d7b6506585a44/Screen_Shot_2022-01-24_at_4.52.19_PM.png)


## 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
Prevent Cookie banner from appearing in review apps

## Goal

We want to disable OneTrust in review apps in order to have a more enjoyable review experience.

### Jobs To Be Done
* **Situation**: *When review apps are deployed for MRs against https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience or https://gitlab.com/gitlab-com/www-gitlab-com*
* **Motivation**: *We want to disable the OneTrust cookie banner from firing*
* **Outcome**: *So we can not have to look at it*

Story points: 2.0
[Transition 50 pages] Child: stages-devops-lifecycle / Monitor

## Goal
We want to move https://about.gitlab.com/stages-devops-lifecycle/monitor/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

## Page(s)

- [Monitor](https://about.gitlab.com/stages-devops-lifecycle/monitor/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [ ] Yes
- [x] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope

* [ ] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review

Story points: 1.0
Drift Chatbox shows messages in tab title

As per [this issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/264#note_823957805)

Drift chat is still showing (2) New Messages in the title of the tab after being dismissed.

![Screen_Shot_2022-01-27_at_1.16.06_PM](/uploads/40e8413d90a430d9af2a90782d30d46b/Screen_Shot_2022-01-27_at_1.16.06_PM.png)

Story points: 1.0
Add a "share to Hacker News" button to the blog

## Goal
Our CEO Sid has created a marketing OKR to get 12 blog posts on Page One of Hacker News. One way to accomplish this is to add a "share to Hacker News" button to every blog post.

### Jobs To Be Done
* **Situation**: *When blogs are published, people can easily share to Hacker News, something Sid cares passionately about.*
* **Motivation**: *We want to dramatically increase our mentions on Hacker News.*
* **Outcome**: *So we can keep Sid happy, grow traffic, keep our jobs, market to developers*

## Page(s)
Which page(s) are involved in this request?
* `GitLab Blog - about.gitlab.com/blog`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: `vsilverthorne`
- [x] Consulted: `jcoghlan`
- [x] Informed: `msmolensky`

## In scope
What is within scope of this request?

- [x] Deliverable 1 - A button on the blog to share directly to Hacker News (You can find ready to go code here: https://www.shareaholic.com/website-tools/social-share-buttons/yc-hacker-news)
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Any other blog changes
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Review and update homepage security banner

## Goal
We would like to ensure our security and compliance banner is up to date which will improve our communications as measured by the accuracy of our claims.


## 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: @Tinaliseng 
- [ ] Consulted: @mpreuss22, @JohnathanHunt, @Julia.Lake  
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Review this [Slack message](https://gitlab.slack.com/archives/C010XFJFTHN/p1639175795014500) and update homepage security and compliance banner as needed.
- [x] ![Screen_Shot_2022-01-25_at_11.52.50_AM](/uploads/2940459b4fa75d2356328dbaaecaa6b1/Screen_Shot_2022-01-25_at_11.52.50_AM.png)

## Out of scope
What is out of scope and not part of this iteration?

- Changing presentation style of banner

## 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
/solutions/startups

## Goal

We would like to migrate `/solutions/startups/` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the solutions template.

### Jobs To Be Done

* **Situation**: *When a user lands on* `/solutions/startups/`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*

## Page(s)

Which page(s) are involved in this request?

* `[GitHub](https://about.gitlab.com/solutions/startups/)`

## DCI

[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

* [ ] DRI: ``
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`

## In scope

What is within scope of this request?

* [x] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [x] Applying the solutions template to this page
* [x] Building a new component if an acceptable one does not exist
* [x] Creating an additional MR to remove this page from the www-gitlab-com repository

## Out of scope

What is out of scope and not part of this iteration?

* Building a new template
* Any work in www-gitlab-com other than removing the 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: 2.0
Migrate all Typography components

## Goal
Convert all the text in the Buyer Experience repo to be wrapped in <SlpTypography> components. When using the component you must select the variant from a predefined list that has been curated by Slippers. The component also automatically adjusts the text size based on screen size and allows us to handle any internationalization efforts in the future. Text needs to read from right to left, text needs to be truncated etc.

Story points: 6.0
Migrate all Button components

## Goal
Replace all <SlpButton> components in the Buyer Experience repo to use <SlpButton> from slippers-ui.


**Storybook:** https://gitlab-com.gitlab.io/marketing/digital-experience/slippers-ui/?path=/story/components-button--default

**Usage:** https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/blob/main/src/components/Button/Button.stories.js

**Steps to complete:**

The slippers-ui buttons are globally imported, remove all local imports.
```
import SlpButton from '~/components/button.vue
components: {
  SlpButton,
}
```

and update the props (if they've changed). I've removed the dataGaName and dataGALocation props on the button component, I felt they were specific to our product and not all consumers of slippers-ui would need them. I'm open to adding them back, but would prefer if we added them on instantiation.

Once that's done, should be safe to remove button.vue

Story points: 2.0
Replace existing styling with Slippers V1

## Goal
We would like to X which will improve Y as measured by Z.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 4.0
Import Slippers V1 into the Buyer Experience project

## Goal
We would like to X which will improve Y as measured by Z.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 2.0
Follow-up from "Navigation MVC4"

The following discussion from gitlab-com/www-gitlab-com!95836 should be addressed:

- [ ] Top banner displayed must result in dropdown offset 

- [ ] Dropping in here that when hovering, the carats don't have the same transition as the rest of the dropdown, so they briefly appear first.

> ![Screen_Recording_2022-01-24_at_9.23.50_AM](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/6fcee07bee84ecc6d6ed643dccc66b79/Screen_Recording_2022-01-24_at_9.23.50_AM.mov)

- [ ] WAVE accessibility errors
 > ![Screen_Shot_2022-01-25_at_12.19.54_PM](/uploads/96dc91f8169a3a48b3b882e0d1d26f3b/Screen_Shot_2022-01-25_at_12.19.54_PM.png)

Story points: 1.0
Document Google Analytics Updates

## Goal
Create new and/or revise existing handbooks to document the marketing website's **Google Analytics 4** data, specifically:  
- Engagement metrics and conversions (how to measure success)
- Tracking methodology (where does the data come from?)
- Dashboard directory (explanation of the visualized data for self-service team members)  

## Page(s)
Which page(s) are involved in this request?
* General GA overview (marketing POV): https://about.gitlab.com/handbook/marketing/inbound-marketing/search-marketing/analytics/
* GA to Bigquery data: https://about.gitlab.com/handbook/business-technology/data-team/data-catalog/web-traffic-analysis/
* DEX dataLayer and element attributes: https://about.gitlab.com/handbook/marketing/digital-experience/data-dictionary/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dennischarukulvanich  
- [ ] Consulted: @mpreuss22 
- [ ] Informed: @fqureshi @justin.vetter @laurenbarker @RLeihe268 

## In scope
What is within scope of this request?

- [ ] Review existing handbook pages about Google Analytics 
- [ ] Update handbooks to align with GA4
- [ ] Optional: add new handbooks 
- [ ] Optional: archive irrelevant handbooks  

## 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
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 2.0
[Transition 50 Pages] Child: Topics / Severless

## Goal
We want to move https://about.gitlab.com/topics/serverless/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

## Page(s)

- [Serverless](https://about.gitlab.com/topics/serverless/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [ ] Yes
- [x] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker  
- [ ] Informed: `Everyone`

## In scope

* [ ] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review

Story points: 2.0
[Transition 50 Pages] Child: Topics / Micro Services

## Goal
We want to move https://about.gitlab.com/topics/microservices/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

## Page(s)

- [Microservices](https://about.gitlab.com/topics/microservices/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [ ] Yes
- [x] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker  
- [ ] Informed: `Everyone`

## In scope

* [ ] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review

Story points: 1.0
[Transition 50 Pages] Child: Topics / Devops Platform

## Goal
We want to move https://about.gitlab.com/topics/devops-platform/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

## Page(s)
Which page(s) are involved in this request?

[Devops Platform Page](https://about.gitlab.com/topics/devops-platform/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [ ] Yes
- [x] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker  
- [ ] Informed: `Everyone`

## In scope

* [ ] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review

Story points: 2.0
[Transition 50 Pages] Child: Topics / Version Control

## Goal
We want to move https://about.gitlab.com/topics/version-control/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

## Page(s)

- [CI/CD](https://about.gitlab.com/topics/version-control/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [ ] Yes
- [x] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: TBD
- [ ] Consulted: @laurenbarker  
- [ ] Informed: `Everyone`

## In scope

* [ ] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review

Story points: 2.0
[Transition 50 Pages] Child: Topics / DevOps

## Goal
We want to move https://about.gitlab.com/topics/devops/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

## Page(s)
Which page(s) are involved in this request?

[DevOps page](https://about.gitlab.com/topics/devops/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [ ] Yes
- [x] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker  
- [ ] Informed: `Everyone`

## In scope

* [ ] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review

Story points: 2.0
Add Linter to Buyer's Experience

## Goal
We would like to add a Linter to our buyer's experience repo which will improve code consistency as measured by xxx.

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jgarc 
- [ ] Consulted: `DE ENG`
- [ ] Informed: `@mpreuss`

## In scope
What is within scope of this request?

- [ ] Add linter to buyer's experience
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Alter linting in Slippers
- Alter linting to `www`

## 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
Turn on GitLab Reviewer Recommender Bot for Buyer Experience

## Goal
We would like to implement GitLab Reviewer Recommender Bot into the Buyer Experience repository which will improve efficiency for team members reviewing are deploying code.

### Jobs To Be Done
* **Situation**: *When a MR is created in the Buyer Experience repository it recommends reviewers based on the changes made*
* **Motivation**: *We want to automate the process of selecting reviewers*
* **Outcome**: *So we can improve efficiency*

## Page(s)
Which page(s) are involved in this request?
* The Buyer Experience repository
* Relevant [blog post](https://about.gitlab.com/blog/2022/01/04/the-road-to-smarter-code-reviewer-recommendations/) by Taylor Mccaskin

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Implement Reviewer roulette for the Buyer Experience repository 

## Out of scope
What is out of scope and not part of this iteration?

- Any design or template work
- Any work in 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: 4.0