giseldo/neodataset huggingface dataset:
Release: Remove Launch Darkly Flag for A/B Test - Remove 'register' from the nav

## Goal
We would like to remove the A/B test and flag switching between our navigation variations.  

This issue is for removing the A/B test and displaying the winner 100%.

### Jobs To Be Done
* **Situation**: *When a user visits our site, 100% get winning variant A*
* **Motivation**: *We want to display the variant that led to more sign ups*
* **Outcome**: *So we can get users to try GitLab*

## Page(s)
Which page(s) are involved in this request?
* Buyer Experience repository

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @miraclebanks 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Removing the feature flag in Launch Darkly
- [ ] Removing feature flag to switch between variation A and B of the navigation in Buyer Experience
- [ ] Removing the loosing nav variation from the navigation repository
- [ ] Notifying this [parent issue that test is over](https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/1)
- [ ] Updating handbook with test winner https://about.gitlab.com/handbook/marketing/digital-experience/engineering-ab-tests/ 

## 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
Release:  Launch Darkly Flag for A/B Test - Remove 'register' from the nav

## Goal
We would like to implement a Launch Darkly feature flag to run the [A/B test proposed here](https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/1).

This A/B test will do a 50/50 split between two nav variations - one with the register link and one with out. 

This issue is for tracking the work required to build this feature flag switch into the Buyer Experience repository and turning it on.

[A/B Test MR](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1006)
[Handbook Page Update](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/111314)

### Jobs To Be Done
* **Situation**: *When a user visits our site, 50% get variant A of the nav and 50% get variant B*
* **Motivation**: *We want to gather data on register link and effect to other CTAs*
* **Outcome**: *So we can get users to try GitLab*

## Page(s)
Which page(s) are involved in this request?
* Buyer Experience repository

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @miraclebanks 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Create feature flag in Launch Darkly
- [x] User feature flag to switch between variation A and B of the navigation
- [x] Turning on the A/B test
- [x] Notifying this [parent issue that test is running](https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/1)
- [x] Updating handbook with correct test dates https://about.gitlab.com/handbook/marketing/digital-experience/engineering-ab-tests/ 

## 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
Address v::deep errors on build

## Goal
We would like to fix the all the `WARN  [@vue/compiler-sfc] ::v-deep ....`  errors when running the Buyer Experience project. This warning is slowing down our build and making it difficult to find errors because there are so many v-deep warnings.

### Jobs To Be Done
* **Situation**: *When the site is built locally or for production, we don't see any v::deep warnings in the console*
* **Motivation**: *We want to keep our build clean and manageable for reading errors*
* **Outcome**: *So we can be efficient when fixing build issues*

## Page(s)
Which page(s) are involved in this request?
* building the site locally or for production

## 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?

- [ ] Fix all `v-deep` warnings for `yarn dev`
- [ ] Fix all `v-deep` warnings for `yarn build`

## 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: Find Alliance - Add new icons

## Goal

Change the icons in the page filters to the ones in the [Figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=254%3A8165) file after new Slippers release

## Page(s)
Which page(s) are involved in this request?
* `[Find a Alliance](https://about.gitlab.com)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @laurenbarker @ctsang-ext 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Change the icons after a new Slippers version with updated icons 

## 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 Alliance Partner Page - Feedback items

## Goal
Solve feedback items on the `Find Alliance Partners` page mentioned [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/982#note_1095473050)

| Comment | In review app | In design |
| ------ | ------ | ------ |
| Can we make sure to show all the body text? | ![image](/uploads/91e9e8f48832341ab7ad97350ce7c9d3/image.png) | c![image](/uploads/eee2d4cc8c359e23750fb4fd8bc5159e/image.png) |
| Under Featured Partners", let's remove the extra card (digital ocean) for now | ![image](/uploads/2b645f3cc2d637d1aea66b669cad6737/image.png) | none |
| Is it possible to move the caret/arrow closer to the text for the double lined links? | ![image](/uploads/bab883ad3b479a54a94e3645f3291db0/image.png) | none |
| Can we reorder the partner list so that it matches the button list? So instead of starting with "Cloud partners," we start with "API Clients"? | ![image](/uploads/93c09a84066dd5cdcea15d2672875a8c/image.png) | ![image](/uploads/61367879a6a37f19a4964fa2e88319e9/image.png)![image](/uploads/fb252b410c2b1be61c885a20df094d56/image.png) |
| Also can we add headers so it's easier to skim as someone scrolls down? | ![image](/uploads/6d2854f9025a371b9f03bb0b039e17d1/image.png) | ![image](/uploads/9c52f4867faaba028103219130f8e81a/image.png) |
| Fix all horizontal icons so their readable | ![Screen_Shot_2022-09-09_at_3.04.15_PM](/uploads/63cf4f49aaf2dfff593bddf523293c37/Screen_Shot_2022-09-09_at_3.04.15_PM.png) |

## Page(s)
Which page(s) are involved in this request?
* `[Find Alliance](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)

- [x] DRI: @jariasc-ext 
- [x] Consulted: @laurenbarker, @ctsang-ext 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Fix feedback items from [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/982#note_1095473050)

## 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
UX: Localization Language Selector

## Goal
We would like to have a language selector to allow our users to access the website in multiple languages.

### Jobs To Be Done
* **Situation**: *When a user visits a page that has other languages available, a drop down displays the offers choices between them*
* **Motivation**: *We want to communicate to users that a page is available in different laungauges*
* **Outcome**: *So we can increase the effectiveness of our marketing webist*

## Page(s)
Which page(s) are involved in this request?
* [Homepage](about.gitlab.com)
* [Why Gitlab] (https://about.gitlab.com/why-gitlab/)
* [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: @ctsang-ext 
- [ ] Consulted: @Tinaliseng @lduggan 
- [ ] Informed: @fqureshi @laurenbarker 

## In scope
What is within scope of this request?

- [ ] A UX design for the language selector

## 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
ENG: Update To top button on Learn page

## Goal
We need to update the button on the [/learn](https://about.gitlab.com/learn) page as well (remove border & update the purple to 900) per this Slippers [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/202)


## Page(s)
Which page(s) are involved in this request?
* `[Learn](https://about.gitlab.com/learn)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ndubord 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] update the button
- [ ] 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: KubeCon NA 2022 LP / Capture feedback

## Goal
Opening this issue to capture feedback for MVC 1 of the KubeCon NA 2022 LP.

## Page(s)
Which page(s) are involved in this request?
* Not yet deployed

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jgarc `@amandawshen` 
- [ ] Informed: @justin.vetter 


## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 1.0
ENG: Nav | Add DevSecOps and Agile Delivery in the Solutions section of the Nav

## Goal
We would like to DevSecOps and Agile Delivery solution pages under the solutions section of the Nav.

### Jobs To Be Done
* **Situation**: *When a user is looking for a solution some of our toped searched pages are not in the nav*
* **Motivation**: *We want to help the user finding the content they are searching for*
* **Outcome**: *So we can give users an easier path to solutions content*

## Page(s)
Which page(s) are involved in this request?
* [DevSecOps](https://about.gitlab.com/solutions/dev-sec-ops/)
* [Agile Delivery](https://about.gitlab.com/solutions/agile-delivery/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@Tinaliseng`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Adding links to DevSecOps and Agile Delivery solution pages under the solutions section of the Nav
- [ ] Deliverable 2


## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
ENG: Adding Great Place to Work badge to GitLab careers site

## Goal
We would like to add a section to the GitLab careers site that highlights we are Great Place to Work certified which will provide a proof point about what it's like to work here as measured by the ratio of site visits to applications over time.

This section was designed as part of [this issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1267).

Here's the [figma](https://www.figma.com/file/JhFZCIRo8AoWrLIFDEOtL4/Careers?node-id=7%3A399).

Also dropping a mock for easy reference here: 
![image](/uploads/210bb71f8be0ba5761bb9b501b63088d/image.png)

### Jobs To Be Done
* Design a section for our careers page using an existing design pattern to highlight the attached badge and content provided by the talent brand team.
* The idea here is that we want people who visit our careers site to know that we are a Great Place to Work.
* So, they are more likely to apply for a job if there is an open role that's the right fit.

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/jobs/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker @drogozinski 
- [ ] Informed: Devin to inform People Leadership Group, Ray/Michael to inform marketing as needed

## In scope
What is within scope of this request?

- Designing a small section to highlight our Great Place to Work certified badge and provided copy

- Creating the MR to add that new section seamlessly into the careers site.

- Provided copy: At GitLab, being a great place to work means building a workplace where everyone can contribute and anyone can thrive. We aim to uphold that ideal in every country where we employ GitLab team members.

- Button text: See our employer awards 
- Button link: <https://about.gitlab.com/handbook/people-group/employment-branding/content-library/#awards-and-lists-recognizing-gitlab-as-a-great-place-to-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: 2.0
ENG: Solutions/ devops-platform / update header to updated brand

### Describe the Bug
Update the main header on [solutions/devops-platfomr](https://about.gitlab.com/solutions/devops-platform/) to match the other /solutions heroes ([example](https://about.gitlab.com/solutions/delivery-automation/))

Change this:

![Screen_Shot_2022-09-08_at_10.39.50_AM](/uploads/bfe50fcb09e5a7e1f1c0a747c664be97/Screen_Shot_2022-09-08_at_10.39.50_AM.png)

To this:

![Screen_Shot_2022-09-08_at_10.42.34_AM](/uploads/fa683dbf42badb41c91c405fda0e3a2e/Screen_Shot_2022-09-08_at_10.42.34_AM.png)

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/devops-platform/

## 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: solutions LP / Update "Join GitLab" CTAs

## Goal
Update all instances of "Join GitLab" CTAs on /solutions pages. The wording is off-brand and unclear.

![Screen_Shot_2022-09-08_at_10.24.21_AM](/uploads/3552ef5b2c8394f2a52c1f9d762b946d/Screen_Shot_2022-09-08_at_10.24.21_AM.png)

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/enterprise/
  * **Primary**: `Start your free trial`
  * **Secondary**: `Talk to an expert`
  * ![Screen_Shot_2022-09-08_at_10.32.18_AM](/uploads/7fd6818a6cb8b07c80de62e2a70dfbff/Screen_Shot_2022-09-08_at_10.32.18_AM.png)
* https://about.gitlab.com/solutions/compliance/
* https://about.gitlab.com/solutions/dev-sec-ops/
* https://about.gitlab.com/solutions/agile-delivery/
  * **Primary**: `Start your free trial`
  * **Secondary**: `Learn about pricing`
  * ![Screen_Shot_2022-09-08_at_10.31.53_AM](/uploads/fe9aa69d4d9cb209282e4e4f3e7fb71c/Screen_Shot_2022-09-08_at_10.31.53_AM.png)

cc: @dennischarukulvanich please update the above CTAs if you have other suggestions.

## 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: 2.0
Enable markdown in support copy component - part 2

## Goal
This issue is part two of enabling markdown in the support copy component. 

### 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?
* TBD update list
* 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: @mduque-ext 
- [ ] Consulted: @laurenbarker @jcolyer 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Enable copy markdown support component to be consumed by the support pages
- [ ] Update all content supplied to the support/copy-markdown.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: 1.0
Document approval flow process in handbook

## Goal
We would like to document the marketing site approval process in the handbook. It should include the following: 

- What the process is and why it exists
- The four approval flows, from minor to major change
- What the approval labels are

### Jobs To Be Done
* **Situation**: *When anyone is looking for information on what the approval process is and steps, they refer to our handbook*
* **Motivation**: *We want to create a single source of truth for this process*
* **Outcome**: *So we can communicate it out effectively*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/handbook/marketing/digital-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?

- [ ] Create a new page OR edit an existing handbook page. Your choice - where does this fit in best? 
- [ ] Collaborate on this process with Digital Experience following [GitLab's handbook first documentation strategy](https://about.gitlab.com/company/culture/all-remote/handbook-first-documentation/)
- [ ] Announcement in #whats-happening-at-gitlab channel

## 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
Apply approval flow labels to merge request template for Buyer Experience

## Goal
We would like to iterate on Buyer Experience merge request templates to reflect the approval flow process documented in our handbook.

### Jobs To Be Done
* **Situation**: *When anyone creates a merge request in Buyer Experience, it describes what label to apply for the approval flow process depending on the type of change.*
* **Motivation**: *To ensure the proper stakeholders review a change to the marketing site.*
* **Outcome**: *So we can ensure changes are reviewed.*

## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/.gitlab/merge_request_templates

## 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?

- [ ] Iterated on existing merge request template with instructions on how to apply a approval flow label and which one.

## 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
Partners: Links to 404 pages

## Goal
Partner links to a 404 page: https://about.gitlab.com/partners/technology-partners/
- Microsft Azure
- Oracle Cloud
- Amazee.io 
- etc. 


## 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 
- [ ] Informed: @ctsang-ext 


## 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