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 | 97,573,365 |
2021-02-03 19:26:37.134
|
ENG: In editor pull-quotes
|
## What
Allow content editors to add pull-quotes anywhere in the body using the Netlify editor.
### Files
[Figma file](https://www.figma.com/file/5mgvis6M0z3GN5kuEFADoW/CMS-Blog-Post?node-id=295%3A1453)
| 1 |
28,847,821 | 95,824,318 |
2021-02-01 16:45:01.360
|
ENG: Translated Demo Page (pre and post gate)
|
<!--
This template is for internal production for a Digital Experience issue/project
-->
## Issue Set-up
1. **Title** <br>
Title this issue as follows:
[DE Prefix (see list below)] + [Project Name] + [MVC# (if appliable)]
1. **Production Issue Type** <br>
Check the relevant box:
- [ ] DSN = Design Update
- [x] ENG = Structural Update
- [ ] CNT = Content Update
- [ ] OTH = Other
- `insert other explanation`
1. **Labels and assignees** <br>
Add additional lower-level labels, and assigness.
## URL
- English/standard: about.gitlab.com/demo (update)
- German: https://about.gitlab.com/de-de/demo (create)
- Japanese: https://about.gitlab.com/ja-jp/demo (create)
- French: https://about.gitlab.com/fr-fr/demo (create)
- Italian: https://about.gitlab.com/it-it/demo (create)
## Goal
Increase MQLs and keep buyers in journey
## Production
#### Working Files
- [Figma file] (LINK)
- [ ] Translation for pre-gate
- [ ] See CNT issue for specifics on translations for CTAs post-gate
#### Scope
- [ ] Update English URL page
- [ ] Create language pages
#### Suggested Additional Scope
- [ ] Suggested scope item 1
- [ ] Suggested scope item 1
#### Out of Scope
- Out of scope 1
- Out of scope 2
#### Requirements
- [ ] Requirement 1
- [ ] Requirement 1
#### Roles & Responsibilies
Tag the appropriate parties below, which may be found in the [team handbook](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/)
The following people are **[responsible](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** for completing the task or deliverable:
- [ ] @assignee
The following person (there can only be one) is **[accountable](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** and is the last one to review the task or deliverable before it’s deemed complete:
- [ ] @bmatturro
The following people must be **[consulted](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** so they can provide input:
- [ ] @rreich
- [ ] @mpreuss22
The following people must be **[informed](https://www.teamgantt.com/blog/raci-chart-definition-tips-and-example)** so they are kept in the loop on project progress: <br>
**CC:**
- @dmor
- @dpduncan
| 2 |
28,847,821 | 95,824,250 |
2021-01-18 17:05:52.496
|
Add newsletter sign-up globally to footer
|
<!--
This template is for requesting work to an existing webpage [marketing website](https://about.gitlab.com/) , or logged out gitlab.com.
DO NOT use this for:
New webpages, docs.gitlab.com, the GitLab product (In app), the handbook or other items.
For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/)
TITLE THIS ISSUE: Page Update: [Your Relevant Title]
-->
## Overview
## Triage (REQUIRED)
**This issue fulfills one of these goals:** (Requestor check one)
- [ ] Traffic
- [x] Supports Inquries
- [ ] Conversion
- [ ] Enable unlocks for conversion and traffic later (example CMS implementation)
- `Add details here (required if this box is checked)`
- [ ] Cross-functional support
- `Link team to OKR (required if this box is checked)`
#### Briefly describe your request
What is going to be added/updated/removed, etc.
Design and add the newsletter sign-up globally to the about.gitlab.com footer
#### Describe why this update is being requested:
What problem(s) are you trying to solve? What are the goals? Example: Users can't find what they're looking for.
Assist with Inbound Marketing Inquiries goal
## Project Management
#### Please identify the DRI, stakeholders, subject matter experts, and their roles
Who should we be asking about questions and reviews?
* A directly responsible individual (DRI) is the singular person leading this project. We will ask them for clarifications, decisions, facilitation, or other assistance.
* A stakeholder is a person who represents an entity that the project impacts. We might ask about their needs, request their feedback, or inform them when the project is complete.
* Subject matter experts (SME) will be asked questions related to their expertise. Example subjects include design, development, copy, analytics, seo, social, ops, handbook, infrastructure, technologies like Marketo, etc.
* You may insert or remove as many lines as needed to list the relevant people involved with the project and their roles.
|Name|Role|
|------|------|
| @mpreuss22 | DRI |
| @vsilverthorne | Content SME|
| `@user2` | UX design |
| `@user3` | Development |
| @bmatturro | Content stakeholder|
| @dmor | Stakeholder|
#### What is the timeframe AND WHY?
Dates without reason are difficult to prioritize. Without enough lead time we will be unable to meet your deadline. Example: Our due date is XXXX-XX-XX. We want to launch this page before a trade show happens on YYYY-YY-YY. We need a week to coordinate press before the event.
*If your ask requires multiple delivery deadlines, consider creating an epic with an issue for each deadline.*
Align with Navigation updates if the footer is included, if not let's aim for mid February
## Project Deliverables
* [ ] Add newsletter sign-up form to global footer
## Related Documents/Information
Link and explain all related documents, websites, assets, logos etc. NOTE: The web team will not be able to meet deadlines unless everything is provided. [Images should follow our guidelines](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/image-guidelines/).
* Newsletter CTA: @vsilverthorne to provide
* Newsletter form URL: @vsilverthorne to provide
Hashicorp as example:
_____________
_____________
_____________
## Requestor Checklist
* [x] All sections have been filled out.
* [ ] All media and relevant documents have been linked or added.
* [ ] A due date and rationale for the due date has been added.
* [ ] Your team labels have been added.
* [ ] Any issues blocking this have been related as blocking.
* [ ] The supplied copy is not a placeholder and is expected to be the final copy, ready for development.
| 4 |
28,847,821 | 123,246,969 |
2023-02-07 21:46:30.274
|
[ENG] Add link to "All blogs" above the fold on the blog landing page
|
## Goal
We would like to swap the search and newsletter sections on the blog home page, and update the `All` pill to `All blogs`
#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## Which page(s) are involved in this request?
* [Blog](https://about.gitlab.com/blog)
## Include any Figma files
* [Figma](https://www.figma.com/file/0vSGFalBjMp59KxG5hUEBs/Blog--homepage-updates?node-id=405%3A5798&t=KvhjnzyoXqfEtzUo-0)
## Include any graphic or design assets
* `Upload any extra files needed to complete this request`
## In scope
What is within scope of this request?
- [ ] Swap the order of blocks [Search/Categories & Newsletter]
- [ ] Update `All` pill to `All blogs`
| 3 |
28,847,821 | 123,241,295 |
2023-02-07 19:12:51.629
|
ENG: Make resource card images proportionally consistent when resizing
|
## Goal
Currently, the aspec ratio for our resource cards is not consistent for our for all variants.
We would like the aspect ratio to match what's in the [slippers figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=7825%3A14624&t=yBtcpRZB5hvSGTeT-1) as closely as possible (more landscape than square)
| Example | Image |
| ------ | ------ |
| Square - example [here](https://about.gitlab.com/solutions/dev-sec-ops/#resources) |  |
| Landscape - example [here](https://about.gitlab.com/features/continuous-integration/) |  |
## Page(s)
Which page(s) are involved in this request?
* All instances
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran @mpenagos-ext (please add the solutions that we discussed via slack)
- [ ] Informed: @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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 123,239,132 |
2023-02-07 18:32:40.439
|
[Eng] Run A/B test for sales and trial header CTAs
|
## Goal of this Issue
The goal of this issue is build the test and run it in launch darkly.
Please see epic for full details
| 4 |
28,847,821 | 123,239,120 |
2023-02-07 18:32:24.983
|
[Eng] Sales and trial header CTAs
|
## Goal
We would like to build 2 navigation variants to A/B/C test the Sales and Trial header CTAs.
#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## Which page(s) are involved in this request?
* Navigation repository + header in Buyer Experience
## Include any Figma files
* [Figma file](https://www.figma.com/file/tDxUnSR5vdHHIVZjOW6nt7/Navigation-Research-and-Refresh?node-id=2138%3A71870&t=VCgUjTdNSik1w7UF-1)
* Please see [UX issue for more detail](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1886)
## In scope
What is within scope of this request?
- [ ] Ship orange button variant navigation
- [ ] Ship gradient button variant navigation
| 4 |
28,847,821 | 123,238,381 |
2023-02-07 18:16:59.446
|
[Eng] /free-trial/ FY24Q1 iteration
|
## Goal
We would like to iterate on our Free Trial page by creating a page that better demonstrates the Free Trial process
#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## Which page(s) are involved in this request?
* [Free Trial](https://about.gitlab.com/free-trial/)
## Include any Figma files
* [Figma](https://www.figma.com/file/u2CD4Lpure0cDRwunzqUZl/Paid-search-landing-page?node-id=9%3A185&t=5xgn28FmiCXTJLtp-1)
## Include any graphic or design assets
* `Upload any extra files needed to complete this request`
## In scope
What is within scope of this request?
- [ ] Refresh Free Trial page
- [ ] Deliverable 2
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @jhalloran @fqureshi
- [ ] Informed: `Everyone`
| 8 |
28,847,821 | 123,229,958 |
2023-02-07 15:55:27.254
|
[ENG] Remove old VS pages and redirect to new BE pages
|
## Goal
We would like to remove and redirect the old VS pages in the WWW repo to the new pages.
- [x] Remove Bitbucket yml content and create redirect /devops-tools/bitbucket-vs-gitlab/ -> /competition/bitbucket/
- [x] Remove Jira yml content and create redirect /devops-tools/jira-vs-gitlab/ -> /competition/atlassian/
- [x] Remove CircleCI yml content and create redirect /devops-tools/circle-ci-vs-gitlab/ -> /competition/circleci/
- [x] Remove GitLab yml content and create redirect /devops-tools/github-vs-gitlab/ -> /competition/github/
- [x] Remove JFrog yml content and create redirect /devops-tools/jfrog-vs-gitlab/ -> /competition/jfrog/
### Files
https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/devops_tools_comparisons.yaml
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@dsteer`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## 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 @jkempton @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove and redirect pages.
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 123,159,128 |
2023-02-06 21:45:17.787
|
Add technology partners
|
## Goal
We would like to add partners with signed agreements to https://about.gitlab.com/partners/technology-partners/ .
List of partners to remove to be provided by @mlebeau @mjoscelyn
#### Jobs To Be Done
* **Situation**: *When a user visits our technology partners page, everyone displayed has a signed agreement with GitLab.*
* **Motivation**: *We want to be compliant.*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## 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 @mlebeau @mjoscelyn
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add partners to [apps.yml](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/apps.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 | 123,150,341 |
2023-02-06 18:22:31.799
|
[ENG] Homepage Content Box for FY24Q1
|
## Goal
We would like to update and change the content presented on the homepage
**How do we measure success?**
- Increase clicks to the featured content
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com
## Update the content to be
---
#### Get Started with GitLab
New to GitLab and not sure where to start? We’ll walk you through the basics so you know what to expect along the way.
[Explore resources >](https://about.gitlab.com/get-started/)
#### How our latest releases support developers
Learn how our two new beta releases help organizations stay competitive by supporting developers and delivering value to customers.
[Read the blog post](https://about.gitlab.com/blog/2023/01/24/the-gitlab-quarterly-how-our-latest-beta-releases-support-developers/) >
#### Forrester study: GitLab enabled 427% ROI
Read the 2022 commissioned Total Economic Impact™ study conducted by Forrester Consulting.
[Read the study >](https://page.gitlab.com/resources-study-forrester-tei-gitlab-ultimate.html)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI:
- [ ] Consulted: @dennischarukulvanich @fqureshi @justin.vetter @jhalloran
- [ ] Informed: `@chandlergibb @rclayman @supadhyaya`
## 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 | 123,138,056 |
2023-02-06 15:24:16.019
|
ENG: Update All Resources page
|
## Goal
We would like update the all resources landing page.
[Figma Design](https://www.figma.com/file/sWcfVXZiDd50SfYlC3tKC7/Resources?node-id=236%3A8976&t=SkXu7OSUlt75O3tU-1)
#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## Which page(s) are involved in this request?
* https://about.gitlab.com/resources/
## In scope
What is within scope of this request?
- [ ] Update template and functionality to match Figma
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI: @mduque-ext
* [ ] Consulted: @jhalloran @Tinaliseng
* [ ] Informed: `Everyone`
| 10 |
28,847,821 | 123,037,154 |
2023-02-04 05:40:23.626
|
Remove pps properties from features.yml
|
## Goal
This is a follow-up to: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/14235#note_1265555484.
| 4 |
28,847,821 | 123,036,516 |
2023-02-04 05:36:09.161
|
incident-8354-2
|
## Goal
This happened the day after https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1870, when the project was set to private, so did the runners. Unfortunately when the project was switched back to public, we were using a mix of private and shared runners. When the BE repo tried to push the artifacts to GitLab pages on a private runner a redirect happens. I'm not entirely sure why, I'm assuming it's some kind of url masking?
| 2 |
28,847,821 | 123,027,513 |
2023-02-03 20:46:12.212
|
Create alerts slack channel
|
When a production pipeline fails, notify the team. Recently there's been a few incidents where we don't catch errors until 1-2 hours later. This will also post failed scheduled jobs (404 checker, etc.)
| 2 |
28,847,821 | 123,019,945 |
2023-02-03 17:35:45.324
|
[ENG] Detect and fix the cause that put all the CSS in a html tag
|
## Goal
We would like to improve the way the CSS code is fetched in the BE site. Also, look to achieve a way to share only 1 slippers-ui.css file for both navigation and BE repos preventing a duplicated file
Sample data:
- https://about.gitlab.com - CSS size 1.28MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/pricing/ - CSS size 1.28MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/install/ - CSS size 1.27MB, 1.25MB CSS unused (98%)
- https://about.gitlab.com/why-gitlab/ - CSS size 1.28MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/enterprise/ - CSS size 1.29MB, 1.25MB CSS unused (97%)
- https://about.gitlab.com/stages-devops-lifecycle/source-code-management/ - CSS size 1.27MB, 1.24MB CSS unused (97%)
**Coverage tab screenshot**
<details><summary>Click to expand</summary>
</details>
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @aleal-ext
- [ ] Consulted: @justin.vetter @laurenbarker @ndubord @lduggan @meganfilo
- [ ] Informed: @hsmith-watson
## In scope
What is within scope of this request?
- [ ] Prevent CSS code in HTML tag
- [ ] Prevent duplicated slippers-ui.css file (from navigation and BE)
## 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 | 123,013,773 |
2023-02-03 15:40:32.320
|
DevOps tools page "category" naming fixes
|
## Goal
We want to edit the /competition/ page so that instead of "categories" it states the stage that the viewer is currently looking at.
#### Jobs To Be Done
See image below:
We want each tab of the [competition page](https://about.gitlab.com/competition/) to replace the word "categories" with the stage that it belongs to, e.g. when you click "Create", the current word "Categories" should be replaced with "Create"; "Monitor" with "Monitor", etc.
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [X] Yes: requested by Sid
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [X] Yes Sid, Ashley, Dave
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/competition/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 1 |
28,847,821 | 122,973,096 |
2023-02-03 01:25:19.631
|
Set our changelog job to run every release Friday
|
## Goal
Schedule the changelog job to run every 2nd Friday (on release days)
| 2 |
28,847,821 | 122,962,375 |
2023-02-02 18:57:14.584
|
[Eng] - Time Calculator
|
## Goal
We would like to create a Time Savings calculator as a second tab on the ROI calculator page.
#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## Which page(s) are involved in this request?
* `[Page Title](URL)`
## Include any Figma files
* [Figma WIP](https://www.figma.com/file/fx89h6j2yToBAE1m7qHez8/ROI-Calculator---time-savings?node-id=5%3A7923&t=xxVWf7z6k6sg97pA-0)
## Include any graphic or design assets
* `Upload any extra files needed to complete this request`
## In scope
What is within scope of this request?
- [ ] Create calculator
- [ ] Deliverable 2
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: 'Engineer'
- [ ] Consulted: `@justin.vetter @laurenbarker @fqureshi`
- [ ] Informed: `Everyone`
| 6 |
28,847,821 | 122,961,748 |
2023-02-02 18:44:05.629
|
[ENG] - Guest users on Ultimate
|
## Goal
We would like to show current Premium SaaS users how much they can save by moving non-coding users to the "Guest" role (free) on Ultimate.
To do this we would like to create a calculator this shows the value of guest users
#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## Which page(s) are involved in this request?
* `[Page Title](URL)` - TBD
## Include any Figma files
* [Figma WIP](https://www.figma.com/file/ufPARcvcyR81uEUQtm82UK/Guest-users-on-Ultimate?node-id=111%3A41930&t=qPkthaA1JvA19CK8-0)
## Include any graphic or design assets
* `Upload any extra files needed to complete this request`
## In scope
What is within scope of this request?
- [ ] Create Guest users calculator component
- [ ] Deliverable 2
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: 'Engineer'
- [ ] Consulted: @justin.vetter @jhalloran @fqureshi
- [ ] Informed: `Everyone`
| 4 |
28,847,821 | 122,879,991 |
2023-02-01 21:42:53.625
|
[ENG] Swap images on AWS partners page to update GitLab logo
|
## Goal
We would like to update the GitLab logos on the [GitLab on AWS](https://about.gitlab.com/partners/technology-partners/aws/) by swapping the two images on the page.
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 122,859,877 |
2023-02-01 17:01:48.023
|
ENG: Add methodology pop-up on DevOps Tools
|
## Goal
>As per Sid's request on the #competitive-website-strategy slack channel, we want to have a synopsis for each stage on the /devops-tools/ page articulating how/why we came to these rankings.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: Sid and Dave requests
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/devops-tools/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jkempton
- [ ] Consulted: @Tinaliseng
- [ ] Informed: @justin.vetter @fqureshi
## In scope
Add a line of copy with a hyperlink in the table under the heading
- Table copy: Learn more about the methodology behind these rankings
- "methodology behind these rankings" triggers pop-up.
- [Popup copy](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1853#methodology-text)
- [Figma prototype](https://www.figma.com/proto/J43LGQRZtINKjHb0XqXYAj/DevOps-Tools?page-id=372%3A9259&node-id=607%3A11540&viewport=-1634%2C643%2C0.41&scaling=min-zoom&starting-point-node-id=607%3A11540&show-proto-sidebar=1) - click hyperlink under the table heading
- [Figma workfile](https://www.figma.com/file/J43LGQRZtINKjHb0XqXYAj/DevOps-Tools?node-id=607%3A11539&t=Mrv2Cf0h0JhTup8G-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
| 2 |
28,847,821 | 122,798,572 |
2023-01-31 22:49:42.506
|
GA4/GTM/OneTrust Blocker
|
## Goal
**Context**
Google Tag Manager (GTM) by itself does NOT store any cookies on the browser. When tags on GTM are configured to send data to different platforms, such as Google Analytics, Linkedin, Google Ads, etc. - that's when cookies for the associated platform are stored on the browser. Each tag already contains a OneTrust condition, and will only fire if the user consents to the specific cookie category, such as functional, performance/analytics, or targeting.
On a related note, we've added the gtag.js code update for GA4's consent feature. This update will send a signal to the browser's dataLayer regarding the user's default consent status based on their country. For example, by default (no user interaction with the consent banner at this point), a user from a European country will NOT be tracked if they take no action (clicking "X" on the OneTrust banner).
The gtag.js code update enables the machine learning capabilities for GA4 to fill in the gap where users deny tracking (by default or by choice).
[More Details](https://docs.google.com/document/d/1i66ayUZTVuff41w6IKPVeSJ_pwL1nIX4pQZbF9Gpcro/edit#)
#### Jobs To Be Done
* **Situation**: *When a user visits the site w*
* **Motivation**: *We want to load GTM at all times and prevent OneTrust from blocking *
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
In attempt to prevent OT from blocking GTM we tried using `data-ot-ignore` and `optanon-category-C0001` from OneTrust's Docs. Both of these slowed down traffic to GA. A ticket was submitted to OneTrust support where they suggested that we focus on our script ordering since OneTRust loads after GTM in our codebase and that may potentially be preventing their auto blocking classes from working. In attempt to do we've tried:
- **Placing OneTrust above GTM in the head file**: no effect [[MR]](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/108574)
- **Using the addEventListener**: Using the addEventListener method to attach a load event listener to the OneTrust script, and then include the Google Tag Manager script inside the event listener function
this prevented GTM from loading at all [[MR]](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1499)
- **Changing GTM’s Triggers to wait for OneTrust** [[MR]](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/118462)
This was suggested by [StackOverflow](https://stackoverflow.com/questions/75073704/onetrust-script-executing-after-google-tag-manager). By adding another trigger that onetrust fires when it's loaded and by adding an exception to existing pageview triggers to not fire if onetrust's consent cookies are missing or denied [[MR]](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/118462)
- **Increasing time interval on GTM attribute `wait_for_update`**: no effect [[MR]](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/118797)
- **Loading OneTrust from GTM:** broke the functionality in the cookie banner and prevented user preferences from persisting [(shown here)](https://gitlab.com/gitlab-com/www-gitlab-com/uploads/e582c4be996eae761a87d0ebb8fa65d7/video2798811226.mp4)
- **Removing GTM from the source of all cookies containing "gtm" individually in the OneTrust Dashboard**: _waiting for response from OT support_
**Does anyone in leadership have eyes on this project?**
- [x] Yes `@laurenbarker`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
All pages, but let's start with about.gitlab.com subdomain for this issue.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @miraclebanks
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: @justin.vetter @lduggan @laurenbarker @mpreuss22 @christinelee @degan @jahye1 @dmicovic
## 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
| 8 |
28,847,821 | 122,761,110 |
2023-01-31 14:06:13.508
|
ENG: Refactor Software Faster Carousel Component
|
[Software Faster page](https://about.gitlab.com/software-faster/)
The current carousel does not render all slide content on the page at once, but renders the content for the slide that's visible. This has made it difficult to render the video on slide two on page load, which is needed for Vimeo analytics to be pushed up to the dataLayer.
Let's refactor the carousel component so that all slide content is rendered in the DOM, but is properly hidden until selected.
Related comment: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1611#note_1258247192
| 4 |
28,847,821 | 122,717,478 |
2023-01-30 22:19:13.926
|
ENG: devops-tools / table UI updates
|
## Goal
We would like to update the table style for [/devops-tools](https://about.gitlab.com/devops-tools/) so that it is consistent with the [/competition](https://about.gitlab.com/competition/) table.
## Page(s)
Which page(s) are involved in this request?
* `https://about.gitlab.com/devops-tools/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: @justin.vetter
## In scope
What is within scope of this request?
| Issue | Image |
| ------ | ------ |
| Update grid border color so they are the same as on /competition = Grey 200 `#E8E7EB` |  |
| Add a border to the entire table to be consistent with the /competition table: Grey 200 `#E8E7EB` |  |
## 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 | 122,707,631 |
2023-01-30 19:13:15.785
|
ENG: Hackerone customer logo distorted in solutions/dev-sec-ops
|
## Goal
Fix the distorted Hackerone logo on the dev-sec-ops solution page.
Sort of urgent as it probably violates brand standards
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/dev-sec-ops/#customers
## 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: @justin.vetter
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 122,706,725 |
2023-01-30 18:49:47.502
|
[ENG] Change table title based on stage /competition
|
## Goal
We want to swap the table title based on the stage/tab the user is on. For example, if the user is on the Create tab, instead of it saying `Categories` below, it should say `Create`. We also want to add the icon for each stage next to the title.
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes `Dave & Sid`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to swap the table title per tab`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `[Competition](https://about.gitlab.com/competition)`
## 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 @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Swap title based on tab
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 122,695,496 |
2023-01-30 16:39:20.805
|
[ENG] Iterate on features section for why Premium & Ultimate pages
|
## Goal
We would like to iterate on the Features section > `Other features` to build in a load more and/or load all features.
#### Jobs To Be Done
* **Situation**: *When a user visits one of our why pages the scroll is way too long for users to make it through the content*
* **Motivation**: *We want to reduce the scroll of the page by allowing the user to load more feature items in*
* **Outcome**: *So we can increase scroll depth and give users a better visualization of the content on the page*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to create a better user flow for these pages`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* [https://about.gitlab.com/pricing/ultimate/](https://about.gitlab.com/pricing/ultimate/)
* [https://about.gitlab.com/pricing/premium/](https://about.gitlab.com/pricing/premium/)
## 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 @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update component to allow user to load more items in
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 122,694,291 |
2023-01-30 16:22:53.278
|
[ENG] solutions/open-source/join page refresh
|
## Goal
We want to update the [solutions/open-source/partners](https://about.gitlab.com/solutions/open-source/join) page to the new brand refresh which will improve users experience as measured by metrics.
### Working Files(s)
[Figma](https://www.figma.com/file/Od5TazELCPPEhkcoReGQvO/Open-Source?node-id=18%3A5847&t=hPIRkHukRahYke06-0)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to refresh the Join page`
**What analytics / data will we need to set-up?**
- [x] Yes: `Standard analytics`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Open-source/partners](https://about.gitlab.com/solutions/open-source/join/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Refresh Open-source/join page
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 122,694,280 |
2023-01-30 16:22:34.990
|
[ENG] solutions/open-source/partners page refresh
|
## Goal
We want to update the [solutions/open-source/partners](https://about.gitlab.com/solutions/open-source/partners) page to the new brand refresh which will improve users experience as measured by metrics.
### Working Files(s)
[Figma](https://www.figma.com/file/Od5TazELCPPEhkcoReGQvO/Open-Source?node-id=18%3A5097&t=hPIRkHukRahYke06-0)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to refresh the partners page`
**What analytics / data will we need to set-up?**
- [x] Yes: `Standard analytics`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Open-source/partners](https://about.gitlab.com/solutions/open-source/partners/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Refresh Open-source/partners page
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 122,694,015 |
2023-01-30 16:19:02.065
|
[ENG] solutions/open-source page refresh
|
## Goal
We want to update the [solutions/open-source](https://about.gitlab.com/solutions/open-source) page to the new brand refresh which will improve users experience as measured by metrics.
## Page(s)
Which page(s) are involved in this request?
* [solutions/open-source](https://about.gitlab.com/solutions/open-source)
### Working File(s)
[Figma](https://www.figma.com/file/Od5TazELCPPEhkcoReGQvO/Open-Source?node-id=18%3A5096&t=hPIRkHukRahYke06-0)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to refresh the open-source/partners page`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [x] Yes: `Standard analytics setup`
- [ ] No
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update layout for solutions/open-source page
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 5 |
28,847,821 | 122,693,055 |
2023-01-30 16:05:22.577
|
[UX] Create an extra content block to feature external content on the blog home page
|
## Goal
Create a way for us to add in a box for podcasts, webcasts, ebooks or whatever we want to promote on the blog home page.
#### Jobs To Be Done
* **Situation**: *The content team has new and existing content that would like to surface on the blog home page but there is no longer a good spot to do so*
* **Motivation**: *We want to give the content team an easy way to highlight new external content items (podcasts, ebooks, webcasts, videos)*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to create a new layout block for the blog homepage to highlight featured external content`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [x] Yes: `Standard GA tracking`
- [ ] No
## 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:
- [ ] Consulted: @fqureshi @Sgittlen @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create a new content block layout for the blog homepage
- [ ] Deliverable: [Figma designs](https://www.figma.com/file/0vSGFalBjMp59KxG5hUEBs/Blog--homepage-updates?node-id=488%3A6640&t=elRWpn9g6xY87oHY-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
- [x] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 122,692,776 |
2023-01-30 16:00:16.618
|
[UX] Add link to "All blogs" above the fold on the blog landing page
|
## Goal
We want to add a link to view all blog posts above the fold on the blog landing page. This will allow users to easily navigate the list of all blog posts.
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to update the blog homepage layout by adding a link to "All posts" above the fold`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## 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: @jhalloran
- [ ] Consulted: @justin.vetter @fqureshi @Sgittlen
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update Blog homepage layout to add link to all blog posts
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 122,692,421 |
2023-01-30 15:55:54.139
|
[ENG] Add new categories to the blog
|
## Goal
We want to add four new categories to the blog:
- DecSecOps
- DevSecOps platform
- Careers
- Product
These categories should be added to the category lists on the main page and on the side nav. These categories should also have a category page ex. https://about.gitlab.com/blog/categories/careers/
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## 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 @fqureshi `@Sgittlen`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add categories to main page and side nav
- [ ] Create category landing page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 122,688,621 |
2023-01-30 15:17:30.794
|
Need to delete two out-of-date blog templates
|
## Goal
The blog team needs the following blog templates deleted because they are no longer in use: blog-PYB-post.md
blog-feature-unfiltered-post.md
No rush...
#### Jobs To Be Done
* **Situation**: *Not urgent*
* **Motivation**: *Streamline our templates and delete old ones to eliminate confusion*
* **Outcome**: *Collaborate better with blog contributors*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why` - just an old template deletion for blogs
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `Streamlined repo for blog templates`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## 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)
- [x] DRI: `@sgittlen`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 122,585,937 |
2023-01-27 20:32:13.361
|
Issue with thumb overlay on blog posts
|
## Post thumb overlay issue
Only the first row of blog posts is showing and overlay on top of the thumbs.
<details><summary>Click to expand</summary>
</details>
| 3 |
28,847,821 | 122,566,432 |
2023-01-27 14:05:35.968
|
Bug: Fix pricing/feature-comparison header height
|
## Goal
FeatureComparison header is not correctly aligned with the navigation menu
## 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 | 122,522,391 |
2023-01-26 23:45:19.723
|
Add GLM parameters to conversion CTAs
|
## Goal
We would like add GLM parameters to the following CTAs:
TBD
1. Related https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/issues/42
1. Related https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/issues/68
#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[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
## 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
| 0 |
28,847,821 | 122,522,321 |
2023-01-26 23:43:00.329
|
Ability to recognize logged in GitLab user
|
## Goal
We would like to recognize when a user is logged into GitLab on the marketing site.
The goal with this issue is to
1. Investigate how we could do this
1. Start a thread for each 'how' that gives a high-level overview, scope, & risks. We'll discuss as a team in each thread.
1. Chose a strategy. We'll determine next steps from there.
**We'll need to schedule these changes in the GDK to be before or after _March 7th_ because of the [Hard Production Change Lock](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#production-change-lock-pcl) where the GDK will be updated to Ruby 3**
| 6 |
28,847,821 | 122,522,218 |
2023-01-26 23:39:52.165
|
Reclassification of technology partners
|
## Goal
We would like to do a reclassification of technology partners on https://about.gitlab.com/partners/technology-partners/ .
List of partners to remove to be provided by @mlebeau @mjoscelyn
#### Jobs To Be Done
* **Situation**: *When a user visits our technology partners page, technology partners are accurately classified.*
* **Motivation**: *We want to be compliant.*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## 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 @mlebeau @mjoscelyn
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Reclassification of [apps.yml](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/apps.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
| 1 |
28,847,821 | 122,522,178 |
2023-01-26 23:36:51.223
|
Removing partners without TPAs
|
## Goal
We would like to removing partners without signed agreements from the https://about.gitlab.com/partners/technology-partners/ .
List of partners to remove to be provided by @mlebeau @mjoscelyn
#### Jobs To Be Done
* **Situation**: *When a user visits our technology partners page, everyone displayed has a signed agreement with GitLab.*
* **Motivation**: *We want to be compliant.*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `We have partners there don't have signed agreements`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
## 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 @mlebeau @mjoscelyn
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove partners from [apps.yml](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/content/apps.yml)
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 122,521,717 |
2023-01-26 23:13:22.889
|
Updates to Search
|
## Goal
We would like to update the Search. There were some features that were left off for MVC1, but we'd like to add them back to enhance the experience.
#### Please provide more information related to this request
| Comment | In design | In production |
| ------ | ------ | ------ |
| 1. Update autocomplete to be more intelligent. It should not just serve up the suggested articles, but autocomplete/autocorrect what the user is typing. |  |  |
| 2. Filter by checkboxes (instead of radio buttons) |  |  |
| 3. Make the search results it’s own page so users can go back to their search after they’ve selected a result. Currently, if a user selects a result, they will have to go back to the page they were on before the search. | | See [loom](https://www.loom.com/share/d2d25d7c14ca4e3c82c87e6998d428a3) |
| 4. Fix the search results so that they show the sources accurately (currently they all show as “About” even if it’s a blog page) |  |  |
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[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
## 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
| 5 |
28,847,821 | 122,503,511 |
2023-01-26 17:50:36.086
|
[ENG] Update Trending posts -> Recent posts
|
## Goal
We would like to update the Trending Posts text to Recent Posts on the blog home page
## 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?
- [ ] Update copy
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 122,501,011 |
2023-01-26 16:58:20.948
|
[ENG] Case Studies component Learn more styles
|
## Goal
We would like to update the styles to make sure `Learn more >` is on a single line
### Figma
[Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=5581%3A13406&t=bPIbHkFHDvFGxnHH-0)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* Pages with Case Studies component
* ex: [Enterprise](https://about.gitlab.com/enterprise/)
## 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?
- [ ] Fix Styling
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 122,451,752 |
2023-01-25 19:03:03.982
|
[ENG] Small business page components have extra spacing from the sidenav
|
## Goal
We would like to remove the extra space that the components are using in the small business page
#### Please provide more information related to this request
this spacing was used before the sidenav was refactored to avoid overlap, it is not necessary anymore
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [X] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [X] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**How do we measure success?**
- No extra spacing
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/small-business/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpenagos-ext
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove spacing
## 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 | 122,388,712 |
2023-01-24 20:19:59.037
|
[ENG] BUG random quotation mark on /features/continuous-integration/
|
## Bug
There is a random `"` on the left above the Resources component that needs to be removed
## Page(s)
Which page(s) are involved in this request?
* [Continous Integration](https://about.gitlab.com/features/continuous-integration/)
## 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?
- [ ] Remove quotation mark
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 122,376,875 |
2023-01-24 16:04:57.037
|
[ENG] VSD sign-up page - Edits
|
## Goal
Follow-up to: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1580
| 1 |
28,847,821 | 122,329,225 |
2023-01-23 22:20:03.405
|
[ENG] Bug horizontal scroll on /solutions & /features page
|
## Bug
We are seeing a horizontal scroll and white space to the right of some components on the /solutions & /features pages
[Loom video](https://www.loom.com/share/3ffc8058df37444ab738a9c2d5fa2d00)
example pages:
- https://about.gitlab.com/features/continuous-integration/
- https://about.gitlab.com/small-business/#case-studies
- https://about.gitlab.com/solutions/dev-sec-ops
## Browsers with issues
Chrome & Firefox
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Fix whitespace and horizontal scroll issue
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 122,325,216 |
2023-01-23 20:29:21.352
|
[ENG] Add JetBrains Mono type to our font stack
|
## Goal
We would like to add JetBrains Mono Regular to our font stack to stay in sync with the product team.
This is a mono type font that will replace all code examples on our site example: [install](https://about.gitlab.com/install/#centos-7)
this font should be used in all <code> blocks
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to add the font to our site and update <code> styles`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## 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: @jhalloran @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add fonts and update styles
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 122,306,871 |
2023-01-23 14:37:28.354
|
Netlify CMS authentication for only members of repository
|
## Goal
For only members of a public GitLab repository to be able to access the Netlify CMS admin.
For our use case, this means `about.gitlab.com/admin `
Currently anyone with a GitLab account can login to the admin. We'd like to restrict access to www-gitlab-com project members.
Here's [the slack thread in #marketing](https://gitlab.slack.com/archives/C0AKZRSQ5/p1674306562076699) that spawned this issue.
Although any account can log in, their actions are still restricted based on their permissions. For example users could see "draft posts" which are just public MRs - already visible via gitlab.com's normal UI - but they wouldn't be able to merge without Maintainer permissions. **There is no current security risk**, just confusing behavior.
#### Jobs To Be Done
* **Situation**: *When anyone tries to login to the `about.gitlab.com/admin`, only those who are project members of [www-gitlab-com](https://gitlab.com/gitlab-com/www-gitlab-com) should be able to authenticate successfully.*
* **Motivation**: *We want to have the admin only available to GitLab team members.*
* **Outcome**: *So that non team-members don't have access to an "admin" site.*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `SIRT got informed that it is possible to log into the https://about.gitlab.com/admin interface with ANY GitLab account`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes @laurenbarker
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
## Page(s)
Which page(s) are involved in this request?
* `about.gitlab.com/admin`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @jroppelt
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Making an open source contribution to the [GitLab Netlify CMS backend](https://github.com/netlify/netlify-cms/tree/master/packages/netlify-cms-backend-gitlab)
- [ ] Bumping the netlify-cms.js package [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/admin/index.html#L12)
- [ ] Verifying on production
## 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 | 122,184,123 |
2023-01-20 12:20:52.944
|
ENG: [Refactor] - Use Vue refs instead of 'getElementById'
|
## Goal
Remove pure javascript element obtention and replace it with native Vue `refs`
## 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
| 3 |
28,847,821 | 122,134,652 |
2023-01-19 16:25:40.586
|
[ENG] /devops-tools -> /competition deep link missing selected style
|
## Issue
When you click on a stage from the /devops-tools page to link to the correct tab on the /competition page we are missing the highlight style for that stage.
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to add the selected style to the open tab when linking directly`
## Page(s)
Which page(s) are involved in this request?
* [DevOps Tools](https://about.gitlab.com/devops-tools/)
* [Competition](https://about.gitlab.com/competition/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Fix missing selected style
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 122,075,467 |
2023-01-18 19:30:22.809
|
[ENG] Source code management components displaying incorrectly
|
## Goal
We would like to fix components in the source code management page as they are displaying incorrectly
| Page section | Current component |
| ------ | ------ |
| Overview |  |
| Benefits |  |
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [X] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [X] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpenagos-ext
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Fix components
## 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 | 121,984,513 |
2023-01-17 16:25:02.976
|
Document how to edit /competitor pages
|
## Goal
Write handbook documentation on how to edit /competition pages.
| 4 |
28,847,821 | 121,984,453 |
2023-01-17 16:24:06.373
|
/competiton coverage bars aren't consistent in pop-up
|
## Goal
Let's make sure the data in the /competition table, matches the pop outs.
| 1 |
28,847,821 | 121,984,381 |
2023-01-17 16:22:51.855
|
Don't show link animation/styling if competitor page doesn't exist
|
## Goal
On /competition for Bitbucket and Synopsis we show the link styling, there's no link, lets keep the styling the same as GitLab.
| 1 |
28,847,821 | 121,973,502 |
2023-01-17 14:34:58.103
|
[ENG] Platform page MVC3
|
## Goal
We would like to update the Platform page which will improve conversion as measured by increased free trials and sales contacts.
#### Jobs To Be Done
* **Situation**: *When a user visits the platform page...*
* **Motivation**: *We want to provide them more context around the devops platform and all of its features...*
* **Outcome**: *So potential customers understand what they are purchasing.*
### Working Files
[Figma](https://www.figma.com/file/n6bowcuTxQeApxMvoT0kqA/Platform-page?node-id=274%3A7751&t=9yrtLTosPBaiMcII-1)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes `@dsteer`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Platform](https://about.gitlab.com/platform/?stage=plan)`
## 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 @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] MVC3 for the Platform page
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 5 |
28,847,821 | 121,971,751 |
2023-01-17 14:11:48.900
|
ENG: [Refactor] - Create generic Mixin to handle screen resizing and the mobile flag
|
## Goal
We would like to create and implement a generic Mixin which will improve the screen resizing watcher and will avoid duplicating the same code over and over the components
## 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 | 121,922,505 |
2023-01-16 19:30:00.995
|
[ENG] Fix table border issues - upper right side
|
## Describe the Bug
The table is wonky on the upper right side
1. Missing border around the top right corner and right side
2. The last stage is breaking out of the table
<details><summary>Click to expand image showing the issue</summary>
</details>
### What's my browser?
Chrome
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/competition/
## 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 | 121,771,246 |
2023-01-13 22:19:36.295
|
[ENG] Bug Get Started blank page
|
## Goal
We would like to fix the blank space appearing when scrolling down fast in the `/get-started/small-business` and `/get-started/enterprise` pages, [as reported here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1396#note_1226694630).
#### Jobs To Be Done
* **Situation**: *When ...* we scroll down fast on loading there's a moment where there's blank space in the page
* **Motivation**: *We want to ...* not have that blank space
* **Outcome**: *So we can ...* scroll down fast without issues
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Small business](/get-started/small-business)`
* `[Enterprise](/get-started/enterprise)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `@mduque-ext`
- [ ] Consulted: `@laurenbarker`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 2 |
28,847,821 | 121,686,562 |
2023-01-12 20:15:38.947
|
[ENG] Update modal links to point to the correct tab /competition page
|
## Goal
We want to update all of the `Read in-depth analysis >` links in the modals to point to the equivalent capability tab instead of the generic vs. page.
This link should link to the Atlassian page with the Design Management tab already selected.
The work to add the deep linking functionality comes from this issue: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1782
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to update all of the Read in-depth analysis link on the /competition page`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Competition](https://about.gitlab.com/competition/)`
## 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?
- [ ] Updating links
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 121,686,211 |
2023-01-12 20:02:53.266
|
[ENG] New Functionality on comparison pages to deep link to tabs
|
## Goal
We want to add deep linking functionality on the vs. pages. This will allow us to link directly to a capability from other parts of the marketing site.
ex:
- https://about.gitlab.com/competition/atlassian/?capability=service-desk
- https://about.gitlab.com/competition/github/?stage=verify&capability=merge-trains
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to enable deep linking functionality
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* [all vs page template](https://about.gitlab.com/competition/atlassian/)
* [GitLab vs. GitHub](https://about.gitlab.com/competition/github/)
## 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?
- [ ] Deep linking on vs GitHub (both params Stage and Capability)
- [ ] Deep linking on all other vs pages (Capability only)
## 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 | 121,684,394 |
2023-01-12 19:15:28.202
|
run www script on blogimages to reduce size
|
## 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 ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[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
## 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 | 121,683,876 |
2023-01-12 18:59:08.056
|
[ENG] Bug / Topics page breadcrumbs behaving oddly
|
## Goal
Breadcrumbs display an empty tooltip and other things on hover. There should be an underline on hover, here is a link to it in [Slippers Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=2330%3A0&t=23OszzqeG2texVr9-1)
### What's my browser?
Chrome
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/topics/devops/
* Maybe more
## 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
| 3 |
28,847,821 | 121,677,955 |
2023-01-12 17:09:13.341
|
[ENG] Feature cards / Force tier pills to stay on the same line
|
## Goal
Is it possible to always have the tier pills sit on the same line (Free, Premium, Ultimate)?
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* [about.gitlab.com/solutions/](https://about.gitlab.com/solutions/)
* [about.gitlab.com/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: @Tinaliseng
- [ ] Consulted:
- [ ] Informed: @justin.vetter
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 121,677,612 |
2023-01-12 17:04:34.096
|
[ENG] Pricing template page styling updates
|
1. Make the feature cards have consistent heights (like the Solutions and Feature page cards)
<details><summary>Screenshot</summary>
https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/d6e296654279f18273f1224ac0f619d5/Screenshot_2023-01-12_at_8.45.21_AM.png
</details>
2. Fix case study card hover state
<details><summary>Screenshot</summary>
</details>
3. Further QA of the page(s) and fixes as necessary
| 2 |
28,847,821 | 121,622,807 |
2023-01-11 22:08:33.415
|
[ENG] Fix card spacing on GitLab Ultimate and Premium pages
|
## Goal
There is too much space between the feature cards. Please reduce to 32px like this:
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/premium/
* https://about.gitlab.com/pricing/ultimate/
## 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 | 121,621,314 |
2023-01-11 21:27:30.295
|
[ENG] Deep link from /devops-tool stage to /competition tab
|
## Goal
We would like to create links from the stages on the /devops-tools page to the correct stage tab on the /competition page
### Working Files
[Figma Prototype](https://www.figma.com/proto/J43LGQRZtINKjHb0XqXYAj/DevOps-Tools?page-id=372%3A9259&node-id=502%3A9758&viewport=-103%2C736%2C0.37&scaling=min-zoom&starting-point-node-id=502%3A9758&show-proto-sidebar=1)
`Create link is the only one linked up in this prototype`
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: Senior leadership is looking for this change
- [ ] No
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Devops Tools](https://about.gitlab.com/devops-tools/)`
## 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 @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add links to from each stage
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 121,621,152 |
2023-01-11 21:22:37.602
|
[ENG] Add sub copy to /devops-tools page
|
## Goal
We would like to add text to the top of the /devops-tools page to make clear that these logos are in stack-rank or prioritized order based on strength or maturity in their category. We will also link to the /competition from here
ex:
### Final Copy:
1. H1: DevOps tools landscape (should be sentence case instead of title case as it currently is)
2. H5: As The DevSecOps Platform, GitLab’s focus is on providing a single application with best-in-class capabilities for the entire DevOps lifecycle.
3. Body-2: There are a ton of DevOps tools to choose from, many of which specialize in a few capabilities. We’ve ranked the tools for each stage of the DevOps lifecycle, starting with the most mature solutions. For more info on the maturity of GitLab and other key competitors, check out our DevOps maturity comparison chart.
4. Add a title to the table - H4: Top tools for each stage of the DevOps lifecycle
- [Google doc](https://docs.google.com/document/d/1WefXucnXBi09wBv_ho7mBQ-BKc0WaeTFjYh7-TUWkkI/edit?usp=sharing)
- See [comment below](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1772#note_1237537954)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: Senior leadership is looking for this change
- [ ] No
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* [DevOps Tools](https://about.gitlab.com/devops-tools/)
## 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 @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add sub-hero copy to devops-tools page
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 121,620,932 |
2023-01-11 21:17:40.168
|
[ENG] Add breadcrumb to /devops-tools from /competition
|
## Goal
We would like to add a breadcrumb nav element on the /competition to the DevOps Tools Landscape page
#### Working Files
[Figma Prototype](https://www.figma.com/proto/J43LGQRZtINKjHb0XqXYAj/DevOps-Tools?page-id=372%3A9259&node-id=516%3A12467&viewport=-103%2C736%2C0.37&scaling=min-zoom&starting-point-node-id=502%3A9758&show-proto-sidebar=1)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: Senior leadership is looking for this change
- [ ] No
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* [Competition](https://about.gitlab.com/competition/)
* [DevOps Tools](https://about.gitlab.com/devops-tools/)
## 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 @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add breadcrumb nav element
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 121,601,937 |
2023-01-11 15:11:44.989
|
[ENG] Add functionality to deep link into tabs on /competition page
|
## Goal
We would like to add the functionality to be able to deep link into tabs/stages on the /competition page
ex: https://about.gitlab.com/competition/?stage=package
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `we want this functionality to then update links on the /devops-tools page`
- [ ] No
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Competition](https://about.gitlab.com/competition/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpenagos-ext
- [ ] Consulted: @justin.vetter @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add new functionality
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 121,588,989 |
2023-01-11 12:30:29.877
|
ENG: [Refactor] - Remove AOS initialization in remaining pages
|
## Goal
Remove AOS initialization from remaining pages that are still initializing AOS in order to reduce duplicated code and only use AOS in the Layout
## 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 | 121,588,537 |
2023-01-11 12:23:49.995
|
ENG: [Refactor] - Remove AOS initialization in partners pages
|
## Goal
Remove AOS initialization from partners pages to reduce duplicated code and only use AOS in the Layout
## 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 | 121,588,527 |
2023-01-11 12:23:28.933
|
ENG: [Refactor] - Remove AOS initialization in competition pages
|
## Goal
Remove AOS initialization from competition pages to reduce duplicated code and only use AOS in the Layout
## 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 | 121,588,474 |
2023-01-11 12:22:16.839
|
ENG: [Refactor] - Remove AOS initialization in topic pages
|
## Goal
Remove AOS initialization from `/topic` pages to reduce duplicated code and only use AOS in the Layout
## 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 | 121,548,653 |
2023-01-10 23:11:48.174
|
[ENG] Remove 7th logo under Monitor
|
## Goal
We would like to remove the 7th logo under the monitor column `chronosphere` to keep the table consistent
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: Just to clean up the table for leadership
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* [Devops Tools](https://about.gitlab.com/devops-tools/)
## 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?
- [ ] Remove 7th logo
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 121,519,157 |
2023-01-10 13:38:36.239
|
ENG: [Refactor] - Remove AOS initialization in "events" pages
|
## Goal
Remove AOS initialization from `/events` pages to reduce duplicated code and only use AOS in the Layout
## 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 | 121,372,320 |
2023-01-06 19:21:27.024
|
UX: Update All Resources page
|
## Goal
We would like to update the All Resources page to increase customer engagement.
#### Jobs To Be Done
* **Situation**: *When I click on the "All Resources" link*
* **Motivation**: *I want to explore all of Gitlab's resources quickly and efficiently*
* **Outcome**: *So I can learn what Gitlab can offer and how they will support my learning as a customer*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[All Resources](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 @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [X] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 5 |
28,847,821 | 121,365,422 |
2023-01-06 17:22:05.246
|
[ENG] Update anchors in the /maturity page to work across all browsers
|
## Goal
We want to update the anchors on the /maturity page in the www repo to fix a Chrome bug that does not scroll to the correct position when linking to the page.
Here is a [thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1491#note_1227983580) to the discovery of the bug:
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `We want to make sure the /competition page links are working as they should across all browsers`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
## Page(s)
Which page(s) are involved in this request?
* `[Maturity page](https://about.gitlab.com/direction/maturity/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @Tinaliseng @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update anchor code on maturity page
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 121,364,420 |
2023-01-06 17:05:31.877
|
ENG: Fix Customer page quote section background
|
[Customers](https://about.gitlab.com/customers/) page. The quote section background and padding need to be fixed.
| 2 |
28,847,821 | 121,364,145 |
2023-01-06 17:02:35.388
|
ENG: Fix Solutions page card icons
|
There is an icon missing from the left [/solutions](https://about.gitlab.com/solutions/) landing page card and I think the one on the right might be too big.
| 1 |
28,847,821 | 121,310,863 |
2023-01-05 18:01:07.997
|
ENG: Update colors on the TeamOps page
|
## Goal
We need to change the colors on the Guiding Principles section of the TeamOps page to match the [updated model graphic](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/7223/designs/teamops-model-01.png)
- Everyone Contributes should be changed to `#966DD9`
- Decision Velocity should be changed to `#FD8249`
<details><summary>Click to see visual</summary>
</details>
## Page(s)
Which page(s) are involved in this request?
* [TeamOps](https://about.gitlab.com/teamops/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `@vicbell`
- [ ] Consulted: @Tinaliseng
- [ ] Informed: @justin.vetter
## In scope
What is within scope of this request?
- [ ] Update colors only
## 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 | 121,182,098 |
2023-01-03 18:21:15.903
|
ENG: Run changelog script for Jan 16 - Jan 29 iteration
|
## Goal
Run the changelog and version script at the end of the iteration from Jan 16 - Jan 29
## Steps to run
1. Monitor the scheduled changelog job
1. Patch up the generated changelog with missed commits
## In scope
What is within scope of this request?
* [ ] Script automatically runs on on Friday Jan 27th
## 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 | 121,176,320 |
2023-01-03 16:55:04.421
|
[ENG] Update hero image on /dedicated/ page
|
## Goal
We would like to update the hero for the Dedicated page
### Working Files
[Figma](https://www.figma.com/proto/1WwNfrykRmR5h0yJ7bX3i6/GitLab-Dedicated?page-id=0%3A1&node-id=686%3A6950&viewport=-4814%2C366%2C0.63&scaling=min-zoom)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to update the hero `
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* [Dedicated](https://about.gitlab.com/dedicated/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update hero image
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 121,175,742 |
2023-01-03 16:39:02.325
|
[ENG] Education solution page
|
## Goal
We would like to update our [/solutions/education](https://about.gitlab.com/solutions/education/) page.
#### Working Files
[Figma] (https://www.figma.com/file/TbJai6MP3eokLeLRqEoEJC/Education-page-MVC1?node-id=63%3A3983&t=ucB5bv3xipSo9plv-1)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* [Education](https://about.gitlab.com/solutions/education/)
## 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?
- [ ] Education solutions page
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 121,018,115 |
2022-12-29 09:19:56.933
|
ENG: [Refactor] - Remove AOS initialization in solutions pages
|
## Goal
Remove AOS initialization from solutions pages to reduce duplicated code and only use AOS in the Layout
## 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 | 120,953,292 |
2022-12-27 15:22:46.978
|
ENG: [Refactor] - Remove AOS initialization in single landing pages
|
## Goal
Remove AOS initialization from single landing pages to reduce duplicated code and only use AOS in the Layout
## 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 | 120,949,118 |
2022-12-27 13:24:02.686
|
ENG: [Refactor] - Add animation initialization to layout
|
## Goal
Add the AOS initialization to the default layout in order to remove the same code from the rest of the pages/components
## In scope
What is within scope of this request?
- [x] Add AOS initialization methods to `/layouts/default.vue`
## 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 | 120,769,882 |
2022-12-21 20:42:42.557
|
Enable anchor links as source for redirects
|
## Goal
We would like to enable anchor links to be the `source` for redirects.
We discovered this functionality didn't work when implementing redirects for the support pages [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/116174#note_1215292915).
Another example is [this one](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/redirects.yml#L1302) which also doesn't work.
```yaml
- sources:
- /handbook/finance/procurement/#prior-to-contacting-procurement
- /handbook/finance/procurement/#prior-to-contacting-procurement/
- /handbook/finance/procurement/prior-to-contacting-procurement/
- /handbook/finance/procurement/prior-to-contacting-procurement
target: /handbook/finance/procurement/vendor-selection-process/
comp_op: '='
```
#### Jobs To Be Done
* **Situation**: *We wan't to enable anchor links to be the source for redirects*
* **Motivation**: *We want to redirect users to the correct place*
* **Outcome**: *So we can get them to the right place*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
## 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?
- [ ] AR for Fastly
- [ ] Research Fastly redirect strategy
- [ ] Determine how to implement anchor links as the `source`
- [ ] Implement functionality and verify it works on existing redirects
## 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 | 120,768,162 |
2022-12-21 19:38:46.295
|
Update Press Kit page to fit new branding
|
Update the [press kit page](https://about.gitlab.com/press/press-kit/) to match our current branding
1. Remove images from hero section + change color to match the [Press page](https://about.gitlab.com/press/)
| 3 |
28,847,821 | 120,711,648 |
2022-12-20 19:12:30.045
|
ENG: competition/GitLab vs: Add progress bar and link to the maturity page for each stage category
|
## Goal
Add a progress bar component for each category within each stage on the GitLab vs pages and a supporting link that points to the [maturity page](https://about.gitlab.com/direction/maturity/#manage) for each stage.
<details><summary>Click to expand image</summary>
</details>
## Files
Figma designs:
- [GitHub](https://www.figma.com/file/mdjWp1mPBwftLJiSQwJa84/DevOps-Comparison-MVC3?node-id=1107%3A42156&t=XYDd8m7DX5j2UQs0-1) (all stages)
- [Jira](https://www.figma.com/file/mdjWp1mPBwftLJiSQwJa84/DevOps-Comparison-MVC3?node-id=1198%3A44683&t=XYDd8m7DX5j2UQs0-1) (single stage)
- [Document](https://docs.google.com/spreadsheets/d/1azy6CIqgN2v4GBGsXWt7Z84eIc-YPbN7x0rssQTYvhU/edit#gid=0) containing progress bar ratings - connect with @jkempton for any questions about this doc.
**Does anyone in leadership have eyes on this project?**
- [x] Yes `@sytses` , `@dsteer`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* All `GitLab vs` pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jkempton
- [ ] Consulted: @Tinaliseng
- [ ] Informed: @justin.vetter @fqureshi
## In scope
What is within scope of this request?
- [ ] Add the progress bar block under the heading for each category within the stage.
- [ ] Add a link to the respective maturity page for each stage. Example: [#plan](https://about.gitlab.com/direction/maturity/#plan), [#create](https://about.gitlab.com/direction/maturity/#create)
## 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 | 120,661,387 |
2022-12-19 23:55:59.146
|
[ENG] Update text on blog homepage
|
## Goal
We would like to update the text under the subscribe sign-up
Change `twice-weekly` to `twice-monthly`
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `[Blog homepage](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?
- [ ] Update text
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 120,650,139 |
2022-12-19 18:25:54.151
|
[ENG] Bug Fix blog homepage
|
## Goal
We would like to squash any bugs on the blog homepage refresh
#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## 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: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 120,647,884 |
2022-12-19 17:29:09.498
|
[ENG] Remove Confetti from blog posts
|
## Goal
We would like to remove the confetti from the blog post to stay more on current brand
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `All blog posts`
## 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
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove confetti from blog posts
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 120,644,057 |
2022-12-19 16:17:41.341
|
ENG: Competition / GitLab vs / UX update GA link data attributes
|
## Goal
There's links within the Markdown that don't have `data-ga-name` and `data-ga-location` attributes. Add inline attributes and component support for all link type content.
#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[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
## 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
| 3 |
28,847,821 | 120,636,588 |
2022-12-19 14:45:50.565
|
UX: MVC3: Nav AB test plan
|
## Goal
We would like to collect feedback on the [latest nav design](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1549#note_1151726453). We'll use that feedback to define the scope of changes in this issue to the Nav and create a spec for ENG.
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [X] DRI: @mpreuss22
- [X] Consulted: @ctsang-ext @Tinaliseng @fqureshi @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] TBD
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 5 |
28,847,821 | 120,537,169 |
2022-12-16 14:44:58.667
|
Fix broken links
|
## Goal
Fix broken links found from weekly 404 checker.
| 1 |
28,847,821 | 120,502,452 |
2022-12-15 21:24:41.901
|
[ENG] Vs pages accessibility
|
## Goal
We would like to improve accessibility on the Vs. page templates.
- [ ] Making the tab controls accessible
- [ ] Adding alt text to progress bars
## Page(s)
Which page(s) are involved in this request?
* Vs page templates
## 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 | 120,494,747 |
2022-12-15 18:50:47.170
|
GitLab Learn updates
|
## Goal
Assist in reviewing/merging/fixing pipelines for /learn
| 1 |
28,847,821 | 120,494,727 |
2022-12-15 18:49:13.172
|
Make sure we're only using marketing=true categories on the platform page
|
## Goal
Filter out marketing=false entries in the /platform page table
| 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.