giseldo/neodataset huggingface dataset:
Add data attributes to nav sign-in button

## Goal
GA data dropped for the Sign In link click within the header on about.gitlab.com. 
<img src="/uploads/16335cb226181db5785944237e0a38a2/Screen_Shot_2022-03-23_at_11.19.59_AM.png" width="500">


Please add back the `data-nav="login"` attribute to the Sign In button:
<img src="/uploads/0eb3c8f31ebd0d47c871978de1dbb9dd/Screen_Shot_2022-03-23_at_11.09.56_AM.png" width="500">


### Jobs To Be Done
* **Situation**: When users click on the Sign In link
* **Motivation**: We want to place a data-* attribute
* **Outcome**: So we can capture the Sign In click event.


## Page(s)
Which page(s) are involved in this request?
* Header on all about.gitlab.com pages


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dennischarukulvanich 
- [ ] Consulted: @mpreuss22 
- [ ] Informed: @laurenbarker 


## 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: 1.0
Follow-up from "Removal of 155 stale images"

As we remove pages from the `www-gitlab-com`, assets are becoming obsolete. Lets write a script that removes unused assets from the repository. This will have compounding beneficial effects - every pipeline is faster, cloning the repository is faster, and the size the repository becomes smaller.

The first iteration of this script [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101054). Unfortunately, that script takes too long to run through the `www-gitlab-com` repository. For the next iteration of this script, we'll create an array of image filenames and search the repository once. This should reduce the amount of time it takes for the script to complete.

## In scope
What is within scope of this request?

- [x] Iterate on https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/scripts/cleanup-delete-stale-images.sh  script that removes unused assets from the www-gitlab-com repository
- [x] Add script to buyer experience repository


--- 

`@tywilliams` outlined a good strategy to make this faster in the following discussion from gitlab-com/www-gitlab-com!101054:

- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101054#note_882910627):  (+3 comments)

    > @tywilliams Got any tips for making this script faster? 
    > 
    > It seems to go slow due to the size of the repository. It only found 9 images in 1 hour before I had to quit it since I'm about to pack up for the day. 
    > 
    > Should I just run it overnight and keep the computer from sleeping?

Story points: 2.0
Make sure all links in Buyer Experience are relative links

This is a follow up to a request from @mpreuss22 in [Slack](https://gitlab.slack.com/archives/CN8AVSFEY/p1647985950478389?thread_ts=1647985257.315629&cid=CN8AVSFEY):

> is there a way to dynamically set all links to go to pages within this experience? Currently they link out to the live site.

Michael is referring to the review app at [https://refresh.about.gitlab-review.app/](https://refresh.about.gitlab-review.app/). But more generally, this issue will happen to *any* review app, if we use absolute URLs.

Our lives will be a lot easier for local development, review app feedback, and production deployments if we use relative paths across this website. 

As an example, an absolute path is: `https://about.gitlab.com/enterprise/`. Whereas the relative path would be `/enterprise/`. 

The advantage of using the relative path is that it keeps users on the same root domain as they navigate a particular deployment. It also ensure that we don't accidentally click links and go to different environments in development. 

This is the same approach we should take for images (until we get a digital asset management tool, which will change the strategy). Images should refer to relative file paths, and should exist in our repository. 

I think the fix for this is for someone to go through and:

1. Search the entire Buyer Experience repository for references to `https://about.gitlab.com`
1. Convert the reference to be a relative link (where applicable - there may be some edge cases that really should always point to production, but I can't think of any off the top of my head)
1. We should consider a linter that will check for this, although truthfully I think that's a hard problem to solve, because sometimes we really truly need to write an absolute path (again, I can't think of when, but we might), and I don't love having linters check every single text file for these kinds of strings. It will slow down our CI. Personally, I would prefer to catch this in code review where we can. But if someone has a better, automated proposal, I'm all ears.

Story points: 2.0
Update release post instructions to new homepage

## Goal
We would like to X which will improve Y as measured by Z.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[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

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 1.0
DataLayer Updates for Contact Sales, Public Sector, and Self-Managed Trials

## Goal
DataLayer values for Contact Sales, Public Sector, and Self Managed Trials form submissions were accidentally updated to "Demo" recently. Conversions for these form types dropped on Google Analytics (Goals 11, 12, 20), and are counted towards the Demo conversion instead (Goal 15). 

Revert the Marketo form submit dataLayer code back to the original values. 

1. **about.gitlab.com/free-trial/**
Update Self Managed form submit dataLayer code back from `demo` to `trial`

2. **about.gitlab.com/solutions/public-sector/**
Update Private Section Contact Sales form submit dataLayer code back from `demo` to `public-sector`

3. **about.gitlab.com/sales/**
Update Contact Sales form submit dataLayer code back, from `demo` to `sales`


### Jobs To Be Done
* **Situation**: When users submit a form
* **Motivation**: We want to capture the event as a dataLayer
* **Outcome**: So we can make analyze leads generated by form type and calculate ROAS across marketing campaigns


## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com/free-trial/
* about.gitlab.com/sales/
* about.gitlab.com/solutions/public-sector/


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dennischarukulvanich 
- [ ] Consult: @mnguyen4 @jahye1 
- [ ] Informed: @mpreuss22 @MihaiConteanu  

## 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
Update @gl-website group with www-gitlab-com project maintainers

Every community contribution MR submitted to the `www-gitlab-com` repository initiates a GitLab Bot message. 

In this message, the @gl-website team is tagged. This group has one active member, @laurenbarker. The other member of the group is @MichaelPreuss, which is not an account. His real account is @mpreuss22.
 


We need to update this group to include the maintainers of the the `www-gitlab-com` repository and remove the Digital Experience team members.

Here is an example of the bot message: 
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100916#note_879874897

Story points: 1.0
Deprecate a fourth batch of non-redirect pages in www-gitlab-com

Based on https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0

Deprecates the remaining pages in that spreadsheet. Doing a larger batch to clear 'em all out: 

- [x] | https://about.gitlab.com/resellers/pillar-global-solutions/  |
- [x] | https://about.gitlab.com/resellers/project-research/         |
- [x] | https://about.gitlab.com/resellers/releaseteam/              |
- [x] | https://about.gitlab.com/resellers/slexn/                    |
- [x] | https://about.gitlab.com/resellers/softmart/                 |
- [x] | https://about.gitlab.com/resellers/soporte-libre/            |
- [x] | https://about.gitlab.com/resellers/swnetwork/                |
- [x] | https://about.gitlab.com/resellers/telstra/                  |
- [x] | https://about.gitlab.com/resellers/thinknyx/                 |
- [x] | https://about.gitlab.com/resellers/tl-consulting/            |
- [x] | https://about.gitlab.com/resellers/twoseed/                  |
- [x] | https://about.gitlab.com/resellers/vertical-sysadmin/        |
- [x] | https://about.gitlab.com/webcast/scaling-remote-with-gitlab/ |
- [x] | https://about.gitlab.com/resellers/norseman/                 |
- [x] | https://about.gitlab.com/resellers/softworks/                |

Story points: 1.0
Remove third batch of 10 pages from www-gitlab-com (reprise)

From https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0

Remove:

- [x] | https://about.gitlab.com/resellers/gitlabhost/                   |
- [x] | https://about.gitlab.com/resellers/goldman-information-services/ |
- [x] | https://about.gitlab.com/resellers/hanul-it/                     |
- [x] | https://about.gitlab.com/resellers/ig-corporate-solutions/       |
- [x] | https://about.gitlab.com/resellers/lsd-information-technology/   |
- [x] | https://about.gitlab.com/resellers/lyra-infosystems/             |
- [x] | https://about.gitlab.com/resellers/megazone-cloud/               |
- [x] | https://about.gitlab.com/resellers/new-context/                  |
- [x] | https://about.gitlab.com/resellers/nous-infosystems/             |
- [x] | https://about.gitlab.com/resellers/onyx-point/                   |

Story points: 1.0
Remove batch of 10 pages from www-gitlab-com (this time with feeling)

From https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0

- [x] | https://about.gitlab.com/resellers/almtoolbox/        |
- [x] | https://about.gitlab.com/resellers/cxrus/             |
- [x] | https://about.gitlab.com/resellers/deviniti/          |
- [x] | https://about.gitlab.com/resellers/dixit/             |
- [x] | https://about.gitlab.com/resellers/dx-solutions/      |
- [x] | https://about.gitlab.com/resellers/eddr-software/     |
- [x] | https://about.gitlab.com/resellers/emerasoft/         |
- [x] | https://about.gitlab.com/resellers/fierce-software/   |
- [x] | https://about.gitlab.com/resellers/fujitsu-australia/ |
- [x] | https://about.gitlab.com/resellers/git/               |

Story points: 1.0
Remove batch of 10 pages from www-gitlab-com

From https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0

- [x] | https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/license/      |
- [x] | https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/product-gaps/ |
- [x] | https://about.gitlab.com/devops-tools/ibm-apm-vs-gitlab/                |
- [x] | https://about.gitlab.com/devops-tools/jenkins-vs-gitlab/news/           |
- [x] | https://about.gitlab.com/devops-tools/jenkins-x-vs-gitlab/              |
- [x] | https://about.gitlab.com/devops-tools/misc/                             |
- [x] | https://about.gitlab.com/devops-tools/misc/tool-template.html           |
- [x] | https://about.gitlab.com/devops-tools/missing/                          |
- [x] | https://about.gitlab.com/devops-tools/new-template/                     |
- [x] | https://about.gitlab.com/devops-tools/tekton-vs-gitlab/                 |

Story points: 1.0
Remove batch of 10 pages from www-gitlab-com

Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/492

Removing these pages in https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0

- [x] | https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/comparison-methodology/  |
- [x] | https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/evaluation-questions/    |
- [x] | https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/news/                    |
- [x] | https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/atlassian-pricing/          |
- [x] | https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/frequently-asked-questions/ |
- [x] | https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/key-features/               |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-BDM.html                    |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-KeyFeatures.html            |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-License.html                |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-Questions-Concerns.html     |
- [x] | https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/key-differentiators/        |

Story points: 1.0
CTA component mobile bugs

When i was trying to [fix bugs](https://gitlab.slack.com/archives/CN8AVSFEY/p1647044055168979) last Friday evening I found this ![Screen_Shot_2022-03-11_at_10.02.49_PM](/uploads/dab55d35b01196c9689a8b6dd1289db3/Screen_Shot_2022-03-11_at_10.02.49_PM.png)

Investigate further

Story points: 1.0
Spike a better solution for handling data in Nuxt pages

## Goal

We'd like to manage the content in the Nuxt site in a more consistent, extensible, flexible way. 

The pages this matters most for are in the upcoming work. `@mpreuss22` gave us the [rundown of our current commitment in Slack]():

Goal is to deliver 10 amazing, newly designed pages with the rest of the site being on brand, live by April 27th:

Tier 01 (Doing 2nd): 3-4 page templates - Complete new vision, design, and content
* Homepage
* Pricing Page
* Solutions / Features Pages
* Install (stretch)

Tier 02 (Doing 3rd): 6-7 page templates - Well considered new design, significant new content, limited new branded/image/motion assets

* Category Leadership (Currently called Topics)
* Demo
* Enterprise
* SMB
* DevOps Lifecycle Pages
* Getting Started
* Contact Sales

Tier 03 (Doing 1st): - New coat of paint: updated fonts, colours, logos
Everything else: https://docs.google.com/spreadsheets/d/1ualGLPCyFjEpiskrfAe2ftqoTAw8t56lO1LMzMT7Ojo/edit

So to start, I'm going to look at the Tier 01 pages and do the following: 

1. See which, if any, we have represented in `content`
1. Take a look at how their page level `.vue` files consume that data
1. Identify common data structures, identify oddities and outliers (stuff that needs special handling)
1. Write up a spec for how we should structure data to be consumed by pages
1. Pitch that spec to @ndubord as a first iteration 

Once I do that, I'll write up an interface and try it out on the Homepage. I'll put together more specific issues for each page as I go. 

I'm going to timebox this to about a day-and-a-half, and see how far I can get on it. Once I know more, I'll add additional points, add additional issues, etc.

Story points: 3.0
Automate removal of unused assets from www-gitlab-com

## Goal
As we remove pages from the www-gitlab-com, assets are becoming obsolete. Lets write a script that removes unused assets from the repository. This will have compounding beneficial effects - every pipeline is faster, cloning the repository is faster, and the size the repository becomes smaller. 

## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/www-gitlab-com

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @ndubord 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create script that removes unused assets from the www-gitlab-com repository
- [ ] Remove the unused assets

## Out of scope
What is out of scope and not part of this iteration?

- Asset management in the Buyer Experience repository

## 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
regressions on buyer's experience repository

https://gitlab.slack.com/archives/CN8AVSFEY/p1647044055168979

![Screen_Shot_2022-03-11_at_16.11.39](/uploads/525853b507b4927b6acb10677a46650d/Screen_Shot_2022-03-11_at_16.11.39.png)

![Screen_Shot_2022-03-11_at_16.13.48](/uploads/35ea68096e19ec44df36dee5fe6af829/Screen_Shot_2022-03-11_at_16.13.48.png)

Story points: 1.0
ENG: Features - Landing Page V1

## Goal
When updating the [Features page](https://about.gitlab.com/features/), I want to design a clear and succinct user experience, so potential customers can learn about the Features that GitLab offers.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [Features](https://about.gitlab.com/features/)

Figma file: https://www.figma.com/file/XsnwxTLYPAN0j19vS6iSXm/Features-2.0?node-id=15%3A3641

## 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?

- [ ] UX Refresh

## 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:

- [ ] Engineering

Story points: 6.0
Pre-push Hook for linter

## Goal
We would like to have a pre-push hook to avoid having lint issues in the pipeline

### Jobs To Be Done
* **Situation**: *When someone does a commit to a Merge Request, sometimes the pipeline fails due to linter issues*
* **Motivation**: *We want to have a pre-push hook to detect linter issues before committing them to the pipeline*
* **Outcome**: *So we can avoid making multiple commits and going back and forth fixing linter issues*

## 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 @jgarc 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create a pre-push hook in the Buyer Experience Repo

## Out of scope
What is out of scope and not part of this iteration?

## 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
H1 Heading Changed

The H1s on /topics pages have been removed and replaced with H2s. H1 headings are a ranking factor for search engines as they use the H1 heading to determine what the page is about. 

Affected URLs:
| URL                                              |
|--------------------------------------------------|
| https://about.gitlab.com/topics/ci-cd/           |
| https://about.gitlab.com/topics/devops-platform/ |
| https://about.gitlab.com/topics/devops/          |
| https://about.gitlab.com/topics/gitops/          |
| https://about.gitlab.com/topics/microservices/   |
| https://about.gitlab.com/topics/multicloud/      |
| https://about.gitlab.com/topics/serverless/      |
| https://about.gitlab.com/topics/version-control/ |

Story points: 1.0
Add Script to Webpages to Hide Web Navigation in PathFactory Tracks

## Goal
We would like to add a script to some of our webpages, so that we can hide the web navigation header and footer when the page is added to a PathFactory track, in order to improve user experience. 
- [Example of a blogpost within a PF track](https://learn.gitlab.com/devsecops-aware/why-implementing-sec)
- [Example of a case study within a PF track](https://learn.gitlab.com/ci-purchase-prac1/goldman-sachs-gitlab)

Additional information about this project can be found [here](https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6077).

### Jobs To Be Done
* **Situation**: *When webpages are added to PathFactory tracks*
* **Motivation**: *We want them to look more organic and to display without the header/foot navigation*
* **Outcome**: *So we can provide a clean, intuitive user experience*

## Page(s)
Which page(s) are involved in this request?
* `All blog posts`
* `All case studies`
* [Pricing page](https://about.gitlab.com/pricing/)
- [x] @eirinipan to confirm that this is an accurate list

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @nikkiroth 
- [ ] Consulted: @eirinipan @mpreuss22 
- [ ] Informed: @jgragnola @amy.waller 

## In scope
What is within scope of this request?

- [ ] Add the following to our web pages (once confirmed above). This will allow the function to hide the header and footer.

// --- Note: The code snippet needs to run after the elements in the script below are loaded.  *---

```
<script>
   var windowURL = window.location.search;
   console.log(windowURL);

   if (windowURL.indexOf('menu=hide') > -1 && window.self!= window.top){                          
     document.querySelector('#global-nav ').style.display = 'none';
     document.querySelector('.footer.footer').style.display = 'none';
}
</script>
```

## Out of scope
What is out of scope and not part of this iteration?

- Any other changes/edits/requests

## 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] Engineering

Story points: 3.0