giseldo/neodataset huggingface dataset:
[Design] Featured Content Block

## Goal
We would like to reintroduce the merchandisable featured content block which will improve engagement as measured by CTA clicks to content items followed by contribution to ARR or Free Trial.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[Homepage](http://about.gitlab.com)`

## 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?

- [ ] Add 3 cards that link to featured content
- [ ] We require a content calendar to change out the content on a biweekly or monthly basis

## Examples
![Screen_Shot_2022-09-01_at_2.15.30_PM](/uploads/2c9274eb5b3501863e63eb08cbaa60ca/Screen_Shot_2022-09-01_at_2.15.30_PM.png)
https://www.uipath.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:

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [x] UX Design
- [x] Engineering

Story points: 2.0
ENG: Full Hero Carousel

## Goal
We would like to test adding a full hero carousel to the homepage which will improve engagement as measured by CTA clicks within the homepage hero.

This issue is to create the functionality for the home carousel not to implement it live.  We also want this to be a new component and not overwrite the current home hero.  We should use the current home hero as a starting point in this carousel.

- [ ] The carousel transition includes left text and image
- [ ] The user should be able to click to move to the next slide
- [ ] The carousel should be flexible that can handle 2-5 slides
- [ ] When a user mouses over the entire carousel the timer should pause
- [x] Work with @dennischarukulvanich so we can track the CTAs per slide

When engineering is done we should make sure the old hero is on the home page and we can merge this new component to wait for content.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[Homepage](http://about.gitlab.com)`

## 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?

- [ ] AB Test current (control) carousel vs. a carousel that changes messaging and CTA links as well.

## Out of scope
What is out of scope and not part of this iteration?

- Experience or behaviour changes beyond in scope description

## Example:
![Screen_Shot_2022-09-01_at_1.17.58_PM](/uploads/551877bef585f89c337c3b6f3f181cb4/Screen_Shot_2022-09-01_at_1.17.58_PM.png)

[https://www.snowflake.com/en/](https://www.snowflake.com/en/)

## 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:

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [x] UX Design
- [x] Engineering

Story points: 5.0
ENG: OneTrust Cookie banner update

## Goal

We would like to see if force choice is an option for the cookie banner which will improve user selection as measured by acceptance or rejection of cookies.

### Jobs To Be Done

* **Situation**: *When a customer visits GitLab...*
* **Motivation**: *We want them to make a choice if they want us to use cookies or not for their sessions...*
* **Outcome**: *So we can deliver the preferred experience.*

## Page(s)

Which page(s) are involved in this request?

* [Home page cookie banner](https://about.gitlab.com/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @lduggan @justin.vetter @fqureshi 
- [ ] Informed: `@mpreuss22` 

## In scope
What is within scope of this request?

- [ ] Remove "x" close icon from non-US cookie banner. But, must keep the "reject-all" button for France.
- [ ] Remove "x" close icon from US cookie banner for future proofing.
- [ ] Stop page scroll until a user has selected their cookie preference.

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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
Broken Link: 404 on Learn

## Goal
The "Learn more about GitLab Certifications" CTA on https://about.gitlab.com/learn/ goes to a 404 page. 


## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/learn/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] 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:

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Create: Overview of Partner Program Template

## Goal
We would like to build a new template and apply it to Overview Partners page. This new template was created as part of [this issue.](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1107)

[Figma Link](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=170%3A5667)


### Jobs To Be Done
* **Situation**: *We'd like a unified landing page for finding GitLab partners*
* **Motivation**: *When users need more information we can direct the to the correct spot*
* **Outcome**: *So we can offer them the best service*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/partners/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @ctsang-ext @mlebeau
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Apply new template to Partners landing page @ https://about.gitlab.com/partners/

## 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
ENG: Blog Images | compress current blog images

## Goal
We would like to reduce the page size and increase core vital scores across about.gitlab.com.  We would like to start with the blog by running a CLI script to compress all images to reduce file size.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## 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
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Run script to compress all images
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Replace or resize the images 
- Not in scope 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: 8.0
ENG: Revert deleted feature images

## Goal
We would like to revert the deleted feature images so they can be used on the refreshed /fetures page

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ndubord 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: @mmanunga-ext 

## In scope
What is within scope of this request?

- [ ] Revert deleted images
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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: Homepage | Update DevSecOps card

## Goal
We would like to update the DevSecOps card in the resources section.

- [ ] Change 2021 to 2022
- [ ] Update the thumbnail image to the one below:

![DevSecOps-thumbnail](/uploads/54bb9070a51a4ad4dd08bc138ee8c0dd/DevSecOps-thumbnail.jpg)

### 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](https://about.gitlab.com)

## 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?

- [ ] Update DevSecOps resource card on the homepage
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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
Smartling Code Repo Connector - POC

### Background

We've contracted the [Code Repo Connector](https://help.smartling.com/hc/en-us/articles/360008038694-Repository-Connector-Overview#:~:text=The%20Repository%20Connector%20is%20designed,translations%20back%20to%20the%20repository.) with Smartling since the contract began, but we haven't used it. This issue is to track a Proof of Concept for the Smartling Code Repo prior to contracting it this year.

* Note the DRI of the POC will be the Product or Eng Teams (this issue can be moved if necessary)
* Digital Experience team will be DRI related to the website as the Code Repo Connector is an alternative to the GDN (this issue can be copied if necessary)

### Proof of Concept Options

1. TBD

### Comments from Smartling

* Prior to any POC, Smartling requested that we define what a successful POC looks like.
* Our next steps on the website evaluation will be to arrange a technical demo of the Code Repo Connector highlighting any specific use cases or actions the team would like to validate.
* We can schedule a discussion of the pros and cons to use our Repository Connector Vs the GDN to support the website translation initiative both are great options, the deciding factors will be based on your overall strategy/objectives of the website translations project and the team's desired experience/LOE.

### Next Steps

* Determine what we would like to get out of the POC? What questions are we trying to answer / what does success look like?
* Determine POC options for the Code Repo Connector.
* Technical discussion with Smartling related to using the GDN or the Code Repo for website translation.

@RLeihe268 @mpreuss22 @davidbrown1 @justin.vetter @laurenbarker @s_awezec 





<!-- Please leave the label below on this issue -->

Story points: 4.0
ENG: Slack integration marketing landing page

## Goal
We would like to create a landing page on about.gitlab.com for the Slack/GitLab integration.

Design is attached in design management :arrow_down: 

This landing page needs to meet the Slack guidelines for the landing page are outlined [here](https://api.slack.com/start/distributing/guidelines#landing).

* Must include privacy policy link
* A clear overview of your Slack app, any associated services, and the problem your app solves.
* A detailed explanation of how your app works in Slack. Screenshots and GIFs are a good way to show people what they can expect in Slack after installing your app.
* A clear path to installing your Slack app, whether that is an Add to Slack button on your landing page or instructions for accessing your Add to Slack button.
* A clear path to using your app. Once people install your app to their workspace, they should be redirected to a page that confirms the installation was successful and provides clear next steps for getting started with your app.
* Needs to be publicly accessible i.e. not behind a login.
* Your landing page is, well, a landing page crafted by you, specifically for your Slack app - not a link to a PDF, document or code repository

### Jobs To Be Done
* **Situation**: *When anyone is looking for information about our integration with Slack, there is publically accessible landing page*
* **Motivation**: *We want roll out new Slack GBP app to all gitlab.com users, but current landing page (https://gitlab.com/-/profile/slack/edit) does not match the Slack guidelines*
* **Outcome**: *So we can improve conversions*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/slack/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @katiemacoy @ctsang-ext 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create a MVC landing page for the Slack integration that meeds requirements from Slack
- [ ] For efficency, use the a solutions template ,[Public Sector](https://about.gitlab.com/solutions/public-sector/)
- [ ] Deploy landing page to `about.gitlab.com`
- [ ] Build page in Buyer Experience

## Out of scope
What is out of scope and not part of this iteration?

- And work in the product codebase or `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: 3.0
Enable markdown in support copy component

## Goal
We would like to enable markdown in the support copy component. This will increase efficiency and self service of content updates by the support team to our support pages.

The end goal of this is issue is to enable markdown content to be consumed by the support template as a MVC.

### Jobs To Be Done
* **Situation**: *When a update is needed to our support pages, content is supplied using markdown*
* **Motivation**: *We want to make it easier for the support team to self serve updates to these pages*
* **Outcome**: *So we can increase cross functional collaboration*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/
* https://about.gitlab.com/support/customer-satisfaction/
* https://about.gitlab.com/support/general-policies/
* https://about.gitlab.com/support/gitlab-com-policies/
* https://about.gitlab.com/support/definitions/
* https://about.gitlab.com/support/portal/
* https://about.gitlab.com/support/us-federal-support/
* All other content files in [/content/support/](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/support)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @jcolyer 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Enable markdown to be consumed by the [components/support/copy.vue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/components/support/copy.vue)
- [ ] Update all content supplied to the support/copy.vue component to markdown
 

## Out of scope
What is out of scope and not part of this iteration?

- Changes to the template
- Changes to any content - other than `HTML` to `MD` in `yml` files.

## 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: 9.0
ENG: Personalization Spike | POC Create a test for personalized content based on URL param

## Goal
We would like to create a Proof of Concept around direct personalization based on incoming URLs with params.  



### Jobs To Be Done
* **Situation**: *When a user clicks on a CTA from a Marketo email, Marketo landing page, or social post the page directed to is not personalized based on the campaign*
* **Motivation**: *We want to help drive user clicks and engagement and have a wholistic marketing funnel*
* **Outcome**: *So we can give users personalized content based on the external campaign*

## Page(s)
Which page(s) are involved in this request?
* [Home](https://about.gitlab.com)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ndubord 
- [ ] Consulted: @justin.vetter `@fqureshi` 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] POC homepage hero change H1 and button text based on 2 different params
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Deploying this POC live
- Not in scope 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
Alliance Partners - Inappropriate use of GitLab logo for partners without own logo

## Goal
We need to stop using our trademark logo to refer to partners.

**Engineering Ask to Resolve Issue**

We just need to replace all gray tanuki logos on the [Alliance page](https://about.gitlab.com/partners/technology-partners/) with the handshake. [See figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=277%3A9473). They should be at 60x60px to match with the height of the other logos.

[Thread link](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1271#note_1079448051)

### Jobs To Be Done
* **Situation**: *As soon as possible or within the next month*
* **Motivation**: *We need to cease use of the GitLab logo for partners listed on this page, that do not have their own logo*
* **Outcome**: *This needs to be done to avoid dilution of our trademarks, and protect GitLab's intellectual property rights and interests*

## Page(s)
Which page(s) are involved in this request?
* `[Alliance Partners](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: @fqureshi 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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: 3.0
Tracking: Add Data Attributes to "View All..." Nav Links

## Goal
Please add the following data- attibutes to the "View all stages" link located in the Why Gitlab and Platform > The DevOps Lifecycle navigation menu. 

- `data-nav-levelone="platform" or "why gitlab"`
- `data-nav-leveltwo="devops lifecycle"`
- `data-nav-levelthree="view all stages"`


## Page(s)
Which page(s) are involved in this request?
* All about.gitlab.com pages in the navigation menu
* Don't forget the ShadowDOM version and mobile site

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] 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: CTA bottom block scroll on about.gitlab.com/solutions/education/campus/

## Goal
An incident of the scroll not being triggered when the Call to action in the bottom section of the page is on the screen. 

![weird-cta-scroll-issue](/uploads/5ee33481eebcea2025eed73174a89347/weird-cta-scroll-issue.mov)

## Page(s)
Which page(s) are involved in this request?
* [about.gitlab.com/solutions/education/campus/](https://about.gitlab.com/solutions/education/campus/)

## 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

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 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