giseldo/neodataset huggingface dataset:
Add transaction event for enhanced ecommerce for successful subscription purchases

## Goal

Track Google Enhanced Ecommerce events in the SaaS purchase flow, based on this specification: https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/f252fc80f1dd6799d19e4d57d6b4c239/Gitlab_GTM_DataLayer_Spec.pdf

### Jobs To Be Done

* **Situation**: *When a customer purchases SaaS subscriptions at `https://gitlab.com/-/subscriptions/new`*
* **Motivation**: *We want to record the transaction `dataLayer` events*
* **Outcome**: *So we can have analytics across the entire purchase flow*

## Page(s)

Which page(s) are involved in this request?
* [New SaaS subscription](https://gitlab.com/-/subscriptions/new)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @tywilliams 
- [ ] Consulted: @dennis106 
- [ ] Informed: @mpreuss22 

## In scope

What is within scope of this request?

- [ ] Transaction `dataLayer` events for SaaS purchases in `gitlab.com`

## Out of scope

What is out of scope and not part of this iteration?

- Checkout events in the `dataLayer`
- Any analytics in `customers.gitlab.com`

## 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
Silent build fails not displaying in CI/CD

## Goal
We would like to display through Nuxt build output in our CI/CD to help diagnose errors and avoid silent build errors.

### Jobs To Be Done
* **Situation**: *When a MR is deployed to `main`*
* **Motivation**: *We want the full output of `yarn generate` in our `build` job*
* **Outcome**: *So we can see exactly where the build failed and avoid silent build errors*

## Page(s)
Which page(s) are involved in this request?
* `.gitlab-ci.yml`

### Examples of past silent build errors
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/123#note_803535037
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/149#note_822804320
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @tywilliams @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Iteration to `.gitlab-ci.yml`

## Out of scope
What is out of scope and not part of this iteration?

- Design, template, or content work

## 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
Update the images used by the pipeline in this project

The following discussion from !122 should be addressed:

- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/122#note_803461115):  (+1 comment)

    > Non blocking for this MR, but I think we should scope work required to create an image specific to our Buyer Experience repository. I'm not sure that tying ourselves to the one used for `www-gitlab-com` is sustainable long term.

We should either: 

1. Create a specific image for this repository
1. Move the deploy stage back to using the Google SDK image once it supports the `-z` flag

Story points: 6.0
Solution page migration - Public Sector

Related to #191.

## Goal

We would like to migrate `/solutions/public-sector/` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the solutions template.

### Jobs To Be Done

* **Situation**: *When a user lands on* `/solutions/public-sector/`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*

## Page(s)

Which page(s) are involved in this request?

* `[Public Sector](https://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: `@jariasc-ext`
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`

## In scope

What is within scope of this request?

* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Applying the solutions template to this page
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository

## Out of scope

What is out of scope and not part of this iteration?

* Building a new template
* Any work in www-gitlab-com other than removing the 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: 5.0
Learn page migration - Landing

## Goal

We would like to migrate `/learn` landing page from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience).

### Jobs To Be Done

* **Situation**: *When a user lands on* `/learn`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*

## Page(s)

Which page(s) are involved in this request?

* `[Learn Landing Page](https://about.gitlab.com/learn/)`

## DCI

[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

* [ ] DRI: `@jariasc-ext`
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`

## In scope

What is within scope of this request?

* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/learn directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository

## Out of scope

What is out of scope and not part of this iteration?

* Any work in www-gitlab-com other than removing the 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: 2.0
Implement New LinkedIn Event-specific tracking using Insight Tag

## Goal
LinkedIn recently announced that it has added a new conversion pixel. TLDR version, there is a new pixel based on an insight called an `insights tag` rather than an `event-specific` action. The insight tag is more accurate than the event tag type. [Here is a link to the LinkedIn update](https://www.linkedin.com/help/lms/answer/a425606?accountId=502663326).

### Jobs To Be Done
* **Situation**: When people visit the GitLab website, there are certain conversion events that we would like to track within LinkedIn. Noted the conversion events that we are tracking in the `Pages` section
* **Motivation**: Because we run a number of ad campaigns in LinkedIn, implementing the new tags will help our demand generation team and agency, optimize to performance of a campaign. 
* **Outcome**: We would be able to see exactly which conversion events are being completed for a campaign.

## Page(s)
Which page(s) are involved in this request?

Here are the conversion tags that we have in LinkedIn that we are looking to get implemented. I am unsure how the conversion tags have been set up in the, so unsure where on the page these need to be added. 

* Free Trial conversions - `window.lintrk('track', { conversion_id: 1111306 });`
* Webcast sign ups- `window.lintrk('track', { conversion_id: 1111314 });`
* Thank You Page For Events - `window.lintrk('track', { conversion_id: 2157650 });`
* Demo - `window.lintrk('track', { conversion_id: 1111250 });`
* Gated Asset download- `window.lintrk('track', { conversion_id: 1111282 });`
* Contact Sales - `window.lintrk('track', { conversion_id: 1111290 });`
* Public Sector - `window.lintrk('track', { conversion_id: 1111274 });`
* Newsletter - `window.lintrk('track', { conversion_id: 1111266 });`
* Live Events - `window.lintrk('track', { conversion_id: 1111258 });`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpreuss22 ? (Michael, I Slacked you about this and you said to tag you)
- [ ] Consulted: @mnguyen4
- [ ] Informed: @lstinson @zbadgley 

## In scope
What is within scope of this request?

- [ ] Implement LinkedIn insight tags to appropriate conversion events
- [ ] 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
- [x] Data / Analytics: This is to add LinkedIn Insight conversion tags to relevant conversion events on the GitLab website. This allows us to optimize our campaigns that we run in LinkedIn. 
- [ ] UX Design
- [ ] Engineering

Story points: 2.0
Replace form on /demo/ page with 3-minute demo video

## Goal
We would like to remove the form on the /demo/ page which will improve user experience per request from leadership. This is related to the following issue (but with simplified scope to only remove the form and display the video): [Proposal for ungated content journeys on the website](https://gitlab.com/gitlab-com/marketing/demand-generation/campaigns/-/issues/1823).

### Jobs To Be Done
* **Situation**: *When someone lands on the /demo/ page*
* **Motivation**: *We want to allow them to watch the 3 minute video without submitting a form*
* **Outcome**: *So we can educate them about GitLab as a DevOps Platform*

## Page(s)
Which page(s) are involved in this request?
* `[/demo/](https://about.gitlab.com/demo/)`

## 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?

- [x] Replace form on /demo/ page with the 3-minute video
- [ ] 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
- [x] Engineering

Story points: 2.0
Better Devops Tools index page

## Goal
We would like to improve the Devops Tools index page so as to:

- Comply with copyright by removing competitor logos
- Make it easier to find specific vendors e.g. using command-F
- Allow for more information to be displayed in the future

### Jobs To Be Done
* **Situation**: *When I go to [Devops Tools](https://about.gitlab.com/devops-tools/)...*
* **Motivation**: *We want to see the names of the vendors instead of the logos*
* **Outcome**: *So we can not sue GitLab, and find specific vendors more easily*

## Page(s)
Which page(s) are involved in this request?
* [Devops Tools](https://about.gitlab.com/devops-tools/)

## Workfiles
* [Figma](https://www.figma.com/file/0avvI8lQ2XgiGbhGEiv2lh/DevOps-Tools-Landscape-1.1?node-id=0%3A1)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `@francispotter`
- [ ] Consulted: `@jfullam @dfrhodes`  
- [ ] Informed: ``

## In scope
What is within scope of this request?

- [ ] Redesign the Devops Tools page so there are no vendor logos, but instead the names of the vendors. Do it in a way that doesn't allocate more space (implied importance) to vendors with longer names. One concept has been developed [here](https://12778-remove-competitor-logos-from-the-devops-tools-index-page.about.gitlab-review.app/devops-tools/) but needs some design improvement.

## 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
- [x] UX Design
- [ ] Engineering

Story points: 4.0
Add "add to cart" event to GTM dataLayer for usage tab

## Goal

We would like to add the "add to cart" dataLayer event to the view at `https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab` so we can gather analytics in GTM enhanced ecommerce.

### Jobs To Be Done

Implement the product impression event for `https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab` as outlined in the [specification doc](https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/f252fc80f1dd6799d19e4d57d6b4c239/Gitlab_GTM_DataLayer_Spec.pdf)

## Page(s)
Which page(s) are involved in this request?
* [https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab](https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @dennis106 
- [ ] Informed: @mpreuss22

## In scope
What is within scope of this request?

- [ ] GTM dataLayer event on `https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab`

## 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
Solutions Template - UX Iteration

## Goal
We would like to gather Solution template iterations for the Buyer Experience repository here which will improve efficiency.

### Jobs To Be Done
* **Situation**: *When we notice a style is incorrect on the Solutions template*
* **Motivation**: *We want to document it here*
* **Outcome**: *So we can make MVC changes within MRs and link them all back to this issue*

## Page(s)
Which page(s) are involved in this request?
* All solutions pages built with the  Buyer Experience repository

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Itemize the solution template updates
- [ ] Create MVC MRs for each adjustment, apply them to all solutions pages

## Out of scope
What is out of scope and not part of this iteration?

- Any adjustment in Slippers
- Any adjustment in www-gitlba-com

## 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
- [x] Engineering

Story points: 6.0
DSN: Update marketing navigation 3.0

## Goal
We would like to update the navigation to include a "Buy now" button (and maybe a "Register" link) and display buttons always on tablet size, which will improve conversion as measured by increased sales.

### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to immediately buy our product...*
* **Outcome**: *so they can start using it right away.*

## Page(s)
Which page(s) are involved in this request?
- Marketing Navigation
- [Figma Designs](https://www.figma.com/file/y2B6qEaGOTDXI1tImIJ5Ct/Navigation-MVC4?node-id=233%3A449)
- [Google Doc Request](https://docs.google.com/document/d/1i9IfkaN6nb8yuzNKET54Kj8qhloo9_fnHg8CTA6NlMU/edit)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: @jgarc @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Display all buttons on tablet size at all times
- [ ] Include a new "Buy now" button option in the nav
- [ ] Consider adding a "Register" link in the nav so users can sign up for a new account
- [ ] Rethink whether this should be two navs

## Out of scope
What is out of scope and not part of this iteration?

- 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: 2.0
Call Bizable script in product via hardcode

## Goal
We would like to hardcode Bizable into the product instead of via GTM to have a consistent implementation across our sign up flow platforms. Calling Bizable via GTM also has data loss risk of 5-10%, so hardcoding it into the product eliminates that risk.

[Related thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/19#note_749577421) 

### The Code

`<script async='' src='//cdn.bizible.com/scripts/bizible.js'></script>`

## Where would this project happen?

#### Insert here a bulleted list containing any URLs that we'll be updating or creating:

All approved gitlab.com pages in the Trial funnel (not Product pages):

* https://gitlab.com/-/trials/new
* https://gitlab.com/-/trials/select
* https://gitlab.com/users/sign_up
* https://gitlab.com/-/trial_registrations/new
* https://gitlab.com/users/almost_there
* https://gitlab.com/users/sign_up/groups/new
* https://gitlab.com/users/sign_up/projects/new
* https://gitlab.com/users/sign_up/groups_projects/new
* https://gitlab.com/users/sign_up/welcome/trial_getting_started
* Any other Trial funnel page(s)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: `@mpreuss22` 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Adding the Bizable script to the pages listed above 

## 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: Build anchor link functionality for heading titles

## Goal
We would like to include the anchor link functionality that displays on hover for section headers in the new repository. Section linking promotes self-service & self-learning which is in line with our all-remote culture.  More on [answering with a link here](https://about.gitlab.com/company/culture/all-remote/self-service/#answer-with-a-link) > 

![Screen_Shot_2021-12-02_at_9.13.25_AM](/uploads/55c6439f5dad8bc9117c29ef956c7195/Screen_Shot_2021-12-02_at_9.13.25_AM.png)

### Jobs To Be Done
* **Situation**: *When looking for information GitLab*
* **Motivation**: *I want the ability to copy a link to a specific section*
* **Outcome**: *So I can save it or share it.*

## Page(s)
Which page(s) are involved in this request?

## Workfiles
Use the pajamas link icon instead of the current one
- Link icon svg:  ![Link.svg](/uploads/6d163e29301c6c85885d415f799ac02b/Link.svg)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @Tinaliseng 
- [ ] 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: 8.0