giseldo/neodataset huggingface dataset:
Page anchors creating internal redirects

Our SEO Auditing tools have detected an increase in internal redirect links caused by missing trailing slash `/` on anchored links. The pages identified all have a drop down menu when viewing on a mobile device.

Everytime a search engine bot encounters a redirect it decreases our crawl budget. This may run out before search engines can crawl updated or newly created pages we want to get indexed.

### Pages affected 
- https://about.gitlab.com/stages-devops-lifecycle/
- https://about.gitlab.com/support/
- https://about.gitlab.com/get-help/

### Page source example 
(snippet from https://about.gitlab.com/stages-devops-lifecycle/)
```
<div class="side-menu" data-v-24faf1f9 data-v-1e8cac17>
   <!----> 
   <ul class="side-menu__list" data-v-24faf1f9>
      <li class="side-menu__item" data-v-24faf1f9>
         <div class="side-menu__item__container" data-v-24faf1f9>
            <a href="/stages-devops-lifecycle#manage" data-ga-name="manage" data-ga-location="header" class="side-menu__link" data-v-24faf1f9>Manage
            </a> 
            <div class="side-menu__line" data-v-24faf1f9></div>
         </div>
         <!---->
      </li>
      <li class="side-menu__item" data-v-24faf1f9>
         <div class="side-menu__item__container" data-v-24faf1f9>
            <a href="/stages-devops-lifecycle#plan" data-ga-name="plan" data-ga-location="header" class="side-menu__link" data-v-24faf1f9>Plan
            </a> 
            <div class="side-menu__line" data-v-24faf1f9></div>
         </div>
```

The link URL should be `<a href="/stages-devops-lifecycle/#manage"`

Story points: 2.0
Create Direct Link to Pricing Page FAQs

## Goal
I have done research into salient events towards conversion of our product. Expanding the pricing page FAQs was **highly predictive** at my initial pass, so much so I believe it would be worthwhile to create a direct link to the FAQs on the pricing page. This would enable customers to be able to share it easier with others and also arrive at this important state easier. 

- Ex: `https://about.gitlab.com/pricing?FAQs/`

### Jobs To Be Done
* **Situation**: We do not have a direct link to the pricing page FAQs
* **Motivation**: Try to improve the number of purchases of our product
* **Outcome**: Create a direct link to the pricing page FAQs to drive traffic directly to these important locations on our pricing page to increase purchase rates.

## Page(s)
Which page(s) are involved in this request?
* [Pricing Page](https://about.gitlab.com/pricing/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpreuss22 
- [x] Consulted: @mpreuss22 
- [x] Informed: @mpreuss22 


## 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
404 Error page in XMLSite

There is a 404 error page in the buyer experience XML sitemap file.

**URL:** https://about.gitlab.com/undefined/
**Sitemap:** https://about.gitlab.com/buyer-experience/sitemap.xml

```
<url>
<loc>https://about.gitlab.com/undefined/</loc>
</url>
```

The XML Sitemap should only contain URLs we wish for search engines to index. URLs in our sitemaps should be clean - i.e. sitemaps should only include URLs that are HTTP status 200 (OK), indexable, canonical and unique. If search engines find 'dirt' in sitemaps, such as 404 pages, they may stop trusting the sitemaps for crawling and indexing signals.

Story points: 1.0
ENG: Migrate support child pages

## Goal
We would like to migrate all Support subpages to the Buyer Experience repository.

https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/sites/uncategorized/source/support 

### Jobs To Be Done
* **Situation**: *We need all support pages to exist in a single place*
* **Motivation**: *We want to make it efficient for managing content*
* **Outcome**: *So we can be efficient*

## Page(s)
Which page(s) are involved in this request?
* All child pages that exist in this directory: https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/sites/uncategorized/source/support

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Create all child support pages
- [ ] Remove child support pages from 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:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Support: controls and ownership

## Goal
We would like to add introduce appropriate controls and ownership to the support page.

### Jobs To Be Done
* **Situation**: *When an change is made to the support page*
* **Motivation**: *We want to ensure content owners approve the change*
* **Outcome**: *So we can make adjustments to the text as required*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @laurenbarker 
- [ ] Consulted: @jcolyer @mpreuss22 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] [Add codeowners feature](https://docs.gitlab.com/ee/user/project/code_owners.html) to Buyer Experience repository
- [ ] Place @jcolyer and @tcooney as owners of support page content
- [ ] Add @jcolyer and @tcooney as project maintainers
- [ ] Remove existing support page from www-gitlab-com to ensure SSoT for content

## 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
Move hardcoded Bizible script into the head tag

## Goal
We would like to move the Bizible tag implemented on trial and signup pages to the head tag, which should ensure the tag fires first and [referral information is not missed as advised by Adobe](https://experienceleague.adobe.com/docs/bizible/using/bizible-tracking/setting-up-tracking/adding-bizible-script.html?lang=en).

### Jobs To Be Done
* **Situation**: *When a trial or signup page is loaded*
* **Motivation**: *We want to track that view, with referral information captured in Bizible*
* **Outcome**: *So we can attribute marketing and particularly paid demand gen activity to new trial and signups*

## Page(s)
Which page(s) are involved in this request?

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)
* https://customers.gitlab.com/customers/sign_in

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @miraclebanks 
- [ ] Consulted: @laurenbarker @jahye1 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Adding the Bizable script to the pages listed above towards the bottom of the head tag

NOTES: 
- [Adobe implementation doc](https://experienceleague.adobe.com/docs/bizible/using/bizible-tracking/setting-up-tracking/adding-bizible-script.html?lang=en)

## 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: 4.0
Pricing Page schema.org markup

**Schema Type:** Product - https://schema.org/Product

**URL:** https://about.gitlab.com/pricing/

**Markup**
```
<script type="application/ld+json">
	{
  	"@context": "https://schema.org/",
  	"@type": "Product",
  	"name": "DevOps Platform",
  	"description": "A DevOps platform combines the ability to develop, secure, and operate software in a single application so everyone involved in the software development process -- from a product manager to an ops pro -- can seamlessly work together to release software faster.",
  	"audience": "Ops Pro,Security, Testers, Product Managers, Product Designers, Finance, The Legal Team",
"sku": "",
  	"mpn": "",
  	"brand": {
    	"@type": "Corporation",
    	"name": "GitLab",
"logo": "https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo.png"
  	},
  	 "offers": [{
    "@type": "Offer",
    "name": "DevOps Platform - Free Plan",
    "Price": "0.00",
    "priceCurrency": "USD"
  },{
    "@type": "Offer",
    "name": "DevOps Platform - Premium Plan - Billed Annually",
   "Price": "228.00",
    "priceCurrency": "USD"
  },{
    "@type": "Offer",
    "name": "DevOps Platform - Ultimate Plan - Billed Annually",
    "Price": "1188.00",
    "priceCurrency": "USD"
  }
    ]}
    </script>
```

Story points: 1.0
Homepage Schema.org markup

**Schema type:** Corporation Schema (https://schema.org/Corporation) - updating existing Organization schema to Corporation Schema

**URL:** https://about.gitlab.com/ only

The ticker symbol is the biggest difference between Organization schema and corporation schema

New Fields Added:
- tickerSymbol
- Description
- Slogan
- Awards
- KnowsAbout

```
{"@context":"https://schema.org",
"@type": "Corporation",
"name":"GitLab",
"legalName":"GitLab Inc.",
"tickerSymbol":"GTLB",
"url":"https://about.gitlab.com",
"logo":"https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo.png",
"description" : "GitLab is The DevOps platform that empowers organizations to maximize the overall return on software development by delivering software faster and efficiently, while strengthening security and compliance. With GitLab, every team in your organization can collaboratively plan, build, secure, and deploy software to drive business outcomes faster with complete transparency, consistency and traceability.

GitLab is an open core company which develops software for the software development lifecycle with 30 million estimated registered users and more than 1 million active license users, and has an active community of more than 2,500 contributors. GitLab openly shares more information than most companies and is public by default, meaning our projects, strategy, direction and metrics are discussed openly and can be found within our website. Our values are Collaboration, Results, Efficiency, Diversity, Inclusion & Belonging , Iteration, and Transparency (CREDIT) and these form our culture.",
"foundingDate":"2011",
"founders":[{"@type":"Person","name":"Sid Sijbrandij"},
{"@type":"Person","name":"Dmitriy Zaporozhets"}],
"slogan": "Our mission is to change all creative work from read-only to read-write so that everyone can contribute.",
"address":{"@type":"PostalAddress","streetAddress":"268 Bush Street #350","addressLocality":"San Francisco","addressRegion":"CA","postalCode":"94104","addressCountry":"USA"},
"awards": "Comparably's Best Engineering Team 2021, 2021 Gartner Magic Quadrant for Application Security Testing - Challenger, DevOps Dozen award for the Best DevOps Solution Provider for 2019, 451 Firestarter Award from 451 Research",
"knowsAbout": [
    {
      "@type": "Thing",
      "name": "DevOps"
    },
    {
      "@type": "Thing",
      "name": "CI/CD"
    },
{
      "@type": "Thing",
      "name": "DevSecOps"
    },
{
      "@type": "Thing",
      "name": "GitOps"
    },
{
      "@type": "Thing",
      "name": "DevOps Platform"
    }
  ],

"sameAs":["https://www.facebook.com/gitlab",
"https://twitter.com/gitlab",
"https://www.linkedin.com/company/gitlab-com",
"https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg"]}</script>
```

Story points: 1.0
Tracking: Vimeo Video

## Goal
Vimeo video dataLayer events (load, play, progress, complete) are not firing on certain pages (ie. Home, Demo). The configuration on Google Tag Manager appears to be setup properly. I think the culprit is from this JS error on the Home page:
<br/>
<img src="/uploads/bc0156e623619e8c4dafeb9ffb9af8a1/Screen_Shot_2022-04-01_at_3.55.57_PM.png" width="600">

<br/>
I do not see the JS error on other pages where Vimeo is firing data properly (ie. /company/history/)
<br/>
<img src="/uploads/cd9b454dc830d7d29b93b3c07a7b1699/Screen_Shot_2022-04-01_at_3.53.06_PM.png" width="600">

### Jobs To Be Done
* **Situation**: When Vimeo video loads...
* **Motivation**: We want to ensure dataLayer events from Vimeo are firing on video load, play, progress, and complete...
* **Outcome**: So we can analyze video engagements, specially on the Home page since it's the first media a user sees.

## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com
* about.gitlab.com/demo/
* etc.

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dennischarukulvanich 
- [ ] Consulted: @mpreuss22 
- [ ] Informed: @ndubord 


## 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: 6.0
ENG: Additional updates to Why GitLab? page

Follow up to #363.

[Figma link](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab?node-id=485%3A6505#174109306)

## Work done as part of this issue
This page is probably best if approached by building the individual sections

- [x] Hero (Megan)
- [x] Small CTA section ('GitLab is unlike anything...') w/ two buttons and image (Tyler)
- [x] GitLab vs. xxxx section (GitHub, Atlassian, JFrog) (Megan)
- [x] Take the next step CTA section. This CTA component is possibly being built as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/593). Not sure if it will be the exact layout though!

Story points: 10.0
ENG: Solutions - By Solution -Hero

## Goal
Create the for the `no-image` Hero section in Solutions- By Solution pages.

Includes the Hero Section with gradient background and the infinity image and also de responsive behavior.

First prototype -> https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/delivery-automation
* https://about.gitlab.com/solutions/continuous-software-security-assurance
* https://about.gitlab.com/solutions/continuous-software-compliance
* https://about.gitlab.com/solutions/devops-platform/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @laurenbarker, @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Solutions - By Solution - Hero Section

## Out of scope
What is out of scope and not part of this iteration?

- Any other 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
ENG: Blog refresh

Based on the meeting documented in https://docs.google.com/document/d/19WfMAXKmZ47baUMwUStFSveOufb03x7aUCf42CuU76g/edit#, we really need to make sure the Blog landing page and blog posts get the refresh styles coming through with the rebrand. 

This issue will track that work, and may be promoted to an epic if need be.

At a high level, here's what I think needs to happen:

- [x] Update the fonts on landing page
- [x] Update the fonts on blog posts
- [x] Grab Inter fonts from Google Fonts
- [x] Remove old colors on landing page
- [x] Update new colors on landing page
- [x] Remove old colors on blog posts
- [x] Update new colors on blog posts
- [x] Isolate changes by pulling them out to a separate style sheet and loading it in those templates (just cleanup work, really)
- [x] Check for substantial regressions and fix them

### Changes from @jhalloran on 2022-04-04

Figma file: https://www.figma.com/file/HdsUOq4gDMjaI1kkhwUWNN/Blog-LP-Refresh?node-id=5%3A1421

I'll come through and enumerate those as well. 

Then I'll loop in @mpreuss22 and @jhalloran to make sure I'm on the right track. Finally I'll reach out to @vsilverthorne to let her know what's getting impacted (there should be no workflow change - just a change in the output of these pages). 

I'm going to start from https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/merge_requests/168, which is the brand update in the Slippers repository, and identify what changes I can make over in https://gitlab.com/gitlab-com/www-gitlab-com to match those.

MR for this will be at https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101723 to start. I think we can get this done in one.

#### Blog landing page

- [x] Change "Subscribe" title to "sign up for GitLab's twice-monthly newsletter"
- [x] Add form field label for "Enter your email address" (Requested in https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6274)
- [x] Add "abc@xyz.com" placeholder text (Requested in https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6274)
- [x] Add title copy to search bar "Search the blog"
- [x] Update search placeholder copy to "search"
- [x] Add YouTube social option (figma file says LinkedIn, but we already had that)
- [x] Add hover states

#### Blog post template

- [x] Add a label for the newsletter field and update placeholder text (Requested in https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6274)
- [x] Match the landing page social icons
- [x] Fix the SVG fill on the social icons to be `#171321`
- [x] Add hover state to CTA

Story points: 6.0
ENG: Solutions - By Company Size - Start Up

## Goal
We would like to X which will improve Y as measured by Z.

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 2.0
UX: Resources - skin Demo, Releases, Analysts, Webcasts

## Goal
We would like to skin our resource pages with our new branding, which will improve consistency, as measured by reduced drop off.

### Jobs To Be Done
* **Situation**: *When visiting our resource pages...*
* **Motivation**: *our customers want to feel like they are on the same website...*
* **Outcome**: *So they can be assured they are in the right plavce.*

## Page(s)
Which page(s) are involved in this request?
* [Releases page](https://about.gitlab.com/releases/)
* [Webcasts page](https://about.gitlab.com/webcast/)
* [Analysts page](https://about.gitlab.com/analysts/)
* [Demo page](https://about.gitlab.com/demo/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Skinned MVC1 version of each page

## 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: 6.0
UX: Format Jam3 Pricing page to Slippers UI

## Goal
We would like to update our pricing page with new branding which will improve how we sell ourselves as a company as measured by increased sales.

### Jobs To Be Done
* **Situation**: *When we are shifting to a new brand...*
* **Motivation**: *We want to update the pricing page to reflect these changes...*
* **Outcome**: *So we can communicate our value as an Enterprise software company.*

## Page(s)
Which page(s) are involved in this request?
* [Pricing page Figma designs](https://www.figma.com/file/4CkayJDu97uNEWBOlgABwE/Pricing-Refresh-2022-04-01?node-id=0%3A1)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: @mpenagos-ext 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Desktop and Mobile pricing page skinned mocks

## 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: 4.0