giseldo/neodataset huggingface dataset:
Hero logo placement on mobile

### Describe the Bug
Logo placement is awkward on mobile

Current layout:

![Screen_Shot_2022-05-02_at_11.27.52_AM](/uploads/684a016ddb7a7534f5a6bcb319dc61be/Screen_Shot_2022-05-02_at_11.27.52_AM.png)

Update to:

![Screen_Shot_2022-05-02_at_11.28.06_AM](/uploads/53812e5755dc7f4a9cb55b03a6965a58/Screen_Shot_2022-05-02_at_11.28.06_AM.png)


## Page(s)
Which page(s) are involved in this request?
* All hero pages - Example: https://about.gitlab.com/small-business/ and https://about.gitlab.com/enterprise/
* [Figma file for reference](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=1787%3A7553) 

## 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
Benefits block: Image disappears when interacting with the accordion

### Describe the Bug
Image disappears when interacting with the accordion.

Watch loom video:
https://www.loom.com/share/377b0963545c4770b83d6b3cca69d05c

### What's my browser? 
Chrome

## Page(s)
Which page(s) are involved in this request?
* [Enterprise](https://about.gitlab.com/enterprise/)
* [Small Business](https://about.gitlab.com/small-business/)

Maybe more 

## 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
UI Fixes SMB - Showcase component spacing

## Goal
We would like to improve the spacing between sections to allow for breathing room. 

Fix this bug https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/820#note_945131372

### Describe the Bug
Not a bug, just an update. Please increase the spacing between sections to 96px

![Screen_Shot_2022-05-02_at_7.26.33_AM](/uploads/52409e069608853868348a605b62ce72/Screen_Shot_2022-05-02_at_7.26.33_AM.png)

## Page(s)
Which page(s) are involved in this request?
* [Solutions/small-business](https://about.gitlab.com/small-business/)

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 3.0
Bug: Footer: Solutions --> Education = wrong page, should direct to Campus

## Goal
The Solutions --> Education = goes to the wrong page, should direct to [Campus](https://about.gitlab.com/solutions/education/campus/). 

It goes here now --> https://about.gitlab.com/solutions/education/
It should go --> https://about.gitlab.com/solutions/education/campus/

Also the frame around the left GitLab for Education Box is missing. 

### Jobs To Be Done
* **Situation**: *When a clicks on Education in our footer...*
* **Motivation**: *We want to direct them to the campus page...*
* **Outcome**: *So we can make sure they are seeing the most relevant content.*

## Page(s)
Which page(s) are involved in this request?
* Footer

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @jhalloran @c_hupy @laurenbarker 
- [ ] Informed: `Everyone`

## 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
Pull Quote carousel is missing chevron/arrow icon on button

### Pages in scope
Any page that uses the pull-quote component (ex: [Sales](https://about.gitlab.com/sales/))

### Components in scope
`/components/pull-quote.vue` is missing the arrow that was on the next button. We should add back, or replace, what ever was at this path previously: (line 77) `/nuxt-images/icons/arrow.svg`

We should also add a label that describes what the button will do once clicked, and then hide the image from screen readers.

Ex:
```
        <button
          v-if="data.multiple_quotes"
          class="quote-button"
          @click="increaseIndex"
          aria-label="Read next quote"
        >
          <img src="/nuxt-images/icons/arrow.svg" alt="" aria-hidden="true" />
        </button>

Story points: 1.0
Fix remaining side menu overlap and positioning issues

This was recently fixed on the Stages DevOps Lifecycle page. ([MR](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/543))


### Components in scope
`/components/side-menu/side-menu.vue`

`/components/anchor-dropdown.vue`

### Pages in scope
[Get Help](https://about.gitlab.com/get-help/)

[Support](https://about.gitlab.com/support)


Desktop: Side menu should stop and/or disappear when it reaches the bottom of the main content. It should not continue scrolling to the footer.

![image](/uploads/7a20efff7587d7239a5d60d48f392669/image.png)


Mobile: The anchor dropdown component replaces the side menu. The positioning of it should be adjusted so it does not cover up the heading of the page and is not overlapped by the nav.

![image](/uploads/27f94e1bb9316884d6e99433fbbbb85e/image.png)

Story points: 2.0
ENG | Tracking: Remove OneTrust Events

## Goal
OneTrust automatically sends events to Google Analytics from the cookie banner script. These events are labeled as an interaction event on Google Analytics, which is skewing bounce rate and creating a "not set" landing page. This can happen when an interaction event fires before or without a pageview. Typically, we would set the event as non-interaction on Google Tag Manager. However, these events are coming directly from OT, so we cannot adjust the event. 

<img src="/uploads/bcc10f7d50780ead590588969ab818ea/Screen_Shot_2022-09-08_at_11.51.42_AM.png" width="600">


Per this [OneTrust guide](https://www.cookiepro.com/integrations/google-analytics/), we can disable OT from sending events to GA by placing this data attribute to the cookie banner script:<br/>
`data-ignore-ga='true'`

<img src="/uploads/6ed68923c5990dee05e324c69a106b47/Screen_Shot_2022-09-08_at_12.31.41_PM.png" width="800">


## Page(s)
Which page(s) are involved in this request?
* All the pages with OneTrust (gitlab.com, about, customers, docs, page, learn, etc.)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: Someone
- [ ] Consulted: @dennischarukulvanich 
- [ ] Informed: @laurenbarker @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: 1.0
H1 Heading Removed

The H1 heading is missing from the URLs highlighted in the table below. The `H1` has been replaced by `H2`.

H1 headings are a ranking factor for search engines as they use the H1 heading to determine what the page is about. On top of that, H1 headings help your visitors to quickly understand the topic of the page.

| URL                                          | H1 (NEW) | H1 (OLD)                               | H1 (CHANGE) | H1 (LAST CHANGED ON) |
|----------------------------------------------|----------|----------------------------------------|-------------|----------------------|
| https://about.gitlab.com/demo/               |          | See GitLab in action                   | removed     | 4/27/2022            |
| https://about.gitlab.com/install/ce-or-ee/   |          | Which GitLab edition is right for you? | removed     | 4/27/2022            |
| https://about.gitlab.com/sales/              |          | Talk to an Expert                      | removed     | 4/27/2022            |
| https://about.gitlab.com/solutions/startups/ |          | GitLab for Startups                    | removed     | 4/27/2022            |

Story points: 2.0
Incorrect meta title and description for SCM page

Revert the existing meta data to the previous. The SCM is ranked in the top 3 results in Google for "source code management" and will be impacted negatively if the title tag isn't reverted.

The title tag is now a duplicate of another page and the meta description is the default description generated by the website.

**Previous**
- Title: `Source Code Management`
- Description: `Source code management enables coordination, sharing, and collaboration across an entire software development team. GitLab supports teams to rapidly collaborate and iterate on new features and deliver business value.`

**Current**
- Title: `GitLab The One DevOps Platform`
- Description: `Code, test and deploy with GitLab. Everyone can contribute!`

Story points: 1.0
Customer Case Study -https://about.gitlab.com/customers/ - Case studies are not showing up

## Goal
We would like to view all the customer case studies that are uploaded in the case study page

### Jobs To Be Done
* **Situation**: When all case studies are uploaded in the parent case study page
* **Motivation**: We want to view and filter them
* **Outcome**: So we can support the sales team

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/customers/

Uploaded case studies dated (2022-03-21) are not showing up on the page under filters etc. Also there has been an additional upload of case studies under the original date (2022-02-22) and these are not coming up. Can someone please look into this, it could be a bug? 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: @FionaOKeeffe 

## In scope
What is within scope of this request?

- [ ] 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
A11y > Navigation unusable by keyboard

## Problem

**Navigation is unusable by keyboard.**

- While it's possible to open a parent nav item with the keyboard, it is not possible to access any of the expanded navigation links or even close the menu, making the rest of the page useless as the focus moves behind an open navigation panel.
- Navigation isn't coded correctly. It uses an unordered list `<ul>` with buttons `<button>` as the child elements, but only list items are allowed so this also fails markup validation.
- The **Support** dropdown can't be closed via keyboard, which also prevent focus from moving efficiently.

## Solution

- Use correct HTML semantics.
- Ensure all functionality can be done via keyboard.
- Ensure focus order is correct.
- Ensure elements don't obscure other elements that can receive focus.

![CleanShot_2022-04-27_at_09.21.17](/uploads/3ee1be62a44122f66955eb90b9bd1bdb/CleanShot_2022-04-27_at_09.21.17.mp4)

## MVC 1

First iteration MVC can be seen in this [merged MR](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/24).

## What has been done

- All unordered lists have been updated to only include list items as direct children elements.
- Focus attributes of the footer section have been updated to be inaccesible whenever the Menu is open.

## What still needs to be done

- Although the links on the footer are hidden whenever the nav menu is open, as a user I cannot reach the submenus directly afterwards as the focus incorrectly goes to the top of the browser to start the page again. [This behavior can be seen here](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/24#note_966838793).
- The **Support** dropdown can only be closed by clicking `Support` again or navigating the whole menu. We would need to add a `Close` button inside that dropdown to have an actionable element with which we could close it with the keyboard.

## MVC2

For the MVC2, an npm package [was tested here ](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/34) but failed to work on production so it was rolled back and focus trap was implemented from scratch [here](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/45).

## What has been done

The focus trap was created in the `navigation-desktop-menu.vue` file using DOM references. The npm packages for the focus trap have been removed from the repo. Focus trap should be working as expected now.

## What still needs to be done

- When `Close` button is clicked, focus should go to the latest focused nav item instead of the Support buttton (first button on page).

Story points: 5.0
/stages-devops-lifecycle has overlap in the footer


### Describe the Bug
On https://about.gitlab.com/stages-devops-lifecycle/ , when the screen is wide enough, there is overlap on the right side, especially noticeable in the footer.

### What's my browser? 
Tested on Firefox and Chrome

## Page(s)
Which page(s) are involved in this request?
* [Unify the DevOps lifecycle with GitLab | GitLab](https://about.gitlab.com/stages-devops-lifecycle/)

## Screenshot
![image__2_](/uploads/956c4c9f979ec22960285e730f0f01a5/image__2_.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
- [x] UX Design
- [x] Engineering

Story points: 2.0
Markdown not rendering on features page

## Goal
There is a markdown render issue as shown an image below

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [SAST Features](https://about.gitlab.com/features/?stage=secure)
* [Page Page](https://about.gitlab.com/features/?stage=package)

![image](/uploads/8782f00bae4a8b0b479bca993bad9b88/image.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: 1.0
Monitor links navigate to wrong location

## Goal
Incident management link takes you to the wrong location.

Should take you to https://docs.gitlab.com/ee/operations/incident_management/

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[Monitor](https://about.gitlab.com/stages-devops-lifecycle/monitor/)`

## 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
Tracking: Navigation Menu

## Goal
Google Tag Manager isn't able to detect clicks within the "be-navigation" navigation menu. 

**Example:**<br/>
When I click on Resource > Blog on the [Install page](https://about.gitlab.com/install/) with the "be-navigation" menu, 
GTM thinks my click element is `nav > be-navigation`, instead of the `<a>` tag:

![Screen_Shot_2022-04-26_at_3.54.39_PM](/uploads/d7e5b6f68e0d871002a806f98d734608/Screen_Shot_2022-04-26_at_3.54.39_PM.png)
<br/><br/>
When I click on the same Resource > Blog link on the Home page, GTM detects the correct `<a>` tag.

![Screen_Shot_2022-04-26_at_3.56.05_PM](/uploads/bbee23a4282c63b752021cea55d6025c/Screen_Shot_2022-04-26_at_3.56.05_PM.png)
<br/>
<br/>
Is there some JS blocking GTM from targeting the correct` <a>` tag? 
## Page(s)
Which page(s) are involved in this request?
* Any page with the be-navigation nav menu, ie: https://about.gitlab.com/install/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dennischarukulvanich 
- [ ] Consulted: @mpreuss22 
- [ ] Informed: `Everyone`


## 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
QA Blog

**UI Fixes for the Blog LP:** 

1. Update "Sign up for GitLab's twice monthly newsletter" from H3 to H4 (23px/32lh)
2. Remove the second repeated line "Sign up for GitLab's twice monthly newsletter"
3. Have the "Subscribe" button the width of the email form

| Existing | Figma |
| ------ | ------ |
| ![Screen_Shot_2022-04-26_at_15.50.23](/uploads/6cb23ac7cf0155200757760873a950e5/Screen_Shot_2022-04-26_at_15.50.23.png) | ![Screen_Shot_2022-04-26_at_15.50.40](/uploads/344de8f8e603f41b2ed8b1ee2918ab1e/Screen_Shot_2022-04-26_at_15.50.40.png) |

Story points: 2.0
Homepage Hero Video continues to play after lightbox is closed

## Goal

Prevent video from playing after Lightbox has been closed.

![Screen_Shot_2022-04-26_at_7.55.20_PM](/uploads/576920c098f66a7863d43503005b8aae/Screen_Shot_2022-04-26_at_7.55.20_PM.png) 



### 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
Fix invisible links Copy/CopyMedia - Solutions

## Goal
We would like to fix invisible links in Copy or CopyMedia component.

https://refresh.about.gitlab-review.app/solutions/cloud-native/

![Screen_Shot_2022-04-26_at_15.39.10](/uploads/b46c439d014a5d35c758853e8b88ac80/Screen_Shot_2022-04-26_at_15.39.10.png)

### 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
- [x] Engineering

Story points: 1.0
ENG: Update Get free trial link on home hero and CTAs

## Goal
Update the Get free trial links on the home hero and CTA components from `/free-trial` to `https://gitlab.com/-/trials/new?glm_content=default-saas-trial&glm_source=about.gitlab.com`

## Page(s)
Which page(s) are involved in this request?
* All pages CTA
* Home 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: 1.0
QA: SCM page

**UI Fix: ** Update all text that is currently font-weigh 700 (all the headers) to font-weight 600 (semi-bold) on [SCM page](https://refresh.about.gitlab-review.app/stages-devops-lifecycle/source-code-management/)

![Screen_Shot_2022-04-26_at_10.37.54](/uploads/1e4bd56993bc1e7b9132f34575a8ec61/Screen_Shot_2022-04-26_at_10.37.54.png)

Story points: 1.0
ENG: Horizontal scroll component performance update

The `horizontal-scroll-bar.vue` currently uses dynamic values in the `left` position property to move the bar as the user scrolls. This can lead to the browser making a lot of calculations on every event trigger, which can lead to performance issues for some users as the DOM gets redrawn each time.

This can be prevented by using the `transform: translateX()` property and value which occurs on a separate layer than the layout, which means the DOM will not be redrawn.

Story points: 2.0