giseldo/neodataset huggingface dataset:
Analytics - Solutions CTAs

## Goal
Please help implement click tracking on the Solutions page:
1. Update the `data-ga-body` attribute on links to `data-ga-location` on the Solutions page 
2. The card links (documentation, pricing tiers) will need specific attributes. Add the following attributes (please see the /features page as an example for coding): `data-ga-features`, `data-ga-features-sub`, `data-ga-features-sub-card`, `data-ga-name`, `data-ga-location`. 
3. Add the data attributes for anchoring links where `data-ga-location="anchor"`. 

Handbook: https://about.gitlab.com/handbook/marketing/digital-experience/analytics/google-tag-manager/#click-tracking

#### 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: existing tracking


**What analytics / data will we need to set-up?**
- [x] Yes: ensure all links have `data-ga-name` and `data-ga-location`
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/

## 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: @hsmith-watson @fqureshi @Tinaliseng 


## 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
[ENG] Fix Delivery Automations Solutions page youtube video embeds

The Youtube embeds on the [/solutions/delivery-automation](https://about.gitlab.com/solutions/delivery-automation/) page are not working correctly.

Seems to be specific to **Chrome**

![YoutubeEmbedIssue](/uploads/951b8634a1d0cfc094e503ed294fb544/YoutubeEmbedIssue.mov)

Story points: 1.0
Tier 3 pages - DevSecOps Platform Branding

## Goal
We would like update tier 3 pages with DevSecOps Platform branding.

## Which page(s) are involved in this request?

Each page should be it's own MR 

| Tier 3 Pages to Update                   |
|--------------------------------------------|
| https://about.gitlab.com/solutions/digital-transformation/  |
| https://about.gitlab.com/solutions/agile-delivery/          |
| https://about.gitlab.com/solutions/gitops/                  |
| https://about.gitlab.com/solutions/dev-sec-ops/             |
| https://about.gitlab.com/solutions/compliance/              |
| https://about.gitlab.com/solutions/cloud-native/            |
| https://about.gitlab.com/solutions/supply-chain/            |
| https://about.gitlab.com/solutions/value-stream-management/ |
| https://about.gitlab.com/solutions/public-sector/           |
| https://about.gitlab.com/solutions/education/campus/        |
| https://about.gitlab.com/company/culture/all-remote/        |
| 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: TBD
* [ ] Consulted: `@rclayman` `@bbula`
* [ ] Informed: Everyone

## Engineering Notes

1 MR per page for the branding update. Tag `@rclayman` or`@bbula` and an engineer for review.

Story points: 5.0
Tier 2 pages - DevSecOps Platform Branding

## Goal
We would like update tier 2 pages with DevSecOps Platform branding.

## Which page(s) are involved in this request?

Each page should be it's own MR 

| Tier 2 Pages to Update                   |
|--------------------------------------------|
| https://about.gitlab.com/features/                   |
| https://about.gitlab.com/get-started/                |
| https://about.gitlab.com/get-started/small-business/ |
| https://about.gitlab.com/get-started/enterprise/     |
| https://about.gitlab.com/teamops/                    |
| https://about.gitlab.com/company/                    |
| https://about.gitlab.com/partners/                   |
| https://about.gitlab.com/install/                    |
| https://about.gitlab.com/customers/                  |
| https://about.gitlab.com/security/                   |
| https://about.gitlab.com/support/                    |

## DCI

[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

* [ ] DRI: TBD
* [ ] Consulted: `@rclayman` `@bbula`
* [ ] Informed: Everyone

## Engineering Notes

1 MR per page for the branding update. Tag `@rclayman` or`@bbula` and an engineer for review.

Story points: 5.0
[ENG]: Create custom eslint rule for catching uses of markdown within a SlpTypography component

## 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 ...*

#### 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: 4.0
[ENG/UX] Work with external team to update form on /open-source/join

## Goal
We would like to work with SheerID to update the look and layout of their form on the [/open-source/join](https://about.gitlab.com/solutions/open-source/join/) page.

| Code | Production |Figma |
| ------ | ------ |------ |
| ``<iframe src="https://offers.sheerid.com/gitlab/member/" width="800" height="1300" ></iframe>``       |   ![Screenshot_2023-02-06_at_12.06.34_PM](/uploads/208a5b351ab90360b0df42096146941c/Screenshot_2023-02-06_at_12.06.34_PM.png)     |  ![Screenshot_2023-02-06_at_12.07.15_PM](/uploads/3a1c39b2f3a3cbda2f5bd4f8a7f93922/Screenshot_2023-02-06_at_12.07.15_PM.png)     |

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* [/open-source/join](https://about.gitlab.com/solutions/open-source/join/)

## Include any Figma files
* [Figma](https://www.figma.com/file/Od5TazELCPPEhkcoReGQvO/Open-Source?node-id=18%3A5847&t=hPIRkHukRahYke06-0)

## Include any graphic or design assets
* `Upload any extra files needed to complete this request`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter @bbehr
- [ ] Informed: `Everyone`

Story points: 2.0
Changelog for DEX Figma

## Goal
We would like to create a changelog for our Digital Experience Figma instance that is autogenerated at the end of every iteration. We will use add at the bottom of each executive iteration update to direct people to if they'd like to dig deeper.

#### Jobs To Be Done
* **Situation**: *When a iteration is completed, all the items completed with Figma are added to changelog.*
* **Motivation**: *We want to create a efficient way to communicate the work completed by the Digital Experience team.*
* **Outcome**: *So we can ensure transparency.*

#### 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.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes 
- [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?**
 - A automated changelog for all changes in our Figma designs during a iteration.

**How do we measure success?**
 - `Changelog exists`

**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?
* Changelog for Dex Figma

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create changelog for the DEX Figma instance
- [ ] Automate changelog to generate at end of iteration cadence 
- [ ] Documentation in the handbook
- [ ] Designer docs in 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
- [x] UX Design
- [ ] Engineering

Story points: 1.0
[ENG] Create new solutions page / Startups

## Goal
We want to create a new solutions page for Startups.

## Workfiles
- [Figma](https://www.figma.com/file/vzlUPQQzbWKxGgTDRNBZob/Start-ups-MVC-1?node-id=10%3A757&t=j0LTfV5AVt7QE852-1)
- [Copy doc](https://docs.google.com/document/d/1rpyYb14ZMI44pqfSK2WfzbMT6rkvA093sa7cLtzpQ0I/edit?usp=sharing)

Which page(s) are involved in this request?
* about.gitlab.com/startup

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 
- [ ] Consulted: @Tinaliseng  
- [ ] Informed: @fqureshi @justin.vetter

Story points: 4.0
Investigate reoccurring artifact upload failures

## Goal
In the last sprint, we have seen three separate incidents where the pipeline in www is failing because of the buyer-experience job. We have mitigated these incidents, but need to investigate a root cause. 


#### Details and Timeline

Thurs, Feb 2nd - [Incident-8354](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1870): Pipelines for the buyer-experience job started 503-ing, implying "no access" to the artifact. After declaring a [prod incident](https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8354), it was discovered that the buyer experience repository had been made private, meaning that the artifacts were being uploaded somewhere inaccessible. Changing the repo to public, and re-uploading a new artifact, seemed to fix the problem. 

Fri, Feb 3rd - [Incident-8354 part 2](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1874): Same job in www starts failing, this time due to a 404 (file not found). After checking the difference between a recent successful "pages" deploy job in buyer experience, and comparing it to the most recent "pages" deploy job, we noticed that the runner was a private runner. We removed all private runners, and re-uploaded a new artifact. This seemed to fix the problem, and we assumed that the private runners were added to our repo when it had been made private yesterday. 

Fri, Feb 10th - Same as last week, the artifact starts 404-ing. The repo is public, there are no private runners. Looking at the last "pages" deploy in buyer experience, it was the automatic changelog job. I created a new MR, merged it in order to create a new artifact, and went over and re-ran the failed jobs in buyer experience, which seemed to fix the problem. 

#### Theories
Simply due to the fact that the changelog job had been run immediately prior to each of the 3 incidents, we may need to investigate how it may be affecting our CI. Especially since we're seeing these 404 failures on Friday's (the changelog script has [recently been changed](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1642) to run every second Friday). My instinct is to let the job run on it's own in 2 weeks and see if we run into problems, or manually run the job and keep an eye on www pipelines. 

**If this is urgent, what is the business need for the urgency?**
- [x]  Yes: This blocks all MRs from building & deploying in the handbook, blog, and some marketing web pages. 
- [ ]  No


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: `@lduggan @ndubord`
- [x] Consulted: `@laurenbarker @justin.vetter `
- [ ] Informed: `Everyone`



## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
[ENG] Identify Enterprise user and display MVC variation in navigation

## Goal

To utilize the [Demandbase API](https://support.demandbase.com/hc/en-us/sections/360011444531-API-Documentation) to identify if a visitor is coming from an Enterprise organization. They will be identified if:

- They have an existing Demandbase cookie set
- That cookie was mapped to a company
- If their IP address has been identified to obtain company identification

If the user is identified as Enterprise, we'll display a very MVC to the navigation. This subtle change in the navigation will be tiny - such as slightly different text on a single nav item. 

The goal of the issue is to simply prove that we can personalize the navigation based on visitor identification using Demandbase. If we can prove successful here, we'll ask our product designers to create two navigation variations for a larger iteration.



## Which page(s) are involved in this request?
* about.gitlab.com - buyer experience pages

## Include any Figma files
* There is no figma for this change - we only want a very small text change here

## In scope
What is within scope of this request?

- [ ] Identify 1 small text change in the navigation we can make for a enterprise user
- [ ] Build logic into navigation that enables us to show and hide the elements based on user type
- [ ] Ship this change to production

Story points: 6.0
Update Why GitLab table to reflect categories.yml updates

## Goal
We would like to update the Platform and Why GitLab pages to reflect recent changes to categories.yml and features.yml made in [this MR from www](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/119568). Those data changes were synced over to Buyer Experience with [this MR](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1670). However the changes are not reflected on the Platform and Why GitLab pages because the data is pulled from a different source.

Related https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1671 

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/platform/
* https://about.gitlab.com/why-gitlab/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @meganfilo 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

Story points: 4.0
Create GDK cookie to recognize logged in user on marketing site

## Goal

We would like to create a first party cookie in the product that will enable the marketing site to recognize a logged in Gitlab user.

### Engineering Notes

The user's session ID can be stored in a cookie on the client-side, and sent with each request to the server. The server can then look up the user's session in the database(or API) to determine if they are logged in or not.

This solution was also suggested by a Staff Support Engineer in the `#g_manage_auth` slack channel

#### How

1. **Assign a unique session ID to each user when they log in**: When a user logs in, generate a unique session ID for them and store it in a cookie on their device.
1. **Store the session ID in a shared database(or API):** Store the session ID in a database that can be accessed by both repositories. This allows us verify the user's login status by checking if their session ID is present in the database.
1. **Verify the user's login status with each request**: On each request from the user's device, both repositories can check the session ID in the cookie against the session ID stored in the database. If the session IDs match, the user is considered to be logged in.
1. **Update the cookie when the user logs out**: When the user logs out, you can delete their session ID from the database and remove the cookie from their device.

#### Problems

1. Potential scaling issues: performance issues may arise with a larger user base but this could be mitigated by sharding
1. Latency
1. Security? May need to flag that team for awareness and implementing some sort of encryption for the cookies
1. Maintenance? May need to onboard more people in GDK to maintain this
1. Cookies are client-side so the user maybe clear the cookies at any point. We should implement a fallback method like a session time-out that requires the user to log back in after \~12-24 hours

## Which page(s) are involved in this request?
* gitlab.org


## In scope
What is within scope of this request?

- [ ] Create the cookie for gitlab.com

Story points: 6.0
[ENG] Iterate on long FAQ sections

## Goal
We would like to iterate on long FAQ sections by adding in a navigation element to allow users to quickly jump to sections.

This may require creating a new dynamic component or modifying an existing one

![CleanShot_2023-02-09_at_10.56.41](/uploads/4dc0491a73ccd8ac066e65d2176ec1ea/CleanShot_2023-02-09_at_10.56.41.jpg)

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.


## Include any Figma files
* [Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=14754%3A25596&t=Fii8BfWc3TN6ZzDu-0)
* [Figma prototype](https://www.figma.com/proto/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?page-id=734%3A2&node-id=14548%3A17629&viewport=-1583%2C1472%2C0.5&scaling=min-zoom&starting-point-node-id=11541%3A13757&hide-ui=1)

## Include any graphic or design assets
* `Upload any extra files needed to complete this request`

## 
DRI:
Consulted: @jhalloran @justin.vetter 

## In scope
What is within scope of this request?

- [ ] Create or modify component
- [ ] Deliverable 2

Story points: 5.0
Tier 1 pages - DevSecOps Platform Branding

## Goal
We would like update tier 1 pages with DevSecOps Platform branding.

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?

Each page should be it's own MR 

| Tier 1 Pages to Update                   |
|--------------------------------------------|
| https://about.gitlab.com/                  |
| https://about.gitlab.com/pricing/          |
| https://about.gitlab.com/pricing/premium/  |
| https://about.gitlab.com/pricing/ultimate/ |
| https://about.gitlab.com/platform/         |
| https://about.gitlab.com/sales/            |
| https://about.gitlab.com/why-gitlab/       |
| https://about.gitlab.com/enterprise/       |
| 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: TBD
* [ ] Consulted: `@rclayman` `@bbula`
* [ ] Informed: Everyone

Story points: 4.0
Why GitLab

## Goal
Complete a Smarting translation job for /why-gitlab/ 

We would like to complete a translation job in Smartling:

* URL: about.gitlab.com/why-gitlab
* Language: German
* Type of Translation: Smartling - Machine Translation + Editing+IR

## In scope
What is within scope of this request?

- [ ] Create job title DE - Why GitLab - FY24Q1 - DEX
- [ ] Completion of job
- [ ] Verify on staging https://globalization-test.about.gitlab-review.app/de-DE/why-gitlab/

Story points: 2.0
German Homepage - Human Translation Review

## Goal
It's come to our attention that the [homepage translation job for German](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1745) needs additional review and strings edited.

## Which page(s) are involved in this request?
* about.gitlab.com/de-de/
* https://globalization-test.about.gitlab-review.app/de-DE/
## In scope
What is within scope of this request?

- [ ] Human review of German translation
- [ ] Editing of strings
- [ ] Publishing updated strings

Story points: 2.0