giseldo/neodataset huggingface dataset:
Automate Schema Generation for Blog Posts

## Goal
We would like automate the generation of schema for blog posts.

@hsmith-watson provided a example of the schema markup to be generated [here](https://gitlab.com/gitlab-com/marketing/inbound-marketing/seo/-/issues/354#note_1307806277). Pasting it below as well. 

```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://about.gitlab.com/blog/2023/03/01/how-to-deploy-react-to-amazon-s3/"
  },
  "headline": "How to deploy a React application to Amazon S3 using GitLab CI/CD",
  "description": "Follow this guide to use OpenID Connect to connect to AWS and deploy a React application to Amazon S3.",
  "image": "https://about.gitlab.com/images/press/logo/png/gitlab-logo-500.png",
  "keywords":"DevOps, CI/CD",
  "articleSection":"Engineering",
  "timeRequired":"PT11M",
  "author": {
    "@type": "Person",
    "name": "Jeremy Wagner",
    "url": "https://about.gitlab.com/company/team/#jeremywagner"
  },  
  "publisher": {
    "@type": "Organization",
    "name": "GitLab",
    "logo": {
      "@type": "ImageObject",
      "url": "https://about.gitlab.com/images/press/logo/png/gitlab-logo-500.png"
    }
  },
  "datePublished": "2023-03-01",
  "dateModified": "2023-03-01"
}
</script>
```

#### 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?
* All blog posts generated by the www repo


## In scope
What is within scope of this request?

- [ ] Adding code to blog post template to generate schema
- [ ] Collaborating with @hsmith-watson to verify and iterate on this MVC 1 implementation


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: `@justin.vetter @laurenbarker`
- [ ] Informed: `Everyone`

Story points: 4.0
[ENG] Localized French and Japanese Sales Landing page

## Goal
We would like to create a localized French and Japanese sales landing page to the Buyer Experience repository. This will enable use to explore the full lifecycle of localizing a page to multiple langauges. 

- https://about.gitlab.com/fr-fr/sales 
- https://about.gitlab.com/ja-jp/sales 

#### Jobs To Be Done
* **Situation**: *When a user visits `/fr-fr/sales` or `/ja-jp/sales`  the see a french/japanese version of our sales page*
* **Motivation**: *We want to learn what the level of effort is to host localized versions of our BE pages in 3 languages*
* **Outcome**: *So we can make informed decisions about our technical localization strategy *

#### 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 @djsulliv 
- [ ]  No

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - Work with MarketingOps to identify french and Japanese versions of our sales form
 - Create a french version of our sales page in Buyer Experience
 - Create a Japanese version of our sales page in Buyer Experience
 - Have this page ignored by our Swiftype search tool
 - Have this page ignored by all search engines (IE Google)


**What analytics / data will we need to set-up?**
- [ ] Yes: We'll sync with @dennischarukulvanich on this once review app is up
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/fr-fr/sales 
* https://about.gitlab.com/ja-jp/sales 

## 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?

- [ ] New Japanese sales page 
- [ ] Contact sales goes to Japanese form
- [ ] New french sales page 
- [ ] Contact sales goes to french form

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 6.0
Globalization for DEX Handbook Documentation

## Goal
We would like create handbook documentation for the globalization of our GitLab Marketing site.

## In scope
What is within scope of this request?

- [ ] How to request translation jobs in Smartling
- [ ] How to view completed translations
- [ ] How building our own localized pages works (/de-de/sales)
- [ ] Removing outdated localization information
- [ ] More TBD


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: `@justin.vetter @laurenbarker @fqureshi`
- [ ] Informed: `Everyone`

Story points: 1.0
Tier 1 pages - German

## Goal
We would like translate tier 1 pages in Smarting to German and have these translated pages display on our https://globalization-test.about.gitlab-review.app/ domain.

#### 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 will need a Smartling translation job completed

| Tier 1 Pages to Update                   |
|--------------------------------------------|
| https://about.gitlab.com/  (completed)                 |
| 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: @lduggan 
* [ ] Consulted: @laurenbarker 
* [ ] Informed: Everyone

Story points: 3.0
[ENG] Personalizing Navigation with Demandbase

## Goal

To utilize the [Demandbase API](https://support.demandbase.com/hc/en-us/sections/360011444531-API-Documentation) serve a personalized navigation if the visitor is coming from an Enterprise or SMB organization.

If the user is identified as Enterprise, we'll display a MVC to the navigation that results in increased engagement and conversions.

The goal of the issue is for the UX team to research the best strategy for personalizing the navigation if visitors are identified as an Enterprise or SMB visitor. From that research, then design a MVC personalized nav for enterprise visitors


#### 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?
* Navigation

## Include any Figma files
* [Figma](https://www.figma.com/file/bJIgvb89G5V7o1nubmDEMk/Demandbase-nav?node-id=0%3A1&t=EJjBDmdulOHRnEkK-1)

## In scope
What is within scope of this request?

- [x] Build the customized navigation
- [x] Verify it goes to production


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: `@justin.vetter @laurenbarker @fqureshi`
- [ ] Informed: `Everyone`

Story points: 3.0
[ENG]: Refactor ROI calculators

To get the Time ROI calculator up and running quickly, I made a completely separate component from the Cost ROI calculator. If one calculator needs some CSS changed, you'd have to go into the other calculator's file and make that match as well.

I'd like to set aside some time to refactor the component to improve future developer experience, reusability, and ultimately minimize file page size.

Setting this as 4 points to focus on other critical issues in this iteration, but I'm happy to up those points if I end up getting a bigger window of time!

Story points: 4.0
[ENG] Add accordion navigation header to Pricing page FAQ

## Goal
We would like to add the accordion navigation header to Pricing page FAQ which will improve discoverability as measured by increased clicks/scroll depth.

#### Jobs To Be Done
* **Situation**: *When a user needs more information about pricing...*
* **Motivation**: *We want to help them navigate quickly to the question they have...*
* **Outcome**: *So we can help them decide on their purchase.*

#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

**If this is urgent, what is the business need for the urgency?**
- [ ]  Yes: `what is the business need for the urgency`
- [x]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes `@personshandle`
- [x]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`

**What is the ultimate end goal vision vs the MVC1 iteration?**
 - `End goal for this MVC iteration is adding the accordion navigation header to Pricing page FAQ`

**How do we measure success?**
 - `Please describe how success will be measured`
 - Increased purchases

**What analytics / data will we need to set-up?**
- [x] Yes: `Please describe what analytics will need to be set up` Clicking on the items in the nav 
- [ ] No

## 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: `GitLab Handle`
- [ ] Consulted: @jhalloran @justin.vetter @fqureshi 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] ENG of pricing page FAQ

## 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
Some links on GitLab Learn page don't have working links to Levelup

## Goal
Some of the course links to LevelUp include an OIDC link that errors when the user clicks the link. These hyperlinks need to be corrected. 

#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

#### Please provide more information related to this request
When trying to click on the "Getting Started with GitLab Learning Path," the browser (chrome on MacOS) returns an OIDC error. Looking at the URL it appears to be malformed (https://levelup.gitlab.com/access/openId/login?returnTo=https://levelup.gitlab.com/learn/learning-path/getting-started-with-gitlab). I looked at the source page (buyer-experience/content/learn/index.yml) and it appears some other links have this same issue. 

**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`
- [ ] 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?**
 - If every link within the learn page is clickable and brings the client to the proper page. 

**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?
* `https://about.gitlab.com/learn/?Registration=Free`
* source: `https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/learn/index.yml`

## 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: 2.0
Pricing changes Go live TBD

## Go live TBD

## Goal
Update pricing to reflect pricing update on April 3rd. This includes unhiding some elements on the marketing site during the transitionary period.

## Scope
- [ ] Update Premium price on /pricing tier cards
- [ ] Update Premium price on /pricing `Compare all features` accordion
- [ ] Add pricing back to /pricing/feature-comparison page
- [ ] Update Premium price on /pricing/feature-comparison page

Story points: 1.0
[ENG] Remove A/B Test and Navigation Variants

## Goal
We would like to remove the remove the multivariate navigation test from production, launch darkly, and the navigation project. 

#### Jobs To Be Done
* **Situation**: *When a user looks at the marketing site, there is one navigation variant available*
* **Motivation**: *We want to ensure we're not loading extra code into the browser.*

#### 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: `We need this completed before new homepage illustration are released 2023-03-07`
- [ ]  No

If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.

**Does anyone in leadership have eyes on this project?**
- [ ]  Yes @laurenbarker 
- [ ]  No

## In scope
What is within scope of this request?

- [ ] Remove nav test from launch darkly
- [ ] Remove nav test from Buyer Experience 
- [ ] Remove nav variants from navigation repository
- [ ] Verify nav variants are removed when next nav release out 

## 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
Startup Page Analytics Tracking

## Goal
Implement data attributes for click tracking
- Update the `data-ga-name` for all `learn more` links to the destination's name. For example, the `learn more` link in the "One platform for the entire lifecycle" card should have `data-ga-name="platform plan"`
- Add `data-ga-name="customers" data-ga-location="customers"` to "view more stories"
- Add `data-ga-name="startup join" data-ga-location="body"` to "Gitlab for startup programs" 
- Add `data-ga-name="roi calculator" data-ga-location="body"` to "roi calculator" 


#### 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?**
- [x]  Yes: This page just launched today, and there will be questions from stakeholders about the page's performance.  
- [ ]  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 @justin.vetter
- [ ]  No

**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`


**What analytics / data will we need to set-up?**
- [x] Yes: see goal section
- [ ] No

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/startups/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @dennischarukulvanich 
- [ ] 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
- [ ] Engineering

Story points: 1.0
[ENG] Add missing Subscription link

## Goal
Add missing Gitlab Subscription Agreement link https://about.gitlab.com/handbook/legal/subscription-agreement/

![Screenshot_2023-03-01_at_18.21.54](/uploads/bb7a0a057f1c5eaa34a9349e38126b59/Screenshot_2023-03-01_at_18.21.54.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?
* [Startups Join](https://about.gitlab.com/solutions/startups/join/)


## In scope
What is within scope of this request?

- [ ] Add missing link
- [ ] Deliverable 2


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpenagos-ext 
- [ ] Consulted: @justin.vetter @fqureshi
- [ ] Informed: `Everyone`

Story points: 1.0
[ENG] Update Home page hero images

## Goal
We would like to update the home hero with new illustrations. This will require a bit of work to our current hero to move some UI elements around.

![CleanShot_2023-03-01-2](/uploads/b2db01e6cfe301548faee331537c3ba3/CleanShot_2023-03-01-2.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?
* [Home page](https://about.gitlab.com)

## Include any Figma files
* [Figma](https://www.figma.com/file/Hy5ukNc5gEF9Khp2LXiP94/Carousel-w%2F-new-illustrations?node-id=62%3A1855&t=O14ouJ7dT1oopZgq-0)

## Include any graphic or design assets
* [Home_illustrations.zip](/uploads/c99d4547c195383d779ac09fb4739da1/Home_illustrations.zip)

## In scope
What is within scope of this request?

- [ ] Modify UI to handle new layout for images
- [ ] Add three new illustrations to home hero


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @fqureshi @jhalloran
- [ ] Informed: `@amittner @mpreuss22`

Story points: 5.0
[ENG] Create New Customer Case Studies article template

## Goal
We would like to create a new Customer Case Studies Article template in BE. This template will be used for all new Case Studies moving forward. The yml structure should be clean to allow the content team to manage the articles.

#### 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?
* [Example from WWW](https://about.gitlab.com/customers/fullsave/)

## Include any Figma files
* [Figma WIP](https://www.figma.com/file/IuGKYwvDxu7PEm9jsQhUrb/Customers-refresh-%2F--MVC-1?node-id=218%3A38060&t=PFVZ9KHah6oXdIjj-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?

- [ ] Create new case studies article template
- [ ] Deliverable 2

## Not in scope

- Migrating legacy case studies to new template.


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @Tinaliseng @fqureshi @jhalloran 
- [ ] Informed: `Everyone`

Story points: 6.0
[ENG] Create Browse all Customer Case Studies Page

## Goal
We would like to create a Browse all Customer Case Studies page 

#### 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?
* [Browse All Case Studies](https://about.gitlab.com/customers/all) *Need final URL*

## Include any Figma files
* [Figma WIP](https://www.figma.com/file/IuGKYwvDxu7PEm9jsQhUrb/Customers-refresh-%2F--MVC-1?node-id=200%3A17833&t=PFVZ9KHah6oXdIjj-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?

- [ ] Create a Filterable page to browse all Customer Case Studies
- [ ] Deliverable 2

## Not in scope

- Creating refreshed Customers page


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @Tinaliseng @fqureshi
- [ ] Informed: `Everyone`

Story points: 3.0
[ENG] Customer Case Studies Page refresh

## Goal
We would like to refresh the Customer Case study page.

#### 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?
* [Customers](https://about.gitlab.com/customers/)

## Include any Figma files
* [Figma WIP](https://www.figma.com/file/IuGKYwvDxu7PEm9jsQhUrb/Customers-refresh-%2F--MVC-1?node-id=200%3A17833&t=PFVZ9KHah6oXdIjj-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?

- [ ] Refresh Customers page
- [ ] Deliverable 2

## Not in scope
- Creating Browse all page


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @fqureshi @Tinaliseng 
- [ ] Informed: `Everyone`

Story points: 8.0