giseldo/neodataset huggingface dataset:
UX: Update customer case studies landing page

Relates to https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/5605

## Goal
Copied from the original issue: 
> I would like to revamp the customer reference landing page up to current content and brand standards, which will be measured by an increase in the click-through rate to single customer reference pages that have already been revamped and updated.

### Jobs To Be Done
Copied from the original issue: 
> * **Situation**: In FY22 Q4
> * **Motivation**: We want to revamp/redesign the customer reference landing page
> * **Outcome**: So that it represents Gitlab well as the first engagement prospective customers have with our customer reference content, improves usability of the overall customer reference online material, and facilitates more engagement with our site.

## 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)

## Documents
- [Planning deck](https://docs.google.com/presentation/d/1odgXn-RUGmZM4hwIF9KKsjnb4jcKgJYwm5gR3wHxcj4/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 @jlparker @lclymer @FionaOKeeffe 
- [ ] Informed: `Everyone` @ctsang-ext 

## 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
- [x] UX Design
- [ ] Engineering

Story points: 6.0
Explore adding prettier to BE repo

## 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
Some HTML is not semantically correct

The following discussion from !191 should be addressed:

- [ ] @jgarc started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/191#note_840163309):  (+1 comment)

    > I went ahead and put this page through https://wave.webaim.org/ and found us to be running into some accessibility issues; I believe most of these are from components pulled elsewhere, and therefore I think are outside the scope of this MR, but I'll try to see if I can call out items that you've directly touched with this change!

Story points: 3.0
ENG: Solutions - By Sector - Public Sector

## Goal
We would like to apply the new template to our Public Sector page.

Final template to use will be located in [this Figma file](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=990%3A4681). 

## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/public-sector/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mduque-ext 
- [ ] Consulted: `@Tinaliseng`  `@laurenbarker`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Reusable ENG template for Solutions by Industry/Department pages only applied to the Public Sector 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
- [x] UX Design
- [x] Engineering

Story points: 6.0
ENG: Features - Continuous Integration

## Goal
We would like to build our individual feature pages with the new template 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.*

## Page(s)
Which page(s) are involved in this request?
* `[Figma File TBD](URL)`

New pages that will use this template:
- Continuous Integration ([Existing page](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/))


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jgarc 
- [ ] Consulted: @laurenbarker @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
- [x] Engineering

Story points: 2.0
Add submit event in the combined groups/projects form GTM handling

## Goal

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 GTM events for new group and project creation*
* **Outcome**: *So we can measure the free trial*

## 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

We're going to track this as a single event and use contextual info about free trial as suggested [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/361#note_845647533). 

So the event should now be:

```
dataLayer.push({
  'event': 'combinedGroupProjectFormSubmit',
})
```

The URL will have `trial_onboarding_flow=true` in it if the user is coming from a free trial onboarding experience, which we can use to differentiate for trials and regular sign up flows.

## 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: 6.0
ENG: Homepage - update security and compliance badges

Related to #307.

## Goal
We would like to ensure our security and compliance banner is up to date which will improve our communications as measured by the accuracy of our claims.

## Page(s)
Which page(s) are involved in this request?
* [Homepage](https://about.gitlab.com)

## In scope

Update security and compliance badges on the homepage.

1. Add [ISO/IEC 27001:2013 Certification](/uploads/f413ee4b72019b355199a58c2138608b/ISO_27001_Logo.png)
2. Add [CSA Trusted Cloud Provider](/uploads/b15cb4a9461b170782c49f47bf0480f0/CSA_Trusted_Cloud_Provider_badge.png)
1. Update the copy for 
SOC2 Certification
 to `SOC 2 & SOC 3 Certification`
1. Remove Bitsight

*Use the badge files linked above :arrow_heading_up: 

| Badge (low res) | Text | Link (open new browser window) |
| ------ | ------ | ------ |
|![Screen_Shot_2022-02-10_at_8.13.47_AM](/uploads/b36ef5f6eb766de0d375b5651fc06716/Screen_Shot_2022-02-10_at_8.13.47_AM.png) |SOC 2 & SOC 3 Certification| https://us.aicpa.org/interestareas/frc/assuranceadvisoryservices/serviceorganization-smanagement |
| ![Screen_Shot_2022-02-10_at_8.14.53_AM](/uploads/b1869a112b2770534de05c17d4497bfe/Screen_Shot_2022-02-10_at_8.14.53_AM.png) |ISO/IEC 27001:2013 Certification| https://www.schellman.com/certificate-directory?certificateNumber=1652216-1 |
|![Screen_Shot_2022-02-10_at_8.17.23_AM](/uploads/2199f9d6d73950101d29dffa27621d82/Screen_Shot_2022-02-10_at_8.17.23_AM.png)|CSA Trusted Cloud Provider|https://cloudsecurityalliance.org/star/registry/gitlab/|

## Final Visual
![Screen_Shot_2022-02-10_at_8.01.20_AM](/uploads/7a61fd125b4d91353a05a1006ee8e291/Screen_Shot_2022-02-10_at_8.01.20_AM.png)

## Out of scope
What is out of scope and not part of this iteration?

- Changing presentation style of banner

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @mpreuss22, '@JohnathanHunt', '@Julia.Lake', @lduggan (original engineer)  
- [ ] Informed: `Everyone`

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
IA Refresh - Redirect Mapping

To minimize the impact of structural change in the IA refresh we need to set up 301 redirects for deprecated and consolidated pages. We need to match your old URLs with the new ones or relevant alternatives. Without proper redirection, our new/consolidated pages will not get the traffic and PageRank of the old pages, which will affect our search engine rankings.

## Redirecting best practices
- To best preserve search rankings and traffic for better performing pages, it is best to keep the URL structure intact.
- When removing, deprecating or consolidating URLs it is important to redirect to a relevant alternative to preserve the SEO value from backlinks 
- Update internal links from the old URLs to the new URLs to prevent internal redirects which impacts crawl budget. 
- Check for existing 301 redirects to URLs that will be removed, relocated or consolidated. Updating these to the new URLs will prevent redirect chains and loops which impacts crawl budget.

## Risks
Combining, changing URLs or deprecating pages comes with risks that will affect SEO efforts. If not properly managed we run the risk of:
- Losing SEO value from backlinks attributed to removed or relocated URLs
- Drop in search traffic and rankings. It might take some time for search engines to update their search index.
- Increase in 404 errors, redirect chains and redirect loops.
- Increase in soft 404s error messages in Google Search Console.


### Tasks to be done
- [x] [Create redirect map document](https://docs.google.com/spreadsheets/d/1Oir6thxzoXuumbk5Lh6CBiznE6KOjJXhjQ88svKac68/edit?usp=sharing)
- [ ] Create redirects (old to new) in redirect.yml file
- [ ] Update internal links to reduce internal redirects

Story points: 10.0
Migrate all card components

## Goal
Replace card components in the Buyer Experience repo to use the cards from slippers-ui.

**Storybook:** https://gitlab-com.gitlab.io/marketing/digital-experience/slippers-ui/?path=/story/components-card--default

**Usage:** https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/blob/main/src/components/Card/Card.stories.js

Story points: 4.0
IA Refresh Content Audit

## Goal
Carry out a content audit to suggest what pages should be kept, deleted, consolidated or redirected in the website refresh. This will be compiled using backlinks, existing website structure and Google Analytics data. 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @hsmith-watson 
- [ ] Consulted: @ncregan 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [x] Content audit of current marketing pages


## Out of scope
What is out of scope and not part of this iteration?

- Blog posts and releases
- Handbook, Direction, Company and Job Families pages


## Documentation
- [Content Audit Spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit?usp=sharing)

### Outcomes
Based on the results of the content audit we have four suggested outcomes.

**Leave as is**

No need to delete or redirect. The page has good traffic and a healthy backlink profile. Removing these pages will have a negative impact on traffic. 
If deleted we must redirect to an alternative page and 301 redirect to ensure the link equity is maintained. 

**Redirect or Update**

The page gets no meaningful traffic but has at least 1 backlink. This needs to be manually reviewed by code owners/departments to ensure nothing of strategic value is removed.

Options:
- Improve SEO by updating the content
- Merge content with similar page and redirect to new location
- Delete page and redirect to alternative

**Manual review**

Pages with OK traffic and little from organic search. This needs to be manually reviewed by code owners/departments to ensure nothing of strategic value is removed.

Options:
- Leave as is
- Improve SEO by updating the content
- Merge content with similar page 
- Delete page and redirect to alternative

**Delete Page**

These pages has no meaningful traffic from any source and no backlinks. This needs to be manually reviewed by code owners/departments to ensure nothing of strategic value is removed.

Options:
- Delete page and redirect to alternative

Story points: 10.0
UX: new page Company size - Startups

## Goal
We would like to create a new page for Early Stage businesses which will improve our Solutions marketing as measured by more early stage businesses signing up for GitLab accounts.

### Jobs To Be Done
* **Situation**: *When a user from an early stage business looks into using GitLab for their company...*
* **Motivation**: *they want to understand how GitLab works for their specific needs...*
* **Outcome**: *so they can make an informed decision on whether to use our product.*

## Page(s)
Which page(s) are involved in this request?
- `[Figma File TBD](URL)`

Similar to:
- [Enterprise page](https://about.gitlab.com/enterprise/)
- [SMB Page](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: @Tinaliseng 
- [ ] Consulted: @jhalloran 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] New early stage page
- [ ] New copy and possibly brand assets acquired

## 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:

- [x] Copy writing
- [x] Illustration
- [x] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering

Story points: 1.0
UX: Support page refresh

## Goal
We would like to consolidate our support pages into 1 page which will improve customer's finding the support they need as measured by less support inquiries.

### Jobs To Be Done
* **Situation**: *When a user is looking for help...*
* **Motivation**: *they want to easily find and quickly understand how to solve their problem or get in touch...*
* **Outcome**: *So they can get back to business as usual ASAP.*

## Page(s)
Which page(s) are involved in this request?
- [Support Page 1 - Contact Support](https://about.gitlab.com/support/)
- [Figma designs for Support page](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=88%3A8051)

- [Support Page 2 - Help Topics](https://about.gitlab.com/get-help/)
- Maybe also [Contact Sales](https://about.gitlab.com/sales/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jhalloran 
- [ ] Consulted: @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Support page 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:

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering

Story points: 8.0
UX: Template for getting started checklist

## Goal
We would like to have a template for getting started checklists, which will improve customer onboarding as measured by decreased support inquiries.

### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand how to begin setting up their GitLab account or other services...*
* **Outcome**: *so they can get started right away and without interruption.*

## Page(s)
Which page(s) are involved in this request?
- [Figma File High Fidelity Designs](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=368%3A3068) (WIP - waiting for Jam3 designs)
- [Figma File JTBD](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab?node-id=218%3A4234)
- ~~[Getting started](https://about.gitlab.com/get-started/)~~ Not included because it's not a net new page.

New pages that will use this template:
- SMB/Enterprise quick set up checklist
- CI quick set up checklist
- SCM quick set up checklist
- Build business case for GitLab checklist
- Transition from GitHub or Jira quick set up checklist
- Scaling your GitLab usage quick set up checklist
- Set up support services

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: Carrie Tsang
- [ ] Consulted: @jhalloran @Tinaliseng 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Reusable UX template for getting started checklists

## 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
UX: Category Leadership - Template refresh

## Goal
We would like to have a consolidated template for our Category Leadership 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 how GitLab is leading the way in a particular category...*
* **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 File TBD](URL)`

New pages that will use this template:
- DevOps ([Existing page 1](https://about.gitlab.com/solutions/devops-platform/), [existing page 2](https://about.gitlab.com/topics/devops/))
- Digital Transformation ([Existing page 1](https://about.gitlab.com/solutions/digital-transformation/))
- Agile Development ([Existing page 1](https://about.gitlab.com/topics/agile-delivery/), [existing page 2](https://about.gitlab.com/solutions/agile-delivery/))
- GitOps ([Existing page 1](https://about.gitlab.com/solutions/gitops/), [existing page 2](https://about.gitlab.com/topics/gitops/))
- Microservices
- DevSecOps
- Security & Compliance
- Cloud Transformation
- Modern Applications

## Files
[Ongoing agenda](https://docs.google.com/document/d/1ielDKrmfHq9QqXH7TNcJXPzAT9I2qkO8vkLN9J6_Blo/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 @hsmith-watson @ncregan @dennischarukulvanich 
- [ ] Informed: @fqureshi 

## In scope
What is within scope of this request?

- [ ] Reusable UX template for Category Leadership pages (designs by Jam3)
- [ ] JTBD (if deemed necessary)
- [ ] High-fidelity wireframes

## 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