giseldo/neodataset huggingface dataset:
Mobile Usability - Text too small

## Overview

The font size for the page is too small to be legible and would require mobile visitors to “pinch to zoom” in order to read. 

**Solution** - After specifying a viewport for your web pages, set your font sizes to scale properly within the viewport.

#### Example Screenshot
URL - https://about.gitlab.com/solutions/benefits-of-using-version-control/

![image](/uploads/49ca4394bdd53989d2aacec5e4bb4deb/image.png)

Screenshot taken with [Google Mobile-Friendly Test Tool](https://search.google.com/test/mobile-friendly?id=wkrb6lCQ4qF8Q_TZAa9fTQ).

### Affected URLs
Initial analysis indicates this error is predominantly found on URLs where the content elements such as tables and images are wider than the viewport.

This can be viewed on the about.gitlab.com [Google Search Console page experience report](https://search.google.com/u/1/search-console/mobile-usability/drilldown?resource_id=https%3A%2F%2Fabout.gitlab.com%2F&item_key=CAw).

Story points: 4.0
Mobile Usability - Content wider than screen

## Overview
Certain pages appears broken when viewed on a mobile device causing the user to scroll horizontally and vertically to view the content. This seems to be affecting URLs with embedded content such as buttons, images, tables and iframes that are not responsive.

### Example Screenshots

![image](/uploads/a01589d97c1745159ebd94b051d81e52/image.png)![image](/uploads/d50d2cd7393d17c8152c714c9d1bed0d/image.png)

### Solution
To fix this error, make sure the pages use relative width and position values for CSS elements, and make sure images can scale as well.

### Affected URLs
This can be viewed on the about.gitlab.com [Google Search Console page experience report](https://search.google.com/u/1/search-console/mobile-usability/drilldown?resource_id=https%3A%2F%2Fabout.gitlab.com%2F&item_key=CAk).

Story points: 4.0
ENG: Netlify CMS: Migrate DevOps Platform child page to Netlify CMS

# Relevant URLs

We recently [fixed a child topics page](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/76751) for `/devops-platform/ten-key-devops-platform-features`, but it's not yet in Netlify CMS.

Need to duplicate our process from the [child topics page migration epic](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/285).  
​
## Scope/Deliverables

- [ ] Move Ten Key DevOps Platform Features into Netlify CMS
​
## Requirements

- [ ]  Review by engineering

## Release history:

```
Move Ten Key DevOps Platform Features into Netlify CMS
```

Story points: 1.0
ENG: <hr> element with single resource type

When there is a single resource type on a topics template, a `<hr>` element displays before the content is outputted. 

Lets remove the `<hr>` element when there is only 1 resource type. 
![Screen_Shot_2021-02-24_at_6.46.15_PM](/uploads/9dad6330d94e80d8f50f713b21eb5457/Screen_Shot_2021-02-24_at_6.46.15_PM.png)

Example of this exist here:
https://about.gitlab.com/topics/ci-cd/continuous-integration-server/

Story points: 1.0
ENG: In editor pull-quotes

## What
Allow content editors to add pull-quotes anywhere in the body using the Netlify editor.

### Files

[Figma file](https://www.figma.com/file/5mgvis6M0z3GN5kuEFADoW/CMS-Blog-Post?node-id=295%3A1453)

![Screen_Shot_2021-02-03_at_11.24.20_AM](/uploads/8bf1b13b013a46483c8b9a0b89da1ba4/Screen_Shot_2021-02-03_at_11.24.20_AM.png)

Story points: 1.0
ENG: Translated Demo Page (pre and post gate)

<!--

This template is for internal production for a Digital Experience issue/project

-->

## Issue Set-up
1. **Title** <br> 
Title this issue as follows: 
[DE Prefix (see list below)] + [Project Name] + [MVC# (if appliable)]

1. **Production Issue Type** <br>
Check the relevant box:
    - [ ] DSN = Design Update
    - [x] ENG = Structural Update
    - [ ] CNT = Content Update
    - [ ] OTH = Other
       - `insert other explanation`

1. **Labels and assignees** <br>
Add additional lower-level labels, and assigness. 

## URL 
- English/standard: about.gitlab.com/demo (update) 
- German: https://about.gitlab.com/de-de/demo (create) 
- Japanese: https://about.gitlab.com/ja-jp/demo (create)
- French: https://about.gitlab.com/fr-fr/demo (create) 
- Italian: https://about.gitlab.com/it-it/demo (create) 

## Goal
Increase MQLs and keep buyers in journey 
​
## Production

#### Working Files​
- [Figma file] (LINK)
- [ ] Translation for pre-gate
- [ ] See CNT issue for specifics on translations for CTAs post-gate

​
#### Scope
- [ ] Update English URL page
- [ ] Create language pages 

#### Suggested Additional Scope
- [ ] Suggested scope item 1
- [ ] Suggested scope item 1


#### Out of Scope
- Out of scope 1 
- Out of scope 2
​
#### Requirements
- [ ]  Requirement 1 
- [ ]  Requirement 1 

#### Roles & Responsibilies
Tag the appropriate parties below, which may be found in the [team handbook](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/)

The following people are **[responsible](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** for completing the task or deliverable:
- [ ]  @assignee

The following person (there can only be one) is **[accountable](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** and is the last one to review the task or deliverable before it’s deemed complete:
- [ ] @bmatturro 

The following people must be **[consulted](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** so they can provide input:
- [ ]  @rreich 
- [ ] @mpreuss22 

The following people must be **[informed](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** so they are kept in the loop on project progress: <br>
**CC:**
- @dmor 
- @dpduncan

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

## Goal
We would like to swap the search and newsletter sections on the blog home page, and update the `All` pill to `All blogs`

![CleanShot_2023-02-07_at_14.43.38](/uploads/cb237fe927554eff608e9e9a6a9388f2/CleanShot_2023-02-07_at_14.43.38.jpg)

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* [Blog](https://about.gitlab.com/blog)

## Include any Figma files
* [Figma](https://www.figma.com/file/0vSGFalBjMp59KxG5hUEBs/Blog--homepage-updates?node-id=405%3A5798&t=KvhjnzyoXqfEtzUo-0)

## Include any graphic or design assets
* `Upload any extra files needed to complete this request`

## In scope
What is within scope of this request?

- [ ] Swap the order of blocks [Search/Categories & Newsletter]
- [ ] Update `All` pill to `All blogs`

Story points: 3.0
ENG: Make resource card images proportionally consistent when resizing

## Goal
Currently, the aspec ratio for our resource cards is not consistent for our for all variants.

We would like the aspect ratio to match what's in the [slippers figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=7825%3A14624&t=yBtcpRZB5hvSGTeT-1) as closely as possible (more landscape than square)

| Example | Image |
| ------ | ------ |
|   Square - example [here](https://about.gitlab.com/solutions/dev-sec-ops/#resources)     |   ![Screenshot_2023-02-07_at_11.06.45_AM](/uploads/e8d67178f650fae525bd83f1e40e1310/Screenshot_2023-02-07_at_11.06.45_AM.png)     |
|  Landscape - example [here](https://about.gitlab.com/features/continuous-integration/)      |    ![Screenshot_2023-02-07_at_11.06.51_AM](/uploads/4614241d3aab7bd3d8ef36fb8cef3008/Screenshot_2023-02-07_at_11.06.51_AM.png)    |


## Page(s)
Which page(s) are involved in this request?
* All instances

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran @mpenagos-ext (please add the solutions that we discussed via slack)
- [ ] Informed: @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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
[Eng] Sales and trial header CTAs

## Goal
We would like to build 2 navigation variants to A/B/C test the Sales and Trial header CTAs. 

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* Navigation repository + header in Buyer Experience

## Include any Figma files
* [Figma file](https://www.figma.com/file/tDxUnSR5vdHHIVZjOW6nt7/Navigation-Research-and-Refresh?node-id=2138%3A71870&t=VCgUjTdNSik1w7UF-1)
* Please see [UX issue for more detail](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1886)


## In scope
What is within scope of this request?

- [ ] Ship orange button variant navigation
- [ ] Ship gradient button variant navigation

Story points: 4.0
[Eng] /free-trial/ FY24Q1 iteration

## Goal
We would like to iterate on our Free Trial page by creating a page that better demonstrates the Free Trial process

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* [Free Trial](https://about.gitlab.com/free-trial/)

## Include any Figma files
* [Figma](https://www.figma.com/file/u2CD4Lpure0cDRwunzqUZl/Paid-search-landing-page?node-id=9%3A185&t=5xgn28FmiCXTJLtp-1)

## Include any graphic or design assets
* `Upload any extra files needed to complete this request`

## In scope
What is within scope of this request?

- [ ] Refresh Free Trial page
- [ ] Deliverable 2


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @jhalloran @fqureshi
- [ ] Informed: `Everyone`

Story points: 8.0
[ENG] Remove old VS pages and redirect to new BE pages

## Goal
We would like to remove and redirect the old VS pages in the WWW repo to the new pages.

- [x] Remove Bitbucket yml content and create redirect /devops-tools/bitbucket-vs-gitlab/ -> /competition/bitbucket/
- [x] Remove Jira yml content and create redirect /devops-tools/jira-vs-gitlab/ -> /competition/atlassian/
- [x] Remove CircleCI yml content and create redirect /devops-tools/circle-ci-vs-gitlab/ -> /competition/circleci/
- [x] Remove GitLab yml content and create redirect /devops-tools/github-vs-gitlab/ -> /competition/github/
- [x] Remove JFrog yml content and create redirect /devops-tools/jfrog-vs-gitlab/ -> /competition/jfrog/

### Files
https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/devops_tools_comparisons.yaml



#### 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 `@dsteer` 
- [ ]  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


## 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 @jkempton @hsmith-watson 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove and redirect pages.
- [ ] 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: 2.0
Add technology partners

## Goal
We would like to add partners with signed agreements to https://about.gitlab.com/partners/technology-partners/ .

List of partners to remove to be provided by @mlebeau @mjoscelyn 

#### Jobs To Be Done
* **Situation**: *When a user visits our technology partners page, everyone displayed has a signed agreement with GitLab.*
* **Motivation**: *We want to be compliant.*

#### 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.

## Page(s)
Which page(s) are involved in this request?
* 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: @laurenbarker @mlebeau @mjoscelyn 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add partners to [apps.yml](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/apps.yml)

## 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] Homepage Content Box for FY24Q1

## Goal
We would like to update and change the content presented on the homepage 

**How do we measure success?**
 - Increase clicks to the featured content 
 
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com

## Update the content to be 

---

#### Get Started with GitLab
New to GitLab and not sure where to start? We’ll walk you through the basics so you know what to expect along the way.

[Explore resources >](https://about.gitlab.com/get-started/) 

#### How our latest releases support developers

Learn how our two new beta releases help organizations stay competitive by supporting developers and delivering value to customers.

[Read the blog post](https://about.gitlab.com/blog/2023/01/24/the-gitlab-quarterly-how-our-latest-beta-releases-support-developers/) >

#### Forrester study: GitLab enabled 427% ROI

Read the 2022 commissioned Total Economic Impact™ study conducted by Forrester Consulting.

[Read the study >](https://page.gitlab.com/resources-study-forrester-tei-gitlab-ultimate.html)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 
- [ ] Consulted: @dennischarukulvanich @fqureshi @justin.vetter @jhalloran 
- [ ] Informed: `@chandlergibb @rclayman @supadhyaya`

## 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 All Resources page

## Goal
We would like update the all resources landing page.

[Figma Design](https://www.figma.com/file/sWcfVXZiDd50SfYlC3tKC7/Resources?node-id=236%3A8976&t=SkXu7OSUlt75O3tU-1)

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* https://about.gitlab.com/resources/

## In scope
What is within scope of this request?

- [ ] Update template and functionality to match Figma

## DCI

[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

* [ ] DRI: @mduque-ext 
* [ ] Consulted: @jhalloran @Tinaliseng  
* [ ] Informed: `Everyone`

Story points: 10.0
incident-8354-2

## Goal
This happened the day after https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1870, when the project was set to private, so did the runners. Unfortunately when the project was switched back to public, we were using a mix of private and shared runners. When the BE repo tried to push the artifacts to GitLab pages on a private runner a redirect happens. I'm not entirely sure why, I'm assuming it's some kind of url masking?

Story points: 2.0
[ENG] Detect and fix the cause that put all the CSS in a html tag

## Goal
We would like to improve the way the CSS code is fetched in the BE site. Also, look to achieve a way to share only 1 slippers-ui.css file for both navigation and BE repos preventing a duplicated file

![image](/uploads/1764d001d7351fd2bcb89575eae0fed3/image.png)

Sample data: 
- https://about.gitlab.com - CSS size 1.28MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/pricing/ - CSS size 1.28MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/install/ - CSS size 1.27MB, 1.25MB CSS unused (98%)
- https://about.gitlab.com/why-gitlab/ - CSS size 1.28MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/enterprise/ - CSS size 1.29MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/stages-devops-lifecycle/source-code-management/ - CSS size 1.27MB, 1.24MB CSS unused (97%)

**Coverage tab screenshot**
<details><summary>Click to expand</summary>
![image](/uploads/fd58b8b460e080f6ca267ef4eab5552a/image.png)
</details>


#### 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


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @aleal-ext 
- [ ] Consulted: @justin.vetter @laurenbarker @ndubord @lduggan @meganfilo
- [ ] Informed: @hsmith-watson 

## In scope
What is within scope of this request?

- [ ] Prevent CSS code in HTML tag
- [ ] Prevent duplicated slippers-ui.css file (from navigation and BE)


## 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
DevOps tools page "category" naming fixes

## Goal
We want to edit the /competition/ page so that instead of "categories" it states the stage that the viewer is currently looking at.

#### Jobs To Be Done
See image below:
![Screenshot_2023-02-03_at_15.30.27](/uploads/ecd860ec12038c45bc006964aa1d153e/Screenshot_2023-02-03_at_15.30.27.png)

We want each tab of the [competition page](https://about.gitlab.com/competition/) to replace the word "categories" with the stage that it belongs to, e.g. when you click "Create", the current word "Categories" should be replaced with "Create"; "Monitor" with "Monitor", etc.

#### 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: requested by Sid
- [ ]  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 Sid, Ashley, Dave
- [ ]  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 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`
- [X] No

## Page(s)
Which page(s) are involved in this request?
* 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: `GitLab Handle`
- [ ] 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
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering

Story points: 1.0
[Eng] - Time Calculator

## Goal
We would like to create a Time Savings calculator as a second tab on the ROI calculator page.

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* `[Page Title](URL)`

## Include any Figma files
* [Figma WIP](https://www.figma.com/file/fx89h6j2yToBAE1m7qHez8/ROI-Calculator---time-savings?node-id=5%3A7923&t=xxVWf7z6k6sg97pA-0)

## Include any graphic or design assets
* `Upload any extra files needed to complete this request`

## In scope
What is within scope of this request?

- [ ] Create calculator
- [ ] Deliverable 2


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: `@justin.vetter @laurenbarker @fqureshi`
- [ ] Informed: `Everyone`

Story points: 6.0
[ENG] - Guest users on Ultimate

## Goal
We would like to show current Premium SaaS users how much they can save by moving non-coding users to the "Guest" role (free) on Ultimate.

To do this we would like to create a calculator this shows the value of guest users

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* `[Page Title](URL)` - TBD

## Include any Figma files
* [Figma WIP](https://www.figma.com/file/ufPARcvcyR81uEUQtm82UK/Guest-users-on-Ultimate?node-id=111%3A41930&t=qPkthaA1JvA19CK8-0)

## Include any graphic or design assets
* `Upload any extra files needed to complete this request`

## In scope
What is within scope of this request?

- [ ] Create Guest users calculator component
- [ ] Deliverable 2


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @jhalloran @fqureshi
- [ ] Informed: `Everyone`

Story points: 4.0