giseldo/neodataset huggingface dataset:
Solution page migration - Devops Platform

Related to #191.

## Goal
We would like to migrate `/solutions/devops-platform/` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the new solutions template.

### Jobs To Be Done
* **Situation**: *When a user lands on* `/solutions/devops-platform/`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*

## Page(s)
Which page(s) are involved in this request?
* `[Accelerating Software Delivery](https://about.gitlab.com/solutions/devops-platform/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dvilchis-ext 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Applying the solutions template to this page
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository

## Out of scope
What is out of scope and not part of this iteration?

* Building a new template
* Any work in www-gitlab-com other than removing the 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: 8.0
UX: Pathfactory implementation / Design mock-ups

## Goal
I would like to create design mock-ups to explore how and where we can display Pathfactory's Web Tools widget and or carousel.

### Jobs To Be Done
* **Situation**: *When visiting about.gitlab.com*
* **Motivation**: *I want to see content that is relevant to my interest quickly*
* **Outcome**: *So that I can learn about a topic with little effort*

## Page(s)
Which page(s) are involved in this request?
* TBD-WIP

## Workfiles

* Figma - N/A

### Documents

* [GitLab <> Pathfactory agenda](https://docs.google.com/document/d/1YzcqYo4AJjXLEZJsTHkuEwGpjk_XxeBLr41aAjLsV2c/edit?usp=sharing)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran @nikkiroth @mackanic @ncregan 
- [ ] Informed: `@mpreuss22` @ndubord

## In scope
What is within scope of this request?

- [ ] Design mock-ups

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 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: 3.0
UX: User research | Why Premium? & Why Ultimate pages

## Goal
When making updates to the [Why Premium?](https://about.gitlab.com/pricing/premium/) & [Why Ultimate?](https://about.gitlab.com/pricing/ultimate/) pricing pages, I want to first do research with our end users, so I can better understand how they use the current layout and what changes they would like to see.

### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to easily find information about pricing*
* **Outcome**: *So I can make an informed purchasing decision.*

## Set up

#### What’s being tested?

* [Why Premium?](https://about.gitlab.com/pricing/premium/)
* [Why Ultimate?](https://about.gitlab.com/pricing/premium/)

#### How?
* https://www.usertesting.com/

- [ ] 1. Draft session: Run with 1 user and review
- [ ] 2. Duplicate test and edit (if it needs editing)
- [ ] 3. A/B tests:
    - [ ] 3.1 Test 1: 4 participants will complete tasks on the current Why Premium? page.
    - [ ] 3.2 Test 2: 4 participants will complete tasks on the current Why Ultimate? page.

#### General Questions

1. Is there anything we want to highlight?
1. Is there anything new we want to add?
1. Is there anything we can remove?

#### Research Questions

* Can users easily find the things they are looking for?
* Are users confused by how content is currently organized?
* Are there any improvements we can make to the current structure of the page?
* Are we using the best terminology?
* Is anything missing that a user would expect to be on the page?
* Is there anything on the page currently that shouldn't be there?


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] 4 user testing sessions [Why Premium?](https://about.gitlab.com/pricing/premium/)
- [ ] 4 user testing sessions [Why Ultimate?](https://about.gitlab.com/pricing/premium/)

## Out of scope
What is out of scope and not part of this iteration?

- Highlights reel
- Analysis and summary

## 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
- [ ] UX Design
- [ ] Engineering

Story points: 3.0
UX: User research | Features Page

## Goal
When making updates to the [Features page](https://about.gitlab.com/features/), I want to first do research with our end users, so I can better understand how they use the current layout and what changes they would like to see.

### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to easily find information about features that are relevant to my needs*
* **Outcome**: *To better understand if GitLab is the right solution for my problems*

## Set up

#### What’s being tested?
* [Features: Current page](https://about.gitlab.com/features/)
* [Features: Figma mock-up](https://www.figma.com/proto/XsnwxTLYPAN0j19vS6iSXm/Features-2.0?page-id=15%3A3641&node-id=37%3A2997&viewport=241%2C48%2C0.45&scaling=min-zoom&starting-point-node-id=37%3A2997) 
#### How?
* https://www.usertesting.com/

- [x] 1. Pilot session(s): Run with 1 user and review
    - [x] 1.1 [Pilot 1](https://app.usertesting.com/v/4929c951-c8eb-4fe2-a822-9ffa62dfc536?encrypted_video_handle=b8e9bd98-021f-46c5-86ea-6b40f219c6df&shared_via=link) - _failed due to mock-up not loading_
    - [x] 1.2 [Pilot 2](https://app.usertesting.com/v/28932e41-4415-4c85-aa57-e3244c8b9a64?encrypted_video_handle=471bacd8-26ac-403a-bb01-7578339d20b5&shared_via=link)
- [ ] 2. A/B tests:
    - [ ] 2.1 Test 1: 4 participants will complete tasks for the current live page and repeat the tasks on the new Figma prototype.
    - [ ] 2.2 Test 2: 4 participants will complete tasks for the new Figma prototype and repeat the tasks on the current live page.

#### General Questions

1. Is there anything we want to highlight?
1. Is there anything new we want to add?
1. Is there anything we can remove?

#### Research Questions

* Can users easily find the things they are looking for?
* Are users confused by how content is currently organized?
* Are there any improvements we can make to the current structure of the page?
* Are we using the best terminology?
* Is anything missing that a user would expect to be on the page?
* Is there anything on the page currently that shouldn't be there?


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran `engineer - TBD`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] 4 user testing sessions [current page](https://about.gitlab.com/features/)
- [ ] 4 user testing sessions [Figma prototype](https://www.figma.com/file/XsnwxTLYPAN0j19vS6iSXm/Features-2.0?node-id=15%3A3641)

## Out of scope
What is out of scope and not part of this iteration?

- Highlights reel
- Analysis and summary

## 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
- [ ] UX Design
- [ ] Engineering

Story points: 3.0
ENG: Dynamic breakpoints for navigation different language support

## Goal
We would like to investigate if it is feasible to create dynamic breakpoints in the navigation which will improve the experience for users who use GitLab in a language other than English as measured by not having overlapping elements.

Based on [this LogRocket session](https://app.logrocket.com/9jygng/gitlab/s/5-777d1b7e-98ed-4c5e-bd2d-d8db30e1df15/0?t=1637598795696) where the user was using GitLab in a Cyrillic language and many elements of the navigation overlapped making them difficult to read potentially unable to click.

### Jobs To Be Done
* **Situation**: *When a user uses the GitLab navigation...*
* **Motivation**: *they want to be able to easily read and click through all of the elements...*
* **Outcome**: *So that they can get wherever they need to go.*

## Page(s)
Which page(s) are involved in this request?
* Navigation (all pages)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jgarc 
- [ ] Consulted: @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Discover if it is possible to create dynamic breakpoints in the navigation as text increases or decreases
- [ ] Find out the difficulty of implementing the fix if it exists

## Out of scope
What is out of scope and not part of this iteration?

- TBD

## 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
[Transition 50 Pages] - Pricing

## Goal
We want to move https://about.gitlab.com/pricing/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*

## Page(s)
- [Pricing](https://about.gitlab.com/pricing/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [x] Yes
- [ ] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope

* [x] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] Apply [feature pop-up](https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/1536)

##3 Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review

Story points: 4.0
[Transition 50 Pages] - Homepage

## Goal
We want to move https://about.gitlab.com to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*

## Page(s)
- [Homepage](https://about.gitlab.com)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [x] Yes
- [ ] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope

* [x] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review

Story points: 4.0
[Transition 50 Pages] - Free Trial

## Goal
We want to move https://about.gitlab.com/free-trial/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*

## Page(s)
- [Free Trial](https://about.gitlab.com/free-trial/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [x] Yes
- [ ] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope

* [x] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review

Story points: 4.0
[Transition 50 Pages] - Install

## Goal
We want to move https://about.gitlab.com/install/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*

## Page(s)
- [Install](https://about.gitlab.com/install/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [x] Yes
- [ ] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @jhalloran @fqureshi @justin.vetter 
- [ ] Informed: `Everyone`

## In scope

* [x] Transition page
* [ ] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review

Story points: 8.0
[Transition 50 Pages] - Support

## Goal
We want to move https://about.gitlab.com/support/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.

### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*

## Page(s)
- [Support](https://about.gitlab.com/support/)

### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?

- [ ] Yes
- [x] No

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope

* [x] Transition page
* [x] Apply Slippers UI

### Stretch goal

- [ ] None as of now

### Out of scope

- Additional design updates 

## Requirements

- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review

Story points: 6.0
Add Buy Now Button to Website

We have a significant eComm new transaction goal for Q4 FY22, which is 1275 total eComm transactions.  In Q3, we achieved 840 transactions.  As the Marketing DRI for eComm, I am requesting that Inbound Marketing team create a buy now button that lands a user on the eComm page.  This will allow us to directly harvest inbound organic traffic and convert it to a sale.  We estimate that buy adding this feature to the website, we can generate an additional 100 eCommerce sales per month.

**Requirements**

[Requirements document for web team review/collaboration is here.](https://docs.google.com/document/d/1i9IfkaN6nb8yuzNKET54Kj8qhloo9_fnHg8CTA6NlMU/edit?usp=sharing)

**Measurement Plan**

[Measurement Plan Document is here.](https://docs.google.com/document/d/11XHQPd4L0_yBGEqgud9gjuSEFeoHffI0z6v7v1dvh0I/edit)

Story points: 8.0
Redirect gitlab.com/pricing To Pricing Page

## Goal
I would like to redirect traffic from this page which will improve traffic (and potentially the amount of people who convert) as measured by pageviews and traffic to the checkout page.

### Jobs To Be Done
* **Situation**: *When someone lands on gitlab.com/pricing*
* **Motivation**: *We want to redirect them to about.gitlab.com/pricing*
* **Outcome**: *So they can get to the content they're looking for*

## Page(s)
Which page(s) are involved in this request?
* [404 Pricing Page](https://gitlab.com/pricing)
* [Pricing Page](https://about.gitlab.com/pricing)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: `@mpreuss22`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] 301 Redirect

## 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:

- [ ] Engineering

Story points: 2.0
Set up social tags site wide for proper sharing

## Goal
We would like to set up the correct tagging for social sharing which will improve the display of content shared from GitLab's Marketing site as measured by social engagement.

### Jobs To Be Done
* **Situation**: *When someone shares content to Twitter, Facebook, or LinkedIn*
* **Motivation**: *We want the correct title, image, and body content to display*
* **Outcome**: *So we can make it easy to engage with content on these channels*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] All Marketing site page

## Out of scope
What is out of scope and not part of this iteration?

- Any Handbook pages

## 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:

- [ ] Engineering

Story points: 2.0
ENG: Stages of DevOps lifecycle page MVC1

Related to: https://gitlab.com/gitlab-com/marketing/inbound-marketing/marketing-website/-/issues/178

[Figma file](https://www.figma.com/file/4Uy6oP7zWfH1r5wnjlaY7g/Stages-of-the-DevOps-Lifecycle?node-id=0%3A1)

Story points: 3.0
Partner page UI updates / fixes

# Goal
Fix inconsistencies and update UI.

## Why
We will be pointing users to [Partners / Google Cloud](https://about.gitlab.com/partners/technology-partners/google-cloud-platform/) from the homepage hero next week. We want visitors to see a fluid and consistent design so they can feel confident about our product.

## Scope
- [ ] Remove confetti from the heading title (positioning is hard to control and there are enough visuals on the page)
- [ ] Swap purple CTA with the outline CTA
- [ ] Update card plate (add stroke) - [Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=2397%3A1400)
- [ ] Remove line that appears behind the cards
- [x] Increase spacing above "Get started with GitLab and GCP joint solutions" to 96px 
- [ ] Increase spacing above and below the testimonial to 96px
- [Screen_Shot_2021-10-08_at_10.38.22_AM](/uploads/b3039cb54997953e72681fb5a0a31e15/Screen_Shot_2021-10-08_at_10.38.22_AM.png)
- [Partner_Page_errors](/uploads/67516f07b0b6ea8341c39bc41fbea319/Partner_Page_errors.png)
- [Partner_Page_errors_2](/uploads/b9b37bec94c67b691b0b952490732922/Partner_Page_errors_2.png)
- [ ] Update Body-2 (14px) copy to Body-1 (16px)
- [Screen_Shot_2021-10-25_at_11.33.17](/uploads/62b81bad1f08a5f65819659131cee20a/Screen_Shot_2021-10-25_at_11.33.17.png)
- [Screen_Shot_2021-10-25_at_11.33.55](/uploads/387ab9ee2c13cdf51a9186713b1a330b/Screen_Shot_2021-10-25_at_11.33.55.png)


### Relates to:
Slack thread > https://gitlab.slack.com/archives/G01JH8CA8F3/p1633639300033500

Story points: 3.0
ENG: Fix card plate inconsistencies

## What
Adjust all card plates for a consistent UX.

Using this [blog card](https://gitlab-com.gitlab.io/marketing/inbound-marketing/slippers-ui/?path=/story/components-cards-blog--blog-card) as a base, make sure all other cards have the same plate.

- [ ] Stroke is consistent
- [ ] Drop shadow on default is consistent
- [ ] Drop shadow on hover is consistent
- [ ] Border radius is consisten

![Screen_Shot_2021-08-09_at_11.26.51_AM](/uploads/ee0083ff98b44896dd83dd1e61f0a5b1/Screen_Shot_2021-08-09_at_11.26.51_AM.png)

DRI:
- @jgarc 
- @Tinaliseng 

Consulted:
- [x] @jhalloran

Story points: 2.0
Update subtitle on comparison infographic

# Relevant URLs

[Tina caught a typo that's hardcoded in the Comparison Infographic component](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/87900#note_645330744). 

We need to update the component to fix this, I think we should do the following: 

1. Make `Feature maturity comparison against set of industry standards` a prop in the component so it's configurable.
1. Make `Learn more about our scoring methodology` a prop in the component so it's configurable as well.
1. Update the component in `www-gitlab-com` to use it as such.
​
## Scope/Deliverables

- [x] Make the heading a prop
- [x] Make the scoring language a prop
- [x] Update the implementation in the `www-gitlab-com` repository.
​
## Requirements

- [ ]  Review by UX/UI
- [x]  Review by engineering

## Release history:

```
Text
```

Story points: 2.0