idproject
int64 7.76k
28.8M
| issuekey
int64 675k
128M
| created
stringlengths 19
32
| title
stringlengths 4
226
| description
stringlengths 2
154k
⌀ | storypoints
float64 0
300
⌀ |
|---|---|---|---|---|---|
28,847,821 | 114,314,851 |
2022-09-01 20:40:46.377
|
ENG: Full Hero Carousel
|
## Goal
We would like to test adding a full hero carousel to the homepage which will improve engagement as measured by CTA clicks within the homepage hero.
This issue is to create the functionality for the home carousel not to implement it live. We also want this to be a new component and not overwrite the current home hero. We should use the current home hero as a starting point in this carousel.
- [ ] The carousel transition includes left text and image
- [ ] The user should be able to click to move to the next slide
- [ ] The carousel should be flexible that can handle 2-5 slides
- [ ] When a user mouses over the entire carousel the timer should pause
- [x] Work with @dennischarukulvanich so we can track the CTAs per slide
When engineering is done we should make sure the old hero is on the home page and we can merge this new component to wait for content.
### 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](http://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?
- [ ] AB Test current (control) carousel vs. a carousel that changes messaging and CTA links as well.
## Out of scope
What is out of scope and not part of this iteration?
- Experience or behaviour changes beyond in scope description
## Example:
[https://www.snowflake.com/en/](https://www.snowflake.com/en/)
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [x] UX Design
- [x] Engineering
| 5 |
28,847,821 | 114,311,459 |
2022-09-01 18:53:06.773
|
Resolve console errors on select Conversion pages
|
Clearing up console errors in browser and in terminal due to incorrect use of v-html within SlpTypography components and deprecated attributes.
1. Home page
2. Pricing page
3. Pricing Premium page
4. Pricing Ultimate page
5. Demo
6. Why GitLab
| 2 |
28,847,821 | 114,255,341 |
2022-08-31 21:27:41.243
|
ENG: OneTrust Cookie banner update
|
## Goal
We would like to see if force choice is an option for the cookie banner which will improve user selection as measured by acceptance or rejection of cookies.
### Jobs To Be Done
* **Situation**: *When a customer visits GitLab...*
* **Motivation**: *We want them to make a choice if they want us to use cookies or not for their sessions...*
* **Outcome**: *So we can deliver the preferred experience.*
## Page(s)
Which page(s) are involved in this request?
* [Home page cookie banner](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: @lduggan @justin.vetter @fqureshi
- [ ] Informed: `@mpreuss22`
## In scope
What is within scope of this request?
- [ ] Remove "x" close icon from non-US cookie banner. But, must keep the "reject-all" button for France.
- [ ] Remove "x" close icon from US cookie banner for future proofing.
- [ ] Stop page scroll until a user has selected their cookie preference.
## 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
| 4 |
28,847,821 | 114,242,398 |
2022-08-31 17:00:34.217
|
Remove unused css in www-gitlab-com
|
## Goal
Clean up all the unused css in www-gitlab
| 2 |
28,847,821 | 114,187,422 |
2022-08-31 00:31:00.746
|
Broken Link: 404 on Learn
|
## Goal
The "Learn more about GitLab Certifications" CTA on https://about.gitlab.com/learn/ goes to a 404 page.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/learn/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter
- [ ] 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:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 114,181,218 |
2022-08-30 20:59:42.769
|
Create: Overview of Partner Program Template
|
## Goal
We would like to build a new template and apply it to Overview Partners page. This new template was created as part of [this issue.](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1107)
[Figma Link](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=170%3A5667)
### Jobs To Be Done
* **Situation**: *We'd like a unified landing page for finding GitLab partners*
* **Motivation**: *When users need more information we can direct the to the correct spot*
* **Outcome**: *So we can offer them the best service*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/partners/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @ctsang-ext @mlebeau
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Apply new template to Partners landing page @ https://about.gitlab.com/partners/
## 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
| 5 |
28,847,821 | 114,167,028 |
2022-08-30 16:52:31.889
|
Remove /learn/ code from www-gitlab
|
## Goal
/learn/ is now live in BE, let's rip it out of www-gitlab
| 1 |
28,847,821 | 114,154,320 |
2022-08-30 13:14:53.540
|
ENG: Blog Images | compress current blog images
|
## Goal
We would like to reduce the page size and increase core vital scores across about.gitlab.com. We would like to start with the blog by running a CLI script to compress all images to reduce file size.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[BLog](https://about.gitlab.com/blog)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Run script to compress all images
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Replace or resize the images
- 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
| 8 |
28,847,821 | 113,934,452 |
2022-08-26 18:30:43.171
|
ENG: Revert deleted feature images
|
## Goal
We would like to revert the deleted feature images so they can be used on the refreshed /fetures page
### 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/features/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: @mmanunga-ext
## In scope
What is within scope of this request?
- [ ] Revert deleted images
- [ ] 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
| 1 |
28,847,821 | 113,913,408 |
2022-08-26 11:33:36.170
|
Fix broken selector on /customers/
|
## Goal
https://gitlab.slack.com/archives/CN8AVSFEY/p1661501727406619?thread_ts=1661458387.966129&cid=CN8AVSFEY
| 1 |
28,847,821 | 113,873,805 |
2022-08-25 18:33:08.408
|
ENG: Homepage | Update DevSecOps card
|
## Goal
We would like to update the DevSecOps card in the resources section.
- [ ] Change 2021 to 2022
- [ ] Update the thumbnail image to the one below:
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Home](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 DevSecOps resource card on the homepage
- [ ] 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
| 1 |
28,847,821 | 113,937,831 |
2022-08-25 18:03:40.773
|
Smartling Code Repo Connector - POC
|
### Background
We've contracted the [Code Repo Connector](https://help.smartling.com/hc/en-us/articles/360008038694-Repository-Connector-Overview#:~:text=The%20Repository%20Connector%20is%20designed,translations%20back%20to%20the%20repository.) with Smartling since the contract began, but we haven't used it. This issue is to track a Proof of Concept for the Smartling Code Repo prior to contracting it this year.
* Note the DRI of the POC will be the Product or Eng Teams (this issue can be moved if necessary)
* Digital Experience team will be DRI related to the website as the Code Repo Connector is an alternative to the GDN (this issue can be copied if necessary)
### Proof of Concept Options
1. TBD
### Comments from Smartling
* Prior to any POC, Smartling requested that we define what a successful POC looks like.
* Our next steps on the website evaluation will be to arrange a technical demo of the Code Repo Connector highlighting any specific use cases or actions the team would like to validate.
* We can schedule a discussion of the pros and cons to use our Repository Connector Vs the GDN to support the website translation initiative both are great options, the deciding factors will be based on your overall strategy/objectives of the website translations project and the team's desired experience/LOE.
### Next Steps
* Determine what we would like to get out of the POC? What questions are we trying to answer / what does success look like?
* Determine POC options for the Code Repo Connector.
* Technical discussion with Smartling related to using the GDN or the Code Repo for website translation.
@RLeihe268 @mpreuss22 @davidbrown1 @justin.vetter @laurenbarker @s_awezec
<!-- Please leave the label below on this issue -->
| 4 |
28,847,821 | 113,810,442 |
2022-08-24 20:56:18.381
|
ENG: Slack integration marketing landing page
|
## Goal
We would like to create a landing page on about.gitlab.com for the Slack/GitLab integration.
Design is attached in design management :arrow_down:
This landing page needs to meet the Slack guidelines for the landing page are outlined [here](https://api.slack.com/start/distributing/guidelines#landing).
* Must include privacy policy link
* A clear overview of your Slack app, any associated services, and the problem your app solves.
* A detailed explanation of how your app works in Slack. Screenshots and GIFs are a good way to show people what they can expect in Slack after installing your app.
* A clear path to installing your Slack app, whether that is an Add to Slack button on your landing page or instructions for accessing your Add to Slack button.
* A clear path to using your app. Once people install your app to their workspace, they should be redirected to a page that confirms the installation was successful and provides clear next steps for getting started with your app.
* Needs to be publicly accessible i.e. not behind a login.
* Your landing page is, well, a landing page crafted by you, specifically for your Slack app - not a link to a PDF, document or code repository
### Jobs To Be Done
* **Situation**: *When anyone is looking for information about our integration with Slack, there is publically accessible landing page*
* **Motivation**: *We want roll out new Slack GBP app to all gitlab.com users, but current landing page (https://gitlab.com/-/profile/slack/edit) does not match the Slack guidelines*
* **Outcome**: *So we can improve conversions*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/slack/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @katiemacoy @ctsang-ext
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create a MVC landing page for the Slack integration that meeds requirements from Slack
- [ ] For efficency, use the a solutions template ,[Public Sector](https://about.gitlab.com/solutions/public-sector/)
- [ ] Deploy landing page to `about.gitlab.com`
- [ ] Build page in Buyer Experience
## Out of scope
What is out of scope and not part of this iteration?
- And work in the product codebase or `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
- [x] UX Design
- [x] Engineering
| 3 |
28,847,821 | 113,809,069 |
2022-08-24 20:19:32.257
|
[SPIKE] Asset manager
|
## Goal
This is going to be a growing issue, I just want to get the ball rolling. Let's investigate adding an asset manager for all the images on the marketing site. We're reaching a phase where it's difficult to track down what asset exists and where, having duplicate assets, and just general organization.
| 10 |
28,847,821 | 113,715,940 |
2022-08-23 17:07:00.062
|
Enable markdown in support copy component
|
## Goal
We would like to enable markdown in the support copy component. This will increase efficiency and self service of content updates by the support team to our support pages.
The end goal of this is issue is to enable markdown content to be consumed by the support template as a MVC.
### Jobs To Be Done
* **Situation**: *When a update is needed to our support pages, content is supplied using markdown*
* **Motivation**: *We want to make it easier for the support team to self serve updates to these pages*
* **Outcome**: *So we can increase cross functional collaboration*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/
* https://about.gitlab.com/support/customer-satisfaction/
* https://about.gitlab.com/support/general-policies/
* https://about.gitlab.com/support/gitlab-com-policies/
* https://about.gitlab.com/support/definitions/
* https://about.gitlab.com/support/portal/
* https://about.gitlab.com/support/us-federal-support/
* All other content files in [/content/support/](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/support)
## 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?
- [ ] Enable markdown to be consumed by the [components/support/copy.vue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/components/support/copy.vue)
- [ ] Update all content supplied to the support/copy.vue component to markdown
## Out of scope
What is out of scope and not part of this iteration?
- Changes to the template
- Changes to any content - other than `HTML` to `MD` in `yml` files.
## 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
| 9 |
28,847,821 | 113,708,881 |
2022-08-23 15:42:54.218
|
ENG: Personalization Spike | POC Create a test for personalized content based on URL param
|
## Goal
We would like to create a Proof of Concept around direct personalization based on incoming URLs with params.
### Jobs To Be Done
* **Situation**: *When a user clicks on a CTA from a Marketo email, Marketo landing page, or social post the page directed to is not personalized based on the campaign*
* **Motivation**: *We want to help drive user clicks and engagement and have a wholistic marketing funnel*
* **Outcome**: *So we can give users personalized content based on the external campaign*
## Page(s)
Which page(s) are involved in this request?
* [Home](https://about.gitlab.com)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @justin.vetter `@fqureshi`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] POC homepage hero change H1 and button text based on 2 different params
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Deploying this POC live
- 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
| 5 |
28,847,821 | 113,676,744 |
2022-08-23 08:13:20.072
|
Alliance Partners - Inappropriate use of GitLab logo for partners without own logo
|
## Goal
We need to stop using our trademark logo to refer to partners.
**Engineering Ask to Resolve Issue**
We just need to replace all gray tanuki logos on the [Alliance page](https://about.gitlab.com/partners/technology-partners/) with the handshake. [See figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=277%3A9473). They should be at 60x60px to match with the height of the other logos.
[Thread link](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1271#note_1079448051)
### Jobs To Be Done
* **Situation**: *As soon as possible or within the next month*
* **Motivation**: *We need to cease use of the GitLab logo for partners listed on this page, that do not have their own logo*
* **Outcome**: *This needs to be done to avoid dilution of our trademarks, and protect GitLab's intellectual property rights and interests*
## Page(s)
Which page(s) are involved in this request?
* `[Alliance Partners](https://about.gitlab.com/partners/technology-partners/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @fqureshi
- [ ] 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
- [x ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 113,656,830 |
2022-08-22 21:47:15.450
|
Tracking: Add Data Attributes to "View All..." Nav Links
|
## Goal
Please add the following data- attibutes to the "View all stages" link located in the Why Gitlab and Platform > The DevOps Lifecycle navigation menu.
- `data-nav-levelone="platform" or "why gitlab"`
- `data-nav-leveltwo="devops lifecycle"`
- `data-nav-levelthree="view all stages"`
## Page(s)
Which page(s) are involved in this request?
* All about.gitlab.com pages in the navigation menu
* Don't forget the ShadowDOM version and mobile site
## 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`
## 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
| 2 |
28,847,821 | 113,651,620 |
2022-08-22 19:15:20.238
|
ENG: CTA bottom block scroll on about.gitlab.com/solutions/education/campus/
|
## Goal
An incident of the scroll not being triggered when the Call to action in the bottom section of the page is on the screen.
## Page(s)
Which page(s) are involved in this request?
* [about.gitlab.com/solutions/education/campus/](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: `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
| 1 |
28,847,821 | 113,650,408 |
2022-08-22 18:45:29.552
|
Commit twitter image is not rendering
|
There's a typo in the Twitter image src that is preventing the open graph image from rendering when the page is shared.
Thank you for bringing it to our attention, @award4!
| 1 |
28,847,821 | 113,731,145 |
2022-08-19 22:43:16.215
|
Smartling GDN - POC - Discovery
|
### Background
We've contracted the GDN with Smartling since the contract began, but we haven't used it. This issue is to track a Proof of Concept for the Smartling GDN prior to contracting it this year.
Note the DRI of the POC will be the Digital Experience team (this issue can be moved if necessary).
### Proof of Concept Options
1) Full Deployment - This includes a full deployment of the Smartling GDN and will require Smartling Professional Services to implement. Professional Services hours for this type of POC ranges from 25-30 hours, estimated cost is $5,000-$8,000. The reason for the cost is that we would be able to continue to use the GDN once it is set-up and we add it to the contract.
1) Partial Deployment - We would select a few pages (number TBD) and Smartling would connect these to show us how it works. If it is only a few pages, there wouldn't be a cost to this.
1) In depth technical demo - This would be a 90 minute call with Smartling where they would show us (on their site), a step-by-step demo of how the GDN works. This would not be on our site.
### Comments from Smartling
- Prior to any POC, Smartling requested that we define what a successful POC looks like.
- Our next steps on the website evaluation will be to arrange a technical demo of the GDN on the GitLab website highlighting any specific use cases or actions the team would like to validate.
- Similarly, we can schedule a discussion of the pros and cons to use our Repository Connector Vs the GDN to support the website translation initiative both are great options, the deciding factors will be based on your overall strategy/objectives of the website translations project and the team's desired experience/LOE.
### Next Steps
- Determine what we would like to get out of the POC? What questions are we trying to answer / what does success look like?
- Determine which POC option we are most interested in based on the POC goals.
- Technical discussion with Smartling related to using the GDN or the Code Repo for website translation.
### Requests from Smartling
Smartling asked that we answer these questions prior to our GDN discussion.
1- What is the business objective surrounding translations? (Ex: Drive more leads to the website, convert more leads on the website, support an existing international sales team to convert more deals, etc)
* Answer: Drive more leads, support an existing sales team to convert more deals
2- What success metric will you be tracking against as it relates to translation (Website metrics (traffic, conversion rates, page views, bounce rate, etc), sales team conversation success, new user adoption, decrease in support tickets, etc)
* Answer: Website metrics, new INQ, trials
3- Please list in the order of priority the content you are looking to translate. (Specific websites, Landing Pages, Blogs, Web application)
* Answer: Ultimately, we will translate about.gitlab.com and all navigation pages. To start with the POC, we will translate the [Homepage](about.gitlab.com), [Why Gitlab](https://about.gitlab.com/why-gitlab/), [Pricing Page] (https://about.gitlab.com/pricing/)
4- What Technology do you use to create and/or serve this content? (CMS, Marketing Automation, E-Comm Platform, Other?)
* **Need answer**
5.1- What source language is your content in?
* Answer: English
5.2- Which language(s) are you translating into?
* Answer: Japanese, French, German
6- What are your annual translation volumes? (best guess of plan is fine)
* Answer: Currently around 160k processed words for marketing, but this is expected to increase. Web hasn't been started yet.
7- Stakeholders
a. Who needs to be involved in the evaluation? Answer: Digital Experience team, Marketing Ops, others TBD
b. Who will be using the tool? Answer: Digital Experience team (technical GDN), project management DRI TBD
c. Who will be vetting the technology and integration path? Answer: Digital Experience team
d. Who is the budget holder for sign-off? Answer: Marketing Operations
8- Describe your ideal translation process.
* **Answer: Need answer**
9- Describe the challenges you are facing in the current process.
* Answer: No solution for web translations currently in place.
10- What do you need to see in our solution to move forward with Smartling?
* **Answer: Need answer, what does success look like**
@RLeihe268 @mpreuss22 @davidbrown1 @justin.vetter @laurenbarker
<!-- Please leave the label below on this issue -->
| 4 |
28,847,821 | 113,421,946 |
2022-08-17 18:52:54.916
|
ENG: Why Premium/Ultimate | Update <title> and H1
|
## Goal
We would like to add the GitLab name into the page title to help with organic search
<title>Why GitLab Premium?</title>
<title>Why GitLab Ultimate?</title>
### Jobs To Be Done
* **Situation**: *When a user searches GitLab tiers adding our name into the results helps brand*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can increase organic search traffic*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/premium/
* https://about.gitlab.com/pricing/ultimate/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @jhalloran @fqureshi `@ncregan`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update Title of the two pages
- [ ] 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
| 1 |
28,847,821 | 113,421,747 |
2022-08-17 18:47:44.619
|
ENG: Features | Update meta description
|
## Goal
We would like to update the Meta description for the page to _Learn about the various features of GitLab Premium, Ultimate, and Free, including issue tracking, time tracking, reporting, file locking, and more._
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Features](https://about.gitlab.com/features)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter `@ncregan`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Updating meta description
- [ ] 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
| 1 |
28,847,821 | 113,419,289 |
2022-08-17 17:53:43.611
|
ENG: Feature Comparison | Update buy links
|
## Goal
At the top of the Feature Comparison page we would like to update the links (Free trial, Buy premium, Buy Ultimate)
- **Free Trial:** -> https://gitlab.com/-/trials/new?glm_content=default-saas-trial&glm_source=about.gitlab.com&_gl=1*nh1qyb*_ga*MzY4MDQ0NjU4LjE2NTIxMjM0Mjk.*_ga_ENFH3X7M5Y*MTY2MDc1MzIyOS4yMi4xLjE2NjA3NTg1OTAuMC4wLjA.
- **Buy Premium** -> https://gitlab.com/-/subscriptions/new?plan_id=2c92a00d76f0d5060176f2fb0a5029ff&test=capabilities
- **Buy Ultimate** -> https://gitlab.com/-/subscriptions/new?plan_id=2c92a0ff76f0d5250176f2f8c86f305a&test=capabilities
### Jobs To Be Done
* **Situation**: *When a user clicks any of the top links on the page they are taken to the home page*
* **Motivation**: *We want to make sure we continue the correct flow for trial or purchase*
* **Outcome**: *So we can direct potential signups to the correct page*
## Page(s)
Which page(s) are involved in this request?
* [Feature Comparison](https://about.gitlab.com/pricing/feature-comparison/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update all 3 links in the header
- [ ] 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
| 1 |
28,847,821 | 113,367,461 |
2022-08-16 22:00:51.278
|
Google Analytics Tracking: SaaS Trial Event
|
## Goal
Review the new SaaS Trial flow here: https://docs.google.com/presentation/d/1K-fwk3n_mqN_JDfGGXWMETfIWLPhRoWsEdmV7yJDD-M/
Add the Google Tag Manager JS and OneTrust (if not already included) to the new "About Your Company" page:
**gitlab.com/users/sign_up/company/new**
Paste this code as high in the `<head>` of the page as possible:
```
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NJXWQL');</script>
<!-- End Google Tag Manager -->
```
Additionally, paste this code immediately after the opening `<body>` tag:
```
<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-NJXWQL"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->
```
Fire the following dataLayer event upon a successful form submission after the "Continue" button click. The `aboutYourCompanyType` should be dynamic. If the user is part of the Free Account flow, they will have an additional toggle field "Gitlab Ultimate Trial". If the user is part of the SaaS flow, the field should not be there, so the variable value should be `ultimate_trial`.
```
dataLayer.push({
'event':'aboutYourCompanyFormSubmit',
'aboutYourCompanyType':'[ultimate_trial or free_account]'
});
```
## Page(s)
Which page(s) are involved in this request?
* gitlab.com/users/sign_up/company/new
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich @tywilliams
- [ ] Consulted: @s_awezec
- [ ] Informed: @mpreuss22 @justin.vetter
## 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
| 4 |
28,847,821 | 113,364,374 |
2022-08-16 20:15:11.621
|
ENG: Integrate Launchdarkly component with the dataLayer
|
## Goal
Note from Dennis:
https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/14#note_1050161026
## 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: `@jgarc`
- [ ] Consulted: `Dennis`
- [ ] 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
| 1 |
28,847,821 | 113,363,430 |
2022-08-16 19:45:36.281
|
Add All Resources link and update page
|
## Goal
We would like to add a link to "[All resources](https://about.gitlab.com/resources/)" and update the page with the latest branding.
### Jobs To Be Done
* **Situation**: *When a website visitor is looking for GitLab resources*
* **Motivation**: *We want to have the newest assets/webcasts accessible \*
* **Outcome**: *So we can drive registrations/downloads from website visitors*
## Page(s)
Which page(s) are involved in this request?
* `[All Resources Page](https://about.gitlab.com/resources/)`
## 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?
- [ ] 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
| 2 |
28,847,821 | 113,362,171 |
2022-08-16 19:03:44.381
|
Eng: Replace minimal footer with version from navigation repo
|
## Goal
Currently some pages (such as the solutions page) use the minimal footer. We should remove the hardcoded footer in BEx, and replace any instances with the minimal footer in the navigation repository.
Example of implementing our minimal header [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/831).
| 1 |
28,847,821 | 113,361,176 |
2022-08-16 18:31:58.879
|
ENG: Resolve Feature Flag evaluation with experiments
|
## Goal
Background can be found in this [support ticket](https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/e6d657282472fe1252bdcb1e592caef5/We_are_using_Launchdarkly_w...___LaunchDarkly.pdf)
I'll be honest. I'm still unclear on what a percentage rollout is compared to an experiment.
## 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
| 1 |
28,847,821 | 113,361,153 |
2022-08-16 18:31:28.652
|
ENG: Implement Launchdarkly with Custom Events
|
## Goal
According to this [support ticket](https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/852679b3678d1a281b31d99956848d78/Hello__We_are_using_Launchd...___LaunchDarkly.pdf), we need to make sure our metrics are set up as custom events within LaunchDarkly.
> If you are changing the URL upon click, you would have to use a custom conversion (Such as if
you were submitting a form that redirects to a new page, etc.).
> If your click metric triggers a page redirect, then the redirect is happening before the click
event can be sent back to LaunchDarkly.
> Click metrics are unfortunately not very robust; I would suggest recreating the metric as a
custom conversion metric instead:
https://docs.launchdarkly.com/home/experimentation/metrics/custom-conversion.
> This way, you have greater control and can call track when you need to and flush immediately
right after to ensure that the metric event is captured prior to redirect.
Hypothesis: The behavior that I have when using click events is that clicking on said targets will result in incrementing the unique visitors by 1.
## 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
| 2 |
28,847,821 | 113,361,109 |
2022-08-16 18:30:46.777
|
ENG: Debug URL parameters hidden class
|
## Goal
Discovered in this MR: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/897
`.hidden` class doesn't update when passing URL parameters to pages with a LaunchDarkly component. Checking the props within the LaunchDarkly components shows us the value of the `loading` data value is correct. This makes me believe that the component is not showing this change in value within the UI.
comment with Megan: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/897#note_1058902114
## 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
| 2 |
28,847,821 | 113,355,718 |
2022-08-16 16:01:53.921
|
Inconsistent Text size on the Footer
|
## Goal
In the footer, we would like to change the text size of "Cookie Preferences" to match the size of the other text.
### Describe the Bug
### What's my browser?
https://www.whatsmybrowser.org/b/GU0G1
## Page(s)
Which page(s) are involved in this request?
* All pages
## 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
| 2 |
28,847,821 | 113,302,494 |
2022-08-15 18:06:52.541
|
Docs Subdomain - Update Google Tag Manager ID
|
## Goal
The current Google Tag Manager account ID on the docs subdomain is set to `GTM-WZCXKT5` - no one can access this GTM account because it was created by a former employee on their personal work email address. There is an issue within the Google Analytics page URL data where `/index.html` needs to be included in order to match the correlated `index.md` file (analyzed by the technical content writers). Related GitLab [issue here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1214#note_1064405619).
In order to affix `/index.html`, we'll need to first update the Google Tag Manager ID from `GTM-WZCXKT5` to `GTM-NJXWQL` on docs.gitlab.com, that way we can configure a new GA tags on a GTM account we have access to.
### Instructions
- Revise the existing GTM code in the `<head>` by switching the ID from `GTM-WZCXKT5` to `GTM-NJXWQL` (<https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/content/assets/javascripts/google_tagmanager.js>):
```js
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NJXWQL');
```
- Additionally, update the ID in GTM `<body>` tag (<https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/layouts/gtm.html>):
```html
<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-NJXWQL"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->
```
## Page(s)
Which page(s) are involved in this request?
* All docs.gitlab.com pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @sselhorn @sarahgerman @axil @marcel.amirault @susantacker
- [ ] Informed: @justin.vetter @laurenbarker @mpreuss22
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 113,300,285 |
2022-08-15 17:08:56.383
|
Release: Launch Qualtrics survey on Help Topics page
|
## Goal
We would like to learn more about the Get Help page to find opportunities for improvement by implementing a Qualtrics survey that was completed as part of this issue.
**What the survey is for**<br>
To determine what users are expecting to find on the [Help Topics](https://about.gitlab.com/get-help/) page.
**Who the survey is to be completed by**<br>
Everyone who comes to the Help Topics page
**How the survey delivered to user**<br>
Immediately on arrival of the Help Topics page using a notification in the corner of the page like [this](https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/791#note_651041011) but with updated branding.
**What URL and platform the survey is hosted on**<br>
[Qualtrics ](https://gitlab.fra1.qualtrics.com/jfe/form/SV_brobq0o5o2Fdtu6)
**How long the survey is open**<br>
Open until we get 200 responses.
### Jobs To Be Done
* **Situation**: *When a user visits the get help page, a notification displays in the corner for the survey*
* **Motivation**: *We want to gather data on what users are looking for when the arrive on the get help page*
* **Outcome**: *So we can improve our get help page*
## Page(s)
Which page(s) are involved in this request?
* `https://about.gitlab.com/get-help/`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @ctsang-ext
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create notification for survey on Get Help Page, linking out to [this survey](https://gitlab.fra1.qualtrics.com/jfe/form/SV_brobq0o5o2Fdtu6)
- [ ] Answer in thread: Is it also possible to gather what page each person is at before they get to the Get Help 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
| 2 |
28,847,821 | 113,300,131 |
2022-08-15 17:03:23.847
|
ENG: Solutions Landing page MVC 1
|
## Goal
We would like to update [/solutions](https://about.gitlab.com/solutions/) which will improve user experience as measured by metrics.
## Page(s)
Which page(s) are involved in this request?
* [/solutions](https://about.gitlab.com/solutions/)
## Workfiles
* [On-going agenda](https://docs.google.com/document/d/1EWheKycnvlBzDSSE3h5RO9h_GPI7R_3uio7MpJ4rohU/edit?usp=sharing)
* [Figma design](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=2144%3A11815)
* [Copy Deck](https://docs.google.com/document/d/1EP8tAlmI7QX1YfnE4J2lPYN29UNf__SLXOHdZjtgrQw/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: `@ncregan` @KristinaWeis @andrewrhickey @chandlergibb
- [ ] Informed: @justin.vetter
## In scope
What is within scope of this request?
- [ ] Landing page
## Out of scope
What is out of scope and not part of this iteration?
- Single landing page for each theme/grouping for this iteration
## 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
| 10 |
28,847,821 | 113,297,210 |
2022-08-15 15:49:05.636
|
Place full navigation on pricing page
|
## Goal
We would like to remove the minimized navigation component from the pricing page and use the full navigation instead.
### Jobs To Be Done
* **Situation**: *When a user visits the pricing page*
* **Motivation**: *We want to display the full navigation component in the header*
* **Outcome**: *So we can provide users with a full navigation experience*
## 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: `GitLab Handle`
- [ ] Consulted: @justin.vetter @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Switch 'minimized-navigation' for default layout on pages/pricing/index.vue`
- [ ] Test pricing page to ensure no regressions
- [ ] Fix all regressions due to nav swap before deploying to prod
- [ ] Deploy and and monitor slack channels
- [ ] Create issue for capturing feedback if needed
## 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
| 3 |
28,847,821 | 113,293,262 |
2022-08-15 14:31:01.082
|
ENG: Spike Personalization Foundation | Detect if a user is logged into the product from marketing site
|
## Goal
start on spike work to evaluate our options for detecting when a user is logged into the product from the marketing site.
### Jobs To Be Done
* **Situation**: *When a user is logged into the product we are able to detect it on about.gitlab.com*
* **Motivation**: *So we can personalize content for users*
* **Outcome**: *Drive users to better content*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @tywilliams
- [ ] Consulted: @justin.vetter @laurenbarker
- [ ] Informed: @ndubord @fqureshi
## In scope
What is within scope of this request?
- [ ] Spike Research on personalization possibilities
- [ ] Integrate with the product so we can create new issues to personalize BE site
## Out of scope
What is out of scope and not part of this iteration?
- Full integration of personalization
- 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
| 10 |
28,847,821 | 113,213,526 |
2022-08-12 18:38:57.448
|
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
| 5 |
28,847,821 | 113,213,290 |
2022-08-12 18:25:27.100
|
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
| 5 |
28,847,821 | 113,160,806 |
2022-08-11 23:08:39.579
|
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
| 1 |
28,847,821 | 113,156,733 |
2022-08-11 21:41:41.547
|
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
| 2 |
28,847,821 | 113,155,287 |
2022-08-11 20:41:51.895
|
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
| 1 |
28,847,821 | 113,153,632 |
2022-08-11 19:40:06.229
|
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
## 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
| 1 |
28,847,821 | 113,146,359 |
2022-08-11 16:48:51.661
|
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
| 1 |
28,847,821 | 113,092,679 |
2022-08-10 19:35:38.819
|
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
| 3 |
28,847,821 | 113,086,343 |
2022-08-10 17:19:01.039
|
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
| 2 |
28,847,821 | 113,360,356 |
2022-08-09 21:48:40.049
|
Website Bug: GitLab Learn for everyone link goes to 404 page
|
This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/
This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.
#### What is/are the relevant URL(s)
https://about.gitlab.com/learn/certifications/public/
#### Briefly describe the bug
Example: A link is broken
The [GitLab Learn for everyone link ](https://about.gitlab.com/learn/public/) is broken and takes user to a 404 page
#### If possible, please specify how to reproduce the bug
1. Navigate to https://about.gitlab.com/learn/certifications/public/
2. Click on the GitLab Learn for everyone link
#### Please provide any relevant screenshots or screencasts
How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/
#### What is your window size, browser, operating system, and versions
Please use the following website to determine your browser specifications and provide a link developers can follow:
What is my browser https://www.whatsmybrowser.org
https://www.whatsmybrowser.org/b/8LTBD
#### What computing device are you using?
Please list the brand and model (Example: Samsung Galaxy S 10 Plus)
Windows 10 desktop
### What type of input are you attempting to use?
Webpage interactivity is often tied to a specific device event.
- [ ] Touchscreen
- [ ] Touchpad
- [x] Mouse click
- [ ] Mouse click and drag
- [ ] Scrollwheel
- [ ] Keyboard
- [ ] Stylus
- [ ] Other (please specify)
#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?
- [x] I tried a fresh incognito window & it had no impact.
- [ ] The problem goes away when using an incognito window.
- [ ] The problem only happens when certain cookies are set to a specific value (please specify below).
#### Please list any browser plugins you have enabled
Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing.
None
#### Are you blocking javascript or any other resources?
Javascript is needed for certain website functionality.
- [ ] I AM blocking javascript or other resources.
- [x] I am NOT blocking javascript or other resources.
#### What is your geographic location
Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies.
New Zealand
#### What type of network are you connected to?
**Type**
- [X] Wired
- [ ] Wifi
- [ ] Cellular (4G, 5G, etc)
- [ ] Satellite
- [ ] Other
`Insert details here if applicable`
**Location**
- [X] Home
- [X] Workplace
- [ ] Travel facility (hotel, airport, conference center, etc)
- [ ] Public venue (restaurant, library, cafe, etc)
- [ ] VPN
- [ ] Other
`Insert details here if applicable`
**Hardware**
- [ ] I am behind a network security appliance such as a firewall
- [ ] I am using a pi-hole or other hardware-based traffic blocker
- [ ] Other
`Insert details here if applicable`
<!-- Please do not remove the items below, they are needed to automatically notify the relevant entities -->
/cc @gl-website
<!-- These labels will be automatically applied unless you edit or delete the following section -->
| 1 |
28,847,821 | 112,964,969 |
2022-08-08 20:28:18.833
|
slippers-ui - v2.1.2: import
|
## Goal
Import the latest version of slippers-ui.
| 1 |
28,847,821 | 112,964,539 |
2022-08-08 20:13:45.277
|
Migrate /learn/
|
## Goal
https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1206
Migrate the /learn/ page to Buyer Experience. Originally we were going to apply some css changes, but the page is very simple, it wouldn't take long with Slippers (1-2 days max).
| 6 |
28,847,821 | 112,964,229 |
2022-08-08 20:03:59.849
|
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
| 1 |
28,847,821 | 112,961,636 |
2022-08-08 18:48:01.303
|
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
| 2 |
28,847,821 | 112,953,304 |
2022-08-08 15:39:23.867
|
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
| 1 |
28,847,821 | 112,862,646 |
2022-08-05 18:53:47.352
|
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
| 1 |
28,847,821 | 112,862,519 |
2022-08-05 18:49:03.167
|
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
| 2 |
28,847,821 | 112,859,478 |
2022-08-05 16:51:46.415
|
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
| 8 |
28,847,821 | 112,817,875 |
2022-08-04 22:14:20.598
|
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
| 1 |
28,847,821 | 112,815,949 |
2022-08-04 20:56:01.516
|
Understanding remaining www-gitlab-com pages
|
## Goal
I wanted to take some time and comb through www-gitlab-com to understand what's still there, and clean-up any unused assets.
| 4 |
28,847,821 | 112,813,699 |
2022-08-04 19:35:57.981
|
www-gitlab-com cleanup
|
## Goal
None of these files appear to be used/referenced anymore.
| 2 |
28,847,821 | 112,806,442 |
2022-08-04 17:03:33.949
|
www-gitlab-com cleanup /source/jobs/ section
|
## Goal
Doesn't seem like any of these files are used/are live on the site. The Apply section redirects to just /jobs/, I'm assuming this section was removed, but the code was never deleted.
| 2 |
28,847,821 | 112,800,272 |
2022-08-04 15:24:16.757
|
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
| 3 |
28,847,821 | 112,758,305 |
2022-08-04 00:58:59.004
|
www-gitlab-com cleanup /source/devops-tools/ section
|
## Goal
None of these files are used/referenced anymore, and there's already redirects setup for all these files.
| 2 |
28,847,821 | 112,750,972 |
2022-08-03 20:03:04.989
|
Remove Commit Virtual from Commit website
|
## Goal
We would like to have the Virtual registration section removed from the Commit website as it's being delayed til February 2023. Mentions of Virtual for speakers should also be removed.
### Jobs To Be Done
* **Situation**: *When users visit the Commit website*
* **Motivation**: *We want to promote only the NY and London events at this time*
* **Outcome**: *So we can encourage registration for the in-person events instead of Virtual*
## Page(s)
Which page(s) are involved in this request?
* [Commit](https://about.gitlab.com/events/commit/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @meganfilo
- [ ] Consulted: ` @jhalloran @khartline `
- [ ] 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
| 1 |
28,847,821 | 112,743,471 |
2022-08-03 16:48:33.244
|
Typography Adjustment - Support Template
|
## Goal
The typography on the main support page seems "off" compared to [the Figma template](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=388%3A12778). Some things I've noticed are:
| Section | Figma | https://about.gitlab.com/support/ | Screen Shot | Style |
|---------|-------|-----------------------------------|-------------|-------------|
| [Test in priorty support table](https://about.gitlab.com/support/#priority-support) | font size: 16px | font size: 20px |  | Body 2 |
| All bulleted text | font size: 16px, line-height: 24px , text-indent: 16px | font size: 20px, line-height: 24px, no text indent |  | Lists |
| More Help @ bottom |  | duplicated text at font-size: 16px, line-height: 24px |  | None, please remove smaller text |
make sure we are following the grid, per comment above:
| In production | In design |
| ------ | ------ |
|  |  |
### What's my browser?
https://www.whatsmybrowser.org/b/M528L
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/
*
## 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
| 3 |
28,847,821 | 112,736,417 |
2022-08-03 14:31:14.412
|
Remove /pricing/gitlab-com/feature-comparison/ and update redirects
|
## Goal
https://gitlab.slack.com/archives/CN8AVSFEY/p1659459944969999
| 2 |
28,847,821 | 112,732,918 |
2022-08-03 14:26:58.022
|
Remove unused pricing/feature code and assets in www v2
|
## Goal
There's been some confusion over what pricing/features data files are what, to simplify this process lets remove all unused data files.
| 2 |
28,847,821 | 112,678,460 |
2022-08-02 17:23:31.156
|
[Phase 1] Copy features.yml into Buyer Experience repo
|
## Goal
As defined in the Phase 1 here: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1093
Copy over features.yml into the Buyer Experience repo. This may also require bringing over categories.yml and stages.yml.
| 2 |
28,847,821 | 112,674,549 |
2022-08-02 15:54:05.247
|
ENG: /features - Implement side nav
|
## Goal
Implement side navigation to all /features pages that have been updated with the most recent template.
## Page(s)
Which page(s) are involved in this request?
* [Continuous Integration](https://about.gitlab.com/features/continuous-integration/)
## 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
| 2 |
28,847,821 | 112,674,384 |
2022-08-02 15:50:45.617
|
ENG: /solutions - Implement side nav
|
## Goal
Implement side navigation to all /solution pages that have been updated with the most recent template.
## Page(s)
Which page(s) are involved in this request?
* [Automated Delivery](https://about.gitlab.com/solutions/delivery-automation/)
* [Continuous Software Security Assurance](https://about.gitlab.com/solutions/continuous-software-security-assurance/)
* [Public Sector](https://about.gitlab.com/solutions/public-sector/)
## 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
| 8 |
28,847,821 | 112,673,600 |
2022-08-02 15:37:14.181
|
ENG: Results by Type - Blog, Handbook, All
|
## Goal
We would like add a feature to our search results that enables users to view results by type.
We want to let users know how many results exist in the Blog, Handbook, Everything, and enable them to view just those results.
### Jobs To Be Done
* **Situation**: *A user can sort results by type that is powered by Swiftype site search API.*
* **Motivation**: *We want to lower bounce rate, increased pages per session, and increased time on site.*
* **Outcome**: *So we can increase engagement.*
## Page(s)
Which page(s) are involved in this request?
* The search bar in the navigation
## 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?
- [ ] Add sort by type (Blog, Handbook, Everything) feature
- [ ] Ship to about.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
| 4 |
28,847,821 | 112,673,581 |
2022-08-02 15:36:47.070
|
ENG: Sort Results
|
## Goal
We would like add a feature to our search results that enables users to sort results.
This issue is for implementing the "Sort by" component at the top of the full panel layover.
[Figma Design](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=137%3A1387)
### Jobs To Be Done
* **Situation**: *A user can sort results that is powered by the Swiftype site search API.*
* **Motivation**: *We want to lower bounce rate, increased pages per session, and increased time on site.*
* **Outcome**: *So we can increase engagement.*
## Page(s)
Which page(s) are involved in this request?
* The search bar in the navigation
## 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?
- [ ] Add sort by feature
- [ ] Ship to about.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
| 4 |
28,847,821 | 112,673,564 |
2022-08-02 15:36:17.915
|
ENG: Results and Pagination
|
## Goal
We would like to implement a new search design template and apply it to the search experience launched from the header of about.gitlab.com.
This issue is for implementing the full panel lay over with results and pagination.
[Figma Design](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=137%3A1387)
### Jobs To Be Done
* **Situation**: *When a user clicks on the search icon in the header, they get the new template design that is powered by the Swiftype site search API.*
* **Motivation**: *We want to lower bounce rate, increased pages per session, and increased time on site.*
* **Outcome**: *So we can increase engagement.*
## Page(s)
Which page(s) are involved in this request?
* The search bar in the navigation
## 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?
- [ ] Build new search template with results and pagination
- [ ] Stretch goal to display the icon and result type
- [ ] Ship to about.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
| 4 |
28,847,821 | 112,606,388 |
2022-08-01 14:15:27.692
|
Commit Registration Page: Add Speakers
|
https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1070#note_1046593435
> We would like to add additional speakers to the featured speakers section of the website.
>
> The three people we would like to add are:
>
> * Fernando Diaz - Senior Technical Marketing Manager ([Fernando's GitLab Profile](https://gitlab.com/fjdiaz))
> * Francis Ofungwu - Global Field CISO ([Francis' GitLab Profile](https://gitlab.com/fofungwu))
> * William Arias - Senior Technical Marketing Manager ([William's GitLab Profile](https://gitlab.com/warias))
>
> [Here is a link to the headshots](https://drive.google.com/drive/folders/1MpT8pY2kUgVm38UzOL3BGARFXm_cqlcq)
## Scope of changes
- [ ] Add speakers to content file
- [ ] Adjust speakers section UI if necessary
- [ ] Update NY address
| 2 |
28,847,821 | 112,521,657 |
2022-07-29 19:42:09.880
|
ENG: Pricing | Add contact sales link to Ultimate tier card
|
## Goal
We would like to add an additional contact sales link to the Ultimate tier card which will improve how customers can buy GitLab as measured by increased Enterprise sales.
### Jobs To Be Done
* **Situation**: *When an Enterprise customer visits our pricing page...*
* **Motivation**: *We want to offer them their preferred method of buying GitLab ...*
* **Outcome**: *So we can finalize their purchase.*
## Page(s)
Which page(s) are involved in this request?
* [Pricing](https://about.gitlab.com/pricing/)
* [Figma designs](https://www.figma.com/file/uwtK7pFI6KRHeQBL8Pk8RP/Pricing---tier-updates?node-id=35%3A7705)
## 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?
- [ ] Add contact sales link to ultimate card
- [ ] 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
| 2 |
28,847,821 | 112,517,772 |
2022-07-29 17:41:32.428
|
ENG: Homepage | remove/hide See what's coming in GitLab 15 and beyond pill
|
## Goal
We would like to remove/hide the `See what's coming in GitLab 15 and beyond →` pill from the homepage header section. We will replace the link with a new pill link in the future.
### 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: @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove the pill link
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Changing the link
- 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
| 1 |
28,847,821 | 112,421,719 |
2022-07-28 23:00:40.179
|
ENG: Content update Commit Landing page
|
## Goal
We would like to add the location venue information for two of the events. We would also like to swap out the image for the virtual 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?
* [Commit](https://about.gitlab.com/events/commit/)
* [Figma](https://www.figma.com/file/zxa7DLEbZrkeh0YJozVOqb/Event-Templates-%2F-Commit-2022?node-id=2150%3A8170)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @jhalloran @fqureshi @justin.vetter
- [ ] Informed: `@khartline`
## In scope
What is within scope of this request?
- [ ] Add links to a Google map address for New York City and London venues
- [ ] Update FAQ section with venue information `When and where` in the [FAQ Doc](https://docs.google.com/document/d/1w_MysOiyfDRW5DFi3NUx1cTCuN3VNBJWwPmZilRdxhE/edit#heading=h.5xovaeihi7p0)
- [ ] Swap thumbnail image for Virtual event
## 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
| 2 |
28,847,821 | 112,378,721 |
2022-07-28 17:23:49.645
|
[Phase 2] Automate the synchronization of features.yml into Buyer Experience
|
## Goal
We would like to synchronize feature.yml in both the www repository and the buyer experience repository.
**How?**
_This is just a rough idea, I haven't looked into it much_
Create a step in the www-gitlab-com pipeline that either uses gitlab-api GET, gitlab pages, or whatever else to host features.yml. Then in Buyer Experience write a script/another step in the build to curl the file down.
| 6 |
28,847,821 | 112,377,583 |
2022-07-28 17:14:22.933
|
ENG: Update pricing faq
|
## Goal
The FAQ section on the pricing page is getting out of sync, there have been changes, like this one: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/107569#note_1040516722
That hasn't been copied over.
## Page(s)
Which page(s) are involved in this request?
* [Pricing](https://about.gitlab.com/pricing) FAQ section
* [Changes to be mirrored](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/107569/diffs#note_1040516722)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter
- [ ] Informed: `@m_taylor`
## In scope
What is within scope of this request?
- [ ] Update FAQ section
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Integrate legacy pricing_faq.yml to current 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
| 1 |
28,847,821 | 112,372,194 |
2022-07-28 15:32:18.199
|
slippers-ui - v2.1.0: import
|
## Goal
Import the latest version of slippers-ui.
| 1 |
28,847,821 | 112,370,202 |
2022-07-28 14:56:20.213
|
Re-add deprecated localized pages
|
## Goal
As per this slack [thread](https://gitlab.slack.com/archives/CN8AVSFEY/p1658752802724089), add back the following pages that were removed in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/971):
- https://about.gitlab.com/fr-fr/pourquoi/integration-continue-pour-construire-et-tester-plus-rapidement/
- https://about.gitlab.com/de-de/warum/nutze-continuous-integration-fuer-schnelleres-bauen-und-testen/
### 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
| 1 |
28,847,821 | 112,331,506 |
2022-07-27 22:14:17.016
|
ENG: Icons on ROI calculator page are showing up very small and filled in rather than outlined
|
## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?
### Describe the Bug
What is the bug?
Icons on ROI calculator page are showing up very small and filled in rather than outlined
### What's my browser?
Share your browser information from https://www.whatsmybrowser.org/
[https://www.whatsmybrowser.org/b/OFL7U](https://www.whatsmybrowser.org/b/OFL7U)
## Page(s)
Which page(s) are involved in this request?
* [ROI Calculator](https://about.gitlab.com/calculator/roi/)
| Live | Figma |
| ------ | ------ |
|  |  |
## 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
| 1 |
28,847,821 | 112,318,113 |
2022-07-27 16:40:02.019
|
Migrate Commit page SVGs to Slippers
|
With a tight due date, I was unable to add the new SVG icons we are using on the new Commit page to Slippers.
As part of this issue I will:
- [x] Add icons to Slippers
- [ ] Once Slippers version is bumped in Buyer Experience, swap out the hardcoded icons for the SlpIcon alternative
| 2 |
28,847,821 | 112,312,292 |
2022-07-27 14:54:52.525
|
Plan: Support Services page (Exploration and Research)
|
## Goal
We would like to learn more about the Support Services page to find opportunities for improvement
### Jobs To Be Done
TBD
## Page(s)
Which page(s) are involved in this request?
- [Support Services](https://about.gitlab.com/services/#contactform)
- [Figma](https://www.figma.com/file/2zmj9hb6MBH40d6NMZm8Jw/Professional-Services?node-id=26%3A3)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @Tinaliseng, @jhalloran, @dennischarukulvanich
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Exploration + Next steps for design and/or research
## 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
- [ ] Engineering
| 6 |
28,847,821 | 112,304,413 |
2022-07-27 13:00:14.844
|
Remove unused pricing/feature code and assets in www
|
## Goal
There's been some confusion over what pricing/features data files are what, to simplify this process lets remove all unused data files.
| 4 |
28,847,821 | 112,262,805 |
2022-07-26 20:59:48.401
|
Define requirements to consume Swiftype API
|
## Goal
We would like to define requirements for about.gitlab.com to consume the Swiftype API. This will enable us to customize the search experience and execute on the parent OKR of this issue.
### Jobs To Be Done
* **Situation**: *We are using a javascript snippet from Swiftype to enable search functionality, as documented in the [quick start guide here](https://swiftype.com/documentation/site-search/crawler-quick-start). This limits our ability to customize the experience.*
* **Motivation**: *We want to implement the [Swiftype site search API](https://swiftype.com/documentation/site-search/overview) to programmatically alter how our
* pages are crawled
* documents are indexed
* searches are completed
* analytics are generated
* and more!
* **Outcome**: *To do this, we need to define requirements to implement the site search API on about.gitlab.com.*
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com - search that exists in the header
* https://swiftype.com/documentation/site-search/overview
## 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?
- [ ] Investigate the Swiftype search API
- [ ] Create a feature branch or sandbox environment that uses the search type api
- [ ] Define requirements to implement Swiftype search API on primary header search on a about.gitlab.com
- [ ] Create issue to implement Swiftype search API
## Out of scope
What is out of scope and not part of this iteration?
- This issue is not for implementing the api, is purely exploratory and to define the 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
| 4 |
28,847,821 | 112,245,985 |
2022-07-26 15:51:46.107
|
Enable feature flags for Buyer Experience repository
|
## Goal
We would like to enable feature flags for the Buyer Experience repository.
### Jobs To Be Done
Feature flags deploy your application’s new features to production in smaller batches. You can toggle a feature on and off to subsets of users, helping you achieve Continuous Delivery. Feature flags help reduce risk, allowing you to do controlled testing, and separate feature delivery from customer launch.
https://docs.gitlab.com/ee/operations/feature_flags.html
Related https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/epics/133
## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience
## 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?
- [ ] Enable feature flag functionality for Buyer Experience repository
- [ ] Create a test feature flag, enable it, monitor, and verify it is working. This test could be a hidden code comment in the footer or similar that is not present to our users.
- [ ] Disable the test feature flag
- [ ] Create a video demonstrating how to use feature flags in the Buyer Experience repository. Post the video to our Digital Experience playlist on GitLab Unfiltered
- [ ] Document the process in our handbook, and link to the video
## Out of scope
What is out of scope and not part of this iteration?
- Any other feature flag testing - those will need new issues. This is just the creation and implementation of a control feature flag to verify the functionality is working.
## 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
| 4 |
28,847,821 | 112,183,796 |
2022-07-25 21:23:45.332
|
ENG: Typography spacing bug mobile | Why GitLab
|
### Describe the Bug
On a mobile device the typography and spacing overlaps on the DevOps chart.
<details><summary>Screen Shot</summary>
</details>
### What's my browser?
Safari, Chrome, & Firefox mobile see this issue.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/why-gitlab/
## 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
| 1 |
28,847,821 | 112,056,565 |
2022-07-22 17:40:29.726
|
Eng: Find a Alliances Partner Page
|
## Goal
We would like to build a new template and apply it to the GitLab Alliance Partners page. This new template was created as part of [this issue.](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1107)
[Figma Link](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=60%3A2135)
### Jobs To Be Done
* **Situation**: *We'd like a unified user experience for finding GitLab partners*
* **Motivation**: *When users need more information we can direct the to the correct spot*
* **Outcome**: *So we can offer them the best service*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/partners/technology-partners/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @ctsang-ext @mlebeau
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Move [`www-gitlab-com/data/applications.yml`](https://gitlab.com/-/ide/project/gitlab-com/www-gitlab-com/tree/master/-/data/applications.yml/) to the Buyer Experience repository
- [ ] Create a tab component ([figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=70%3A3995) )
- [ ] Enable search functionality of alliance partners (applications.yml). Search bar located in tabed component
- [ ] Create partner card ([figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=70%3A3995))
- [ ] Build "Find a Partner" template
- [ ] Modify template to link out to Impartner platform for Channel partner search (https://partners.gitlab.com/English/directory/)
- [ ] Apply "Find a Partner" template to https://about.gitlab.com/partners/technology-partners/
## Out of scope
What is out of scope and not part of this iteration?
- Creating search functionality for channel partners
- API integration for Impartner
## 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
| 8 |
28,847,821 | 111,863,275 |
2022-07-19 14:59:18.076
|
ENG: Remove grayscale styling from GitLab logo on Alliance Partners page
|
## Goal
We would like to remove the grayscale styling from the GitLab logo on the Alliance Partners page.
[Slack conversation](https://gitlab.slack.com/archives/CN8AVSFEY/p1658242096480099)
## Page(s)
Which page(s) are involved in this request?
* [Alliance Partners Page](https://about.gitlab.com/partners/technology-partners/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter
- [ ] Informed: `@smccreesh`
## In scope
What is within scope of this request?
- [ ] Removing the `filter: grayscale(100%);` from the logo svg
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Swapping any other logos from the 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
| 1 |
28,847,821 | 111,797,987 |
2022-07-18 16:10:42.639
|
Remove GitLab vs Sysdig page
|
## Goal
Please remove GitLab vs Sysdig page from staging as requested here: https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/4852#note_1028103314
## Page(s)
Which page(s) are involved in this request?
* `https://about.staging.gitlab.com/devops-tools/sysdig-vs-gitlab.html`
## 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?
- [ ] Remove page from staging
## 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
| 1 |
28,847,821 | 111,756,203 |
2022-07-18 03:12:02.315
|
Improve how bullets are presented on pricing page
|
Bullets in the Pricing Page FAQ are rendered incorrectly, for example:
We should try to fix this, as it is hard to convey more than a few lines in these answers clearly otherwise.
| 1 |
28,847,821 | 111,732,476 |
2022-07-17 00:12:00.866
|
Update to SlpDropdown to allow option names different from their values
|
Our SlpDropdown component currently takes in a list of options and gives each `<option>` tag's `name` and `value` attribute the same name. This is problematic for items where the value needs to be altered from the name/label that the user sees.
Example:
Building a filter by location for the Commit page. We want the filter option to read 'New York City', but the list of items it's filtering through have a location of 'NYC'. It would be nice if the HTML could look like `<option name="New York City" value="nyc" />`
| 4 |
28,847,821 | 111,711,066 |
2022-07-15 20:10:12.502
|
Eng: Sales page redesign
|
## Goal
We would like to update the sales page as per the [Figma design](https://www.figma.com/file/GuCqkaoZG8BqkBV6eE7xxT/Sales?node-id=43%3A2214).
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/sales/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@ctsang-ext`
- [ ] Informed: `@fqureshi`
## Out of scope
- Changing the form content on Marketo (updating any text, fields etc)
## 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
| 5 |
28,847,821 | 111,707,604 |
2022-07-15 18:18:25.735
|
Add link from Homepage "Stages of the DevOps Lifecycle" section to Stages of DevOps table on Why GitLab
|
## Goal
We would like to add a link to the second section of the homepage that links to the DevOps table on the Why GitLab page which will make a visitors experience more efficient as measured by pages per session.
### Jobs To Be Done
* **Situation**: *When a prospective user wants more information on the Stages of The DevOps cycle*
* **Motivation**: *We want to make it easy for them to view all the features listed in the DevOps Stages table*
* **Outcome**: *So we can efficiently communicate the breadth of our product.*
## Page(s)
Which page(s) are involved in this request?
* [Homepage](https://about.gitlab.com)
* [Why GitLab](https://about.gitlab.com/why-gitlab)
## 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?
- [ ] Add a text link to the subheader of the "Stages of the DevOps Lifecycle" section of the homepage that links to the Stages of DevOps table on Why GitLab
## 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
| 1 |
28,847,821 | 111,667,052 |
2022-07-14 23:26:00.743
|
GA: Turn off tracking for Denmark, Norway, France, Italy, and Austria
|
## Goal
Related note: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/997#note_1025872795
Recent laws were passed that declared Google Analytics illegal since EU data is processed on a US server. Turn off Google Analytics entirely in Denmark, Austria, France, Italy and Norway.
Please refer to this OneTrust Geolocation Exposure script:
https://community.cookiepro.com/s/article/UUID-f1caf6bb-0003-8e79-6caf-2a7d04e357d7?language=en_US
This line will grab the country ID from OneTrust:
`var country = options.country.toString();`
The geolocation script is already on placed:
<img src="/uploads/d3c7e7d08afbce3c549c6ed33ae52d4f/Screen_Shot_2022-11-12_at_11.49.49_AM.png" width="800">
Please place the following code before the GTM script, but after the Geolocation Exposure script on all pages:
- about.gitlab.com
- page.gitlab.com
- learn.gitlab.com
- gitlab.com (public facing pages)
- docs.gitlab.com
```
<script>
window.dataLayer = window.dataLayer || [];
dataLayer.push({
'oneTrustCountryId': options.country.toString();,
'event' : 'OneTrustCountryLoad'
});
</script>
```
On Google Tag Manager, apply the oneTrustCountryId dataLayer variable to all Google Analytics tags to the trigger, so the tag doesn't fire for: DK, AT, FR, IT and NO.
## Page(s)
Which page(s) are involved in this request?
- about.gitlab.com
- page.gitlab.com
- learn.gitlab.com
- gitlab.com (public facing pages)
- docs.gitlab.com
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich @miraclebanks @jgarc
- [ ] Consulted: @laurenbarker @justin.vetter @RobRosu @emccrann @BronwynBarnett @MihaiConteanu
- [ ] Informed: @mpreuss22 @christinelee @dmicovic @jahye1 @degan @rkohnke
## 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
| 3 |
28,847,821 | 111,664,333 |
2022-07-14 21:07:31.404
|
Add Minimized Footer to Navigation Repository
|
## Goal
We would like to add the minimized footer to the Nav repository so we can use it within Buyer Experience
As part of the refresh a few months ago, we created a minimized footer with a goal for it to be used on the Pricing page. Looks like it is not being used there anymore, but the mini-footer still lives in BE. It would be nice to use for our Commit page, but the Web IDE and View Source buttons are not dynamic to the page/do not work. Also, @justin.vetter proposed a good point in that the mini-footer does not contain any legal type of links, such as our Privacy policy.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `Search, Nav, and Support Team`
- [ ] Consulted: @jhalloran @meganfilo @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
1. Investigate and add, if applicable, any necessary links to the minimized footer
2. Add the mini-footer html and styles (found in BE at `/components/footer/minimized-footer.vue`) to the Navigation repository (OR! Refactor the current footer to take in some kind of prop that will make it change to be mini on a page)
3. Fix the View Source and Web IDE links to work dynamically depending on what page the footer is used on
## Out of scope
What is out of scope and not part of this iteration?
- Add the minimized footer to any pages, we can save that for future issues.
## 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 (maybe, depending on if extra links are needed)] UX Design
- [x] Engineering
| 2 |
28,847,821 | 111,661,310 |
2022-07-14 19:36:28.584
|
[SPIKE] Understanding features.yml
|
# Investigate features.yml
### Introduction
The www-gitlab-com repository has 1 massive data file, features.yml, and 2 smaller related files, categories.yml and stages.yml:
- features.yml is over 11,000 lines long with 554 features.
- categories.yml is over 2500 lines long with 132 categories.
- stages.yml is over 2300 lines long.
### Why is it an issue?
Last year (2021) the decision was made to start migrating the marketing site from the www-gitlab-com repository into a new repository (buyer experience). This year, there are efforts being made to migrate the handbook out of the www-gitlab-com repository and into it's own. Since the features.yml file feeds content to both the handbook and buyer experience pages, we need to come up with an automated solution. While coming up with the solution we should also rethink the data structure, and how we can best serve the people using it (product). How can we make the product teams life easier while satisfying the needs of handbook and buyer experience.
# Usage
Last 20 updates to features.yml
- 18 unique contributors
- 12 from product
- 6 from engineering
- 8 added features
- 2 removed features
- 9 modified features
- 1 Update to PPS scores
~2 changes a week to file
### Related pages/links:
- https://about.gitlab.com/handbook/marketing/digital-experience/website/ - Resource
### Pages that read from features.yml
**www-gitlab-com**
- https://about.gitlab.com/handbook/marketing/strategic-marketing/dot-com-vs-self-managed/
- https://about.gitlab.com/features/by-theme/
- https://about.gitlab.com/features/by-paid-tier/
- https://about.gitlab.com/devops-tools/
- https://about.gitlab.com/pricing/gitlab-com/feature-comparison/
- https://about.gitlab.com/stages-devops-lifecycle/ (for everything in stages-devops-lifecycle/)
- https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/ (all the comparison pages)
**Buyer Experience**
- https://about.gitlab.com/pricing/
- https://about.gitlab.com/features/
- https://about.gitlab.com/pricing/premium/
- https://about.gitlab.com/pricing/ultimate
- https://about.gitlab.com/stages-devops-lifecycle/ (for everything in stages-devops-lifecycle/)
- https://about.gitlab.com/pricing/self-managed/feature-comparison/
### features.yml properties (116 unique)
```
[
"anchore",
"ansible",
"asana",
"atlassian_confluence",
"aws_ecr",
"azure_cr",
"azure_devops",
"bamboo",
"basecamp",
"bitbucket",
"bitbucket_data_center",
"bitbucket_data_centre",
"bitbucket_org",
"blueprint_storyteller",
"broadcom_rally",
"buildkite",
"ca_agile_central",
"ca_veracode",
"capability",
"category",
"checkmarx",
"chef",
"circle_ci",
"codefresh",
"codestar",
"collabnet_continuum",
"crucible",
"deployhq",
"description",
"docker_hub",
"docker_trusted_registry",
"electric_flow",
"feature_page",
"fogbugz",
"gerrit",
"gitea",
"github",
"github_com",
"github_enterprise",
"github_pages",
"gitlab_bronze",
"gitlab_ci",
"gitlab_com",
"gitlab_com_parity",
"gitlab_core",
"gitlab_free",
"gitlab_gold",
"gitlab_issue_boards",
"gitlab_merge_requests",
"gitlab_pages",
"gitlab_premium",
"gitlab_security",
"gitlab_silver",
"gitlab_starter",
"gitlab_stater",
"gitlab_ultimate",
"gogs",
"google_cr",
"harness",
"hcl_appscan",
"hours_per_incident",
"incidents_per_year",
"jenkins",
"jfrog",
"jira",
"jira_align",
"jira_servicedesk",
"launchdarkly",
"link",
"link_descipition",
"link_description",
"logo",
"microfocus_alm_octane",
"microfocus_fortify",
"microfocus_ppm",
"nagios",
"parity_description",
"planview",
"pluralsight_flow",
"plutora",
"pps_aggregate",
"pps_recent",
"pricing_page",
"pricing_theme",
"puppet",
"qualys",
"quay",
"rapid7",
"redmine",
"roi_case",
"saas",
"saltstack",
"semmle",
"shortand",
"shorthand",
"snyk",
"solution",
"sonarqube",
"sonatype_nexus_platform",
"sonatype_nexus_repo",
"spinnaker",
"splunk",
"svn",
"synopsys",
"sysdig",
"targetprocess",
"teamcity",
"tfs_vsts",
"title",
"travis_ci",
"trello",
"version_one",
"whitesource",
"works_by_default",
"xebialabs",
"zoho_sprints"
]
```
| 8 |
28,847,821 | 111,545,154 |
2022-07-13 00:54:21.496
|
next steps CTA block on why gitlab page is only visible at awkward viewports
|
## Sitation
When a user is scrolling to the `/why-gitlab` page, we find that the section is only visible when the section is halfway away from the viewport.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/why-gitlab/
## 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?
- [ ] Fix AOS scroll
## 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
| 3 |
28,847,821 | 111,519,769 |
2022-07-12 15:14:24.299
|
DEX Marketing Ladder
|
## Goal
We would like to look at the DEX Marketing Ladder document and fill out/modify the development paths as needed for the Engineering group.
[Document Link](https://docs.google.com/spreadsheets/d/1yyet37qc5MDnXmSpQM7N8b8lQj5AwSyvbchlPbzR9tg/edit#gid=1731665174)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @justin.vetter @laurenbarker
| 3 |
28,847,821 | 111,519,296 |
2022-07-12 15:04:34.000
|
Complete Career Dev document
|
## Goal
Fill out [Career Dev 2022](https://docs.google.com/document/d/1XBcvklVTD32LqrYYPmL8R1-tP6HYgSf9jFYbK-2ULc4/edit?usp=sharing) Document
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @justin.vetter
| 3 |
28,847,821 | 105,624,218 |
2022-03-28 14:16:26.808
|
ENG: Template for features v1
|
## 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?
* Mock: https://www.figma.com/file/vwJWOaWyiNzCmqM4gLjvz4/Single-feature-template?node-id=2%3A2266
* [Current Features Page](https://about.gitlab.com/stages-devops-lifecycle/source-code-management/)
## 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
| 14 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.