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 | 123,333,641 |
2023-02-08 23:32:05.461
|
German Homepage - Human Translation Review
|
## Goal
It's come to our attention that the [homepage translation job for German](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1745) needs additional review and strings edited.
## Which page(s) are involved in this request?
* about.gitlab.com/de-de/
* https://globalization-test.about.gitlab-review.app/de-DE/
## In scope
What is within scope of this request?
- [ ] Human review of German translation
- [ ] Editing of strings
- [ ] Publishing updated strings
| 2 |
28,847,821 | 123,252,659 |
2023-02-08 01:49:09.800
|
Update social previews to new branding
|
## Goal
There are also social previews on some pages that use the old GitLab logo branding.
I saw it recently on LinkedIn with a URL to page.gitlab.com - and it sometimes seems to happen with about.gitlab.com/handbook too. I could not debug further yet.
An easy way to test social preview cards and tags is https://www.opengraph.xyz/ (documented in the [Developer evangelism handbook](https://about.gitlab.com/handbook/marketing/community-relations/developer-evangelism/social-media/#social-card-validators)).
#### 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.gitlab.com
* about.gitlab.com
## In scope
What is within scope of this request?
- [ ] Ensure social previews for www-gitlab-com are using new branding (new logo)
- [ ] Ensure social previews for Buyer Experience are using new branding (new logo)
- [ ] Ensure social previews for page.gitlab.com are using new branding (new logo)
| 2 |
28,847,821 | 123,249,130 |
2023-02-07 23:07:31.650
|
Slippers devops stage icons rename to simplify template logic in Buyer Experience repo
|
The following discussion from !1651 should be addressed:
- [ ] @mpenagos-ext started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1651#note_1269445712): (+1 comment)
> I think it would be better to rename the icons in slippers rather than having this specific logic for these stages :thinking: it's just a small nitpick so I'll mark the MR as approved!
| 2 |
28,847,821 | 111,334,240 |
2022-07-07 20:06:41.618
|
Update Icons on Get Started page
|
## Goal
As per the comment thread in [this MR](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/734#note_1016611043), we're waiting for the latest slippers icons to be released so we can make some updates on this page.
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com/get-started
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mduque-ext
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 111,281,300 |
2022-07-06 23:27:48.992
|
UX: Solutions Landing Page / Design / MVC 1
|
## Goal
We would like to update the [/solutions](https://about.gitlab.com/solutions/) page which will improve customers' product understanding as measured by CTA clicks further down the purchasing path.
## Page(s)
Which page(s) are involved in this request?
* [/solutions](https://about.gitlab.com/solutions/)
## Workfile
* [Figma file](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=2102%3A8148)
* [Copy doc](https://docs.google.com/document/d/1EP8tAlmI7QX1YfnE4J2lPYN29UNf__SLXOHdZjtgrQw/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @KristinaWeis @jhalloran
- [ ] Informed: @fqureshi `@justin.vetter` `@dennischarukulvanich` `@hsmith-watson`
## In scope
What is within scope of this request?
- [ ] Page redesign
## Out of scope
What is out of scope and not part of this iteration?
-
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 111,279,224 |
2022-07-06 21:43:26.888
|
ENG: Category Leadership / Add CTA to header area
|
## Goal
We would like to add relevant CTAs to the header area of the /topic pages which will reduce exit rates as measured by analytics.
## Page(s)
Which page(s) are involved in this request?
- about.gitlab.com/topics/devops/
- about.gitlab.com/topics/gitops/
- about.gitlab.com/topics/ci-cd/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI:
- [ ] Consulted: @ncregan @dennischarukulvanich @Tinaliseng
- [ ] Informed: @fqureshi @justin.vetter
## In scope
What is within scope of this request?
- [ ] ENG - Add buttons under the intro copy
- [ ] CNT - Provide links
## Out of scope
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 1 |
28,847,821 | 111,269,209 |
2022-07-06 17:04:47.393
|
Access to Sisense and Periscope
|
## Goal
We would like to acquire access to Sisense and Periscope to process data from the the `/gitlab-com/marketing/digital-experience` group. Then let's set up a dashboard using existing issue label data. This will enable our team to learn how to use these platforms and make informed decisions while we [implement and measure MRs by type](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1021).
### Resources
- https://about.gitlab.com/handbook/business-technology/data-team/platform/sisensecdt/
- https://app.periscopedata.com/app/gitlab/976854/Merge-Request-Types-Detail
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Submit a group access request to Sisense for @mpreuss22 @dennischarukulvanich @justin.vetter @laurenbarker and @fqureshi
- [ ] Submit a group access request to Periscope for @mpreuss22 @dennischarukulvanich @justin.vetter @laurenbarker and @fqureshi
- [ ] Set up a dashboard that pulls in existing issue label data from `/gitlab-com/marketing/digital-experience`
## Out of scope
What is out of scope and not part of this iteration?
- [ ] Creating new labels
- [ ] Creating dashboards to measure MRs by type
## 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
- [ ] Engineering
| 1 |
28,847,821 | 111,269,124 |
2022-07-06 17:02:46.230
|
Blog cards category is white
|
## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?
### Describe the Bug
At the bottom of our blog posts there is section displaying blog post cards users can click. These blog post cards display the category. This text is white resulting it being unreadable.
### What's my browser?
Share your browser infromation from https://www.whatsmybrowser.org/b/M528L
## Page(s)
Which page(s) are involved in this request?
* All blog posts
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 2 |
28,847,821 | 111,269,757 |
2022-07-06 16:39:11.517
|
Fix broken "Security risk mitigation" link on "Why Ultimate" page
|
This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/
This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.
#### What is/are the relevant URL(s)
`https://about.gitlab.com/pricing/ultimate/#security-risk-mitigation`
#### Briefly describe the bug
Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned.
`The linked page for Security risk mitigation does not exist - 404 error`
#### Recommended fix
Per [comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1075#note_1019040664) by @supadhyaya below lets update the link to https://about.gitlab.com/solutions/dev-sec-ops/
#### If possible, please specify how to reproduce the bug
`Insert answer here`
#### Please provide any relevant screenshots or screencasts
How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/
`Insert screenshot here`
#### What is your window size, browser, operating system, and versions
Please use the following website to determine your browser specifications and provide a link developers can follow:
What is my browser https://www.whatsmybrowser.org
`Insert results URL here`
#### What computing device are you using?
Please list the brand and model (Example: Samsung Galaxy S 10 Plus)
`Insert answer here`
### What type of input are you attempting to use?
Webpage interactivity is often tied to a specific device event.
- [ ] Touchscreen
- [ ] Touchpad
- [ ] Mouse click
- [ ] Mouse click and drag
- [ ] Scrollwheel
- [ ] Keyboard
- [ ] Stylus
- [ ] Other (please specify)
#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?
- [ ] I tried a fresh incognito window & it had no impact.
- [ ] The problem goes away when using an incognito window.
- [ ] The problem only happens when certain cookies are set to a specific value (please specify below).
#### Please list any browser plugins you have enabled
Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing.
`Insert answer here`
#### Are you blocking javascript or any other resources?
Javascript is needed for certain website functionality.
- [ ] I AM blocking javascript or other resources.
- [ ] I am NOT blocking javascript or other resources.
#### What is your geographic location
Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies.
`Insert answer here`
#### What type of network are you connected to?
**Type**
- [ ] Wired
- [ ] Wifi
- [ ] Cellular (4G, 5G, etc)
- [ ] Satellite
- [ ] Other
`Insert details here if applicable`
**Location**
- [ ] Home
- [ ] Workplace
- [ ] Travel facility (hotel, airport, conference center, etc)
- [ ] Public venue (restaurant, library, cafe, etc)
- [ ] VPN
- [ ] Other
`Insert details here if applicable`
**Hardware**
- [ ] I am behind a network security appliance such as a firewall
- [ ] I am using a pi-hole or other hardware-based traffic blocker
- [ ] Other
`Insert details here if applicable`
<!-- Please do not remove the items below, they are needed to automatically notify the relevant entities -->
/cc @gl-website
<!-- These labels will be automatically applied unless you edit or delete the following section -->
| 1 |
28,847,821 | 111,259,966 |
2022-07-06 14:13:33.054
|
slippers-ui - v2.0.15: import
|
## Goal
| 2 |
28,847,821 | 111,201,712 |
2022-07-05 16:14:22.802
|
Redirect Gitlab 15 Reg Page
|
## Goal
We would like to redirect the Gitlab 15 Reg Page to the on demand page which will improve customer ability to access the ondemand event as measured by video views/downloads.
## Page(s)
Which page(s) are involved in this request?
* `[GitLab 15 registration page--source](https://about.gitlab.com/fifteen/)`
* `[GitLab 15 on demand event page--destination](https://page.gitlab.com/fifteen.html)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `@kbolton1`
- [ ] Consulted: `@cblake` @khartline
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ X] Engineering
| 1 |
28,847,821 | 111,201,133 |
2022-07-05 16:02:09.137
|
UX: Features landing page / Design Iteration / MVC 4
|
## Goal
After conducting [UX research](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1023) on the [/features](https://about.gitlab.com/features/) landing page, we would like to make additional updates which will improve how potential customers learn about the Features that GitLab offers and move them closer to our [conversion goals](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1067#note_1016931422).
### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to review the features that are relevant to my needs*
* **Outcome**: *So I can make an informed purchasing decision.*
## Approach
* We will explore taking an e-commerce approach to how we design the UI for this page
* Revisit the grouping and move away from stages to align with the recent /solutions groupings and pricing tiers
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/
## Workfiles
- [Figma file](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=1083%3A8910) - WIP
## In scope
What is within scope of this request?
- [ ] Design updates
## Out of scope
What is out of scope and not part of this iteration?
-
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: `@cblake` `@davistye` `@supadhyaya` `@awaters3` @jhalloran @dennischarukulvanich
- [ ] Informed: @fqureshi @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
- [x] UX Design
- [ ] Engineering
| 10 |
28,847,821 | 111,029,836 |
2022-07-01 14:50:08.300
|
Sidebar navigation broken on Commit landing page
|
## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?
### Describe the Bug
The sidebar on the commit landing page is floated to the center.
### What's my browser?
https://www.whatsmybrowser.org/b/M528L
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/events/commit/
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/events/commit/index.html.haml
## 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
## Additional Information
We are in the process of [migrating events over to the Buyer Experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/953). Therefore this issue is for making the page usable but we will be doing a full rebuild shortly.
| 2 |
28,847,821 | 110,982,472 |
2022-06-30 18:51:57.872
|
ENG: Revert depreciation of this page /services/implementation/enterprise/
|
## Goal
We would like to revert the depreciation of this page https://about.gitlab.com/services/implementation/enterprise/
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/services/implementation/enterprise/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jgarc
- [ ] Consulted: @justin.vetter
- [ ] Informed: `@bryan-may`
## In scope
What is within scope of this request?
- [ ] Revert the depreciation of page
## Out of scope
What is out of scope and not part of this iteration?
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 110,976,128 |
2022-06-30 16:08:29.765
|
ENG: Launchdarkly: Iteration 2
|
## Goal
In trying to [run a test experiment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/503), we see that conversions are showing up as unique clicks.
From Launchdarkly support:
> 1) What does the button/link do (Purchase button, opens a new page/website, etc.)?
> 2) Do you see the event ever fire (You can check this in both the debugger and the network tab of your browser console)
> 3) Are you using Do Not Track/Adblock?
>
> If you are changing the URL upon click, you would have to use a custom conversion (Such as if you were submitting a form that redirects to a new page, etc.).
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 5 |
28,847,821 | 110,926,349 |
2022-06-29 21:28:18.416
|
Follow-up from "Release navigation version 1.0.36"
|
## What does this affect? Check all that apply.
- [x] Navigation
- [x] Mobile
- [x] Desktop
- [ ] Footer
- [ ] Other (please explain)
## Problem
There's a critical A11y issue as reported by the Axe devtools when run in this repo as shown in the screenshot below
## Goal
We would like to solve the reported issue and have zero critical issues in the Axe devtools report
## 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`
| 2 |
28,847,821 | 110,923,308 |
2022-06-29 20:22:46.757
|
ENG: Release Post template - Brand refresh (post release) pt 1
|
## Goal
Iterate over the recently updated blog post release template to match the [Figma](https://www.figma.com/file/JzLrT0korZQuRmnCv7md4K/Release-template?node-id=2%3A53) design as close as possible
| Element | Figma | Current |
| ------ | ------ | ------ |
| Update twitter link styling |  |  |
| Gitlab MVP Profile Image and reduce width to match rest of sections |  | |
| SaaS Self Managed buttons |  |  |
| Images+Text Layout |  |  |
| Update "performance improvements" and "usability improvements" section headers |  |  |
| Newsletter Structure |  |  |
### Jobs To Be Done
* **Situation**: Our recently updated release template still needs more work to match the intended brand refresh
* **Motivation**: Align the release template with the brand refresh
* **Outcome**: When someone goes to our release page the brand matches our new brand refresh
## Page(s)
Which page(s) are involved in this request?
* [Release Post Example](https://about.gitlab.com/releases/2022/05/22/gitlab-15-0-released/)
## 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`
## 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
| 4 |
28,847,821 | 110,915,077 |
2022-06-29 16:53:35.975
|
UX: Solutions / CTA Block to Get Started pages
|
## Goal
We would like to add links to get to the Get Started pages on the Solutions pages.
### Jobs To Be Done
* **Situation**: *When a customer visits GitLab and wants to get started quickly*
* **Motivation**: *We want to show them ways to get started*
* **Outcome**: *So we can increase conversions*
## Page(s)
Which page(s) are involved in this request?
- Solutions pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @ctsang-ext, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Design for ENG
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 110,911,542 |
2022-06-29 15:47:16.449
|
UX: Navigation to the Get Started pages
|
## Goal
We would like to add links to get to the Get Started pages.
### Jobs To Be Done
* **Situation**: *When a customer visits GitLab and wants to get started quickly*
* **Motivation**: *We want to show them ways to get started*
* **Outcome**: *So we can increase conversions*
## Page(s)
Which page(s) are involved in this request?
- [Figma design](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=1225%3A13216)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @Tinaliseng @jhalloran @cblake
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Design for ENG
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 110,571,131 |
2022-06-22 18:33:30.646
|
ENG: Release Post template - Brand refresh (post release)
|
## Goal
Iterate over the recently updated blog post release template to match the [Figma](https://www.figma.com/file/JzLrT0korZQuRmnCv7md4K/Release-template?node-id=2%3A53) design as close as possible
| Element | Figma | Current |
| ------ | ------ | ------ |
| Gitlab Release H1 | | ------ |
| Split H1 and H2 copy in header |  |  |
| Update share icons |  |  |
| Add side navigation |  | |
| Update twitter link styling |  |  |
| Gitlab MVP Profile Image and reduce width to match rest of sections |  | |
| SaaS Self Managed buttons |  |  |
| Images+Text Layout |  |  |
| Update "performance improvements" and "usability improvements" section headers |  |  |
| Ref Buttons icon update|  |  |
| Newsletter Structure |  |  |
| Truncate and reposition previous and next pages |  |  |
| Questions or comments section |  |  |
| Add button to GitLab Forum option |  |  |
| Invert comments and "last call" section |  |  |
### Jobs To Be Done
* **Situation**: Our recently updated release template still needs more work to match the intended brand refresh
* **Motivation**: Align the release template with the brand refresh
* **Outcome**: When someone goes to our release page the brand matches our new brand refresh
## Page(s)
Which page(s) are involved in this request?
* [Release Post Example](https://about.gitlab.com/releases/2022/05/22/gitlab-15-0-released/)
## 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`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 10 |
28,847,821 | 110,570,429 |
2022-06-22 18:11:38.647
|
GA4: Content Security Policy
|
## Goal
Related: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/922#note_1000045146
Events are not sending to GA4 on gitlab.com. This is the JS error message I receive:
> it violates the following Content Security Policy directive: "connect-src 'self'
@tywilliams 's recommendation:
> To resolve that, we'll need to update the content security policy in `lib/gitlab/content_security_policy/directives.rb`, [similar to how it was updated in this MR](https://gitlab.com/gitlab-org/gitlab/-/commit/6bb099039e20bca19de5f61ecf98bc51e0a3c858/#3fe66e137a17241d7e683542368b77aa4f8c7b8d_11_11) and make it compatible with whatever GA4 needs, [which I think is listed here](https://developers.google.com/tag-platform/tag-manager/web/csp#google_analytics_4_google_analytics).
## Page(s)
Which page(s) are involved in this request?
gitlab.com pages with GTM and OneTrust in the registration flow
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @miraclebanks @tywilliams
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: @laurenbarker
## 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 | 110,563,533 |
2022-06-22 16:16:19.303
|
Add link to Leadership Team to People Sub Navigation
|
## Goal
We would like to add a link to GitLab's Leadership team within the People Sub Navigation which will improve access to this information as measured by traffic to the Leadership page.
## Page(s)
Which page(s) are involved in this request?
* Main navigation -> Resources -> People
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add Navigation item `Leadership` that links to https://about.gitlab.com/company/team/e-group/
## 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 | 110,563,373 |
2022-06-22 16:12:37.112
|
Update link for Always Iterating in Main Navigation
|
## Goal
We would like to update the link for Always Iterating in the main navigation which will improve the user experience as measured by session duration and time on page.
## Page(s)
Which page(s) are involved in this request?
* Main navigation -> Why GitLab -> Always Iterating
## 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?
- [ ] Change Always Iterating to link to https://about.gitlab.com/releases/categories/releases/
## 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 | 110,563,251 |
2022-06-22 16:09:57.724
|
All instances of GitLab's DevOps lifecycle should be in the correct order
|
## Goal
We would like to have GitLab's DevOps lifecycle in the correct order which will improve consistency as measured by the correct representation of the DevOps lifecycle on our Marketing site.
## Page(s)
Which page(s) are involved in this request?
* Main Navigation -> Why GitLab? -> The DevOps Lifecycle
* Main Navigation -> Platform -> The DevOps Lifecycle
* Please check all instances on the Marketing site.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update all instances of GitLab's DevOps Lifecycle to:
1. Plan
2. Create
3. Verify
4. Package
5. Secure
6. Release
7. Configure
8. Monitor
9. Protect
10. Manage
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 2 |
28,847,821 | 110,505,774 |
2022-06-21 20:11:15.299
|
Implement suggested results for top 5 search queries in Swiftype
|
## Goal
We would like to reorder our search results for our commonly searched terms which will improve our clickthrough rate. This is a small test to see if improving our search results for customer sought-out topics and content (ex: CI/CD, DevOps, etc) will keep users more engaged.
## Background
From our [metrics](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/994#note_982711036), customers with a strong intention of making a search tend to navigate to a lot more pages than the average visit. Additionally, studies show how optimizing your internal search not only [improves usability](https://www.nngroup.com/articles/search-visible-and-simple/), but also significantly [increases conversion rates](https://econsultancy.com/is-site-search-less-important-for-niche-retailers/).
## Jobs To Be Done
* **Situation**: *When I am searching for a customer related topic (ex: CI/CD, DevOps, etc)*
* **Motivation**: *I want to see the most relevant information first*
* **Outcome**: *So I can quickly learn about how GitLab can solve my DevOps problem*
## Page(s)
Which page(s) are involved in this request?
Implementing suggested results for the following search qurtird:
1. gitlab
1. docker
1. devops
1. careers
1. handbook
1. login
[Excel sheet with re-ordering](https://docs.google.com/spreadsheets/d/10FILy6r0DV6j-QuED7XnNpUIlkFHXvAJ5LcPmtF85XE/edit#gid=0)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `@ctsang-ext` @lduggan
- [ ] Consulted: @Tinaliseng @jhalloran
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Implement suggest results for 5 search queries in Swiftype
- [ ] Determining if we can edit the copy displayed for these results
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [X] Copy writing / Content
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [x] UX Design
- [x] Engineering
| 2 |
28,847,821 | 110,490,017 |
2022-06-21 17:03:28.876
|
Add Side Navigation to pages with missing navigation
|
## Goal
With closing https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/677, we now have functional side navigation that we can add to existing high-value pages. This issue pertains to adding that to those specific pages.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Enterprise page, small business page
## Out of scope
What is out of scope and not part of this iteration?
- [ ] Feature child pages
- [ ] Solution child pages (originally scoped, but layouts aren't standardized)
## 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 | 110,489,046 |
2022-06-21 16:36:04.626
|
ENG: Get Started for Enterprise
|
## Goal
We would like to build a single template for our Get Started pages which will give users quick tutorials on how to get started using GitLab for Enterprise.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/get-started/enterprise
* All Get Started pages will use the same template
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @miraclebanks
- [ ] Consulted: @ctsang-ext @cblake
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Iterate on template
- [ ] Apply template to parent and child pages
- [ ] Depreciate pages with duplicate content and set redircts
## Design
- [Figma file](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=368%3A3068)
## Out of scope
What is out of scope and not part of this iteration?
- Side anchor nav is being addressed in this issue https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148
## 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 | 110,443,336 |
2022-06-20 23:41:53.231
|
ROI calculator - add legal disclaimer
|
## Goal
As per @rchachra - we should add a legal disclaimer in the ROI calculator. See note below.
> This page should have a disclaimer on it that the output is purely an estimate and subject to change based on various factors that went into the calculation.
Proposed text:
The results are purely an estimate and subject to change based on various factors that went into the calculation.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)` https://about.gitlab.com/calculator/roi
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle` @supadhyaya
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Disclaimer in ROI calculator page
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 110,321,088 |
2022-06-17 22:52:02.799
|
View page source link broken
|
At bottom of https://about.gitlab.com/install/ view page source link broken is broken
| 2 |
28,847,821 | 110,317,501 |
2022-06-17 19:49:01.069
|
Bizible script shows twice in <head> in product
|
## Goal
After adding Bizible script to sign up pages and enabling it for gitlab.com, @dennischarukulvanich noticed that the `https://cdn.bizible.com/scripts/bizible.js` script was displaying twice in the `<head>`.
This issue is for further iterating on the original feature MR here to ensure the script only displays once.
[Related slack thread in #digital-experience-team](https://gitlab.slack.com/archives/CN8AVSFEY/p1655491092242909)
## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/-/trials/new
* https://gitlab.com/-/trials/select
* https://gitlab.com/users/sign_up
* https://gitlab.com/-/trial_registrations/new
* https://gitlab.com/users/almost_there
* https://gitlab.com/users/sign_up/groups/new
* https://gitlab.com/users/sign_up/projects/new
* https://gitlab.com/users/sign_up/groups_projects/new
* https://gitlab.com/users/sign_up/welcome/trial_getting_started
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @degan @dennischarukulvanich
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] `gdk update` and fixing issues to enable local development
- [ ] MR to iterate on Bizible feature for GitLab
- [ ] Ensure change is enabled on production for gitlab.com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 5 |
28,847,821 | 110,316,406 |
2022-06-17 19:02:08.146
|
ENG: Refresh Update page
|
## Goal
We would like to update the /update/ page to match the card styles created on the /install/ page
### Jobs To Be Done
* **Situation**: *When ...*When a user goes from the Install page to the update page the styles are different*
* **Motivation**: *To have a consistent user experience*
* **Outcome**: *Clean up code*
## Page(s)
Which page(s) are involved in this request?
* [Update](https://about.gitlab.com/update/)
* [Install](https://about.gitlab.com/install)
## 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?
- [ ] Update styles/template
## Out of scope
What is out of scope and not part of this iteration?
- Updating Copy
## 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 | 110,262,862 |
2022-06-16 21:33:05.033
|
Bug: Features LP - Pipeline security link points to a 404 page
|
### Describe the Bug
Clicking on `Pipelines security` from https://about.gitlab.com/features/?stage=verify leads to a [404 page](https://docs.gitlab.com/ee/user/project/new_ci_build_permissions_model.html). Unsure which docs page it should point to.
Also, should it read 'Pipeline security' without the plural 's'?
### What's my browser?
Chrome
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/?stage=verify
* https://docs.gitlab.com/ee/user/project/new_ci_build_permissions_model.html
## 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 | 110,249,931 |
2022-06-16 15:56:45.536
|
UX: Features landing page / UX research
|
## Goal
When making updates to the [Features page](https://about.gitlab.com/features/), I want to first do research so I can better understand what improvements are needed for a better user experience.
### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to easily find information about features that are relevant to my needs*
* **Outcome**: *To better understand if GitLab is the right solution for my problems*
## Page(s)
Which page(s) are involved in this request?
- [/features](https://about.gitlab.com/features/)
## Workfiles
[UX research doc](https://docs.google.com/document/d/1fHF4Hf5J-AxVYB_eb5vAC1MeaU72IqZQmcPDLufNR8U/edit?usp=sharing) - WIP
[See comment re: conversion goals](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1067#note_1016931422)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran @ctsang-ext @dennischarukulvanich
- [ ] Informed: @fqureshi
## In scope
What is within scope of this request?
- [x] [Analytics report](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/941#note_970044291) - completed by @dennischarukulvanich
- [ ] Review LogRocket Sessions
- [ ] Usability testing - MVC 3 vs MVC 4
- [x] [Stakeholder interviews](https://docs.google.com/document/d/18p_IC9q6iWD68lQ7hoMOGXixCVy0fbM_v9aEUYcIr-I/edit?usp=sharing)
- [x] Review [post-purchase survey](https://docs.google.com/presentation/d/1OQRID4vKwpeUAfgVYlDDrsv4whqSmb7R9Us_Q1EaiFY/edit?usp=sharing)
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 10 |
28,847,821 | 110,198,486 |
2022-06-15 22:50:54.415
|
ENG: Features landing page / UX Updates / MVC 3
|
## Goal
We would like to update the UX on [/features](https://about.gitlab.com/features/) which will improve how potential customers learn about the Features that GitLab offers.
### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to review the features that are relevant to my needs*
* **Outcome**: *So I can make an informed purchasing decision.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: `@dzalbo` `@cblake` @jhalloran
- [ ] Informed: @justin.vetter @fqureshi
## In scope
What is within scope of this request?
- [ ] Design updates as annotated in this [Figma file](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=971%3A4672)
## Out of scope
What is out of scope and not part of this iteration?
- content refresh
## 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 | 110,194,972 |
2022-06-15 20:59:51.302
|
Implement and Measure MR by Type
|
## Goal
After sitting in the Cross-functional prioritization adoption AMA AMER/EMEA discussion 6/15 8:30am Pacific, I learned a lot on how product teams allocate work. [Here's that agenda doc](https://docs.google.com/document/d/13iobEuygqGi3L4Lczu72zoKuzuL_8fHmUpN7xQzZZGs/edit?usp=sharing) & [recording](https://drive.google.com/file/d/1w-4-DsUaIgbMXHF2f3rxjzxfpSa8OdvA/view?usp=sharing).
To support [GitLab's long-term product health and stability](https://about.gitlab.com/handbook/product-development-flow/cross-functional-prioritization.html), teams are asked to plan their milestones with an appropriate mix of `type::feature`, `type::maintenance`, and `type:bug` work. MR Type labels help us report what we're working on to leadership in a way that's consistent across the engineering department.
This issue is for aligning with the Digital Experience team on these items:
1. Introduce merge request types for the Digital Experience team to align with the [Cross Functional Prioritization](https://about.gitlab.com/handbook/product-development-flow/cross-functional-prioritization.html) process of product groups. We have some merge request types being implement as part of the approval process being worked on [here](https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/epics/135). Should we add additional types for bugs, maintenance, and features?
1. Create a dashboard for MR by Type for Digital Experience. Dashboards listing MR by Type were created and added to every group for product as part of [this issue](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13294). Here is the [Merge Request Types Detail periscope dashboard](https://app.periscopedata.com/app/gitlab/976854/Merge-Request-Types-Detail) for product.
1. Update [Repository Health Days and Weeks](https://about.gitlab.com/handbook/marketing/digital-experience/#repository-health-day) with our new process
### Jobs To Be Done
* **Situation**: *Digital Experience has no way to measure MRs or what type of work it's contributing to*
* **Motivation**: *We want to implement MR types and measure them*
* **Outcome**: *So we can support GitLab's long-term product health and stability*
## Page(s)
Which page(s) are related to this request?
* https://about.gitlab.com/handbook/marketing/digital-experience/#repository-health-day
* https://about.gitlab.com/handbook/product-development-flow/cross-functional-prioritization.html
* https://about.gitlab.com/company/team/structure/working-groups/next-prioritization/
* https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13294
* https://app.periscopedata.com/app/gitlab/976854/Merge-Request-Types-Detail
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @mpreuss22 @fqureshi @justin.vetter @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Implementing MR by Type
- [ ] Create Digital Experience Periscope dashboard to measure MR by Type
- [ ] Updating the Digital Experience handbook
## 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
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 110,187,080 |
2022-06-15 17:48:18.931
|
ENG: Swap old logo from press page
|
## Goal
We would like to swap out the old Tanuki logo from the /press page
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[/press](https://about.gitlab.com/press/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jgarc
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Swap logo
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 110,182,484 |
2022-06-15 16:09:59.701
|
SPIKE - Automate MR labels
|
## Goal
| 2 |
28,847,821 | 110,126,182 |
2022-06-15 00:15:20.819
|
CODEOWNERS iteration - Add /company
|
## Goal
We should ensure that CODEOWNERS for /company pages that have been migrated from [www-gtilab-com](https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/sites/uncategorized/source/company) to our [Buyer Experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/company) or communicate these permissions have been changed.
Here is a [related slack thread](https://gitlab.slack.com/archives/C81PT2ALD/p1655183589470129) to CODEOWNERS for pages within the [/company](url) directory.
### Jobs To Be Done
* **Situation**: *When anyone makes a change to a page within the /company URL, the proper people are notified to review the merge request.*
* **Motivation**: *We want to ensure owners of these pages have oversight changes.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/company/
* https://about.gitlab.com/company/culture/all-remote/
## 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?
- [ ] Determine appropriate people to be listed as code owners of company pages in the Buyer Experience repository
- [ ] Update CODEOWNERS in Buyer Experience with these people
- [ ] Communicate changes to GitLab if necessary
## 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
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 110,121,293 |
2022-06-14 20:33:28.650
|
Public Sector quote carousel previous button is facing the wrong direction
|
## Goal
The Previous button's chevron is facing the wrong way in the quote carousel, so it looks like there are two next buttons.
## Page(s)
Which page(s) are involved in this request?
* `/solutions/public-sector` [link](https://about.gitlab.com/solutions/public-sector/)
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 110,117,645 |
2022-06-14 19:07:36.093
|
ENG: Case Study LP - Remove horizontal padding around the title
|
## Goal
We would like to remove the horizontal padding around the titles in the hero of the case study landing page which will improve readability as measured by click-through rates.
### Describe the Bug
Large padding splits the title up over too many lines making it difficult to read and absorb.
This was a [community contribution](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/105962) for the blog that I agree with and would like to implement on the case study pages as well.
Here is a screenshot of the blog improvements:
### What's my browser?
- This change is for mobile only
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/customers/
## 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 | 110,117,461 |
2022-06-14 19:03:23.083
|
ENG: Remove Parts Unlimited Case Study
|
## Goal
We would like to remove the [Parts Unlimited](https://about.gitlab.com/customers/parts_unlimited/) case study from the site
### Jobs To Be Done
* **Motivation**: This is a fictitious company and having it in our customers page makes us loose credibility
## Page(s)
Which page(s) are involved in this request?
* [Parts Unlimited](https://about.gitlab.com/customers/parts_unlimited/)
## 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: @FionaOKeeffe
## In scope
What is within scope of this request?
- [ ] Remove Parts Unlimited case study
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 110,109,743 |
2022-06-14 16:34:07.377
|
ENG: Tool tip icon cut off in Safari
|
## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?
### Describe the Bug
In Safari, the information tool tip icon is cut off. Can we remove the height of `.tooltip` to display the full icon?
### What's my browser?
https://www.whatsmybrowser.org/b/GSXCV
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/
## 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 | 110,033,521 |
2022-06-13 14:46:13.947
|
ROI Calculator tests
|
## Goal
Add Jest to the Buyer Experience project and write Jest tests for the new ROI calculator. These tests will give us peace of mind when there are calculator updates that the calculations are still correct.
## Page(s)
Which page(s) are involved in this request?
* `/calculator/roi`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @tywilliams
- [ ] Informed: `Everyone`
## In scope
- [ ] Add Jest testing to our Buyer Experience repository
- [ ] Add Jest tests for functions within the `/lib/roiCalculate.js` file
- [ ] Ensure all tests are passing
| 4 |
28,847,821 | 109,937,396 |
2022-06-10 19:03:42.808
|
Site Search with Multiple Domains - add gitlab.com
|
## Goal
Users who mistaken the marketing site's search feature for the product search feature. These includes searches for namespace, group, or project names.
Our current search provide has the ability to set-up [Site Search with multiple domains](https://swiftype.com/documentation/site-search/guides/multiple-domains).
Let's add the gitlab.com domain to our site search.
Related https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/994#note_982711036
### Jobs To Be Done
* **Situation**: *When a user searches for a namespace, group, or project names it returns a result.*
* **Motivation**: *We want to reduce the number of searches with no action taken.*
* **Outcome**: *So we can increase site search from 1% to 3.4%.*
## Page(s)
Which page(s) are involved in this request?
* Swfittype and every page with search
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @dennischarukulvanich
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Add gitlab.com to Swfitype search configuration
- [ ] Monitor search analytics
## Out of scope
What is out of scope and not part of this iteration?
- Editing the search design
## 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
| 1 |
28,847,821 | 109,930,180 |
2022-06-10 15:35:49.432
|
Banner - Privacy Policy Updated
|
## Goal
We would like to place a banner on the marketing site that notifies users of our updated Privacy Policy.
[Slack Thread](https://gitlab.slack.com/archives/C62ERFCFM/p1654821112375479)
Banner text:
`We've updated our Privacy Policy. Please click [here - link] to learn more about how we process your personal data`
Related https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/102770
### Jobs To Be Done
* **Situation**: *When a user visits our marketing site they see a banner of the privacy policy update.*
* **Motivation**: *We want to be transparent about this update to our privacy policy.*
* **Outcome**: *So we can notify users.*
## Page(s)
Which page(s) are involved in this request?
- Every page on about.gitlab.com
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @mpreuss22 @emccrann @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] MR to [navigation repository](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation) with banner
- [ ] Push update to NPM package
- [ ] MR Pull update into [www-gitlab-com](https://gitlab.com/gitlab-com/www-gitlab-com)
- [ ] MR Pull update into [Buyer Experience](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience)
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [x] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 109,801,751 |
2022-06-08 18:14:10.641
|
Regression in slp-tooltip within free trial page
|
https://gitlab.slack.com/archives/CN8AVSFEY/p1654633608430129
> the small “SaaS” label on the tab here: https://about.gitlab.com/free-trial/ is that by design?
## Page(s)
Which page(s) are involved in this request?
* [Free trial page](https://about.gitlab.com/free-trial/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 109,661,887 |
2022-06-06 16:55:27.018
|
ENG: Clean up removal of ten-oh-announcement from www template
|
## Goal
With the updated home page we would like to clean up the www repo by cleaning up templates. In [this](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/105499#note_972755555) MR @brhea tried to remove the template and all references but the pipeline failed.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* template: includes/home/ten-oh-announcement
* Unused www homepage & template
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @tywilliams
- [ ] Consulted: @brhea
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 109,581,900 |
2022-06-03 21:34:12.893
|
DataLayer Events for SaaS Trial Flow
|
## Goal
There are some pages within the SaaS Trial Flow without GA event tracking/GTM code snippet. Adding dataLayer events and GTM code will allow us to see the full picture in the user's journey from the marketing site to an ultimate trial.
For context, I've created a [deck of all possible paths](https://docs.google.com/presentation/d/11PiN-e79QLXaURmNfVemOexYX2_yEjKBziHzHeH4nWE/edit#slide=id.g11b167403ab_0_104) the user may experience.
## Page(s)
**gitlab.com/-/users/terms**<br/>
Fire on "Accept Terms" button click
```
window.dataLayer = window.dataLayer || [];
dataLayer.push({
'event': 'saasTrialAcceptTerm'
});
```
<br/>
**gitlab.com/users/sign_in**<br/>
Place OneTrust banner first! Paste this code as high in the `<head>` of the page as possible:
```
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NJXWQL');</script>
<!-- End Google Tag Manager -->
```
Additionally, paste this code immediately after the opening `<body>` tag:
```
<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-NJXWQL"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->
```
<br/>
**gitlab.com/users/sign_up/welcome**<br/>
Fire on "Continue" button click
```
window.dataLayer = window.dataLayer || [];
dataLayer.push({
'event': 'saasTrialWelcome'
});
```
<br/>
**gitlab.com/users/sign_up/welcome/continuous_onboarding_getting_started**<br/>
Fire on "Okay Let's Go" button click
```
window.dataLayer = window.dataLayer || [];
dataLayer.push({
'event': 'saasTrialContinuousOnboarding'
});
```
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich @tywilliams
- [ ] Consulted: @jstemmer1
- [ ] Informed: @mpreuss22
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
## Progress
1. [x] `gitlab.com/-/users/terms`: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/91936
2. [x] `gitlab.com/users/sign_in`: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92124
3. [x] `gitlab.com/users/sign_up/welcome`: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96187
4. [x] `gitlab.com/users/sign_up/welcome/continuous_onboarding_getting_started`: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96187
| 3 |
28,847,821 | 109,568,601 |
2022-06-03 15:24:20.382
|
ENG: Release Post template - Brand refresh
|
## Goal
We would like to update the release post template to be better inlined with our refreshed brand. This is similar to the blog refresh where we need to make sure the styles work for previous posts as well.
All changes with this issue should revolve around the styles and theme of the template.
Slack thread [here](https://gitlab.slack.com/archives/CN8AVSFEY/p1652798710579189)
### Jobs To Be Done
* **Situation**: Our release template theme is not on brand
* **Motivation**: We want to have this before the June 22nd release
* **Outcome**: When someone goes to our release page the brand matches our new brand refresh
## Page(s)
Which page(s) are involved in this request?
* [Release post example](https://about.gitlab.com/releases/2022/04/22/gitlab-14-10-released/)
* [Figma file](https://www.figma.com/file/JzLrT0korZQuRmnCv7md4K/Release-template?node-id=2%3A53)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mmanunga-ext
- [ ] Consulted: @jhalloran @amittner @justin.vetter @ndubord
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update styles related to the GitLab release post
## Out of scope
What is out of scope and not part of this iteration?
- Modifying the markup of the template
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 8 |
28,847,821 | 109,527,452 |
2022-06-02 20:34:49.651
|
Deprecate 24 Webcast pages - Batch2
|
## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.
| Webcast Pages to Deprecate |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/webcast/integration-developpement-deploiement-continus-cloud/ |
| https://about.gitlab.com/webcast/justcommit-reduce-cycle-time/ |
| https://about.gitlab.com/webcast/keys-to-devops-success-portugese/ |
| https://about.gitlab.com/webcast/keys-to-devops-success-spanish/ |
| https://about.gitlab.com/webcast/keys-to-devops-success/ |
| https://about.gitlab.com/webcast/managing-compliance-with-gitlab/ |
| https://about.gitlab.com/webcast/mastering-ci-cd-italian/ |
| https://about.gitlab.com/webcast/mastering-continuous-development-fr/ |
| https://about.gitlab.com/webcast/mastering-continuous-development-portuguese/ |
| https://about.gitlab.com/webcast/mission-mobility/ |
| https://about.gitlab.com/webcast/monthly-release/gitlab-11.0---auto-devops/ |
| https://about.gitlab.com/webcast/monthly-release/gitlab-11.1---security/ |
| https://about.gitlab.com/webcast/monthly-release/gitlab-11.2---get-started-and-iterate-faster/ |
| https://about.gitlab.com/webcast/portable-serverless/ |
| https://about.gitlab.com/webcast/rethinking-devops-resiliency/ |
| https://about.gitlab.com/webcast/sales/bankofirelandwebcast/ |
| https://about.gitlab.com/webcast/sales/juniperwebcast/ |
| https://about.gitlab.com/webcast/scaled-continuous-integration-and-delivery/ |
| https://about.gitlab.com/webcast/securing-serverless/ |
| https://about.gitlab.com/webcast/starting-scaling-devops/ |
| https://about.gitlab.com/webcast/trek10-aws-cicd/ |
| https://about.gitlab.com/webcast/weeds-cloud-native/ |
| https://about.gitlab.com/webcast/whats-next-for-gitlab/ |
| https://about.gitlab.com/webcast/zerotrust-cloudnative/ |
These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet.
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed
## 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 | 109,527,448 |
2022-06-02 20:34:42.782
|
Deprecate 24 Webcast pages - Batch 1
|
## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.
| Webcast Pages to Deprecate |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/webcast/adoption-paths-portuguese/ |
| https://about.gitlab.com/webcast/adoption-paths-spanish/ |
| https://about.gitlab.com/webcast/agile-transformation/ |
| https://about.gitlab.com/webcast/auto-devops/ |
| https://about.gitlab.com/webcast/automate-security-ci/ |
| https://about.gitlab.com/webcast/avantages-du-devsecops-fr/ |
| https://about.gitlab.com/webcast/avoid-devops-tax/ |
| https://about.gitlab.com/webcast/aws-tmobile-gitlab/ |
| https://about.gitlab.com/webcast/breakthrough-devops-successful-devops-adoption-strategies/ |
| https://about.gitlab.com/webcast/cicd-in-ihrer-organisation/ |
| https://about.gitlab.com/webcast/critical-workloads-k8-clusters/ |
| https://about.gitlab.com/webcast/customer-success/ha-geo-setup/ |
| https://about.gitlab.com/webcast/dev-sec/ |
| https://about.gitlab.com/webcast/devops-automation/ |
| https://about.gitlab.com/webcast/devsecops-livestream/ |
| https://about.gitlab.com/webcast/digital-devops-series-reduce-costs/ |
| https://about.gitlab.com/webcast/digital-transformation-northwestern-mutual/ |
| https://about.gitlab.com/webcast/fintech-developer-forum/ |
| https://about.gitlab.com/webcast/gary-gruver-discussion/ |
| https://about.gitlab.com/webcast/gitlab-premium-cicd/ |
| https://about.gitlab.com/webcast/gitlab-premium-implementation/ |
| https://about.gitlab.com/webcast/gitlab-premium-security/ |
| https://about.gitlab.com/webcast/gitops-gitlab-aws-helecloud/ |
| https://about.gitlab.com/webcast/gitops-gitlab-pulumi/ |
These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet.
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed
## 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 | 109,527,437 |
2022-06-02 20:34:03.189
|
Deprecate 12 Solution pages
|
## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.
| Solutions Pages to Deprecate |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/solutions/apm/ |
| https://about.gitlab.com/solutions/developer-platform/ |
| https://about.gitlab.com/solutions/no-ticket-provisioning/ |
| https://about.gitlab.com/solutions/ops-insights/ |
| https://about.gitlab.com/solutions/program-management/ |
| https://about.gitlab.com/solutions/public-sector/secure-software/ |
| https://about.gitlab.com/solutions/public-sector/speed-to-mission/ |
| https://about.gitlab.com/solutions/reference-architectures/gitlab-reference-architectures.html |
| https://about.gitlab.com/solutions/release-controls/ |
| https://about.gitlab.com/solutions/security-risk-mitigation/ |
| https://about.gitlab.com/solutions/self-managed-reliability/ |
| https://about.gitlab.com/solutions/simplify-devops/ |
These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet.
Related https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/703
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [x] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed
## 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 | 109,527,410 |
2022-06-02 20:33:28.564
|
Deprecate 4 Service and 5 Snapshot pages
|
## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.
| Pages to Deprecate |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/services/implementation/enterprise/ |
| https://about.gitlab.com/services/innersourcing/ |
| https://about.gitlab.com/services/pse-certifications/ |
| https://about.gitlab.com/services/specialized/ |
| https://about.gitlab.com/snapshots/ |
| https://about.gitlab.com/snapshots/agile-management/ |
| https://about.gitlab.com/snapshots/continuous-delivery/ |
| https://about.gitlab.com/snapshots/continuous-integration/ |
| https://about.gitlab.com/snapshots/security/ |
These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet.
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed
## 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 | 109,527,369 |
2022-06-02 20:32:18.320
|
Deprecate 16 Resource pages
|
## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.
| Pages to Deprecate |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/resources/demo-agile-delivery/ |
| https://about.gitlab.com/resources/ebook-agile-culture-techniques/ |
| https://about.gitlab.com/resources/ebook-agile-delivery-models/ |
| https://about.gitlab.com/resources/ebook-dev-guide-app-security/ |
| https://about.gitlab.com/resources/ebook-guide-remote-devops/ |
| https://about.gitlab.com/resources/gitlab-vs-atlassian/ |
| https://about.gitlab.com/resources/video-gitlab-security-demo/ |
| https://about.gitlab.com/resources/video-going-cloud-native/ |
| https://about.gitlab.com/resources/video-security-capabilities/ |
| https://about.gitlab.com/resources/whitepaper-agile-iteration/ |
| https://about.gitlab.com/resources/whitepaper-bridging-the-divide/ |
| https://about.gitlab.com/resources/whitepaper-DevSecOps-Proactive-security-reduce-risk/ |
| https://about.gitlab.com/resources/whitepaper-exec-briefing-series-digital-transformation/ |
| https://about.gitlab.com/resources/whitepaper-planning-for-success/ |
| https://about.gitlab.com/resources/whitepaper-speed-to-mission/ |
| https://about.gitlab.com/resources/whitepaper-whats-your-digital-readiness/ |
These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet.
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed
## 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 | 109,527,346 |
2022-06-02 20:31:43.492
|
Deprecate 5 Learn pages
|
## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.
| Pages to Deprecate |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/learn/classification/ |
| https://about.gitlab.com/learn/registration/ |
| https://about.gitlab.com/learn/registration/paid/ |
| https://about.gitlab.com/learn/use-case/ |
| https://about.gitlab.com/learn/use-case/public/ |
These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet.
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed
## 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 | 109,527,321 |
2022-06-02 20:30:56.101
|
Deprecate 7 Events pages
|
## Goal
We would like to deprecate the following solutions pages because they have no meaningful traffic from any source and no backlinks.
| Pages to Deprecate |
|------------------------------------------------------------------------------------------------|
| https://about.gitlab.com/de-de/warum/nutze-continuous-integration-fuer-schnelleres-bauen-und-testen |
| https://about.gitlab.com/events/commit/2020/ |
| https://about.gitlab.com/events/commit/speakers/ |
| https://about.gitlab.com/events/hacktoberfest-21/ |
| https://about.gitlab.com/events/kubecon-amsterdam/ |
| https://about.gitlab.com/events/kubecon-na/ |
| https://about.gitlab.com/fr-fr/pourquoi/integration-continue-pour-construire-et-tester-plus-rapidement/ |
These pages were defined in the [IA Refresh Content Audit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354). You can find them in the [Cleaned audit - Phase 1 - website refresh spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit#gid=116929303) in the "Delete" sheet.
### Jobs To Be Done
* **Situation**: *Pages listed above to removed from the marketing site and if a user hits that URL, they are presented with a 404 page*
* **Motivation**: *We want to reduce the number of pages in the marketing site*
* **Outcome**: *So we can be efficient*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove the listed pages. They most likely exist in the www-gitlab-com repository.
- [ ] Mark the pages as "complete" in the [Cleaned audit - Phase 1 - website refresh spreadsheet] once removed
## 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 | 109,522,122 |
2022-06-02 17:46:44.489
|
ENG: Support Child Pages
|
## Goal
We would like to redesign the support pages which will give users a place to self-help.
## Page(s)
This requires the following:
1. A new design for the [main page](https://www.figma.com/proto/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?page-id=388%3A12778&node-id=388%3A12869&viewport=6507%2C1774%2C0.66&scaling=min-zoom&starting-point-node-id=388%3A12869). We'll be using this [copy deck](https://docs.google.com/document/d/14QciHeozCNpNg_hAjXhO9J5I5jf6BXS1lx8OO-YYMKY/edit#) for final copy.
2. Reformatting of individual pages. With the new design, we will be breaking out the existing long page into individual pages. For the individual pages, reformat them using [this design](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=388%3A13106) as a template/guide.
List of individual pages:
- [Customer Satisfaction](https://about.gitlab.com/support/customer-satisfaction/)
- [Support Definitions](https://about.gitlab.com/support/definitions/)
- [Managing Support Contacts](https://about.gitlab.com/support/managing-support-contacts/)
- [General Support Practices](https://about.gitlab.com/support/general-policies/)
- [GitLab Policies](https://about.gitlab.com/support/gitlab-com-policies/)
- [Providing Large Files](https://about.gitlab.com/support/providing-large-files/)
- [Scheduling Upgrade Assistance](https://about.gitlab.com/support/scheduling-upgrade-assistance/)
- [Sensitive Information](https://about.gitlab.com/support/sensitive-information/)
- [Statement of Support](https://about.gitlab.com/support/statement-of-support/)
- [US Federal Support](https://about.gitlab.com/support/us-federal-support/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @ctsang-ext @jcolyer
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Build template
- [ ] Apply template to parent and child pages
## Design
- [Figma file](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=368%3A3068)
## Out of scope
What is out of scope and not part of this iteration?
- Side anchor nav is being addressed in this issue https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 10 |
28,847,821 | 109,521,118 |
2022-06-02 17:20:08.373
|
ENG: Why Gitlab scroll | Animation
|
## Goal
We would like to iterate on the scroll animation for the Why GitLab page
[Frame.io link](https://app.frame.io/reviews/6e6f4cb3-6a37-46b0-9d2e-d0d9e3e137e1/8c09dbda-d19e-4f81-a6c1-d6cd4f1da271)
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Why GitLab](https://about.gitlab.com/why-gitlab/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `Engineer` & @jhalloran (for general design support)
- [ ] Consulted: @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Scroll animation for the One Dev Ops Infinity Loop
## Out of scope
What is out of scope and not part of this iteration?
- Any other animations 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
- [x] UX Design
- [x] Engineering
| 8 |
28,847,821 | 109,520,457 |
2022-06-02 17:00:09.856
|
ENG: Hero image mask | Animation
|
## Goal
We would like to create a mask-style animation for the page load in the hero.
[Figma link](https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26734)
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* Pages with circle hero 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: @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] CSS/JS to create mask animation
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 109,519,908 |
2022-06-02 16:44:16.448
|
ENG: Header scroll animation | Animation
|
## Goal
We would like to create a class that can be added to headers that would allow for on-scroll animation on header text.
[Figma link}(https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26327)
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* All
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create class (css/js) for the on scroll animation
- [ ] Add class to homepage components
## Out of scope
What is out of scope and not part of this iteration?
- Adding class to all pages in this iteration
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 109,519,775 |
2022-06-02 16:39:43.468
|
ENG: Tertiary buttons hover | Animation
|
## Goal
We would like to iterate on our animation/transitions for our tertiary buttons
[Figma link](https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26237)
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* All
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Tertiary button hover class
## Out of scope
What is out of scope and not part of this iteration?
- Other animations
## 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 | 109,519,607 |
2022-06-02 16:35:49.224
|
ENG: Ghost button hover | Animation
|
## Goal
We would like to iterate on our animation/transitions for our secondary buttons
[Figma link](https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT/%5BEXT%5D-2294---Design?node-id=2233%3A26206)
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* All
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Secondary button hover animation
## Out of scope
What is out of scope and not part of this iteration?
- All other animation/transitions
## 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 | 109,518,654 |
2022-06-02 16:13:50.893
|
ENG: Update old fall back logo | Technology Partners
|
## Goal
We would like to update the fallback old tanuki logo from the Technology Partners page
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Alliance Partners](https://about.gitlab.com/partners/technology-partners/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter
- [ ] Informed: '@mlebeau'
## In scope
What is within scope of this request?
- [ ] Update fallback logo
## Out of scope
What is out of scope and not part of this iteration?
- Any other dev work on this 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
| 2 |
28,847,821 | 109,471,822 |
2022-06-01 22:58:11.088
|
Add The Last Mile Video to SMB Page
|
## Goal
We would like to post The Last Mile video which will improve the value of the SMB page as measured by views and time on page.
### Jobs To Be Done
* **Situation**: *When a customer arrives on the SMB marketing page*
* **Motivation**: *We want to display The Last Mile video in an engaging way*
* **Outcome**: *So we can motivate customers to watch it and take the next step into the funnel*
## Page(s)
Which page(s) are involved in this request?
* `GitLab for Small Businesses(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: `brianglanz`
- [ ] Consulted: `cblake`
- [ ] Informed: `kbolton1`
## In scope
What is within scope of this request?
- [ ] Incorporate The Last Mile video (https://drive.google.com/drive/folders/1vQY3gHc5jg8b6Jt8h9YqfIMz9zkGev4n?usp=sharing) onto the existing https://about.gitlab.com/small-business/ page.
- [ ] Include copy (to come)
- [ ] Track performance
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ X] Copy writing
- [X ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ X] UX Design
- [X ] Engineering
| 1 |
28,847,821 | 109,469,621 |
2022-06-01 21:50:47.152
|
Remove What is Gitlab and redirect to Why GitLab
|
## Goal
We would like to remove [/what-is-gitlab/](https://about.gitlab.com/what-is-gitlab/) and redirect that url to [/why-gitlab/](https://about.gitlab.com/why-gitlab/).
This page was listed to redirect in the following issues:
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/950
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/354
### Jobs To Be Done
* **Situation**: *When a user hits the `/what-is-gitlab` URL they are redirected to` /why-gitlab`.*
* **Motivation**: *We want to remove duplicative content.*
* **Outcome**: *So we can reduce the number of page in the marketing site.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/what-is-gitlab/
* https://about.gitlab.com/why-gitlab/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove https://about.gitlab.com/what-is-gitlab/
- [ ] Update all internal links to that page to https://about.gitlab.com/why-gitlab/
- [ ] Set redirect in www-gitlab-com repository
## 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 | 109,469,455 |
2022-06-01 21:44:33.415
|
Delete 9 pages with > .005 page views
|
## Goal
We would like to delete 10 pages with > .005% page view ratio. This data was sourced as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/950).
### Jobs To Be Done
* **Situation**: *These pages have > .005% of the page views.*
* **Motivation**: *We want to continue the depreciation of unused marketing webpage.*
* **Outcome**: *So we can reduce the # of pages in the marketing site.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/2020-devsecops-survey/new/
* https://about.gitlab.com/DIY-DevOps/
* ~~https://about.gitlab.com/cloud-native/~~ Keep. [Related thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/950#note_970907596).
* https://about.gitlab.com/competition/
* https://about.gitlab.com/corporate-philanthropy/
* https://about.gitlab.com/customer-care/
* https://about.gitlab.com/demo-leader/
* https://about.gitlab.com/en-test/
* https://about.gitlab.com/githost/
* https://about.gitlab.com/speakers/
* https://about.gitlab.com/wip/
## 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?
- [ ] Remove these pages from the www-gitlab-com repository
## 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 | 109,468,870 |
2022-06-01 21:25:13.332
|
Create plan for moving blog out of www-gitlab-com
|
## Goal
We would like to create a plan moving the blog out of the `www-gitlab-com` repository.
### Jobs To Be Done
* **Situation**: *When team member creates a blog post it is a efficient process the enables effective content creation for the marketing site.*
* **Motivation**: *We want to improve deployment times, conversion rates, and drive traffic to our key pages from our blog posts.*
* **Outcome**: *So we can help drive the growth of GitLab.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/blog/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @vsilverthorne @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Collaborate with GitLab team to create actionable plan to move the blog from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
- Any engineering work. This issue is for discussion, planning, and feedback.
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [x] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 109,468,582 |
2022-06-01 21:12:13.794
|
ENG: Migrate Events landing page to Buyer Experience
|
## Goal
We would like to migrate the https://about.gitlab.com/events/ to the Buyer Experience repository.
### Jobs To Be Done
* **Situation**: *Events listed on the https://about.gitlab.com/events/ are managed in the Buyer Experience repository, and the landing page is built with Nuxt*
* **Motivation**: *We want to centralize the marketing site in the Buyer Experience repository.*
* **Outcome**: *So we can be efficient*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/events/
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/events.yml
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/events/index.html.haml
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @lduggan
- [ ] Consulted: @laurenbarker
- [ ] Informed: @nataliepicci @Helenadixon @krogel @amandawshen @ttran5
## In scope
What is within scope of this request?
- [ ] Migrate the Events page to the Buyer Experience repository
- [ ] Apply "fresh coat of paint" to the template to match our new branding
- [ ] Remove existing events template and `events.yml` from the www-gitlab-com repository
- [ ] Update [handbook](https://about.gitlab.com/handbook/marketing/events/#how-to-add-events-to-aboutgitlabcomevents) with documentation on how to add events to the marketing site
## Out of scope
What is out of scope and not part of this iteration?
- A new template designed by UX ( they will help review and provide feedback in the MR )
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 5 |
28,847,821 | 109,463,547 |
2022-06-01 18:56:47.862
|
DISCOVERY: side navs/table of anchor links + a11y
|
The screen reader experience of navigating and using the side nav to auto-scroll to different sections on the page seems a little clunky. I'm not sure what is expected for this kind of element on the page, so I'd like to do some research and see how other a11y-minded developers approach functionality like this.
This side nav is used on a number of pages, including [Install](https://about.gitlab.com/install/).
| 2 |
28,847,821 | 109,459,904 |
2022-06-01 17:20:07.008
|
Remove child topic pages - DevOps
|
## Goal
We would like to remove the following child topics pages:
- https://about.gitlab.com/devops/build-a-devops-team/
- https://about.gitlab.com/devops/how-and-why-to-create-devops-platform-team/
- https://about.gitlab.com/devops/reduce-devops-costs/
- https://about.gitlab.com/devops/seven-tips-to-get-the-most-out-of-your-devops-platform/
- https://about.gitlab.com/devops/use-devops-platform-to-avoid-devops-tax/
- https://about.gitlab.com/devops/what-is-a-devops-platform-engineer/
All these URls redirect to the parent topic page at https://about.gitlab.com/devops/. Therefor, I think we can remove the data files for those child topic page that exist here:
https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/data/topic_children
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Removing the data files from the www-gitlab-com repository
## 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
| 1 |
28,847,821 | 109,452,177 |
2022-06-01 14:42:59.979
|
ENG: Get Started for Small Business
|
## Goal
We would like to build a single template for our Get Started pages which will give users quick tutorials on how to get started using GitLab.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/get-started/SMB
* All Get Started pages will use the same template
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @ctsang-ext @cblake
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Build template
- [ ] Apply template to parent and child pages
- [ ] Depreciate pages with duplicate content and set redirects
- [ ] Create video that walks through the `yml` file structure
## Design
- [Figma file](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=368%3A3068)
## Content
- [Get Started Google Doc](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/947)
## Out of scope
What is out of scope and not part of this iteration?
- Side anchor nav is being addressed in this issue https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 8 |
28,847,821 | 109,407,606 |
2022-05-31 20:51:13.825
|
ENG: Category leadership (Topics) - Build Template
|
## Goal
We would like to build a single template for our Category Leadership (Topic) pages which will improve the hierarchy of information as measured by increased search ranking.
## Page(s)
Which page(s) are involved in this request?
* [topics/devops/](https://about.gitlab.com/topics/devops/)
* All topic pages including child pages will use the same template
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpenagos-ext
- [ ] Consulted: @Tinaliseng @ncregan @hsmith-watson @dennischarukulvanich
- [ ] Informed: @fqureshi @justin.vetter
## In scope
What is within scope of this request?
- [ ] Build template using [topics/devops/](https://about.gitlab.com/topics/devops/) as a first use-case.
- [ ] Apply template to parent and child pages
- [ ] The components need to be rendered dynamically instead of statically for this template.
## Design
- [Figma file](https://www.figma.com/file/QVyiaPnW9F5h50yZ9YCliQ/Category-Leadership-refresh?node-id=0%3A1)
## Out of scope
What is out of scope and not part of this iteration?
- Side anchor nav is being addressed in this issue https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148
- Full mobile designs in Figma. Only some elements have mobile designs. We will address breakpoints on a case-by-case basis.
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 10 |
28,847,821 | 109,161,817 |
2022-05-26 13:34:26.181
|
UX: Main Get Started Page (Navigate Tutorials)
|
## Goal
We would like to improve the main Get Started page so that it will help customers navigate tutorials and improve customer onboarding as measured by decreased support inquiries.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand how to begin setting up their GitLab account or other services...*
* **Outcome**: *so they can get started right away and without interruption.*
## Page(s)
Which page(s) are involved in this request?
* [Current page](https://about.gitlab.com/get-started/)
* [New Design (Figma)](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=689%3A7331)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @jhalloran @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 5 |
28,847,821 | 109,051,442 |
2022-05-24 16:49:40.915
|
Open source program pages aren't easily accessible
|
## Goal
The [GitLab for Open Source page](https://about.gitlab.com/solutions/open-source/) isn't easily accessible from the GitLab home page. It does not appear with other community programs, such as the Education program, in `Solutions > Industry`, nor does it appear in the page footer.
We would like to increase visibility of the GitLab for Open Source program pages in light of upcoming changes to the free user tier. This will help us improve discoverability and increase applications to the program from projects impacted by the changes.
### Jobs To Be Done
* **Situation**: When a user visits `gitlab.com`, they cannot easily navigate to the GitLab for Open Source solutions page
* **Motivation**: We want to enhance navigability and assist users seeking information about this program
* **Outcome**: Better assist users seeking to apply for the program in light of upcoming changes to GitLab's free tier.
## Page(s)
* `https://about.gitlab.com/solutions/open-source/`
## DCI
- [ ] DRI: `@bbehr`
- [ ] Consulted: `@c_hupy`
- [ ] Informed: `Everyone`
## In scope
- [ ] An easily accessible link to the program page from the same location(s) other community programs appear
## Out of scope
- Changes to pages contents
## Requirements
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [x] Engineering
| 2 |
28,847,821 | 108,892,487 |
2022-05-20 20:30:01.813
|
Create Slippers Card Component
|
## Goal
Update card component in Slippers to use the four card variants in [Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=1305%3A182).
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: @jhalloran
- [x] Consulted: @ndubord
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 8 |
28,847,821 | 108,837,129 |
2022-05-19 21:35:45.236
|
Migrate all SlpColumn components
|
## Goal
Remove the SlpColumn component from the Buyer Experience repository and use the SlpColumn import from Slippers instead.
| 3 |
28,847,821 | 108,837,119 |
2022-05-19 21:34:47.865
|
Migrate all SlpRow components
|
## Goal
Remove the SlpRow component from the Buyer Experience repository and use the SlpRow import from Slippers instead.
| 3 |
28,847,821 | 108,837,081 |
2022-05-19 21:34:02.199
|
Migrate all SlpContainer components
|
## Goal
Remove the SlpContainer component from the Buyer Experience repository and use the SlpContainer import from Slippers instead.
| 5 |
28,847,821 | 108,836,726 |
2022-05-19 21:20:10.814
|
GA4: gtag learn.gitlab.com
|
## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.
Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US
Place the default `gtag` script *before* the Google Tag Manager and OneTrust scripts across all **learn.gitlab.com** pages.
Gtag script logic: By default, deny cookie storage for users from the EU, UK, Peru, and Russia; grant cookie storage for all other geolocation. Later on, Google Consent Mode will be enabled on OneTrust, which will dynamically update the values to "denied" or "granted" based on the user's preference.
```
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'analytics_storage': 'granted',
'ad_storage': 'granted',
'functionality_storage': 'granted',
'wait_for_update': 500
});
gtag('consent', 'default', {
'analytics_storage': 'denied',
'ad_storage': 'denied',
'functionality_storage': 'denied',
'region': ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'IS', 'LI', 'NO', 'GB', 'PE', 'RU'],
'wait_for_update': 500
});
</script>
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXX');</script>
<!-- End Google Tag Manager -->
<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js" type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```
## Page(s)
Which page(s) are involved in this request?
* All learn.gitlab.com pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker @justin.vetter
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: @mpreuss22
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 108,836,712 |
2022-05-19 21:19:26.578
|
GA4: gtag gitlab.com
|
## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.
Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US
Place the default `gtag` script *before* the Google Tag Manager and OneTrust scripts across **gitlab.com** pages. See list of page below, as not all pages on this subdomain is tracked.
Gtag script logic: By default, deny cookie storage for users from the EU, UK, Peru, and Russia; grant cookie storage for all other geolocation. Later on, Google Consent Mode will be enabled on OneTrust, which will dynamically update the values to "denied" or "granted" based on the user's preference.
```
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'analytics_storage': 'granted',
'ad_storage': 'granted',
'functionality_storage': 'granted',
'wait_for_update': 500
});
gtag('consent', 'default', {
'analytics_storage': 'denied',
'ad_storage': 'denied',
'functionality_storage': 'denied',
'region': ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'IS', 'LI', 'NO', 'GB', 'PE', 'RU'],
'wait_for_update': 500
});
</script>
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NJXWQL');</script>
<!-- End Google Tag Manager -->
<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js" type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```
## Page(s)
Which page(s) are involved in this request?
- **gitlab.com/users/sign_in** (Please add the GTM Snippet. This is the only page missing GTM.)
- gitlab.com/-/profile/usage_quotas
- gitlab.com/-/subscriptions/buy_minutes
- gitlab.com/-/subscriptions/new
- gitlab.com/-/trial_registrations
- gitlab.com/-/trial_registrations/new
- gitlab.com/-/trials/apply
- gitlab.com/-/trials/create_lead
- gitlab.com/-/trials/new
- gitlab.com/-/trials/select
- gitlab.com/-/users/terms
- gitlab.com/groups/ForgottenDream/-/usage_quotas
- gitlab.com/users
- gitlab.com/users/almost_there
- gitlab.com/users/sign_up
- gitlab.com/users/sign_up/groups_projects
- gitlab.com/users/sign_up/groups_projects/import
- gitlab.com/users/sign_up/groups_projects/new
- gitlab.com/users/sign_up/groups/new
- gitlab.com/users/sign_up/welcome
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker @justin.vetter
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: @mpreuss22
- [ ] [MR](https://gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/2646)
## 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
| 1 |
28,847,821 | 108,836,706 |
2022-05-19 21:19:09.678
|
GA4: gtag about.gitlab.com
|
## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.
Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US
Place the default `gtag` script *before* the Google Tag Manager and OneTrust scripts across all **about.gitlab.com** pages.
Gtag script logic: By default, deny cookie storage for users from the EU, UK, Peru, and Russia; grant cookie storage for all other geolocation. Later on, Google Consent Mode will be enabled on OneTrust, which will dynamically update the values to "denied" or "granted" based on the user's preference.
```
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'analytics_storage': 'granted',
'ad_storage': 'granted',
'functionality_storage': 'granted',
'wait_for_update': 500
});
gtag('consent', 'default', {
'analytics_storage': 'denied',
'ad_storage': 'denied',
'functionality_storage': 'denied',
'region': ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'IS', 'LI', 'NO', 'GB', 'PE', 'RU'],
'wait_for_update': 500
});
</script>
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXX');</script>
<!-- End Google Tag Manager -->
<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js" type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```
## Page(s)
Which page(s) are involved in this request?
* All about.gitlab.com pages
* @dennischarukulvanich to verify that GA4 is running properly on about.gitlab.com
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker @justin.vetter
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: @mpreuss22
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 108,836,701 |
2022-05-19 21:18:54.103
|
GA4: gtag docs.gitlab.com
|
## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.
Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US
Place the default `gtag` script *before* the Google Tag Manager and OneTrust scripts across **docs.gitlab.com** pages.
Gtag script logic: By default, deny cookie storage for users from the EU, UK, Peru, and Russia; grant cookie storage for all other geolocation. Later on, Google Consent Mode will be enabled on OneTrust, which will dynamically update the values to "denied" or "granted" based on the user's preference.
```
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'analytics_storage': 'granted',
'ad_storage': 'granted',
'functionality_storage': 'granted',
'wait_for_update': 500
});
gtag('consent', 'default', {
'analytics_storage': 'denied',
'ad_storage': 'denied',
'functionality_storage': 'denied',
'region': ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'IS', 'LI', 'NO', 'GB', 'PE', 'RU'],
'wait_for_update': 500
});
</script>
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NJXWQL');</script>
<!-- End Google Tag Manager -->
<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js" type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```
## Page(s)
Which page(s) are involved in this request?
- all docs.gitlab.com pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker @justin.vetter
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: @mpreuss22
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 108,773,506 |
2022-05-18 21:52:53.119
|
ENG: Implement Slipper Icons in BE
|
## Goal
We would like to remove all icons from the Buyer Experience repository and use the slipper icon component added as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/42).
### Jobs To Be Done
* **Situation**: *When we use an icon in the Buyer Experience repository we are using a Slippers UI component and not added the icon svg/png/image directly to the project*
* **Motivation**: *We want to improve the performance of our code*
* **Outcome**: *So we can be consistent with our icons across the marketing site*
## Page(s)
Which page(s) are involved in this request?
* All pages built by the Buyer Experience repository
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jariasc-ext
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Pulling in a new Slippers package to the Buyer Experience project
- [ ] Updating all instances of an icon to a Slippers vue component
- [ ] QA every component that includes the new vue icon component
- [ ] QA every page that includes these components
## Out of scope
What is out of scope and not part of this iteration?
- www-gitlab-com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 108,763,350 |
2022-05-18 17:27:49.984
|
Customize Swiftype css to be on brand
|
## Goal
We would like to iterate on custom css to style our Swifttype search bar and results to be on brand.
### Jobs To Be Done
* **Situation**: *When the search bar is used, the colors and fonts are on brand*
* **Motivation**: *We want to be consistent with our branding on the marketing site*
* **Outcome**: *So we can increase engagement*
## 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)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Customize the css https://swiftype.com/documentation/site-search/tutorials/custom_styles#custom_css
- [x] Implement on the Buyer Experience repository
- [ ] Implement on the www-gitlab-com repository
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 3 |
28,847,821 | 108,750,930 |
2022-05-18 14:23:02.053
|
/customers/ change filter to ALL
|
## Goal
Change filters on the /customers/ page to AND instead of ANY.
## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @Tinaliseng
- [ ] Informed: @FionaOKeeffe
## In scope
What is within scope of this request?
- [ ] Change filters to work as follows: Company size and Industry and Region
## 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:
- [ ] Engineering
| 2 |
28,847,821 | 108,691,708 |
2022-05-17 15:27:35.862
|
Accessibility Updates: Pricing Page Modal
|
## Goal
The 'buy now modal 'Get started/Buy GitLab Premium/Buy GitLab Ultimate' modal is currently not accessible.
There is no way to use a keyboard to focus or navigate on the modal once it's opened. A screenreader will not prompt the user that the modal is opened / closed.
The modal close/exit button should have appropriate labels that will allow a screenreader to tell the user that the modal will closed once the button is clicked.
## Page(s)
Which page(s) are involved in this request?
* `[Pricing](https://about.gitlab.com/pricing/)`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Engineering
| 2 |
28,847,821 | 108,772,188 |
2022-05-17 07:24:30.028
|
Updating Resource page banner report
|
The current banner highlighted report on https://about.gitlab.com/resources/ is the DevSecOps 2020 report ( Screenshot below).
Since this is a 2 year old report, and we have a more recent version, can we swap this out for the [2021 DSO survey results](https://about.gitlab.com/developer-survey/)?
@cblake has confirmed [here](https://gitlab.com/gitlab-com/marketing/demand-generation/campaigns/-/issues/2371#note_948126826) that we should consider this swap if there are no other concerns.
<!-- Please leave the label below on this issue -->
| 1 |
28,847,821 | 108,624,358 |
2022-05-16 15:34:33.860
|
Horizontal spacing, Blog
|
## Goal
Page: https://about.gitlab.com/blog/2022/04/18/gitlab-releases-15-breaking-changes/
The blog post above has extra horizontal whitespace, have confirmed in both Firefox and Chrome.
Slack thread: https://gitlab.slack.com/archives/C261VMGCX/p1652412685592939
| 1 |
28,847,821 | 108,531,734 |
2022-05-13 19:56:54.123
|
ENG: Swiftype API Consumption
|
## Goal
We would like to consume the Swiftype API in our search experience.
This will enable us to create the search experience designed here: [Figma Design](https://www.figma.com/file/ndNo84yjW3SbTuXPuwjJQ3/Search?node-id=137%3A1387)
### Jobs To Be Done
* **Situation**: *We enable the Navigation repository to consume the Swiftype API*
* **Motivation**: *We want to build custom search experience*
* **Outcome**: *So we can increase engagement.*
## Page(s)
Which page(s) are involved in this request?
* Navigation repository
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jariasc-ext
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Enable the Swiftype API in the Navigation repository
## 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 | 108,518,674 |
2022-05-13 15:32:48.307
|
Follow up from Pricing Page Screen Reader Testing - Engineering updates
|
Fix critical items within the Pricing page that failed criteria on this sheet: https://docs.google.com/spreadsheets/d/1GrfrpWAf39NOt2GMxYwKnE8_JnAaxK9G7dE2ha98eo8/edit#gid=0
**Scope:**
- Tooltips
- Table
- Addons
- FAQ Accordion
| 2 |
28,847,821 | 108,512,888 |
2022-05-13 13:59:25.556
|
Pricing Page - Screen Reader Testing
|
Review the Pricing page with the [WCAG A/AA guideline sheet](https://docs.google.com/spreadsheets/d/1GrfrpWAf39NOt2GMxYwKnE8_JnAaxK9G7dE2ha98eo8/edit#gid=0) and test with a screen reader.
Create issues, if necessary, for any remaining failed criterion.
| 1 |
28,847,821 | 108,461,491 |
2022-05-12 16:38:59.046
|
ENG: Remove quote section from customers page
|
## Goal
We would like to remove the quote section from the customers page as the content is repetitive.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpenagos-ext
- [ ] Consulted: @justin.vetter
- [ ] Informed: @FionaOKeeffe
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 108,460,962 |
2022-05-12 16:27:31.289
|
ENG: Fix Leding/spacing in Customers hero
|
## Goal
On the Customers page in the hero when you click on "Drupal Association" the spacing for the stats is not right.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: Fix the spacing
## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mmanunga-ext
- [ ] Consulted: @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 108,332,268 |
2022-05-10 20:36:03.912
|
Record process of signing up for a Free Trial from pricing page
|
## Goal
We would like to create a screen recording of the process required to sign up for a Free Trial of GitLab.
### Jobs To Be Done
* **Situation**: *When a user clicks on any free trial button on the marketing site.*
* **Motivation**: *We want to have a screen recording of the entire process to complete that action.*
* **Outcome**: *So we can verify what the process is and potential improvements.*
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com -> free trial button
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: @gherrera-ext
- [x] Consulted: @laurenbarker
- [x] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Upload this screen recording to our [GitLab Unfiltered channel](https://about.gitlab.com/handbook/marketing/marketing-operations/youtube/#uploading-conversations-to-youtube). There's a direct link to the YouTube upload page in #6. Or send video to @laurenbarker
- [x] Post a link to this video in our #digital-experience-team slack channel
- [x] Post a link to this video in this issue
## 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
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 108,327,043 |
2022-05-10 18:21:29.451
|
Remove webcasts page and move events page in the navigation
|
## Goal
We would like to remove the [Webcasts](https://about.gitlab.com/webcast/) page and replace "Webcasts" in the `Learn` navigation with [Events](https://about.gitlab.com/events/) which is currently listed under `People`.
We stopped updating the webcasts page months ago in favor of keeping the events page up to date with both webcasts and live events.
### Jobs To Be Done
* **Situation**: *When ...* a person is looking for live or virtual events
* **Motivation**: *We want to ...* have a single location to view all upcoming events
* **Outcome**: *So we can ...* make it easier for a person to find what they are looking for.
## Page(s)
Which page(s) are involved in this request?
* [Webcasts](https://about.gitlab.com/webcast/)
* [Events](https://about.gitlab.com/events/)
Updated navigation - Remove webcasts, replace with Events
Remove events from the `People` section
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: `@jgragnola`
- [x] Consulted: `@lblanchard`
- [x] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove Webcasts page from the navigation of `Learn` section
- [ ] Move Events page from the `People` section of the navigation to the `Learn` section
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 108,258,731 |
2022-05-09 16:53:19.556
|
DISCOVERY: Improving the 404 experience for about.gitlab.com
|
## Goal
We would like to increase engagement on about.gitlab.com by improving the 404 page.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/404/
### Jobs To Be Done
* **Situation**: *When want to gather input from our team members on what they think a great 404 page experience is for about.gitlab.com*
* **Motivation**: *We want to be transparent and collaborate on the new 404 experience for about.gitlab.com*
* **Outcome**: *So we can live our GitLab CREDIT values and increase engagement on the marketing site.*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted:`@mpreuss22`
- [ ] Informed: `Everyone`
| 2 |
28,847,821 | 108,258,724 |
2022-05-09 16:53:00.823
|
DISCOVERY: Improving the search experience for about.gitlab.com
|
## Goal
We would like to improve the search experience of the marketing website.
### Jobs To Be Done
* **Situation**: *When a using our search experience on about.gitlab.com, the user finds what they are looking for OR something related and helpful to their search.*
* **Motivation**: *We want to lower the bounce rate, increase pages viewed per session, and increase time on site.*
* **Outcome**: *So we can increase engagement.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/search/
* Search bar in primary navigation
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: `@mpreuss22 `
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Gather feedback from team on good search experiences
- [ ] Update handbook documentation with our current search tool and architecture
## 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
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 108,257,259 |
2022-05-09 16:06:40.854
|
GitLab Team page still uses old Tanuki logo
|
This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/
This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.
#### What is/are the relevant URL(s)
https://about.gitlab.com/company/team/
#### Briefly describe the bug
The old GitLab Tanuki is still used in the following locations on the above page:
1. As a placeholder for team members who have not added a photo
2. As a link to our `GitLab.com/<profile>`
#### If possible, please specify how to reproduce the bug
Issue should be visible to any visitor of the page.
#### Please provide any relevant screenshots or screencasts
How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/
[Screen_Shot_2022-05-09_at_11.58.40_AM](/uploads/473eac7de79fea5d1f431a4095d8f464/Screen_Shot_2022-05-09_at_11.58.40_AM.png)
#### What is your window size, browser, operating system, and versions
Please use the following website to determine your browser specifications and provide a link developers can follow:
What is my browser https://www.whatsmybrowser.org
https://www.whatsmybrowser.org/b/HI3BS
#### What computing device are you using?
Please list the brand and model (Example: Samsung Galaxy S 10 Plus)
MacBook Pro 16-inch 2021
### What type of input are you attempting to use?
Webpage interactivity is often tied to a specific device event.
- [ ] Touchscreen
- [x] Touchpad
- [ ] Mouse click
- [ ] Mouse click and drag
- [ ] Scrollwheel
- [ ] Keyboard
- [ ] Stylus
- [ ] Other (please specify)
#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?
- [x] I tried a fresh incognito window & it had no impact.
- [ ] The problem goes away when using an incognito window.
- [ ] The problem only happens when certain cookies are set to a specific value (please specify below).
#### Please list any browser plugins you have enabled
Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing.
* uBlock Origin
* I don't care about cookies (*that's the actual name of the plugin*)
#### Are you blocking javascript or any other resources?
Javascript is needed for certain website functionality.
- [ ] I AM blocking javascript or other resources.
- [x] I am NOT blocking javascript or other resources.
#### What is your geographic location
Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies.
United States
#### What type of network are you connected to?
**Type**
- [ ] Wired
- [x] Wifi
- [ ] Cellular (4G, 5G, etc)
- [ ] Satellite
- [ ] Other
`Insert details here if applicable`
**Location**
- [x] Home
- [ ] Workplace
- [ ] Travel facility (hotel, airport, conference center, etc)
- [ ] Public venue (restaurant, library, cafe, etc)
- [ ] VPN
- [ ] Other
`Insert details here if applicable`
**Hardware**
- [ ] I am behind a network security appliance such as a firewall
- [x] I am using a pi-hole or other hardware-based traffic blocker
- [ ] Other
`Insert details here if applicable`
<!-- Please do not remove the items below, they are needed to automatically notify the relevant entities -->
/cc @gl-website
<!-- These labels will be automatically applied unless you edit or delete the following section -->
| 1 |
28,847,821 | 108,247,023 |
2022-05-09 13:56:34.655
|
Home Page - Post-accessibilty audit fixes
|
## Page(s)
Which page(s) are involved in this request?
* [Home page](https://about.gitlab.com/)
## In scope
What is within scope of this request?
Home page html/component updates that will remedy failed tests for the following WCAG success criteria:
1. Info and Relationships
2. Meaningful Sequence
3. Keyboard
4. Link Purpose
5. Consistent Identification
6. Name, Role, Value
See these documents for more details:
1. [Spreadsheet](https://docs.google.com/spreadsheets/d/1pCfGv8xHjY39Oeft37pGjgot_lg0_j3cSyty0H9njv8/edit#gid=0)
2. [Google Doc](https://docs.google.com/document/d/1PtJ0areq87xkXmr5odb45Xk56l3hfycpkxbsz5GiPnY/edit) with more information on some component updates
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 108,115,840 |
2022-05-05 23:03:51.988
|
Record the process of signing up for a Free Trial of GitLab
|
## Goal
We would like to create a screen recording of the process required to sign up for a Free Trial of GitLab.
### Jobs To Be Done
* **Situation**: *When a user clicks on any free trial button on the marketing site.*
* **Motivation**: *We want to have a screen recording of the entire process to complete that action.*
* **Outcome**: *So we can verify what the process is and potential improvements.*
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com -> free trial button
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @miraclebanks
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Upload this screen recording to our [GitLab Unfiltered channel](https://about.gitlab.com/handbook/marketing/marketing-operations/youtube/#uploading-conversations-to-youtube). There's a direct link to the YouTube upload page in #6.
- [x] Post a link to this video in our #digital-experience-team slack channel
- [x] Post a link to this video in this issue
## 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
- [ ] UX Design
- [x] Engineering
| 2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.