giseldo/neodataset huggingface dataset:
[ENG] Add sub copy to /devops-tools page

## Goal
We would like to add text to the top of the /devops-tools page to make clear that these logos are in stack-rank or prioritized order based on strength or maturity in their category.  We will also link to the /competition from here

ex:
![CleanShot_2023-01-12_at_09.49.20](/uploads/2e970338bbbb3b5ee29bfa3abcef81c7/CleanShot_2023-01-12_at_09.49.20.jpg)

### Final Copy: 
1. H1: DevOps tools landscape (should be sentence case instead of title case as it currently is)
2. H5: As The DevSecOps Platform, GitLab’s focus is on providing a single application with best-in-class capabilities for the entire DevOps lifecycle.
3. Body-2: There are a ton of DevOps tools to choose from, many of which specialize in a few capabilities. We’ve ranked the tools for each stage of the DevOps lifecycle, starting with the most mature solutions. For more info on the maturity of GitLab and other key competitors, check out our DevOps maturity comparison chart.
4. Add a title to the table - H4: Top tools for each stage of the DevOps lifecycle

- [Google doc](https://docs.google.com/document/d/1WefXucnXBi09wBv_ho7mBQ-BKc0WaeTFjYh7-TUWkkI/edit?usp=sharing)
- See [comment below](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1772#note_1237537954)

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: Senior leadership is looking for this change
- [ ]  No

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* [DevOps Tools](https://about.gitlab.com/devops-tools/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @fqureshi @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add sub-hero copy to devops-tools page
- [ ] Deliverable 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] Add breadcrumb to /devops-tools from /competition

## Goal
We would like to add a breadcrumb nav element on the /competition to the DevOps Tools Landscape page

![CleanShot_2023-01-11_at_14.15.09](/uploads/33833afd35f1ec0b06898c997916044d/CleanShot_2023-01-11_at_14.15.09.jpg)

#### Working Files
[Figma Prototype](https://www.figma.com/proto/J43LGQRZtINKjHb0XqXYAj/DevOps-Tools?page-id=372%3A9259&node-id=516%3A12467&viewport=-103%2C736%2C0.37&scaling=min-zoom&starting-point-node-id=502%3A9758&show-proto-sidebar=1)

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: Senior leadership is looking for this change
- [ ]  No


**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* [Competition](https://about.gitlab.com/competition/)
* [DevOps Tools](https://about.gitlab.com/devops-tools/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @fqureshi @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add breadcrumb nav element
- [ ] Deliverable 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] Add functionality to deep link into tabs on /competition page

## Goal
We would like to add the functionality to be able to deep link into tabs/stages on the /competition page

ex: https://about.gitlab.com/competition/?stage=package

![CleanShot_2023-01-11_at_08.09.09_2x](/uploads/cc5dfa44e8b6cb5bf41faad87f07fa16/CleanShot_2023-01-11_at_08.09.09_2x.jpg)

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: `we want this functionality to then update links on the /devops-tools page`
- [ ]  No


**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[Competition](https://about.gitlab.com/competition/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpenagos-ext 
- [ ] Consulted: @justin.vetter @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add new functionality 
- [ ] Deliverable 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: 3.0
ENG: [Refactor] - Remove AOS initialization in remaining pages

## Goal

Remove AOS initialization from remaining pages that are still initializing AOS in order to reduce duplicated code and only use AOS in the Layout

## 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: [Refactor] - Remove AOS initialization in partners pages

## Goal

Remove AOS initialization from partners pages to reduce duplicated code and only use AOS in the Layout

## 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: [Refactor] - Remove AOS initialization in competition pages

## Goal

Remove AOS initialization from competition pages to reduce duplicated code and only use AOS in the Layout

## 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: [Refactor] - Remove AOS initialization in topic pages

## Goal

Remove AOS initialization from `/topic` pages to reduce duplicated code and only use AOS in the Layout

## 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] Remove 7th logo under Monitor

## Goal
We would like to remove the 7th logo under the monitor column `chronosphere` to keep the table consistent 


#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: Just to clean up the table for leadership
- [ ]  No

## Page(s)
Which page(s) are involved in this request?
* [Devops Tools](https://about.gitlab.com/devops-tools/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove 7th logo
- [ ] Deliverable 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: [Refactor] - Remove AOS initialization in "events" pages

## Goal

Remove AOS initialization from `/events` pages to reduce duplicated code and only use AOS in the Layout

## 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
UX: Update All Resources page

## Goal
We would like to update the All Resources page to increase customer engagement.

#### Jobs To Be Done
* **Situation**: *When I click on the "All Resources" link*
* **Motivation**: *I want to explore all of Gitlab's resources quickly and efficiently*
* **Outcome**: *So I can learn what Gitlab can offer and how they will support my learning as a customer*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[All Resources](https://about.gitlab.com/resources/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @Tinaliseng @jhalloran @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 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
- [X] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering

Story points: 5.0
[ENG] Update anchors in the /maturity page to work across all browsers

## Goal
We want to update the anchors on the /maturity page in the www repo to fix a Chrome bug that does not scroll to the correct position when linking to the page.

Here is a [thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1491#note_1227983580) to the discovery of the bug:


#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: `We want to make sure the /competition page links are working as they should across all browsers`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

## Page(s)
Which page(s) are involved in this request?
* `[Maturity page](https://about.gitlab.com/direction/maturity/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @Tinaliseng @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update anchor code on maturity page
- [ ] Deliverable 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: 3.0
ENG: Update colors on the TeamOps page

## Goal
We need to change the colors on the Guiding Principles section of the TeamOps page to match the [updated model graphic](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/7223/designs/teamops-model-01.png) 

- Everyone Contributes should be changed to `#966DD9`
- Decision Velocity should be changed to `#FD8249`

<details><summary>Click to see visual</summary>
![Screen_Shot_2023-01-05_at_9.58.45_AM](/uploads/7ac8288861eb4af6f366bd7fc01e4d40/Screen_Shot_2023-01-05_at_9.58.45_AM.png)
</details>

## Page(s)
Which page(s) are involved in this request?
* [TeamOps](https://about.gitlab.com/teamops/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `@vicbell`
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: @justin.vetter 

## In scope
What is within scope of this request?

- [ ] Update colors only

## 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: Run changelog script for Jan 16 - Jan 29 iteration

## Goal

Run the changelog and version script at the end of the iteration from Jan 16 - Jan 29

## Steps to run

1. Monitor the scheduled changelog job
1. Patch up the generated changelog with missed commits


## In scope

What is within scope of this request?

* [ ] Script automatically runs on on Friday Jan 27th

## 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 hero image on /dedicated/ page

## Goal
We would like to update the hero for the Dedicated page 


### Working Files
[Figma](https://www.figma.com/proto/1WwNfrykRmR5h0yJ7bX3i6/GitLab-Dedicated?page-id=0%3A1&node-id=686%3A6950&viewport=-4814%2C366%2C0.63&scaling=min-zoom)


#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to update the hero `

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* [Dedicated](https://about.gitlab.com/dedicated/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update hero image
- [ ] Deliverable 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] Education solution page

## Goal
We would like to update our [/solutions/education](https://about.gitlab.com/solutions/education/) page.

#### Working Files
[Figma] (https://www.figma.com/file/TbJai6MP3eokLeLRqEoEJC/Education-page-MVC1?node-id=63%3A3983&t=ucB5bv3xipSo9plv-1)


#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* [Education](https://about.gitlab.com/solutions/education/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @jhalloran @justin.vetter @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Education solutions page
- [ ] Deliverable 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: 6.0
ENG: [Refactor] - Remove AOS initialization in solutions pages

## Goal
Remove AOS initialization from solutions pages to reduce duplicated code and only use AOS in the Layout

## 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: [Refactor] - Remove AOS initialization in single landing pages

## Goal

Remove AOS initialization from single landing pages to reduce duplicated code and only use AOS in the Layout

## 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: [Refactor] - Add animation initialization to layout

## Goal
Add the AOS initialization to the default layout in order to remove the same code from the rest of the pages/components

## In scope
What is within scope of this request?

- [x] Add AOS initialization methods to `/layouts/default.vue`

## 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