giseldo/neodataset huggingface dataset:
ENG: Header scroll animation | Animation

## Goal
We would like to create a class that can be added to headers that would allow for on-scroll animation on header text.

![CleanShot_2022-06-02_at_10.54.56](/uploads/64b6d6a0ef274ab5b3d030a0b5c8449b/CleanShot_2022-06-02_at_10.54.56.gif)

[Figma link}(https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26327)

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* All

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create class (css/js) for the on scroll animation
- [ ] Add class to homepage components

## Out of scope
What is out of scope and not part of this iteration?

- Adding class to all pages in 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
- [x] Engineering

Story points: 3.0
ENG: Tertiary buttons hover | Animation

## Goal
We would like to iterate on our animation/transitions for our tertiary buttons

![CleanShot_2022-06-02_at_10.41.26](/uploads/b443da8fb756e5623aa26eba7dcf646d/CleanShot_2022-06-02_at_10.41.26.gif)

[Figma link](https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26237)

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* All

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Tertiary button hover class

## Out of scope
What is out of scope and not part of this iteration?

- Other animations

## 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
ENG: Ghost button hover | Animation

## Goal
We would like to iterate on our animation/transitions for our secondary buttons

![CleanShot_2022-06-02_at_10.34.37](/uploads/17d5d8e00723b47d8b27d29fad7c0cc6/CleanShot_2022-06-02_at_10.34.37.gif)

[Figma link](https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26206)

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* All
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Secondary button hover animation

## Out of scope
What is out of scope and not part of this iteration?

- All other animation/transitions

## 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 old fall back logo | Technology Partners

## Goal
We would like to update the fallback old tanuki logo from the Technology Partners page

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [Alliance Partners](https://about.gitlab.com/partners/technology-partners/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter 
- [ ] Informed: '@mlebeau' 

## In scope
What is within scope of this request?

- [ ] Update fallback logo

## Out of scope
What is out of scope and not part of this iteration?

- Any other dev work on this 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
Add The Last Mile Video to SMB Page

## Goal
We would like to post The Last Mile video which will improve the value of the SMB page as measured by views and time on page.

### Jobs To Be Done
* **Situation**: *When a customer arrives on the SMB marketing page*
* **Motivation**: *We want to display The Last Mile video in an engaging way*
* **Outcome**: *So we can motivate customers to watch it and take the next step into the funnel*

## Page(s)
Which page(s) are involved in this request?
* `GitLab for Small Businesses(https://about.gitlab.com/small-business/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `brianglanz`
- [ ] Consulted: `cblake`
- [ ] Informed: `kbolton1`

## In scope
What is within scope of this request?

- [ ] Incorporate The Last Mile video (https://drive.google.com/drive/folders/1vQY3gHc5jg8b6Jt8h9YqfIMz9zkGev4n?usp=sharing) onto the existing https://about.gitlab.com/small-business/ page.
- [ ] Include copy (to come)
- [ ] Track performance


## 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
- [X ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ X] UX Design
- [X ] Engineering

Story points: 1.0
Remove What is Gitlab and redirect to Why GitLab

## Goal
We would like to remove [/what-is-gitlab/](https://about.gitlab.com/what-is-gitlab/) and redirect that url to [/why-gitlab/](https://about.gitlab.com/why-gitlab/).

This page was listed to redirect in the following issues: 
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/950
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354


### Jobs To Be Done
* **Situation**: *When a user hits the `/what-is-gitlab` URL they are redirected to` /why-gitlab`.*
* **Motivation**: *We want to remove duplicative content.*
* **Outcome**: *So we can reduce the number of page in the marketing site.*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/what-is-gitlab/
* https://about.gitlab.com/why-gitlab/

## 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?

- [ ] Remove https://about.gitlab.com/what-is-gitlab/
- [ ] Update all internal links to that page to https://about.gitlab.com/why-gitlab/
- [ ] Set redirect in 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
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Delete 9 pages with > .005 page views

## Goal
We would like to delete 10 pages with > .005% page view ratio. This data was sourced as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/950). 

### Jobs To Be Done
* **Situation**: *These pages have > .005% of the page views.*
* **Motivation**: *We want to continue the depreciation of unused marketing webpage.*
* **Outcome**: *So we can reduce the # of pages in the marketing site.*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/2020-devsecops-survey/new/ 
* https://about.gitlab.com/DIY-DevOps/                
* ~~https://about.gitlab.com/cloud-native/~~ Keep. [Related thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/950#note_970907596).             
* https://about.gitlab.com/competition/               
* https://about.gitlab.com/corporate-philanthropy/   
* https://about.gitlab.com/customer-care/             
* https://about.gitlab.com/demo-leader/               
* https://about.gitlab.com/en-test/                   
* https://about.gitlab.com/githost/                   
* https://about.gitlab.com/speakers/                  
* https://about.gitlab.com/wip/

## 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?

- [ ] Remove these pages from 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
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Create plan for moving blog out of www-gitlab-com

## Goal
We would like to create a plan moving the blog out of the `www-gitlab-com` repository.

### Jobs To Be Done
* **Situation**: *When team member creates a blog post it is a efficient process the enables effective content creation for the marketing site.*
* **Motivation**: *We want to improve deployment times, conversion rates, and drive traffic to our key pages from our blog posts.*
* **Outcome**: *So we can help drive the growth of GitLab.*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/blog/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker
- [ ] Consulted: @vsilverthorne @justin.vetter
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Collaborate with GitLab team to create actionable plan to move the blog from the www-gitlab-com repository

## Out of scope
What is out of scope and not part of this iteration?

- Any engineering work. This issue is for discussion, planning, and feedback. 

## 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
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 4.0
ENG: Migrate Events landing page to Buyer Experience

## Goal
We would like to migrate the https://about.gitlab.com/events/ to the Buyer Experience repository.

### Jobs To Be Done
* **Situation**: *Events listed on the https://about.gitlab.com/events/ are managed in the Buyer Experience repository, and the landing page is built with Nuxt*
* **Motivation**: *We want to centralize the marketing site in the Buyer Experience repository.*
* **Outcome**: *So we can be efficient*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/events/
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/events.yml
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/events/index.html.haml

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @lduggan 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: @nataliepicci @Helenadixon @krogel @amandawshen @ttran5 

## In scope
What is within scope of this request?

- [ ] Migrate the Events page to the Buyer Experience repository
- [ ] Apply "fresh coat of paint" to the template to match our new branding
- [ ] Remove existing events template and `events.yml` from the www-gitlab-com repository
- [ ] Update [handbook](https://about.gitlab.com/handbook/marketing/events/#how-to-add-events-to-aboutgitlabcomevents) with documentation on how to add events to the marketing site

## Out of scope
What is out of scope and not part of this iteration?

- A new template designed by UX ( they will help review and provide feedback in the MR )


## 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: 5.0
DISCOVERY: side navs/table of anchor links + a11y

The screen reader experience of navigating and using the side nav to auto-scroll to different sections on the page seems a little clunky. I'm not sure what is expected for this kind of element on the page, so I'd like to do some research and see how other a11y-minded developers approach functionality like this.

This side nav is used on a number of pages, including [Install](https://about.gitlab.com/install/).

Story points: 2.0
Remove child topic pages - DevOps

## Goal
We would like to remove the following child topics pages: 
- https://about.gitlab.com/devops/build-a-devops-team/
- https://about.gitlab.com/devops/how-and-why-to-create-devops-platform-team/
- https://about.gitlab.com/devops/reduce-devops-costs/
- https://about.gitlab.com/devops/seven-tips-to-get-the-most-out-of-your-devops-platform/
- https://about.gitlab.com/devops/use-devops-platform-to-avoid-devops-tax/
- https://about.gitlab.com/devops/what-is-a-devops-platform-engineer/

All these URls redirect to the parent topic page at https://about.gitlab.com/devops/. Therefor, I think we can remove the data files for those child topic page that exist here: 
https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/data/topic_children

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @hsmith-watson 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Removing the data files from 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
ENG: Get Started for Small Business

## Goal
We would like to build a single template for our Get Started pages which will give users quick tutorials on how to get started using GitLab.

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/get-started/SMB
* All Get Started pages will use the same template

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @ctsang-ext @cblake 
- [ ] Informed: @fqureshi @laurenbarker 

## In scope
What is within scope of this request?

- [ ] Build template
- [ ] Apply template to parent and child pages
- [ ] Depreciate pages with duplicate content and set redirects
- [ ] Create video that walks through the `yml` file structure

## Design
- [Figma file](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=368%3A3068)

## Content
- [Get Started Google Doc](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/947)

## Out of scope
What is out of scope and not part of this iteration?

- Side anchor nav is being addressed in this issue https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148

## 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: 8.0
ENG: Category leadership (Topics)  - Build Template

## Goal
We would like to build a single template for our Category Leadership (Topic) pages which will improve the hierarchy of information as measured by increased search ranking.

## Page(s)
Which page(s) are involved in this request?
* [topics/devops/](https://about.gitlab.com/topics/devops/)
* All topic pages including child pages will use the same template

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpenagos-ext 
- [ ] Consulted: @Tinaliseng @ncregan @hsmith-watson @dennischarukulvanich 
- [ ] Informed: @fqureshi @justin.vetter 

## In scope
What is within scope of this request?

- [ ] Build template using [topics/devops/](https://about.gitlab.com/topics/devops/) as a first use-case.
- [ ] Apply template to parent and child pages
- [ ] The components need to be rendered dynamically instead of statically for this template.

## Design
- [Figma file](https://www.figma.com/file/QVyiaPnW9F5h50yZ9YCliQ/Category-Leadership-refresh?node-id=0%3A1)

## Out of scope
What is out of scope and not part of this iteration?

- Side anchor nav is being addressed in this issue https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148
- Full mobile designs in Figma. Only some elements have mobile designs. We will address breakpoints on a case-by-case basis.

## 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
UX: Main Get Started Page (Navigate Tutorials)

## Goal
We would like to improve the main Get Started page so that it will help customers navigate tutorials and improve customer onboarding as measured by decreased support inquiries.

### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand how to begin setting up their GitLab account or other services...*
* **Outcome**: *so they can get started right away and without interruption.*


## Page(s)
Which page(s) are involved in this request?
* [Current page](https://about.gitlab.com/get-started/)
* [New Design (Figma)](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=689%3A7331)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @jhalloran @Tinaliseng 
- [ ] 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:

- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering

Story points: 5.0
Open source program pages aren't easily accessible

## Goal

The [GitLab for Open Source page](https://about.gitlab.com/solutions/open-source/) isn't easily accessible from the GitLab home page. It does not appear with other community programs, such as the Education program, in `Solutions > Industry`, nor does it appear in the page footer.

We would like to increase visibility of the GitLab for Open Source program pages in light of upcoming changes to the free user tier. This will help us improve discoverability and increase applications to the program from projects impacted by the changes.

### Jobs To Be Done

* **Situation**: When a user visits `gitlab.com`, they cannot easily navigate to the GitLab for Open Source solutions page
* **Motivation**: We want to enhance navigability and assist users seeking information about this program
* **Outcome**: Better assist users seeking to apply for the program in light of upcoming changes to GitLab's free tier.

## Page(s)

* `https://about.gitlab.com/solutions/open-source/`

## DCI

- [ ] DRI: `@bbehr`
- [ ] Consulted: `@c_hupy`
- [ ] Informed: `Everyone`

## In scope

- [ ] An easily accessible link to the program page from the same location(s) other community programs appear

## Out of scope

- Changes to pages contents

## Requirements

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [x] Engineering

Story points: 2.0
Create Slippers Card Component

## Goal

Update card component in Slippers to use the four card variants in [Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=1305%3A182).


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: @jhalloran 
- [x] Consulted: @ndubord 
- [ ] 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: 8.0