giseldo/neodataset huggingface dataset:
Enable feature flags for Buyer Experience repository

## Goal
We would like to enable feature flags for the Buyer Experience repository.

### Jobs To Be Done
Feature flags deploy your application’s new features to production in smaller batches. You can toggle a feature on and off to subsets of users, helping you achieve Continuous Delivery. Feature flags help reduce risk, allowing you to do controlled testing, and separate feature delivery from customer launch.

https://docs.gitlab.com/ee/operations/feature_flags.html

Related https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/epics/133 

## 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: `GitLab Handle`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Enable feature flag functionality for Buyer Experience repository
- [ ] Create a test feature flag, enable it, monitor, and verify it is working. This test could be a hidden code comment in the footer or similar that is not present to our users.
- [ ] Disable the test feature flag
- [ ] Create a video demonstrating how to use feature flags in the Buyer Experience repository. Post the video to our Digital Experience playlist on GitLab Unfiltered
- [ ] Document the process in our handbook, and link to the video

## Out of scope
What is out of scope and not part of this iteration?

- Any other feature flag testing - those will need new issues. This is just the creation and implementation of a control feature flag to verify the functionality is working.

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 4.0
ENG: Typography spacing bug mobile | Why GitLab

### Describe the Bug
On a mobile device the typography and spacing overlaps on the DevOps chart.

<details><summary>Screen Shot</summary>
![IMG_4557C49F1325-1](/uploads/f8c5af84fc6c670f4c0335e69fb5d383/IMG_4557C49F1325-1.jpeg)
</details>



### What's my browser? 
Safari, Chrome, & Firefox mobile see this issue.

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/why-gitlab/

## 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: Find a Alliances Partner Page

## Goal
We would like to build a new template and apply it to the GitLab Alliance 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=60%3A2135)


### Jobs To Be Done
* **Situation**: *We'd like a unified user experience 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/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 @ctsang-ext @mlebeau
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Move [`www-gitlab-com/data/applications.yml`](https://gitlab.com/-/ide/project/gitlab-com/www-gitlab-com/tree/master/-/data/applications.yml/) to the Buyer Experience repository 
- [ ] Create a tab component ([figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=70%3A3995) )
- [ ] Enable search functionality of alliance partners (applications.yml). Search bar located in tabed component
- [ ] Create partner card ([figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=70%3A3995))
- [ ] Build "Find a Partner" template
- [ ] Modify template to link out to Impartner platform for Channel partner search (https://partners.gitlab.com/English/directory/)
- [ ] Apply "Find a Partner" template to https://about.gitlab.com/partners/technology-partners/ 

## Out of scope
What is out of scope and not part of this iteration?

- Creating search functionality for channel partners
- API integration for Impartner

## 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: Remove grayscale styling from GitLab logo on Alliance Partners page

## Goal
We would like to remove the grayscale styling from the GitLab logo on the Alliance Partners page.

[Slack conversation](https://gitlab.slack.com/archives/CN8AVSFEY/p1658242096480099)



## Page(s)
Which page(s) are involved in this request?
* [Alliance Partners Page](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: @justin.vetter 
- [ ] Informed: `@smccreesh`

## In scope
What is within scope of this request?

- [ ] Removing the `filter: grayscale(100%);` from the logo svg
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Swapping any other logos from the page.
- 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
Remove GitLab vs Sysdig page

## Goal
Please remove GitLab vs Sysdig page from staging as requested here: https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/4852#note_1028103314

## Page(s)
Which page(s) are involved in this request?
* `https://about.staging.gitlab.com/devops-tools/sysdig-vs-gitlab.html`

## 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?

- [ ] Remove page from staging

## 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
Update to SlpDropdown to allow option names different from their values

Our SlpDropdown component currently takes in a list of options and gives each `<option>` tag's `name` and `value` attribute the same name. This is problematic for items where the value needs to be altered from the name/label that the user sees.

Example:
Building a filter by location for the Commit page. We want the filter option to read 'New York City', but the list of items it's filtering through have a location of 'NYC'. It would be nice if the HTML could look like `<option name="New York City" value="nyc" />`

Story points: 4.0
Eng: Sales page redesign

## Goal
We would like to update the sales page as per the [Figma design](https://www.figma.com/file/GuCqkaoZG8BqkBV6eE7xxT/Sales?node-id=43%3A2214).


## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/sales/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@ctsang-ext`
- [ ] Informed: `@fqureshi`


## Out of scope
- Changing the form content on Marketo (updating any text, fields etc)

## 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
Add link from Homepage "Stages of the DevOps Lifecycle" section to Stages of DevOps table on Why GitLab

## Goal
We would like to add a link to the second section of the homepage that links to the DevOps table on the Why GitLab page which will make a visitors experience more efficient as measured by pages per session.

### Jobs To Be Done
* **Situation**: *When a prospective user wants more information on the Stages of The DevOps cycle*
* **Motivation**: *We want to make it easy for them to view all the features listed in the DevOps Stages table*
* **Outcome**: *So we can efficiently communicate the breadth of our product.*

## Page(s)
Which page(s) are involved in this request?
* [Homepage](https://about.gitlab.com)
* [Why GitLab](https://about.gitlab.com/why-gitlab)

## 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 a text link to the subheader of the "Stages of the DevOps Lifecycle" section of the homepage that links to the Stages of DevOps table on Why GitLab


## 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: 1.0
GA: Turn off tracking for Denmark, Norway, France, Italy, and Austria

## Goal
Related note: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/997#note_1025872795

Recent laws were passed that declared Google Analytics illegal since EU data is processed on a US server. Turn off Google Analytics entirely in Denmark, Austria, France, Italy and Norway. 

Please refer to this OneTrust Geolocation Exposure script:
https://community.cookiepro.com/s/article/UUID-f1caf6bb-0003-8e79-6caf-2a7d04e357d7?language=en_US

This line will grab the country ID from OneTrust: 
`var country = options.country.toString();`

The geolocation script is already on placed:
<img src="/uploads/d3c7e7d08afbce3c549c6ed33ae52d4f/Screen_Shot_2022-11-12_at_11.49.49_AM.png" width="800">

Please place the following code before the GTM script, but after the Geolocation Exposure script on all pages:
- about.gitlab.com
- page.gitlab.com
- learn.gitlab.com
- gitlab.com (public facing pages) 
- docs.gitlab.com 

```
<script>
window.dataLayer = window.dataLayer || [];

dataLayer.push({
  'oneTrustCountryId': options.country.toString();,
  'event' : 'OneTrustCountryLoad'
});
</script>
```

On Google Tag Manager, apply the oneTrustCountryId dataLayer variable to all Google Analytics tags to the trigger, so the tag doesn't fire for:  DK, AT, FR, IT and NO. 

## Page(s)
Which page(s) are involved in this request?
- about.gitlab.com
- page.gitlab.com
- learn.gitlab.com
- gitlab.com (public facing pages) 
- docs.gitlab.com 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dennischarukulvanich @miraclebanks @jgarc 
- [ ] Consulted: @laurenbarker @justin.vetter @RobRosu @emccrann @BronwynBarnett @MihaiConteanu 
- [ ] Informed: @mpreuss22 @christinelee @dmicovic @jahye1 @degan @rkohnke 


## 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 3.0
Add Minimized Footer to Navigation Repository

## Goal
We would like to add the minimized footer to the Nav repository so we can use it within Buyer Experience

As part of the refresh a few months ago, we created a minimized footer with a goal for it to be used on the Pricing page. Looks like it is not being used there anymore, but the mini-footer still lives in BE. It would be nice to use for our Commit page, but the Web IDE and View Source buttons are not dynamic to the page/do not work. Also, @justin.vetter proposed a good point in that the mini-footer does not contain any legal type of links, such as our Privacy policy.





## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `Search, Nav, and Support Team`
- [ ] Consulted: @jhalloran @meganfilo @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

1. Investigate and add, if applicable, any necessary links to the minimized footer
2. Add the mini-footer html and styles (found in BE at `/components/footer/minimized-footer.vue`) to the Navigation repository (OR! Refactor the current footer to take in some kind of prop that will make it change to be mini on a page)
3. Fix the View Source and Web IDE links to work dynamically depending on what page the footer is used on

## Out of scope
What is out of scope and not part of this iteration?

- Add the minimized footer to any pages, we can save that for future issues.


## 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 (maybe, depending on if extra links are needed)] UX Design
- [x] Engineering

Story points: 2.0
next steps CTA block on why gitlab page is only visible at awkward viewports

## Sitation
When a user is scrolling to the `/why-gitlab` page, we find that the section is only visible when the section is halfway away from the viewport.

![Screen_Recording_2022-07-12_at_5.53.08_PM](/uploads/404ce4361cd3e563baf36204eaaf2f06/Screen_Recording_2022-07-12_at_5.53.08_PM.mov)

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/why-gitlab/

## 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?

- [ ] Fix AOS scroll

## 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
DEX Marketing Ladder

## Goal
We would like to look at the DEX Marketing Ladder document and fill out/modify the development paths as needed for the Engineering group.

[Document Link](https://docs.google.com/spreadsheets/d/1yyet37qc5MDnXmSpQM7N8b8lQj5AwSyvbchlPbzR9tg/edit#gid=1731665174)


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @justin.vetter @laurenbarker

Story points: 3.0
Complete Career Dev document

## Goal
Fill out [Career Dev 2022](https://docs.google.com/document/d/1XBcvklVTD32LqrYYPmL8R1-tP6HYgSf9jFYbK-2ULc4/edit?usp=sharing) Document



## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @justin.vetter

Story points: 3.0
ENG: Template for features v1

## Goal
We would like to X which will improve Y as measured by Z.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
*  Mock: https://www.figma.com/file/vwJWOaWyiNzCmqM4gLjvz4/Single-feature-template?node-id=2%3A2266
* [Current Features Page](https://about.gitlab.com/stages-devops-lifecycle/source-code-management/)

## 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: 14.0
ENG: Main Support page

## Goal
We would like to apply a new template the support page.

### Jobs To Be Done
* **Situation**: *The support page does not match are new brand.*
* **Motivation**: *We want to apply a new template.*
* **Outcome**: *So we can be consistent.*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/
* [Figma Redesign](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=388%3A12778)
* [Main Support page copy deck](https://docs.google.com/document/d/14QciHeozCNpNg_hAjXhO9J5I5jf6BXS1lx8OO-YYMKY/edit?usp=sharing)
* 
## 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 @jcolyer 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create new template
- [ ] Apply to support page
- [ ] Apply content
- [ ] Ship to production

## 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
- [x] UX Design
- [x] Engineering

Story points: 10.0
ENG: Getting Started

Work based on https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/344

Designs in https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=241%3A760

## Steps: 

- [x] Create a content model based on Figma design with Lorem Ipsum
- [x] Build out semantics
- [x] Use Slippers components where available to fill in design
- [ ] Create custom components as necessary
- [ ] Identify Slippers gaps, cover them, and open issues in Slippers about them.

Story points: 8.0
ENG: Homepage Lifecycle

## Goal
Create the DevOps lifecycle section of the homepage.
- We're NOT doing the draggable scrub bar this iteration.

The carousel has already been implemented, can re-use that functionality.

Design/Figma: https://www.figma.com/file/hKvIRhVlrgXrB1WcyuDBiQ/Home-Page-Refresh-2022-03-29?node-id=0%3A1

Story points: 6.0
CNT: Net new page - Solutions - Software Delivery Automation

## Goal
We would like to get content for a net new page which will improve our new site infrastructure as measured by increased trials and adoption.

### Jobs To Be Done
* **Situation**: *When a user enters our site... or when they're searching for continuous software compliance...*
* **Motivation**: *they want to learn how to stay compliant with regulations and policies without slowing down software delivery...*
* **Outcome**: *so they can make an informed choice about whether to try or buy GitLab Ultimate.*

## Page(s)
Which page(s) are involved in this request?
- New page needed
- See Existing page for reference: https://about.gitlab.com/solutions/delivery-automation/
- Related: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/delivery-automation/
- [Jam3 design brief](https://docs.google.com/document/d/1lu9-Izo7j1RG22hlxW4SdJyuepxdUGGbd8CCOvPweRs/edit#)
- [Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=69%3A2485)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @supadhyaya 
- [ ] Consulted: @Tinaliseng @KristinaWeis @cblake 
- [ ] Informed: @jhalloran @mpreuss22

## In scope
What is within scope of this request?
- [ ] Net new copy for page

## 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:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 3.0
Enable Free Trial url to accept string parameters

## Goal
This link (https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org) is used in 100,000s of self managed instances. So we need to get that URL working correctly. Right now - it does not. It works without index.html, but we can't update that link on all the self managed instances. So we need to enable it in the Buyer Experience repository. 

### Jobs To Be Done
* **Situation**: The self-managed Epic discovery links to `https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org` which is broken
* **Outcome**: When a user clicks on the epic discovery link from the product, it is properly rendered.



## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org
* https://gitlab.com/gitlab-org/gitlab/-/issues/355655#note_887854257

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @a_akgun 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Enable https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org

## Out of scope
What is out of scope and not part of this iteration?

- slipers UI or www-gitlab-com work

## 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