giseldo/neodataset huggingface dataset:
Require code owner approval

## Goal
We would like to require a code owner approval for protect branches in the Buyer Experience repository.

### Jobs To Be Done
* **Situation**: *A merge request needs to be approved before merging to a protected branch.*
* **Motivation**: *We want to ensure that any change deployed to the marketing site is approved before it goes live.*
* **Outcome**: *So we can ensure control over the marketing site.*

## Page(s)
Which page(s) are involved in this request?
* https://docs.gitlab.com/ee/user/project/protected_branches.html#require-code-owner-approval-on-a-protected-branch
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/.gitlab/CODEOWNERS

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpreuss22 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?
- [ ] Iterate on CODEOWNERS and who owns what parts of the project
- [x] Adjust project settings in Buyer Experience project

Story points: 2.0
Homepage hero carousel progress bars

## Goal
- For each image in the carousel, have a progress bar representing it's state
- Transition each image with a fade-in

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* home (refresh)



![Screen_Shot_2022-04-25_at_11.31.30_AM](/uploads/0e502d0937d3d9a574f864ab0b08179f/Screen_Shot_2022-04-25_at_11.31.30_AM.png)

Story points: 3.0
Follow-up from "ENG: Solutions - By Sector - Public Sector""

The following discussion from !433 should be addressed:

- [ ] @mduque-ext started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/433#note_921322831):  (+1 comment)

    > @dennischarukulvanich tagging you in this MR which has [the public sector page](https://feature-quotes-carousel.about.gitlab-review.app/solutions/public-sector/). 
    > 
    > Could you please take a look and make sure we are not missing important Analytics stuff that should be in place? Thank you very much in advance!

We would like to address feedback received concerning the GA tags and Analytics elements that should be in place for the `/solutions/public-sector` page

Pages involved: 
`/solutions/public-sector`

**@dennischarukulvanich original feedback for the Public Sector Page:**


Update all `data-ga-location` values to align with section name. The reason for this is to distinguish identical links. For example, there are 2 "hardened" links under solutions block and value prop.

* [x] hero
* [x] benefits
* [ ] quotes carousel
* [x] solutions block
* [ ] value prop
* [x] case studies
* [x] resource cards

Update "Start your free trial" CTA button:

* [x] `data-ga-name="free trial"`

Under "Security. Efficiency. Control.", add data-ga-name/location to each Learn More link.

* [x] `<a data-ga-name="reduce security learn more" data-ga-location="benefits">`
* [x] `<a data-ga-name="free up learn more" data-ga-location="benefits">`
* [x] `<a data-ga-name="modernize learn more" data-ga-location="benefits">`

Add these data attributes to each toggle div section:  

* [x] `<div data-inbound-analytics="public-sector-leap-target" data-toggle-group="example: Reduce security and compliance risk" data-ga-toggle="expand or collapse" class="accordion"`

Add data attributes to the "Trusted by government" carousel per slide  

* [x] `<div data-ga-carousel="example: public-sector us army" class="quotes-carousel__quote">`

Update "Off-line Environment" learn more link:

* [x] `data-ga-name="offline environment"`

Add attributes to "Low to High Environment":

* [x] `data-ga-name="low to high" data-ga-location="quotes carousel"`

Add attributes to "GitLab meets NIST SSDF 1.1 guidance" and "hardened"

* [x] `data-ga-name="gitlab meets nist" data-ga-location="value prop"`
* [x] `data-ga-name="hardened" data-ga-location="value prop"`

* [x] I noticed the "All Case Studies" link has an `<a>` tag nested inside another `<a>` tag. Not sure if this is a mistake, but Google Tag Manager will target the inner `<a>` tag, so the data-attributes will need to go on both `<a>` tags.

* [x] Same as above for the case study learn more links. 
* [x] Also, need to update data-ga-name from "learn more" to include the customer's name, ie. "us army cyber school learn more".

Add data attributes to the "View all resources" link:

* [x] `data-ga-name="view all resources" data-ga-location="resource cards"`

Story points: 1.0
Missing Open Graph Tags

Some Open Graph tags are missing from the URLs in the Buyer Experience repo.

With Open Graph, you get full control over how your posts look when they're shared on social media platforms like Facebook. Adding Open Graph markup code to HTML makes it easy to set an attractive visual, title and description for your page.

Open Graph helps you improve the way your content looks, which leads to a higher click-through rate.

#### Missing Tags
- `og:url`
- `og:title`
- `og:image`
- `og:type`

Story points: 2.0
ENG: Horizontal scroll bar component

We need a component to use for sections horizontal scroll sections on mobile to hint to the viewer that there is content to the right. 

Example: [Figma link](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=1174%3A8136)

Story points: 4.0
ENG: Apply intro text component to Delivery Automation

## Goal
We would like to iterate on the [solutions intro component](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/649) and apply it to https://refresh.about.gitlab-review.app/solutions/delivery-automation/.

## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/delivery-automation/
* [Solutions Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11) with full layout for Automated Software Delivery
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/refresh/components/solutions/by-solution/by-solution-intro.vue

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Iterate on the solutions intro component to match Figma
- [ ] Apply the updated component to `/solutions/delivery-automation/` for the `refresh` branch

## 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
Deprecate and Redirect Solutions/Feature pages

After auditing the content of the website for the upcoming Marketing IA site refresh we identified `/solutions/` and `/stages-devops-lifecycle/` pages that could be deprecated, redirected or remain.

In the new structure some solutions and stages pages will remain or be moved to newly created folders. The remaining pages will be deprecated and redirected to an alternative page but I want to ensure that no page of strategic value is unnecessarily culled.

[List of pages to kept, redirected or deprecated.](https://gitlab.slack.com/files/U014T1XSKT6/F0371BSQGTE/solutions_-_ia_refresh)

Story points: 2.0
ENG: Refresh app is failing to load javascript

## Goal
The refresh review app is failing to load javascript. Because of this pages arn't loading correcting.

For example: 
- https://refresh.about.gitlab-review.app/ - image caresoul not displaying
- https://refresh.about.gitlab-review.app/features/ - first paint is empty
- https://refresh.about.gitlab-review.app/pricing/ - CTA bottom module blank ( think this all pages )
- https://refresh.about.gitlab-review.app/solutions/public-sector/ - hero is blank

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @tywilliams 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `Everyone`

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
ENG: Migrate Continuous Delivery from www-gitlab-com

## Goal
We would like to migrate the Continuous Delivery page to the Buyer Experience repository and use the new template for the child stages dev ops lifecycle pages. 

### Jobs To Be Done
* **Situation**: *When a user lands on https://about.gitlab.com/stages-devops-lifecycle/continuous-delivery/ it is using the same template as https://about.gitlab.com/stages-devops-lifecycle/enablement/*
* **Motivation**: *We want to have this page built in the Buyer Experience repository.*
* **Outcome**: *So we can be consistent with where pages are built for the stages devops lifecycle section of the website.*

## Page(s)
Which page(s) are involved in this request?
* Live -> https://about.gitlab.com/stages-devops-lifecycle/continuous-delivery/ 
* Current location -> https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/stages-devops-lifecycle/continuous-delivery/index.html.haml
* Move content here -> https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/stages-devops-lifecycle 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Migrate content to BE repo and create yml file for it
- [ ] Apply the template used for other child stages-dev-ops lifecylce pages
- [ ] Create MR to remove page from www-gitlab-com

## Out of scope
What is out of scope and not part of this iteration?

- Changing the template

## 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 order of Stages DevOps Lifecycle

## Goal
“Manage” is something that would happen at the end not the beginning of the dev ops lifecycle. Therefore, we'd like to update the order of stages when they appear on the site, placing "Manage" at the end. 

This includes the following places in https://refresh.about.gitlab-review.app/: 
- [ ] Homepage section - "For every stage of the DevOps Lifecycle"
- [ ] Navigation - Why GitLab > "The DevOps Lifecycle"
- [ ] Features - https://refresh.about.gitlab-review.app/features/ 

### Jobs To Be Done
* **Situation**: *When a user encounters a "Stages Dev Ops Lifecycle" section on the marketing site, the manage stage is last*
* **Motivation**: *We want to be concise on the order of stages in the Dev Ops Lifecycle.*
* **Outcome**: *So we can be  consistent and a leader in the category.*

## Page(s)
Which page(s) are involved in this request?
* Any page built by the Buyer Experience repository

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
ENG: Why GitLab content updates

### Scope

Iteration 3 of Why GitLab
- New hero
- New cta / devops stages section
- Update content throughout the page to match [Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05)
- Accordion section styling updates
- Cards section styling updates

Story points: 4.0
Why GitLab: Comparison Graph

Design isn't totally finalized yet, but it seems that we're going with something in [this direction](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=981%3A5770). 

I'll take this on this iteration. I'll try to get it done before Thursday for release stuff, but if not I should be able to wrap by the end of the week regardless.

Story points: 6.0
Why GitLab Analytics updates

Relates to #638 

From this [comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/393#note_913406026):

> **New MR**  

> SCM Learn More link  
`data-ga-name="scm learn more" data-ga-location="body"`   
CI/CD Learn More link  
`data-ga-name="cicd learn more" data-ga-location="body"`   
GitOps Learn More link  
`data-ga-name="gitops learn more" data-ga-location="body"`   
(Our Customers Have Spoken) See More  
`data-ga-name="customers see more" data-ga-location="body"`   
View All Case Studies  
`data-ga-name="case studies view all" data-ga-location="body"`   

> **Comparison**  
See GitLab vs button  
`<button class="next-comparison-button" data-ga-name="see gitlab vs [name of brand, ie. atlassian]" data-ga-location="why-compare">`   
See more details  
`data-ga-name="[name of brand, ie. Atlassian] details" data-ga-location="why-compare"`   
The div container per Brand  
`<div class="slp-container" data-inbound-analytics="[name of brand, ie. atlassian] compare">`   
Need this to see how visible each brand is, and how many clicks per brand to gauge interest. Ex) 100 users saw the Atlassian comparison, 10 clicks on See More = 10% click rate for Atlassian.

Story points: 2.0
Add stock images to solutions hero and  no-image hero component

This is a follow up issue to build a no-image hero component: https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=871%3A2092

As part of this issue, please also update the hero image on the following pages ([thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/389#note_911631595 
)):

* [Public Sector 1](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=816%3A1668)
* [Startups 2](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=833%3A1908)
* [Enterprise 1](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=833%3A1881)
* [No image 4](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=871%3A2092)


----

The following discussions from !389 should be addressed:

- [ ] @mduque-ext started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/389#note_910636846):  (+2 comments)

    > @laurenbarker Here's the Hero for Solutions component created and applied to all solutions pages (except the ones using the `by-solution-hero` that Javi did). It has configuration for 1 or 2 buttons and rounded or rectangle image. 
    > 
    > Should we use a placeholder image for pages which don't have an image or sould we have an option in this component to handle pages w/o image in the Hero section (such as [agile delivery](https://about.gitlab.com/solutions/agile-delivery/))?
    > 
    > What do you think?

- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/389#note_910664686):  (+5 comments)

    > @Tinaliseng Are the hero image styles in [this figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11) ready to build? Miguel is out Thursday and Friday this week, so I'd like to get this MR deployed tomorrow if possible. 
    > 
    > I'll be going through all these page as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/666) as well, so we'll have more review cycles here.

Story points: 1.0
Deprecate or Redirect Event pages

After auditing the content of the website for the upcoming Marketing IA site refresh we identified `/events/` pages that could be deprecated. 

[Events page deprecate list](https://docs.google.com/spreadsheets/d/1ZgCOSiIkAK8Kj_NXizFUE74uMDn5piNuo8wz9RIwOJI/edit#gid=0)

Story points: 2.0
Fix sticky nav in refresh branch

The sticky nav in the refresh branch has white on white links. 

1. https://refresh.about.gitlab-review.app/solutions/education/
2. https://refresh.about.gitlab-review.app/analysts/

Fix these links so they're visible and use the correct colors. 

It also seems the stickiness is starting at the wrong part with the navigation. I'm going to check with @ndubord to make sure it plays nice with the nav.

Story points: 2.0
ENG: Footer updates

Related to #616

From this [comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/341#note_911860714): 
> Hi @meganfilo! We have updates for the footer - let me know if we need to create another issue. here is the [figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=5021%3A9923) link and a link [an excel](https://docs.google.com/spreadsheets/d/1D9O84YDXxfjoRhUiwtWySe6Az6pQ2MsjiB6iqhUJHLU/edit#gid=0) that explains what is is changing.

Story points: 1.0
Add cache bust to Nuxt favicons

Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/631

Now that we have [fixed the 404 files](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/102323), some users may have cached assets with the broken favicon in their browsers. 

This will resolve over time, but we can also cache bust the old favicon with a query string at the end of the assets. I will also check to see if Nuxt has a conventional way to do this - most CSS/JS files with Nuxt get a cache bust at build time, but these are hardcoded strings, so we may have to do it the old fashioned way.

Story points: 1.0
ENG: 'No-Image' fallback library - Resource cards

## Goal
We would like to have a set of fallback images to choose from when a resource card doesn't have an associated image. These should live somewhere in our repo.


## Page(s)
Which page(s) are involved in this request?
* Any page that displays resource cards.

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Set of fallback cards
- [ ] Somewhere for them to live

## What's involved

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
CODEOWNERS and deployment permissions during release week

## Goal
We would like to define ownership permissions for the Buyer Experience repository the week of our big release. There are alot of moving parts and there is a high risk of something breaking if it's not synced correctly with our release branch. 

### Jobs To Be Done
* **Situation**: *When a MR is deployed to the Buyer Experience main or refresh branches the week of 4/27 it is reviewed and deployed by our team*
* **Motivation**: *We want tighter ownership of our codebase during the big reveal*
* **Outcome**: *So we can ensure a smooth launch of the new site architecture and brand release*

## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @gitlab-com/marketing/digital-experience 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Define process for adding member as a maintainer to our Buyer Experience repository
- [ ] Iterate on our CODEOWNERS 
- [ ] Document in the handbook

## Out of scope
What is out of scope and not part of this iteration?

- www-gitlab-com

## 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
- [x] Engineering

Story points: 1.0
ENG: GitLab 15 landing page

## Goal
We would like to build a GitLab 15 landing page.

### Jobs To Be Done
We need a GitLab 15 a landing page at about.gitlab.com/fifteen. This landing page will use the existing GitLab 10 template that exists in the Buyer Experience repository. Changes to this template will be: 
- Create new template for GitLab 15 that applies the "fresh coat of paint" to GitLab 10 template
- Fullwidth hero image - Sync with @amittner to get the asset
- [Content doc](https://docs.google.com/document/d/1tnLr8oOty02s_bg6F626Crt4J7B1P-GcunLKnJYPxjU/edit#)
- Stretch goal - add countdown timer component

## Resources
* [Buyer Experience Template for about.gitlab.com/ten ](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/pages/ten.vue)
* https://about.gitlab.com/ten/
* https://about.gitlab.com/gitlab-14/
* [Figma file for a simpler version](https://www.figma.com/file/PRnQFROp9rDgKvfix9WA5E/14.0-Release-Landing-Page?node-id=49%3A95)
* [content doc](https://docs.google.com/document/d/1tnLr8oOty02s_bg6F626Crt4J7B1P-GcunLKnJYPxjU/edit#)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Build new landing page at /fifteen
- [ ] Start with existing template used for /ten
- [ ] Confirm assets and content

## Out of scope
What is out of scope and not part of this iteration?

- anything in www-gitlab-com

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering

Story points: 4.0