giseldo/neodataset huggingface dataset:
ENG: Automatic version bumping, changelog creation and tag creation

## Goal
We would like to automate the project version bumping and the tag creation following [semantic-versioning](https://semver.org/)

#### Jobs To Be Done
* **Situation**: When we merge a new feature/fix/change into the `main` branch
* **Motivation**: We want to raise the version of the project and create a tag with this new version (i.e v1.0.0)
* **Outcome**: So we can have a consistent project tagging and versioning and also be able to update the changelog file

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [X]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [X]  Yes @laurenbarker 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - Bump the package.json version and create a tag with the new version automatically

**How do we measure success?**
 - When merging a new change in the `main` branch, a new tag with the new version of the project is created automatically

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @laurenbarker, @lduggan 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] A script to raise the version of the package.json file
- [ ] A GitLab Job to create a new tag based on the package.json version (Only in the main branch/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:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering

Story points: 5.0
ENG: Analysts MVC 2

## Goal
We would like to update the Analysts page to include updates.

[Design for the Analyst page MVC2](https://www.figma.com/file/7Q7VE1wjbM8iGxloOP0u9b/Analysts?node-id=631%3A6262) is ready!

Updates include:

* copy in hero
* feature cards to have images and updated layout; content needs to be editable for stakeholders
* add peer review section
* remove "Reports mentioning GitLab" section
* add "Market research of interest" section; content needs to be editable for stakeholders
* change header size and padding for "Categories" section, and put lists in accordions (closed on default)
* update "Contacts" section

## Page(s)
Which page(s) are involved in this request?
- [Analysts](https://about.gitlab.com/analysts/) 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 
- [ ] Consulted: @ctsang-ext @rragozzine 
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?

- [ ] Engineering

## 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: 2.0
Tracking: Home Page Content Block

## Goal
Please add the following data attributes to the Home page content block on the `<a>` level. 

<img src="/uploads/f86f2748327bedd22187c68b3c5e0ad9/Screen_Shot_2022-11-03_at_11.42.27_AM.png" width="600">

- data-ga-name="name of card" (e.g. get started, dev survey, roi calculator)
- data-ga-location="home content block"

![Screen_Shot_2022-11-03_at_2.53.48_PM](/uploads/ce2c9f55cd8bfbd53d3248b2dbf9e4cc/Screen_Shot_2022-11-03_at_2.53.48_PM.png)

- data-ga-name="name of case study" (e.g. ubs)
- data-ga-location="home case studies"

## Page(s)
Which page(s) are involved in this request?
* 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: @fqureshi @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
Move away from the SideNavigationVariant being absolutely positioned

## Goal

Right now, the Side Navigation component does not take up any space in the DOM. We would like to change this to a flex container that takes up a certain amount of columns in `SlpRow`.

WIP Proposal
```vue
<SideNavParent>
  <SideNav>
    // side nav content here
  </SideNav>
  <SideNavChildren>
    // children of side nav
  </SideNavChildren>
</SideNavParent>
```
## In Scope
Cleaning up the styles will be a lot of work across various templates.

## 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`

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 html validator to mitigate hydration errors

## Goal
We are starting to wrap more components in <client-only> tags to force client side rendering, as a solution for invalid html markup. The [nuxt/html-validator library](https://html-validator.nuxtjs.org/) is a dev tool to point out potential invalid html markup. The goal is to implement this tool in dev mode only, to catch common hydration errors. 

#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`

## 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

## 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: 2.0
Why Pricing Pages - Safari - Mobile Breakpoint + Sidebar

## Goal
We would like to ensure the sidebar navigation behaves correctly on smaller Safari viewports. Users need to be able to read the main content.

### Describe the Bug
In safari, when you make the viewport narrower than 1024px the nav switches to the mobile version. On the Why Ultimate and Why Premium pricing pages, there's a sidebar navigation that floats out from the right side and begins to overlap the content. As the screen gets smaller, the conent becomes unreadable because the sidebar nav is laying ontop. 

![Screen_Shot_2022-11-03_at_9.09.04_AM](/uploads/f071a6d5fa257667f06405114a3e3740/Screen_Shot_2022-11-03_at_9.09.04_AM.png)

I discovered this while QA testing the [2.0 navigation MR for BE](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1271). These pages are now linked to directly from the footer. 

But since this is a current bug in production, it's not blocking to the release of the 2.0 nav.

This is probably the case on other pages using that sidebar component.

### What's my browser? 
https://www.whatsmybrowser.org/b/GSXCV

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/premium/
* https://about.gitlab.com/pricing/ultimate/

## 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: Make touch target full-width on mobile for the tertiary button on the Take a Spin CTA component

## Goal
We would like the tertiary button of the CTA above the footer to have a full-width touch-target on mobile, which will increase users' ability to click.

![Screen_Shot_2022-11-02_at_9.09.14_AM](/uploads/00f5076b07844a630974020c8abecf90/Screen_Shot_2022-11-02_at_9.09.14_AM.png)

## Page(s)
Which page(s) are involved in this request?
* All instances in Buyers Experience

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: @jhalloran @ctsang-ext @justin.vetter 

## In scope
What is within scope of this request?

- [ ] Activate full-width touch target on mobile for the tertiary button on the `Take a Spin` CTA component

![Screen_Shot_2022-11-02_at_9.08.25_AM](/uploads/636429a99f2d69bb506c58cfb6d16853/Screen_Shot_2022-11-02_at_9.08.25_AM.png)


## 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: Update pricing page title copy to use Slippers style

## Goal
We would like to update the title styles on the pricing page to use Slippers and not a custom style

Related to this [MR thread](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/merge_requests/263#note_1156377325)

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `To make sure the page uses our Slippers styled fonts`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* [Pricing](https://about.gitlab.com/pricing)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @jhalloran @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Update pricing page hero/title styles
- [ ] 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
"DevSecOps Platform" language across marketing site

## Goal
We would like to get clarity from stakeholders on "DevSecOps Platform" language across marketing site.

This issue was created from the conversation here: https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/113#note_1153230956 

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: We've implemented this language in the primary navigation and footer. This should be aligned with other marketing language on the site.
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes @fqureshi 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - clarity from stakeholders if we'd like to make this a sweeping change across the site or if we're testing this out from a branding POV.

**How do we measure success?**
 - We understand the scope of this change 

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* Buyer Experience

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: @fqureshi 
- [ ] Consulted: @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] clarity from stakeholders
- [ ] define scope of change and task

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [x] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 1.0
ENG: Update /security/ with new branding - MVC 1

## Goal
We would like to update /security/ to the new branding guidelines 

### Files

* [Figma](https://www.figma.com/file/K2G9h2iuQ4qNutyLSUOkOZ/Trust-Center?node-id=0%3A1)

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [X]  Yes: Trust centre will be linked from the [changes on the homepage](https://www.figma.com/proto/tDxUnSR5vdHHIVZjOW6nt7/Navigation-Research-and-Refresh?page-id=848%3A21756&node-id=848%3A26454&viewport=949%2C766%2C0.1&scaling=scale-down-width&starting-point-node-id=848%3A22168) under the 'Information Security' link
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [X]  Yes: Sid, Ashley
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - new branding

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No

## Page(s)
Which page(s) are involved in this request?
* [Security](https://about.gitlab.com/security/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 
- [ ] Consulted: @justin.vetter @fqureshi @Tinaliseng 
- [ ] Informed: `@mpreuss22`

## In scope
What is within scope of this request?

- [ ] Refresh /security page
- [ ] Remove /security page from www repo

## 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
Partner Program Overview - Enable user to dive deeper into pages

## Goal
We would like to add links to enable users to search existing partners.

### Describe the Bug
https://about.gitlab.com/partners/benefits/
- [x] See the GitLab Channel Partner Handbook should link to https://about.gitlab.com/partners/technology-partners/integrate/
- [x] Alliance Program for Cloud and Technology Partners - needs button "Find an Alliance Partner", link to https://about.gitlab.com/partners/technology-partners/  

https://about.gitlab.com/partners/
- [x]  Fix title - Cloud, Platform and Technology Alliance Partners
- [x]  Cloud Parter card, link to https://about.gitlab.com/partners/technology-partners/#cloud-partners
- [x]  Cloud Platform Partner card, link to https://about.gitlab.com/partners/technology-partners/#platform-partner
- [x]  Cloud Technology Partner card, link to https://about.gitlab.com/partners/technology-partners/#technology-partners
![Screen_Shot_2022-10-31_at_2.37.03_PM](/uploads/e36be0030721ca86720e1d9065a7b465/Screen_Shot_2022-10-31_at_2.37.03_PM.png)
- [ ]  Fix bottom CTA does not appear at the [bottom of page](https://about.gitlab.com/Partners/). 
![image](/uploads/4a00e5252bdbcdc2f90380d45695846f/image.png)

https://about.gitlab.com/partners/technology-partners
- [ ]  Create Platform Partner category @ https://about.gitlab.com/partners/technology-partners/#platform-partner
- [ ]  Create Technology Partner category @https://about.gitlab.com/partners/technology-partners/#technology-partner

For all Partner pages:
- [ ]  Ensure [we are using all Slippers font styles](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/236#note_1157877682).

## 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
MLHF - Slippers Issue Creation

Taking some time, once Conversion group priorities are complete, to create additional issues in our Slippers project for our MLHF group to work on.

This block of time will include [creating and refining issues](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/?label_name%5B%5D=dex-mlhf) in addition to updating the [group handbook page](https://about.gitlab.com/handbook/marketing/digital-experience/major-league-hacking-fellows/).

Story points: 2.0
Purge Swiftype Cache

## Goal
We would like to have only english results return on our Swiftype search. 

When the POC was enabled, German, French, and Japanese translations showing up in our search.

#### Jobs To Be Done
* **Situation**: *When a user searches for something, 1 english results returns for each match*
* **Motivation**: *We want to have the search work*


#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: `search is cluttered`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [x]  Yes @laurenbarker 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is XYZ`

**How do we measure success?**
 - `German, French, and Japanese translations do not return in search`


## Page(s)
Which page(s) are involved in this request?
* `https://app.swiftype.com/engines/about-dot-gitlab-dot-com/domains?observe_changes=true`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: @laurenbarker 
- [ ] Consulted: @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Recrawl for about.gitlab.com/handbook search engine - 2,511 pages
- [x] Recrawl for  about.gitlab.com search engine - 24,620 pages
- [ ] Recrawl for  about.gitlab.com/blog search engine - 1,788 pages 

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
UX: MVC2: Nav Iterations

## Goal
We would like to collect feedback on the 2.0.0 navigation. We'll use that feedback to define the scope of changes in this issue to the Nav and create a spec for ENG.

## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [X] DRI: @mpreuss22 
- [X] Consulted: @ctsang-ext @Tinaliseng @fqureshi @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] swapping By industry with By company size so we can display Enterprise and SMB higher up giving them a more predominant position in the menu.
- [ ] adding 'View plans' with a link to pricing as pricing is the most visited page after /solutions on the customer's journey.
- [ ] More TBD

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering

Story points: 2.0