giseldo/neodataset huggingface dataset:
Need to delete two out-of-date blog templates

## Goal
The blog team needs the following blog templates deleted because they are no longer in use: blog-PYB-post.md
blog-feature-unfiltered-post.md 

No rush...

#### Jobs To Be Done
* **Situation**: *Not urgent*
* **Motivation**: *Streamline our templates and delete old ones to eliminate confusion*
* **Outcome**: *Collaborate better with blog contributors*

#### 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`
- [x] No: `Please describe why` - just an old template deletion for blogs

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `Streamlined repo for blog templates`

**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?
* `[Page Title](URL)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: `@sgittlen`
- [ ] 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
Bug: Fix pricing/feature-comparison header height

## Goal

FeatureComparison header is not correctly aligned with the navigation menu

![image](/uploads/f37730e90112acdb28b2b7edbf5b376a/image.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
- [X] Engineering

Story points: 1.0
Add GLM parameters to conversion CTAs

## Goal
We would like add GLM parameters to the following CTAs: 

TBD 

1. Related https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/issues/42 
1. Related https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/issues/68

#### 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: 0.0
Ability to recognize logged in GitLab user

## Goal
We would like to recognize when a user is logged into GitLab on the marketing site. 

The goal with this issue is to

1. Investigate how we could do this
1. Start a thread for each 'how' that gives a high-level overview, scope, & risks. We'll discuss as a team in each thread.
1. Chose a strategy. We'll determine next steps from there.

**We'll need to schedule these changes in the GDK to be before or after _March 7th_ because of the [Hard Production Change Lock](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#production-change-lock-pcl) where the GDK will be updated to Ruby 3**

Story points: 6.0
Reclassification of technology partners

## Goal
We would like to do a reclassification of technology partners on https://about.gitlab.com/partners/technology-partners/ .

List of partners to remove to be provided by @mlebeau @mjoscelyn 

#### Jobs To Be Done
* **Situation**: *When a user visits our technology partners page, technology partners are accurately classified.*
* **Motivation**: *We want to be compliant.*

#### 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.

## 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 @mlebeau @mjoscelyn 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Reclassification of [apps.yml](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/apps.yml)


## 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
Removing partners without TPAs

## Goal
We would like to removing partners without signed agreements from the https://about.gitlab.com/partners/technology-partners/ .

List of partners to remove to be provided by @mlebeau @mjoscelyn 

#### Jobs To Be Done
* **Situation**: *When a user visits our technology partners page, everyone displayed has a signed agreement with GitLab.*
* **Motivation**: *We want to be compliant.*

#### 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 have partners there don't have signed agreements`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

## 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 @mlebeau @mjoscelyn 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove partners from [apps.yml](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/apps.yml)
- [ ] 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: 1.0
Updates to Search

## Goal
We would like to update the Search. There were some features that were left off for MVC1, but we'd like to add them back to enhance the experience. 

#### Please provide more information related to this request
| Comment | In design | In production |
| ------ | ------ | ------ |
| 1. Update autocomplete to be more intelligent. It should not just serve up the suggested articles, but autocomplete/autocorrect what the user is typing. | ![image](/uploads/24c35df65235794f5306ad3231816b52/image.png) | ![image](/uploads/4de35ad8ad287ad402ab00ab3b2576dc/image.png) |
| 2. Filter by checkboxes (instead of radio buttons) | ![image](/uploads/0710617b711bd4193cf156ec0157692b/image.png) | ![image](/uploads/53d52b9dda147e7bfdfc292304b2a67a/image.png) |
| 3. Make the search results it’s own page so users can go back to their search after they’ve selected a result. Currently, if a user selects a result, they will have to go back to the page they were on before the search. |  | See [loom](https://www.loom.com/share/d2d25d7c14ca4e3c82c87e6998d428a3) |
| 4. Fix the search results so that they show the sources accurately (currently they all show as “About” even if it’s a blog page) | ![image](/uploads/e97898ac4ba11a1eacc303b9ec370e57/image.png) | ![image](/uploads/5298c8b8ba72a65747ce3fa1833f60e1/image.png) |

**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: 5.0
[ENG] Update Trending posts -> Recent posts

## Goal
We would like to update the Trending Posts text to Recent Posts on the blog home page


![CleanShot_2023-01-26_at_10.49.00](/uploads/baf8e178e9e6ee6d1c41697fa699ebfa/CleanShot_2023-01-26_at_10.49.00.jpg)


## 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?

- [ ] Update copy
- [ ] 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: 1.0
[ENG] Case Studies component Learn more styles

## Goal
We would like to update the styles to make sure `Learn more >` is on a single line


![CleanShot_2023-01-26_at_09.54.33](/uploads/05d9ce9cccfec75d9713ffd4f5a87b48/CleanShot_2023-01-26_at_09.54.33.jpg)

### Figma
[Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=5581%3A13406&t=bPIbHkFHDvFGxnHH-0)

#### 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

## Page(s)
Which page(s) are involved in this request?
* Pages with Case Studies component
* ex: [Enterprise](https://about.gitlab.com/enterprise/)

## 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?

- [ ] Fix Styling
- [ ] 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: 1.0
[ENG] Small business page components have extra spacing from the sidenav

## Goal
We would like to remove the extra space that the components are using in the small business page

#### Please provide more information related to this request
this spacing was used before the sidenav was refactored to avoid overlap, it is not necessary anymore

**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`
- [X] No: `Please describe why`



**How do we measure success?**
 - No extra spacing

**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?
* https://about.gitlab.com/small-business/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpenagos-ext 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Remove spacing

## 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] BUG random quotation mark on /features/continuous-integration/

## Bug
There is a random `"` on the left above the Resources component that needs to be removed

![CleanShot_2023-01-24_at_13.17.40](/uploads/a4c681ad1c4ada903f118176ea823efd/CleanShot_2023-01-24_at_13.17.40.jpg)



## Page(s)
Which page(s) are involved in this request?
* [Continous Integration](https://about.gitlab.com/features/continuous-integration/)

## 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?

- [ ] Remove quotation mark
- [ ] 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: 1.0
[ENG] Bug horizontal scroll on /solutions & /features page

## Bug
We are seeing a horizontal scroll and white space to the right of some components on the /solutions & /features pages

![CleanShot_2023-01-23_at_15.17.30](/uploads/c04dc6aa5a4a14b45abcc35775d423f8/CleanShot_2023-01-23_at_15.17.30.jpg)

[Loom video](https://www.loom.com/share/3ffc8058df37444ab738a9c2d5fa2d00)

example pages:
- https://about.gitlab.com/features/continuous-integration/
- https://about.gitlab.com/small-business/#case-studies
- https://about.gitlab.com/solutions/dev-sec-ops

## Browsers with issues
Chrome & Firefox

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Fix whitespace and horizontal scroll issue
- [ ] 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] Add JetBrains Mono type to our font stack

## Goal
We would like to add JetBrains Mono Regular to our font stack to stay in sync with the product team.

![CleanShot_2023-01-23_at_13.26.47](/uploads/469f8872cde520104f928dba45f4ff55/CleanShot_2023-01-23_at_13.26.47.jpg)

![CleanShot_2023-01-23_at_13.45.09](/uploads/6440613b2767b8203362e912d3db0740/CleanShot_2023-01-23_at_13.45.09.jpg)

This is a mono type font that will replace all code examples on our site example: [install](https://about.gitlab.com/install/#centos-7)
this font should be used in all <code> blocks


#### 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`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is to add the font to our site and update <code> styles`


**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: `GitLab Handle`
- [ ] Consulted: @jhalloran @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add fonts and update 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: 1.0
Netlify CMS authentication for only members of repository

## Goal
For only members of a public GitLab repository to be able to access the Netlify CMS admin. 

For our use case, this means `about.gitlab.com/admin `

Currently anyone with a GitLab account can login to the admin. We'd like to restrict access to www-gitlab-com project members. 

Here's [the slack thread in #marketing](https://gitlab.slack.com/archives/C0AKZRSQ5/p1674306562076699) that spawned this issue.

Although any account can log in, their actions are still restricted based on their permissions. For example users could see "draft posts" which are just public MRs - already visible via gitlab.com's normal UI - but they wouldn't be able to merge without Maintainer permissions. **There is no current security risk**, just confusing behavior.

#### Jobs To Be Done
* **Situation**: *When anyone tries to login to the `about.gitlab.com/admin`, only those who are project members of [www-gitlab-com](https://gitlab.com/gitlab-com/www-gitlab-com) should be able to authenticate successfully.*
* **Motivation**: *We want to have the admin only available to GitLab team members.*
* **Outcome**: *So that non team-members don't have access to an "admin" site.*

#### 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: `SIRT got informed that it is possible to log into the https://about.gitlab.com/admin interface with ANY GitLab account`
- [ ]  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`

## Page(s)
Which page(s) are involved in this request?
* `about.gitlab.com/admin`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @jroppelt 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Making an open source contribution to the [GitLab Netlify CMS backend](https://github.com/netlify/netlify-cms/tree/master/packages/netlify-cms-backend-gitlab)
- [ ] Bumping the netlify-cms.js package [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/admin/index.html#L12)
- [ ] Verifying on 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: 3.0