giseldo/neodataset huggingface dataset:
Enable anchor links as source for redirects

## Goal
We would like to enable anchor links to be the `source` for redirects. 

We discovered this functionality didn't work when implementing redirects for the support pages [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/116174#note_1215292915). 

Another example is [this one](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/redirects.yml#L1302) which also doesn't work.

```yaml
- sources:
  - /handbook/finance/procurement/#prior-to-contacting-procurement
  - /handbook/finance/procurement/#prior-to-contacting-procurement/
  - /handbook/finance/procurement/prior-to-contacting-procurement/
  - /handbook/finance/procurement/prior-to-contacting-procurement
  target: /handbook/finance/procurement/vendor-selection-process/
  comp_op: '='
``` 

#### Jobs To Be Done
* **Situation**: *We wan't to enable anchor links to be the source for redirects*
* **Motivation**: *We want to redirect users to the correct place*
* **Outcome**: *So we can get them to the right place*

#### 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.


## 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?

- [ ] AR for Fastly
- [ ] Research Fastly redirect strategy
- [ ] Determine how to implement anchor links as the `source`
- [ ] Implement functionality and verify it works on existing redirects

## 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: competition/GitLab vs: Add progress bar and link to the maturity page for each stage category

## Goal
Add a progress bar component for each category within each stage on the GitLab vs pages and a supporting link that points to the [maturity page](https://about.gitlab.com/direction/maturity/#manage) for each stage.  

<details><summary>Click to expand image</summary>
![Screen_Shot_2022-12-20_at_11.04.18_AM](/uploads/7f8b75c60e03372b9f342bd90e4d27c4/Screen_Shot_2022-12-20_at_11.04.18_AM.png)
</details>

## Files
Figma designs:
- [GitHub](https://www.figma.com/file/mdjWp1mPBwftLJiSQwJa84/DevOps-Comparison-MVC3?node-id=1107%3A42156&t=XYDd8m7DX5j2UQs0-1) (all stages)
- [Jira](https://www.figma.com/file/mdjWp1mPBwftLJiSQwJa84/DevOps-Comparison-MVC3?node-id=1198%3A44683&t=XYDd8m7DX5j2UQs0-1) (single stage)

- [Document](https://docs.google.com/spreadsheets/d/1azy6CIqgN2v4GBGsXWt7Z84eIc-YPbN7x0rssQTYvhU/edit#gid=0) containing progress bar ratings - connect with @jkempton for any questions about this doc.


**Does anyone in leadership have eyes on this project?**
- [x]  Yes `@sytses` , `@dsteer` 
- [ ]  No


## Page(s)
Which page(s) are involved in this request?
* All `GitLab vs` pages

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jkempton 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: @justin.vetter @fqureshi 

## In scope
What is within scope of this request?

- [ ] Add the progress bar block under the heading for each category within the stage.
- [ ] Add a link to the respective maturity page for each stage. Example: [#plan](https://about.gitlab.com/direction/maturity/#plan), [#create](https://about.gitlab.com/direction/maturity/#create)

## 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] Update text on blog homepage

## Goal
We would like to update the text under the subscribe sign-up

Change `twice-weekly` to `twice-monthly`

![CleanShot_2022-12-19_at_16.54.13](/uploads/866bdc2c0e6df81cdc4b0f84660c8aa6/CleanShot_2022-12-19_at_16.54.13.jpg)


#### 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: `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`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`


**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?
* `[Blog homepage](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 text
- [ ] 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] Bug Fix blog homepage

## Goal
We would like to squash any bugs on the blog homepage refresh

#### 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?**
- [x]  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`
- [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 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`
- [x] No

## 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: `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
- [x] Engineering

Story points: 3.0
[ENG] Remove Confetti from blog posts

## Goal
We would like to remove the confetti from the blog post to stay more on current brand

![CleanShot_2022-12-19_at_10.25.40](/uploads/5fa8c3824dd403b5899f12ed2daf72e4/CleanShot_2022-12-19_at_10.25.40.jpg)

#### 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 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?
* `All blog posts`

## 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?

- [ ] Remove confetti from blog posts
- [ ] 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: Competition / GitLab vs / UX update GA link data attributes

## Goal
There's links within the Markdown that don't have `data-ga-name` and `data-ga-location` attributes. Add inline attributes and component support for all link type content. 

#### 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: 3.0
UX: MVC3: Nav AB test plan

## Goal
We would like to collect feedback on the [latest nav design](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1549#note_1151726453). 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?

- [ ] 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: 5.0
[ENG] Vs pages accessibility

## Goal
We would like to improve accessibility on the Vs. page templates.
- [ ] Making the tab controls accessible
- [ ] Adding alt text to progress bars


## Page(s)
Which page(s) are involved in this request?
* Vs page templates

## 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
Create blogpost vue template in new blog repository

## Goal
We would like to create a bare bones blog post template that we can iterate from and apply our design system to. This template should be applied to the few dummy blog posts that exist in our new repository and be displayed on localhost. 

## In scope
What is within scope of this request?

- [ ] Create blog post template file
- [ ] Have this template applied to a blog post ( can be loriom ipsum ) that exists in the repository

Story points: 2.0
Create new blog repository

## Goal
We would like to create a new project in the Digital Experience group for The Blog.

https://gitlab.com/gitlab-com/marketing/digital-experience 

#### Jobs To Be Done
* **Situation**: *When user navigates to our subgroup, there is a project for The Blog.*
* **Motivation**: *We want to create a blank repository the the team the collaborate on*
* **Outcome**: *So we can have team members contribute*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @lduggan 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create blank project in Digital Experience group
- [ ] Ensure DEX team members have access to project (let's use same user levels as Buyer Experience) 
- [ ] 1st iteration of [project settings ](https://docs.gitlab.com/ee/user/project/settings/) 

## 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
Investigate using Nuxt as a tool for blog repository

## Goal
We would like to gather documentation and resources for using Nuxt for a blog. 

#### Jobs To Be Done
* **Situation**: *We wan't to gather links to docs, blog articles, and example projects for using Nuxt to generate a blog.*
* **Motivation**: *We want to make sure Nuxt can be used for a blog and have resources ready for our engineers to look at.*

---- List of Resources ----

1.

Story points: 2.0
Remove Slippers source code from navigation

## Goal
If you look at our /dist html files the navigation includes the full Slippers package, not minified. It's affecting our page load times and our dom size.

We'll need to fix this for www-gitlab-com navigation as well (if it's an issue)

#### 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: Affects page load times, SEO scores
- [ ]  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 @mpreuss22 
- [ ]  No

**How do we measure success?**
 - Smaller DOM size

## Page(s)
Which page(s) are involved in this request?
* All Buyer Experience pages

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ndubord 
- [ ] Consulted: @laurenbarker @justin.vetter 
- [ ] Informed: Everyone, post update to BE slack 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: 5.0
ENG: Pricing/licensing-faq Refresh

## Goal
The /licensing-faq page is a feeder page into the /pricing/ page and currently looks like a handbook page. There is an opportunity to improve this page to be more conversion-focused. We would like to redesign /pricing/licensing-faq/ which will improve user experience. 

### Notes
There is currently no slippers component for the accordion. We would like to have this page updated using a BE accordion component now and we will iterate to the slippers component in Q4

#### Jobs To Be Done
* **Situation**: *When users land on the licensing page*
* **Motivation**: *We want to provide them the information they are looking for*
* **Outcome**: *So we can eventually lead them to a free trial *

## Workin Files
- [ ] [Figma design](https://www.figma.com/file/I1RYrS4BtJEvS1rpRJvgBa/Licensing-FAQ-MVC1?node-id=53%3A5419)


**If this is urgent, what is the business need for the urgency?**
- [X]  Yes: There is a gap to plan in free trial conversions. 
- [ ]  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?**
 - Initial MVC for the licensing page that aligns to the new redesign 

**How do we measure success?**
 - Increased session duration 
 - Increased clicks to free trial

**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?
* `[Licensing Page](https://about.gitlab.com/pricing/licensing-faq/)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @fqureshi 
- [ ] Consulted: @jhalloran @justin.vetter @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?
- [ ] Refresh Licensing FAQ page in BE
- [ ] Remove old page from www

## Not in scope
- [ ] 

## 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: 6.0
ENG: Update to CE v. EE install page

## Goal
We would like to update the UX for the CE v EE install page

#### Jobs To Be Done
* **Situation**: *When a user goes needs to make a decision between the community or enterprise edition of GitLab...*
* **Motivation**: *We want to guide them to the best option for their needs...*
* **Outcome**: *So we can provide them the best result for their business.*

## Working Files

- [ ] [Figma designs](https://www.figma.com/file/SbTRvhGGPqSVJzuYTPf500/CE-v-EE-MVC3?node-id=17%3A1030)

#### 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 deploy updated page`

**How do we measure success?**
 - `Please describe how success will be measured`

**What analytics / data will we need to set-up?**
- [x] Yes: `Reach out to Dennis regarding what analytics to add to button clicks`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* [CE v EE](https://about.gitlab.com/install/ce-or-ee/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @takamine-ext 
- [ ] Consulted: @fqureshi @jhalloran @justin.vetter `@dennischarukulvanich` 
- [ ] 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: 4.0
ENG: Left side anchor nav / colour change to the hover state

## Goal
We would like to add a colour change to the hover state to our left-side anchor nav (used on /solution pages) which will improve engagement.

See [prototype](https://www.figma.com/proto/2Mp2QTbudj3q9q8zN0z9h7/hover-test?page-id=0%3A1&node-id=1%3A986&viewport=768%2C840%2C0.17&scaling=min-zoom)

![Screen_Shot_2022-10-14_at_3.31.44_PM](/uploads/fc7bc98a196644ecb62fd108a822dff0/Screen_Shot_2022-10-14_at_3.31.44_PM.png)



## Page(s)
Which page(s) are involved in this request?
* All instances

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: @justin.vetter 

## In scope
What is within scope of this request?

- [ ] Add a hover state: colour change = `$slp/color/text/300` `#171321`

## 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