giseldo/neodataset huggingface dataset:
Header & Footer JS package size non BE repo

## Goal
I would like to discuss the JS package size for the main nav and footer.  In the handbook, blog, and non-BE www pages these two js files are usually the largest load on the page.

When the Nav repo is added to BE our webpack does some smart splitting on what is loaded and when, but not when we just load in the files. 

<details><summary>Screen Shot</summary>
![CleanShot_2022-09-27_at_09.09.03](/uploads/1216125bd537ab8943570ff4bc3da2a3/CleanShot_2022-09-27_at_09.09.03.jpg)
</details>

#### 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`
- [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 discuss options on reducing resource load for the packages we manage`

**How do we measure success?**
 - `We will look at Core Page scores to determine if reducing filesize will help`

**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 non BE pages`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker @ndubord @justin.vetter 
- [ ] Consulted: @dennischarukulvanich 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Come up with a plan on how we can reduce Nav package size for non BE pages.
- [ ] 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: Update Ultimate-tier link on Free Trial page

## Goal
We would like to update the Ultimate-tier link on the /free-trial page 

Ultimate-tier link -> https://about.gitlab.com/pricing/ultimate/

#### Jobs To Be Done
* **Situation**: *When a user clicks on the Ultimate-tier link they are taken to the /pricing page*
* **Motivation**: *We want to direct users to the most recent content*
* **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`
- [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 is to point users to the correct content

**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?
* `[Free Trial](https://about.gitlab.com/free-trial/)`

## 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: `@RLeihe268` 

## In scope
What is within scope of this request?

- [ ] Update Ultime Tier link
- [ ] 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
Document visual changes on the website since rebrand

From Michael:
- Put together a list of URLs and before and after screenshots of all page refreshes we’ve done since Q2
- Single pager kind of things from the Slack integration to the Features page etc. 
- I believe there is a lot of work that leadership is not aware of and I’d like to put together a list with visuals to inform them of how much we’ve done.

Story points: 4.0
Release: Overview Partner Program

## Goal
We would like to build a new template and apply it to Overview Partners page and a new Benefits for Partners. This new template was created as part of [this issue.](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1107)

- ~~[Figma Link](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=170%3A5667)~~
- [Update Figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=556%3A12097)

For copy:
- Nav: [New GitLab Partner Page Layout - Navigation](https://docs.google.com/document/d/1PLzmWVokewbVWTkT4vPUmQKt46veH0Ia7ohVVBW1EOo/edit#)
- Overview: [New GitLab Partner Page Layout - GitLab Partner Program Overview {new}](https://docs.google.com/document/d/1du1nu8dINnmiyd2CwkFddZbPQ_2dohS0HhO4AWpmh9U/edit#)
- Benefits: [New GitLab Partner Page Layout - Overview & Benefits {new}](https://docs.google.com/document/d/1eX1-we2XqqxBkVe5AIIL4TqVFEwKBcEHiVDu38F7Nmw/edit?usp=sharing)


### Jobs To Be Done
* **Situation**: *We'd like a unified landing page for GitLab partners overview and benefits*
* **Motivation**: *When users need more information we can direct the to the correct spot*
* **Outcome**: *So we can offer them the best service*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/partners/
* https://about.gitlab.com/partners/benefits

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mduque-ext 
- [ ] Consulted: @laurenbarker @ctsang-ext @mlebeau
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Releasing new Overview Partners page to production @ https://about.gitlab.com/partners/
- [ ] Creating and releasing a new Benefits for Partners to production @ https://about.gitlab.com/partners/benefits/
- [ ] Updating our navigation as specified in the Figma

## 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: Release Post MVC 1 Rebrand

## Goal
We would like to create a new review app link for the engineering work that has been done for the Release Post template from this previous [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1201) and [MR](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/110472)

**The MR should not be merged until we have signoff from all stakeholders**__

### Jobs To Be Done
* **Situation**: *When a customer goes to read the release post ...*
* **Motivation**: *We want to have a similar experience to the rest of the site...*
* **Outcome**: *So we can maintain our brand and make sure our site is accessible.*

## Page(s)
Which page(s) are involved in this request?
* [Example release post](https://about.gitlab.com/releases/2022/07/22/gitlab-15-2-released/)
* [Figma designs](https://www.figma.com/file/GpqMIWNYZW2fC58BHwMbWf/Release-post-MVC1?node-id=2%3A928)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @fqureshi @jhalloran @justin.vetter @ndubord 
- [ ] Informed: `@fseifoddini` `@amittner` `@brhea`

## In scope
What is within scope of this request?

- [x] Skin existing release post with updated brand colors and typography
- [x] Address any existing accessibility issues

## Out of scope
What is out of scope and not part of this iteration?

- Changing the structure of the page
- Hero image
- Anything else

## 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: Free Trial Tab component

## Goal
We keep the /free-trial/ page around for SEO purposes and to drive some links to the Self-Managed sign up form.  Currently there is no way to link to the page and have the Self-Managed tab automatically selected.

#### Jobs To Be Done
* **Situation**: *When we link to this page driving to the Self-Managed form the user needs to click the tab to fill out the form*
* **Motivation**: *We want to be able to link to this page and have an option to have the Self-Managed tab selected*
* **Outcome**: *So we can drive users directly to the Self-Managed form*

#### 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 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?
* `[Free Trial](https://about.gitlab.com/free-trial/)`

## 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 tab component so a direct link can highlight the `GitLab Self-Managed` tab
- [ ] Add accessibility tab targeting to the tab component

## 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
Tracking: Site Search Result Sort dataLayer

## Goal
Push the following dataLayer code when the Sort By selection is made on the search result window:<br/>
<img src="/uploads/c5570a4f8a3d0e20d8aef0a170d79ce6/Screen_Shot_2022-09-22_at_3.23.14_PM.png" width="300">


```
dataLayer.push({
 'event': 'siteSearchResultSort',
 'siteSearchSort': '[dynamic value of most popular, suggested, last updated]',
 'siteSearchQuery': '[dynamic searched query goes here]'
});
```

#### Please provide more information related to this request<br/>
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
- [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 @laurenbarker 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: Addition to existing Google Analytics data set 

**What analytics / data will we need to set-up?**
- [x] Yes: Click tracking within the Site Search section
- [ ] No

## 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: `GitLab Handle`
- [ ] Consulted: @dennischarukulvanich 
- [ ] 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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Tracking: Site Search Result Filter dataLayer

## Goal
Push the following dataLayer code when the Source radio buttons are clicked on:<br/>
<img src="/uploads/72e64a8cfdb1faae3d7ac74d5aa177a7/Screen_Shot_2022-09-22_at_3.16.56_PM.png" width="200">

```
dataLayer.push({
 'event': 'siteSearchResultFilter',
 'siteSearchFilter': '[dynamic value of about gitlab, handbook, or blog goes here]',
 'siteSearchQuery': '[dynamic searched query goes here]'
});
```

#### Please provide more information related to this request<br/>
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
- [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 @laurenbarker 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: Addition to existing Google Analytics data set 

**What analytics / data will we need to set-up?**
- [x] Yes: Click tracking within the Site Search section
- [ ] No

## 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: `GitLab Handle`
- [ ] Consulted: @dennischarukulvanich 
- [ ] 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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Tracking: Site Search Result dataLayer

## Goal
Objective is to push a dataLayer event when a search is made, along with the searched query. 

Push dataLayer on search result load<br/>
<img src="/uploads/78a766243e5f442462784e6379d688b7/Screen_Shot_2022-09-22_at_2.55.15_PM.png" width="500">

```
dataLayer.push({
 'event': 'siteSearchResult',
 'siteSearchQuery': '[dynamic searched query goes here]'
});
```

Note: The dataLayer should be pushed when the user enters a query in the search field AND when the user clicks on a suggested searched query - both methods will lead the user to the result page as a next step. 


#### Please provide more information related to this request<br/>
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
- [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 @laurenbarker 
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: Addition to existing Google Analytics data set 

**What analytics / data will we need to set-up?**
- [x] Yes: Click tracking within the Site Search section
- [ ] No

## 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: `GitLab Handle`
- [ ] Consulted: @dennischarukulvanich 
- [ ] 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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Plan: Analysts (Design) MVC 2

## Goal
We would like to update the Analysts page to include updates [per this comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1384#note_1104043751)

### Jobs To Be Done
TBD

## 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: @ctsang-ext 
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?

- [ ] Design

## 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: 4.0
Release: Support Services template

## Goal
We would like to release a new Support Services template in the Buyer Experience repository.

This will involve final touches to template. 

To release this template, undo the changes made with this [commit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1097/diffs?commit_id=cceaec7d8a2961f3b4c4c09e913e1bf0d35ee372). 

### Jobs To Be Done
Release [the new template ](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1361)in Buyer Experience, migrate content from www-gitlab-com

## Page(s)
Which page(s) are involved in this request?
- [Support Services](https://about.gitlab.com/services/#contactform) 
- [Figma](https://www.figma.com/file/2zmj9hb6MBH40d6NMZm8Jw/Professional-Services?node-id=26%3A3)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted:  @ctsang-ext @laurenbarker  
- [ ] Informed: @fqureshi 

## In scope
What is within scope of this request?

- [ ] Create merge request releasing template to prodcution
- [ ] Tag stakeholders for review in merge reuqest
- [ ] Tag @fqureshi for review in merge request
- [ ] Remove URl from the routes.ignore.js 
- [ ] Remove the page from www-gitlab-com
- [ ] Update handbook instructions for how to find and update this page

## 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
Release: New Analysts Page

## Goal
We would like to release the new Analysts page using the new template built in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1394)

## 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: TBD
- [ ] Consulted: @ctsang-ext @laurenbarker
- [ ] Informed: @fqureshi 

## In scope
What is within scope of this request?

- [ ] Prepare a MR for stakeholder review and tag @fqureshi for review
- [ ] Release the new Analyst page to production
- [ ] Remove the Analysts page from `www-gitlab-com`
- [ ] Update any references on location of this page and how to update it in the handbook

## 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: Analysts Template

## Goal
We would like to update the Analysts page using the new template planned in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1384#note_1107954781). 

Here is the[ Figma template.](https://www.figma.com/file/7Q7VE1wjbM8iGxloOP0u9b/Analysts?node-id=0%3A1) 

### Jobs To Be Done
Create the template in Buyer Experience.

## 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: @ctsang-ext 
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?

- [ ] Build the [Figma template](https://www.figma.com/file/7Q7VE1wjbM8iGxloOP0u9b/Analysts?node-id=0%3A1) in Buyer Experience
- [ ] Add this page to BE but disclude it from building in production using routes ignore file. We will release this template in a separate issue. 

## 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
Plan: Analysts (Design)

## Goal
We would like to update the Analysts page.

### Jobs To Be Done
TBD

## 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: @ctsang-ext 
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?

- [ ] Design

## 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: 4.0