giseldo/neodataset huggingface dataset:
[ENG] Swap images on AWS partners page to update GitLab logo

## Goal
We would like to update the GitLab logos on the [GitLab on AWS](https://about.gitlab.com/partners/technology-partners/aws/) by swapping the two images on the page.

![0d608d](/uploads/2c8b89281cb5e8acb1bac3092277246b/0d608d.png)

![9c5167](/uploads/2fad8e383d56f8a13693631afc031a10/9c5167.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
- [ ] UX Design
- [x] Engineering

Story points: 1.0
ENG: Add methodology pop-up on DevOps Tools

## Goal
>As per Sid's request on the #competitive-website-strategy slack channel, we want to have a synopsis for each stage on the /devops-tools/ page articulating how/why we came to these rankings.


**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: Sid and Dave requests
- [ ]  No

## Page(s)
Which page(s) are involved in this request?
* 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: @jkempton 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: @justin.vetter @fqureshi 

## In scope
Add a line of copy with a hyperlink in the table under the heading

- Table copy: Learn more about the methodology behind these rankings
  - "methodology behind these rankings" triggers pop-up.
- [Popup copy](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1853#methodology-text)
- [Figma prototype](https://www.figma.com/proto/J43LGQRZtINKjHb0XqXYAj/DevOps-Tools?page-id=372%3A9259&node-id=607%3A11540&viewport=-1634%2C643%2C0.41&scaling=min-zoom&starting-point-node-id=607%3A11540&show-proto-sidebar=1) - click hyperlink under the table heading 
- [Figma workfile](https://www.figma.com/file/J43LGQRZtINKjHb0XqXYAj/DevOps-Tools?node-id=607%3A11539&t=Mrv2Cf0h0JhTup8G-1)

## 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: Refactor Software Faster Carousel Component

[Software Faster page](https://about.gitlab.com/software-faster/)

The current carousel does not render all slide content on the page at once, but renders the content for the slide that's visible. This has made it difficult to render the video on slide two on page load, which is needed for Vimeo analytics to be pushed up to the dataLayer. 

Let's refactor the carousel component so that all slide content is rendered in the DOM, but is properly hidden until selected.

Related comment: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1611#note_1258247192

Story points: 4.0
ENG: devops-tools / table UI updates

## Goal
We would like to update the table style for [/devops-tools](https://about.gitlab.com/devops-tools/) so that it is consistent with the [/competition](https://about.gitlab.com/competition/) table.

## Page(s)
Which page(s) are involved in this request?
* `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: @Tinaliseng 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: @justin.vetter 

## In scope
What is within scope of this request?

| Issue | Image |
| ------ | ------ |
|  Update grid border color so they are the same as on /competition = Grey 200 `#E8E7EB`  |   ![Screenshot_2023-01-16_at_11.19.51_AM](/uploads/7d49abd8ac869cfe382ff6d72c59beb3/Screenshot_2023-01-16_at_11.19.51_AM.png)   |
|  Add a border to the entire table to be consistent with the /competition table: Grey 200 `#E8E7EB`      |     ![Screenshot_2023-01-16_at_11.36.44_AM](/uploads/a659dda524c8078541171563aebf99c8/Screenshot_2023-01-16_at_11.36.44_AM.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
- [ ] UX Design
- [x] Engineering

Story points: 1.0
ENG: Hackerone customer logo distorted in solutions/dev-sec-ops

## Goal
Fix the distorted Hackerone logo on the dev-sec-ops solution page. 

Sort of urgent as it probably violates brand standards

![Screenshot_2023-01-30_at_11.13.53_AM](/uploads/b04e7d87e5ae4129454b8fa09f2abff0/Screenshot_2023-01-30_at_11.13.53_AM.png)

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/dev-sec-ops/#customers

## 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: @justin.vetter 

## 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
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 1.0
[ENG] Change table title based on stage /competition

## Goal
We want to swap the table title based on the stage/tab the user is on.  For example, if the user is on the Create tab, instead of it saying `Categories` below, it should say `Create`.  We also want to add the icon for each stage next to the title.

![CleanShot_2023-01-30_at_11.46.55](/uploads/f03dec00e3580868819298dd5950a241/CleanShot_2023-01-30_at_11.46.55.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?**
- [ ]  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?**
- [x]  Yes `Dave & Sid`
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to swap the table title per tab`


**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?
* `[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: `GitLab Handle`
- [ ] Consulted: @justin.vetter @fqureshi @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Swap title based on tab
- [ ] 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] Iterate on features section for why Premium & Ultimate pages

## Goal
We would like to iterate on the Features section > `Other features` to build in a load more and/or load all features.

#### Jobs To Be Done
* **Situation**: *When a user visits one of our why pages the scroll is way too long for users to make it through the content*
* **Motivation**: *We want to reduce the scroll of the page by allowing the user to load more feature items in*
* **Outcome**: *So we can increase scroll depth and give users a better visualization of the content on the page*

#### 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`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to create a better user flow for these pages`

**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?
* [https://about.gitlab.com/pricing/ultimate/](https://about.gitlab.com/pricing/ultimate/)
* [https://about.gitlab.com/pricing/premium/](https://about.gitlab.com/pricing/premium/)

## 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 @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update component to allow user to load more items in
- [ ] 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] solutions/open-source/join page refresh

## Goal
We want to update the [solutions/open-source/partners](https://about.gitlab.com/solutions/open-source/join) page to the new brand refresh which will improve users experience as measured by metrics.

### Working Files(s)
[Figma](https://www.figma.com/file/Od5TazELCPPEhkcoReGQvO/Open-Source?node-id=18%3A5847&t=hPIRkHukRahYke06-0)

#### 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`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to refresh the Join page`

**What analytics / data will we need to set-up?**
- [x] Yes: `Standard analytics`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[Open-source/partners](https://about.gitlab.com/solutions/open-source/join/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Refresh Open-source/join 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] solutions/open-source/partners page refresh

## Goal
We want to update the [solutions/open-source/partners](https://about.gitlab.com/solutions/open-source/partners) page to the new brand refresh which will improve users experience as measured by metrics.

### Working Files(s)
[Figma](https://www.figma.com/file/Od5TazELCPPEhkcoReGQvO/Open-Source?node-id=18%3A5097&t=hPIRkHukRahYke06-0)

#### 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`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to refresh the partners page`

**What analytics / data will we need to set-up?**
- [x] Yes: `Standard analytics`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[Open-source/partners](https://about.gitlab.com/solutions/open-source/partners/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Refresh Open-source/partners 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: 4.0
[ENG] solutions/open-source page refresh

## Goal
We want to update the [solutions/open-source](https://about.gitlab.com/solutions/open-source) page to the new brand refresh which will improve users experience as measured by metrics.

## Page(s)
Which page(s) are involved in this request?
* [solutions/open-source](https://about.gitlab.com/solutions/open-source)

### Working File(s)
[Figma](https://www.figma.com/file/Od5TazELCPPEhkcoReGQvO/Open-Source?node-id=18%3A5096&t=hPIRkHukRahYke06-0)

#### 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`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to refresh the open-source/partners page`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [x] Yes: `Standard analytics setup`
- [ ] No


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update layout for solutions/open-source 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: 5.0
[UX] Create an extra content block to feature external content on the blog home page

## Goal
Create a way for us to add in a box for podcasts, webcasts, ebooks or whatever we want to promote on the blog home page.

#### Jobs To Be Done
* **Situation**: *The content team has new and existing content that would like to surface on the blog home page but there is no longer a good spot to do so*
* **Motivation**: *We want to give the content team an easy way to highlight new external content items (podcasts, ebooks, webcasts, videos)*
* **Outcome**: *So we can ...*

#### 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`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to create a new layout block for the blog homepage to highlight featured external content`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [x] Yes: `Standard GA tracking`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[Blog](https://about.gitlab.com/blog)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI:  
- [ ] Consulted: @fqureshi @Sgittlen @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create a new content block layout for the blog homepage
- [ ] Deliverable: [Figma designs](https://www.figma.com/file/0vSGFalBjMp59KxG5hUEBs/Blog--homepage-updates?node-id=488%3A6640&t=elRWpn9g6xY87oHY-1)

## 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
- [ ] Engineering

Story points: 4.0
[UX] Add link to "All blogs" above the fold on the blog landing page

## Goal
We want to add a link to view all blog posts above the fold on the blog landing page. This will allow users to easily navigate the list of all blog posts. 


#### 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`
- [x] 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 blog homepage layout by adding a link to "All posts" above the fold`

**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?
* `[Blog](https://about.gitlab.com/blog)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: @justin.vetter @fqureshi @Sgittlen 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update Blog homepage layout to add link to all blog posts
- [ ] 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
- [x] UX Design
- [ ] Engineering

Story points: 1.0
[ENG] Add new categories to the blog

## Goal
We want to add four new categories to the blog:
- DecSecOps
- DevSecOps platform
- Careers
- Product

These categories should be added to the category lists on the main page and on the side nav.  These categories should also have a category page ex. https://about.gitlab.com/blog/categories/careers/


#### 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`
- [x] No: `Please describe why`


**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?
* `[blog](https://about.gitlab.com/blog)`

## 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 `@Sgittlen` 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add categories to main page and side nav
- [ ] Create category landing 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: 4.0