giseldo/neodataset huggingface dataset:
UX: Template for Solutions page - by industry / by department

## Goal
We would like to have a template for our Solutions `by industry` pages which will improve consistency of information as measured by increased GitLab accounts created. We will use the same template for the `by department` pages.

### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand what solutions we offer for their industry ...*
* **Outcome**: *So they can decide if we are the right product for their needs.*

## Page(s)
Which page(s) are involved in this request?
* [Figma Template](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A1765)


New pages that will use this template:

**by Industry**
- Finance
- Retail
- Public Sector
- Technology

## Workfiles
* [JTBD Template](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=69%3A2485)

**by Department**
* Engineering
* Product Management
* IT
* QA/Testing

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Reusable UX template for Solutions by industry pages

## 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: 1.0
UX: Template for Solutions page - by solution

## Goal
We would like to have a template for our Solutions pages which will improve consistency of information as measured by increased GitLab accounts created.

### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand what solutions we offer that could help their business ...*
* **Outcome**: *So they can decide if we are the right product for their needs.*

## Page(s)
Which page(s) are involved in this request?
* [Figma Template](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A722)

New pages that will use this template:
- Delivery Automation
- Continuous Software Security Assurance
- Continuous Software Compliance

## Workfiles
- [Figma JTBD templates](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=69%3A2485)
- [WIP AI spreadsheet](https://docs.google.com/spreadsheets/d/1ualGLPCyFjEpiskrfAe2ftqoTAw8t56lO1LMzMT7Ojo/edit?usp=sharing)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Reusable UX template for Solutions pages

## 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: 1.0
UX: Template for individual feature page

## Goal
We would like to have a consolidated template for our individual feature pages which will improve consistency of information as measured by increased GitLab accounts created.

### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand each of the main features of GitLab's product ...*
* **Outcome**: *so they can decide if we are the right product for their needs.*

## Workfiles
Which page(s) are involved in this request?
* [JTBD Template](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=38%3A263)
* [V1 Mock - skinned template](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=173%3A596)


New pages that will use this template:
- Continuous Integration ([Existing page](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/))
- Source Code Management ([Existing page](https://about.gitlab.com/stages-devops-lifecycle/source-code-management/))
- Security Training
- Security Dashboards
- Code Owners
- Code Search
- Roadmaps
- Vulnerability Management
- Epic & Issue Boards
- Merge Trains
- Licenses Compliance

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Reusable UX template for individual features pages

## 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: 8.0
Deploy script for buyer experience that deletes pages

## Goal
We would like to iterate on our deploy script to remove files from GCP if the page was been deleted from the Buyer Experience repository.

### Jobs To Be Done
* **Situation**: *When a page is deleted from the Buyer Experience repository*
* **Motivation**: *We want to delete it form our GCP bucket*
* **Outcome**: *So we can ensure the URL is no longer discoverable*

## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/scripts/deploy#L69

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Iterating on our deploy script to remove files from our GCP bucket

## Out of scope
What is out of scope and not part of this iteration?

- 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: 6.0
Mermaid Charts Integration

## Goal
We would like to integrate mermaid chart functionality into the Buyer Experience repository.

### Jobs To Be Done
* **Situation**: *When we migrate pages to this repository that contain mermaid charts, we can implement them.*
* **Motivation**: Mermaid chart are used extensively in the www-gitlab-com repository.*
* **Outcome**: *So we can increase efficiency for migrating pages to this repository.*

## Page(s)
Which page(s) are involved in this request?
* Example of page the includes mermaid chart: https://about.gitlab.com/company/cadence/ 
* https://mermaid-js.github.io/mermaid/#/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Integrating the mermaid chart functionality into this repository


## Out of scope
What is out of scope and not part of this iteration?

- Any work in 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
ENG: Page Update - about.gitlab.com/analysts

Related to #240.

## Goal
Design for the Analysts page is ready for engineering.

## Page(s)
Which page(s) are involved in this request?
* [Industry Analyst Research](about.gitlab.com/analysts)

## Workfiles
* [Figma design](https://www.figma.com/file/yhOmOuXxET1rWd9hMHyT8A/Analysts-MVC-1?node-id=0%3A1)
* [Content outline](https://docs.google.com/document/d/1D23GF8KgWHq9IKD_hQNbcElffRPLsAbFzVcu0N9sNC4/edit?usp=sharing)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @dvilchis-ext 
- [ ] Consulted: @rragozzine @Tinaliseng  
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Engineering the updated mockup 

## Out of scope
What is out of scope and not part of this iteration?

- [ ] Improving UX for page updates
- [ ] User Testing

## 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
SaaS Revision: Currency Code

## Goal
CurrencyCode is visible in the dataLayer code, but GTM is not able to locate it due to the syntax. Moving the currencyCode line in the ecommerce array before the checkout line may help. 

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/-/subscriptions/new?plan_id=

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpreuss22 
- [ ] Consulted: @dennis106 
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
SaaS Revision: Variant

## Goal
Premium’s Variant should be “SaaS” instead of “Self-hosted” for the Add To Cart event. 

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* 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 
- [ ] Consulted: @dennis106 
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
SaaS Revision: Price

## Goal
1. Add Premium’s Price ($288) for the Product Impression and Add To Cart events 
2. Update Ultimate’s Price to '1188' for the Product Impression and Add To Cart events since it’s billed annually. This will also match the price on the Checkout event.
3. Price should be in single quote on the Checkout event. 

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/
* https://gitlab.com/-/subscriptions/new?plan_id=

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpreuss22 
- [ ] Consulted: @dennis106 
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 2.0
Topics Template Layout Changes

We've have looking at the recently migrated CI/CD topics page and we have identified a few changes and issues (listed below) that may have a negative impact on our current and future SEO efforts.

### Topic Navigation Links
All the "More on this topic" links are external and in most cases the link is irrelevant to the topic. Before the switch these were all internal. This can be amended but we need to ensure we preserve all internal links when migrating.

### Heading Heirachy
Headings gives search engines important clues about the page structure and relevancy. headings should be logically structured, starting with a h1 followed by h2's, and subsequent h3's fir related subsections, etc. The current structure isn't in a logical order. Search engines utilse header structures to decipher the informational structure and topical hierarchy of a page.

For example:

- `<h2 class="copy__title" data-v-b44de53e="" data-v-34d03aa1="">Continuous integration and continuous delivery (CI/CD)</h2> `. This should be **H1**.

- `<h3 class="header slp-text-xxl" data-v-b44de53e="" data-v-daaa09f2=""> What is CI/CD? </h3> `. This should be **H2**.

### FAQ schema
The FAQ schema.org markup is missing from the page. This was implemented to make search engine better understand page contents and display the pages in the form of Rich Snippets in SERPs.

### Self referencing canonical path
Self referencing canonical path is missing from this page and other pages that have migrated. This is needed to prevent search engines from indexing URLs with tracking parameters. Search performance is not affected but tracking statistics will be skewed. Search clicks will be wrongly attributed to other marketing activities in Google Analytics or other tracking tools.

Story points: 4.0
Solution page migration - Education section - Join

Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/248

## Goal

We would like to migrate `/solutions/education/join` 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* any page within the `/solutions/education/join` section of the site, 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?

* https://about.gitlab.com/solutions/education/join

## 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
Solution page migration - Education section - Edu Survey

Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/248

## Goal

We would like to migrate `/solutions/education/edu-survey` 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* any page within the `/solutions/education/edu-survey` section of the site, 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?

* https://about.gitlab.com/solutions/education/edu-survey

## 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: 3.0
Solution page migration - Education section - Campus

Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/248

## Goal

We would like to migrate `/solutions/education/campus` 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* any page within the `/solutions/education/campus` section of the site, 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?

* https://about.gitlab.com/solutions/education/campus

## 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: 4.0
Navigation Menu Click: Revision

## Goal
Add the `data-nav-tab` attribute to all `<a>` tags within the navigation menu. Essentially, items in the main navigation menu already has data-nav-tab, however it seems like there's a different version of the same nav menu that doesn't have the attribute. For example, the nav menu on the Home page has it. The nav menu on this page doesn't have it: https://about.gitlab.com/enterprise/

Please ensure data-nav-tab is placed across all versions of the navigation menu. 

## Page(s)
Which page(s) are involved in this request?
- about.gitlab.com/enterprise/
- about.gitlab.com/demo/
- about.gitlab.com/get-started/
- about.gitlab.com/company/
- about.gitlab.com/get-help/ 
- ...and many more


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mpreuss22 
- [ ] Consulted: @dennis106 
- [ ] 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: 1.0