giseldo/neodataset huggingface dataset:
ENG: Search Mobile

## Goal
We would like to build the search for mobile screens

### Jobs To Be Done

When the user access the search from a mobile device, the search should be fully usable so we can guide the users an redirect them to the correct page in mobile devices

[Figma](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=639%3A5609)

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/search

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @laurenbarker, @ctsang-ext 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Define the scope of the search feature in a mobile screen/device
- [ ] Build the mobile template of the search bar/page

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1

## 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
ENG: Make Search Results a New Page

## Goal
We would like to separate the search results from the navigation overlay to be a new page in order to be able to return to past search executions

### Jobs To Be Done

Move the search results to Buyers Experience and make it a new page, after the users make a search in the navigation overlay the page should be redirected to https://about.gitlab.com/search?q=&per_page=&page=&

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/search

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @laurenbarker, @ctsang-ext 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1

## Out of scope
What is out of scope and not part of this iteration?

- Move the search results code from Navigation to Buyers Experience
- Make the corresponding routing in order to do a search from a url

## 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
ENG: Define scope for API search via mobil

## Goal
We would like to define scope for API search via mobile. 


### Jobs To Be Done
* **Situation**: *When the search is used on a mobile device it works well.*
* **Motivation**: *We want to ensure anyone on any device can use our new api driving search*
* **Outcome**: *So we can increase conversion*

## Page(s)
Which page(s) are involved in this request?
* Navigation 
* BE
* www

## 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?

- [ ] Check the new search experience on mobile devices and define what we need to do to make it functional.


## 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
Plan: Define scope A/B testing the navigation

## Goal
We would like to research and define how A/B tests can be run on the marketing site navigation. 

### Jobs To Be Done
* **Situation**: *We need to research how the A/B testing works currently and how to run these tests on the navigation. *
* **Motivation**: *We want to define what is needed to be able to run A/B navigation tests*
* **Outcome**: *So we can build that integration now, and be ready when the time comes to run a A/B test on the nav.*

## Page(s)
Which page(s) are involved in this request?
* Navigation repository
* Launch Darkly
* Feature Flags (maybe) 
* More TBD

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jariasc-ext 
- [ ] Consulted: @laurenbarker @jgarc 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Define what we need to do to enable A/B tests on the nav


## Out of scope
What is out of scope and not part of this iteration?

- Implementing anything, we'll do that in a separate issue. This is for defining scope and requirements. 

## 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: BUG | Features page filter not working as intended

## Goal
The filter is not working as intended when filtering on Sass/Self-Managed

[Slack Thread](https://gitlab.slack.com/archives/CN8AVSFEY/p1660239305730119)

### Jobs To Be Done
* **Situation**: *When the users filter a feature the filter is not working as it should*
* **Motivation**: *Update the filter to function properly*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [Features](https://about.gitlab.com/features/?stage=manage)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ndubord 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Fix filter functionality 
- [ ] 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
- [x] Engineering

Story points: 1.0
UX: Improve Search Suggestions

## Goal
We would like to improve the default suggestions for search. 

### Jobs To Be Done
TBD

## Page(s)
Which page(s) are involved in this request?
- Search
![image](/uploads/73087ef98c5a342dad92ddee09e7b5cb/image.png)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?


## 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
ENG: Swap Minimal Nav to standard Navigation on the Pricing page

## Goal
We would like to remove the Minimal Nav from the Pricing page and replace it with the standard default navigation.

### Jobs To Be Done
* **Situation**: *When a user lands on the pricing page, they may feel stuck and can navigate to other parts of the site*
* **Motivation**: *We want to make sure users don't feel stuck on the pricing page*
* **Outcome**: *So we can track user traffic after landing on the pricing page*

## Page(s)
Which page(s) are involved in this request?
* [Pricing](https://about.gitlab.com/pricing/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @tywilliams 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `@mpreuss22` 

## In scope
What is within scope of this request?

- [ ] Swapping minimal nav to standard nav on the pricing page
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Touching the nav on any other page
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
Use `nuxt/image` to compress and lazy load images

## Goal
We would like to set loading="lazy" to defer loading of an image until it appears in the viewport.

https://image.nuxtjs.org/components/nuxt-img#loading

Related thread https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/885#note_1057393955 


### Jobs To Be Done
* **Situation**: *We defer loading of images until it appears in the viewport*
* **Motivation**: *We want to optimize images to improve CWV score*
* **Outcome**: *So we can improve first content pane*

## Page(s)
Which page(s) are involved in this request?
* All `<nuxt-img src="/**nuxt-icon.png****" loading="lazy" />` components

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @laurenbarker 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Update all instances of `<nuxt-img src="/fake-image.png"/>` to `<nuxt-img src="/fake-image.png" loading="lazy"/>`


## Out of scope
What is out of scope and not part of this iteration?

- Image compression or build modifications

## 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
Request to Remove Event Details Section from PubSec Page

## Goal
We would like to remove the event details section from the [PubSec page](https://about.gitlab.com/solutions/public-sector/). Unfortunately, this is a completely manual process and we have to remember to update the page every time an event listed occurs so old events are not still listed on the page. We don't believe we're getting much traction from the page for events and would like to, instead, just link to our [GitLab Events Page](https://about.gitlab.com/events/).

### Jobs To Be Done
* **Situation**: Remove event details from PubSec page
* **Motivation**: Very inefficient and manual process
* **Outcome**: Be more efficient and just link to our current events page

## Page(s)
Which page(s) are involved in this request?
* [PubSec Page](https://about.gitlab.com/solutions/public-sector/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @krogel 
- [ ] Consulted: @KiraAubrey 
- [ ] 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
- [x] UX Design
- [ ] Engineering

Story points: 2.0
ENG: Update T-mobile link on homepage

## Goal
We currently have a 404 link on the home page when you click on the T-mobile logo.  

Lets update the link to this: https://learn.gitlab.com/c/learn-how-t-mobile-i?x=04KSqy

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* [homepage](https://about.gitlab.com)

## 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?

- [ ] Update the T-mobile link to https://learn.gitlab.com/c/learn-how-t-mobile-i?x=04KSqy
- [ ] 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
- [x] Engineering

Story points: 1.0
Add sidebar to Get Started template

## Goal
We would like to add the sidebar component to our Get Started template. It's designed in the [Figma](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started) file, but missing from our Get Started for Small Business page on production. Looks like it's missing from the template. 


### Jobs To Be Done
* **Situation**: *When a user visits any child get started page, there is a sidebar nav that enables the user to jump to the section of the page their interested in.*
* **Motivation**: *We want to help the user get to the information they need faster*
* **Outcome**: *So we can improve conversion.*

## Page(s)
Which page(s) are involved in this request?
* `/get-started/small-business`

Related epic https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/epics/112 

## 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?

- [ ] Add sidebar component to /get-started/_slug.vue
- [ ] Add sidebar data to content/get-started/small-business.yml

## 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
UX: Learn / Update UI

## Goal
We would like to update the UI on https://about.gitlab.com/learn/ 

## Page(s)
Which page(s) are involved in this request?
* [Learn](https://about.gitlab.com/learn/)

## Workfiles
* [Figma](https://www.figma.com/file/xvVvOI4d9kH2oPjpLaLg7o/Learn-%2F-UI-Refresh?node-id=52%3A2458)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @jhalloran @ctsang-ext @ndubord 
- [ ] Informed: @fqureshi @justin.vetter 

## In scope
What is within scope of this request?

- [ ] Fresh coat of paint


## Out of scope
What is out of scope and not part of this iteration?

- Content updates
- Heavy technical lift updates


## 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: Search Mobile Experience

## Goal
We would like to create a mobile experience for the new search

### Jobs To Be Done
TBD

## Page(s)
Which page(s) are involved in this request?
TBD

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @Tinaliseng @jhalloran 
- [ ] Informed: @laurenbarker @fqureshi 

## 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: 1.0
ENG: Search Loading Bar

## Goal
We would like to add a progress/loading bar for the search page.

### Jobs To Be Done
Implement a loading bar within the navigation repository.

Here's the loading bar.
- [Individual screens](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=579%3A4474)
- [Prototype](https://www.figma.com/proto/ndNo84yjW3SbTuXPuwjJQ3/Search?page-id=137%3A1387&node-id=579%3A4474&viewport=533%2C-285%2C0.18&scaling=min-zoom&starting-point-node-id=579%3A4474&show-proto-sidebar=1) (Click on "continuous integration (CI) to trigger)

## Page(s)
Which page(s) are involved in this request?
- Navigation repository

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext TBDengineer
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?
Design the loading bar (complete)
Implement the loading bar (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
ENG: Release Post template rebrand MVC1

## Goal
We would like to do a first pass at rebranding the existing release post template which will improve continuity and accessibility as measured by reduced drop off.

### Jobs To Be Done
* **Situation**: *When a customer goes to read the release post ...*
* **Motivation**: *We want to have a similar experience to the rest of the site...*
* **Outcome**: *So we can maintain our brand and make sure our site is accessible.*

## Page(s)
Which page(s) are involved in this request?
* [Example release post](https://about.gitlab.com/releases/2022/07/22/gitlab-15-2-released/)
* [Figma designs](https://www.figma.com/file/GpqMIWNYZW2fC58BHwMbWf/Release-post-MVC1?node-id=2%3A928)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mmanunga-ext 
- [ ] Consulted: @fqureshi @jhalloran @justin.vetter
- [ ] Informed: @fseifoddini @amittner @brhea

## In scope
What is within scope of this request?

- [x] Skin existing release post with updated brand colors and typography
- [x] Address any existing accessibility issues

## Out of scope
What is out of scope and not part of this iteration?

- Changing the structure of the page
- Hero image
- Anything else

## 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
Privacy Policy - Footer Link Changes on Marketing Site

## Goal

We would like to do two things:

1.  Remove the Privacy Policy parenthetical on the about.gitlab.com site that states the "last updated" date.  It's been over one-month now so we can remove that information
2. Change the name of the footer link from `Privacy Policy` to `Privacy Statement`

## Date/Timeline

We would not like to make this update until the end of August 2022.  

### Jobs To Be Done
* **Situation**: *When a user goes to our site they wont' be informed of the last updated date, as the period for notice/comments is effectively over.  Also, the name change to the link is more accurate.*
* **Motivation**: *We want to update the terminology to better reflect the intent of the document*
* **Outcome**: *So we can inform users*

## Page(s)
Which page(s) are involved in this request?
* `Every page on about.gitlab.com`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [X] Consulted: `@lasayers`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] MR to change parenthetical on all marketing sites

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering

Story points: 1.0
SPIKE: Enable support pages to consume markdown

## Goal
We would like to investigate using markdown for support content. HTML markup mixed in with the [support.yml](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/support/index.yml#L101) content. 

### Jobs To Be Done
* **Situation**: *Investigate level of effort to enable markdown content in support content files*
* **Motivation**: *We want to enable the support team to manage content through markdown*
* **Outcome**: *So we can help the support self serve updates to our support pages*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/ and all child pages

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @jcolyer 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Investigate if markdown content is consumable [`support-copy:block:text`](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/support/index.yml#L101) area of the content file
- [ ] Determine how to enable markdown if it is not and level of effort

## Out of scope
What is out of scope and not part of this iteration?

- Actually enabling it or implementing markdown


## 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