giseldo/neodataset huggingface dataset:
Request: add child pages to the topic pages

## Goal
Go to market campaigns are launching for the quarter and there is new, supporting content that needs to be "made live" but that's not possible at this time. 

### Jobs To Be Done
* **Situation**: *When I tried to post these two pages (https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100373 and https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100368) they didn't appear because the child topic pages aren't visible? ...*
* **Motivation**: *We want to support the go to market campaigns ongoing this quarter...*
* **Outcome**: *So we can drive traffic, get leads, convert......*

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100373
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100368

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [x] DRI: `vsilverthorne`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Deliverable 1 - posting those pages and turning that functionality back on
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1 - anything other than the above
- 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
Update FAQ Schema function to take in and render markdown

Related to [485](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/485#note_867644026)

We want the ability for our FAQSchema function in `craftSchema.ts` to take in Markdown from YML files and render appropriate HTML tags.
A use case for this would be the CI/CD topics page's FAQPage schema that [contains unordered lists](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/96884/diffs#975ff1cbc57036d902929f48442254eea9dc1f92_149_0).


+a reminder to check and see if the topics/DevOps FaqPage schema is working in search engines.

Story points: 2.0
ENG: Update customer case studies landing page

|  Relates to|
| ------ |
| https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/373|


## Goal
We would like to update the customer case studies page to the current content and Slippers UI.

## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)

## Workfiles
- [Figma](https://www.figma.com/file/LvXKj0FACzSabahTD7zA5j/Customer-Stories-Landing-Page?node-id=15%3A3641)
- [Desktop Prototype](https://www.figma.com/proto/LvXKj0FACzSabahTD7zA5j/Customer-Stories-Landing-Page?page-id=15%3A3641&node-id=326%3A5872&viewport=241%2C48%2C0.44&scaling=min-zoom&starting-point-node-id=326%3A5872)
- [Mobile Prototype](https://www.figma.com/proto/LvXKj0FACzSabahTD7zA5j/Customer-Stories-Landing-Page?page-id=38%3A5133&node-id=474%3A7085&viewport=241%2C48%2C0.42&scaling=min-zoom&starting-point-node-id=474%3A7085)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: (insert engineer handle)
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone` @ctsang-ext 
## Out of scope
What is out of scope and not part of this iteration?

- Updates to single customer story pages
- Updates to the homepage customer stories section

## 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
Add filter to Featured Reports section - MVC2 of /analysts page

## Goal
We would like to filter by creator (Forrester, Gartner, IDC) in the Featured Reports section which will improve usability as measured by the control user will have on the rendered content + in time spent looking for information.

### Jobs To Be Done
* **Situation**: I load the /analysts page
* **Motivation**: I want to have a filter in the Featured Reports section
* **Outcome**: So I can filter the reports by creator
## 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: `@mduque-ext`
- [ ] Consulted: `@tinaliseng`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create filter for Featured Reports in the page

## Out of scope
What is out of scope and not part of this iteration?

- Any other work in this or another 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
Homepage - Brag Wall Badge Updates

Related to gitlab-com/marketing/inbound-marketing/marketing-website#168.

Hey @Tinaliseng - our Winter 2022 badges just came out, and we've got some awesome new ones (Best ROI and the Top 50/100 ones are probably my fav)

All badges can be found [here](https://drive.google.com/drive/folders/1u9jK3dSbe21DI1nlXz7yAseloYDAziJQ?usp=sharing) in the G-drive, but I also believe you have [login access to G2](https://my.g2.com/gitlab/badges) if you need a different filetype (I uploaded PNG, G2 has SVG)

You can see where I've got an associated issue in my project [here](https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/6098)

Relating this to the first iteration.

ALSO if you still need the [Trust Radius badge link](https://www.trustradius.com/products/gitlab/reviews)

Story points: 2.0
IA Refresh - Add schema.org tags

## Goal
We would like to add schema.org tags to 10 key pages which will improve SERP as measured by search rankings for key word/pages.

## Page(s)
Which page(s) are involved in this request?
1. [Homepage](http://about.gitlab.com)
1. [Pricing Page](https://about.gitlab.com/pricing/)
1. [Install](https://about.gitlab.com/install/)
1. Why GitLab
1. Solutions
1. TBD
1. TBD
1. TBD
1. TBD
1. TBD

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @hsmith-watson 
- [ ] Consulted: @ndubord @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Adding appropriate schema.org tags to the above pages


## Out of scope
What is out of scope and not part of this iteration?

- Significant changes to structure of pages that is not already planned

## 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
UX: Navigation update - Minimal footer

## Goal
We would like to rethink the navigation based on the new buyer repo pages which will improve findability as measured by reduced bounce rate.

### Jobs To Be Done
* **Situation**: *When a user comes to GitLab...*
* **Motivation**: *they want to find the page they are looking for quickly and easily...*
* **Outcome**: *so they can make decisions or learn new information.*

## Page(s)
Which page(s) are involved in this request?
* Navigation
* [Figma designs](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=5021%3A9923)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: @Tinaliseng @ctsang-ext  
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Updated minimal footer navigation layout
- [x] UI skin navigation with new brand guidelines

## Out of scope
What is out of scope and not part of this iteration?

- Header navigation

## 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
UX: Navigation update - Full footer

## Goal
We would like to rethink the navigation based on the new buyer repo pages which will improve findability as measured by reduced bounce rate.

### Jobs To Be Done
* **Situation**: *When a user comes to GitLab...*
* **Motivation**: *they want to find the page they are looking for quickly and easily...*
* **Outcome**: *so they can make decisions or learn new information.*

## Page(s)
Which page(s) are involved in this request?
* [Excel with explanations](https://docs.google.com/spreadsheets/d/1D9O84YDXxfjoRhUiwtWySe6Az6pQ2MsjiB6iqhUJHLU/edit?usp=sharing) - see column G for changes and column H for reasoning
* [Figma designs](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/branch/UYZLoPAD4pMunezYiaFhpW/Slippers_foundations?node-id=5021%3A9923)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: @Tinaliseng @ctsang-ext  
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Updated footer navigation layout
- [ ] UI skin navigation with new brand guidelines

## Out of scope
What is out of scope and not part of this iteration?

- Header navigation

## 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
UX: Navigation update - Minimal header

## Goal
We would like to rethink the minimal header navigation based on the new buyer repo pages which will improve focus as measured by increased time on page.

### Jobs To Be Done
* **Situation**: *When a user comes to GitLab and they are in a funnel experience...*
* **Motivation**: *they want to be focused on the task at hand...*
* **Outcome**: *so they can make decisions or learn new information.*

## Page(s)
Which page(s) are involved in this request?
* Navigation
* [Figma designs](https://www.figma.com/file/fPzNDCzZAUlAHuq9iQSFmn/Navigation-Refresh?node-id=487%3A5261)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: @Tinaliseng @ctsang-ext  
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Updated minimal header navigation layout
- [ ] UI skin navigation with new brand guidelines

## Out of scope
What is out of scope and not part of this iteration?

- Footer navigation
- Content blurbs for navigation items

## 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
Linked in Event Tracking for Gated Asset download

## Goal
Follow up from https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/238. 

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.

* Gated Asset download- `window.lintrk('track', { conversion_id: 1111282 });`

* PathFactory form submit event is hardcoded for GA. Would it be possible to add the LinkedIn conversion event code for Gated Asset right below this line? `ga('send', 'event', 'forms', 'submit', 'PathFactory');` ![Screen_Shot_2022-02-24_at_11.20.51_AM](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/d9c889c5c0392d6e1eddfa479ccc2dcd/Screen_Shot_2022-02-24_at_11.20.51_AM.png)

### Jobs To Be Done
* **Situation**: *When we want to track Gated Asset downloads*
* **Motivation**: *We want to add LinkedIn conversion codes*
* **Outcome**: *So we can efficiently track the clicks of our users' data*

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @dennis106 `
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Follow-up from "Resolve "Launch Darkly Integration""

The following discussion from !230 should be addressed:

- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/230#note_853364600):  (+1 comment)

    > **Suggestion:** Provide URL parameters that enable a reviewer to view both versions of an experiment. 
    > 
    > For example, in www-gitlab-com you can use `?experiment-review-control` to view the control variant
    > and ?`experiment-review-test` to view the test variant.
    > 
    > I'd consider this non-blocking @jgarc ... but we should address it in the next iteration.

NOT IN SCOPE

- [ ] https://docs.launchdarkly.com/home/code/gitlab

Story points: 3.0
UX: Homepage refresh for SKO / Add new brand

## Goal
Apply the new brand guidelines provided by Gold Front to a homepage design for the Sales Kick Off.

## Page(s)
Which page(s) are involved in this request?
* Homepage - Fimga mock only (no engineering required)

## Workfiles
- [Figma Mocks](https://www.figma.com/file/CgCuf1LVuEZH8DEijhAzCt/Home-Page-Refresh?node-id=0%3A1)

## Documents
- [Jam 3 Homepage brief](https://docs.google.com/document/d/1lu9-Izo7j1RG22hlxW4SdJyuepxdUGGbd8CCOvPweRs/edit#heading=h.n4tqr0k7lvyy)
- [Brand guides - PDF](https://drive.google.com/file/d/1zbHfV90kxI_PgTUXixEs-6p7F4VAGg7Y/view?usp=sharing)
- [Grand guides - Figma](https://www.figma.com/file/36n655EAUGJPz2DEwrjrOo/2022-GitLab---Brand-Design-Guidelines?node-id=2156%3A29)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran @ctsang @mpreuss22 
- [ ] 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:

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering

Story points: 4.0
Create GA View to track Customer Portal and other purchasing flows

<!-- Please submit issue with the following format: As a _____ (role in marketing), I would like to ____________(need), so that ________________(reason).-->
<!-- Example: As GTM management, I would like to know that all Trials are MQLing, so that MQL metrics are accurate and we can rely on them for decision making.-->

## As a team focused on customer self-service transactions, I would like a dedicated GA View to provide fast reporting on trial and checkout flows without having to set up custom reports or drill down many levels.

# What we need to know:

## The problem

The Self-Service team would like to track sessions, pageviews, and events (clicks) on the areas of our marketing site and customer portal that our customers use to subscribe and grow. These areas of the site get relatively less traffic compared to marketing and handbook pages, and so are more challenging to report on using the default GA view.

## What specific questions do we need to answer?

- General default GA reporting (Audience, Acquisition, Content, Events) but specific to these parts of the site/customer portal

## What are your must-have's?

These subdomains and pages:

Subdomain:

* customers.gitlab.com

Pages within gitlab.com (regex match):

* /-/subscriptions
* /-/profile/usage_quotas
* /-/usage_quotas
* /trials/
* /pricing/
* /sign_up
* /trial_registrations/

## Do you have any specific metrics, categories or charts in mind?

No, standard GA

## Context

- Audience: Internal GitLab team members, especially Self-Service, Product Intelligence
- When will this likely deliver business value? Immediately
- Due date: ASAP
- Format: GA View


<!-- Please leave the label below on this issue -->
Related to gitlab-com/marketing/marketing-strategy-performance#612.

Story points: 1.0
retire-js-dependency_scanning

## Goal
We would like to retire-js-dependency_scanning in the www-gitlab-com pipeline.

### Jobs To Be Done
* **Situation**: *When any MR is merged with master it throws errors*
* **Motivation**: *We want to reduce these errors because the job is depreciated*
* **Outcome**: *So we can improve efficiency*

https://gitlab.slack.com/archives/CVDP3HG5V/p1645467364747489

Story points: 1.0
FAQ Schema

## Goal
We would like to enable FAQ schema on the Buyer Experience repository.

### Jobs To Be Done
* **Situation**: *When someone visits a page built with the Buyer Experience repository, FAQ Schema displays if data exists in the `yml` file.*
* **Motivation**: *We want to improve SEO*
* **Outcome**: *This was implemented on topics and solutions pages in www-gitlab-com to make search engine better understand page contents and display the pages in the form of Rich Snippets in SERPs.*

## Page(s)
Which page(s) are involved in this request?
* Topics
* Solutions

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Enabling FAQ schema in the buyer experience repository
- [ ] Configuring FAQ schema for existing topic pages
- [ ] Configuring FAQ schema for solution pages

## Out of scope
What is out of scope and not part of this iteration?

- www-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:

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 6.0
Regression - Border around hero image on Solutions

## Goal
We would like to remove the grey border that exists around the hero image on https://about.gitlab.com/solutions/digital-transformation/.

https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/9e554ab3ae6df8c70efd3d41e2a11d7c/Screen_Shot_2022-02-18_at_14.14.02.png

## In scope
What is within scope of this request?

- [ ] Remove border

## 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
Slp-button / link regression

Noticed this on the topics children pages. Not sure if any other pages fall under this scope.

Currently:
![image](/uploads/3a797b3136cb3e7ea880d827742be17b/image.png)

Previous:
![image](/uploads/0b67db3f49de63a0a131279bafa1b8a9/image.png)

Story points: 1.0
Add import button GTM events in the combined groups/projects form

## Goal

This issue is related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/361, which will be closed with https://gitlab.com/gitlab-org/gitlab/-/merge_requests/81035.

The combined groups/projects form is [now a part of the free trial flow](https://docs.google.com/presentation/d/17e-EyBU7gHIZb_C0LrTfAuncLQW6q4LsuqIQ5qh0FTo/edit#slide=id.g110748f05b3_0_42).

The [old spec](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/63d466fbba4fca773f6c5a2a356a37c8/Gitlab_GTM_DataLayer_Spec_for_Free_Trial.pdf) had events handled separately for group/project forms. Now we need to combine them. 

### Jobs To Be Done

* **Situation**: *When a user goes through the sign up flow*
* **Motivation**: *We want to track the import project GTM events*
* **Outcome**: *So we can measure free trials and other form interactions against Google Analytics data*

## Page(s)

Which page(s) are involved in this request?
* `gitlab.com/users/sign_up/groups_projects/new`

## DCI

[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @tywilliams 
- [ ] Consulted: @dennis106 @gdoud 
- [ ] Informed: @mpreuss22 

## In scope

Add the `saasTrialProjectImport` events to those buttons. But as we did in https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/361, we should change this event to `projectImport`, since the form is shown to regular user sign ups as well as trial sign ups. 

We can use the `trial_onboarding_flow=true` parameter in the URL to filter against true/false. 

I will preserve the other data points and track `'projectImport': '[PLATFORM]'` as we were before for which platform people click. 

## 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
- [x] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 4.0
ENG: /company/culture page is trying to render from Nuxt even though it only exists in www

Because we have a /company/culture/all-remote page, Nuxt thinks that [/company/culture](https://about.gitlab.com/company/culture/) is an existing path even though we technically don't have a page for that created in this repository. It currently is rendering the Free Trial CTA when I think it should be rendering the page from www-gitlab-com.

We should be able to add 'content/company/culture' to the route.ignore.js file in our project.

Story points: 1.0