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 | 120,488,211 |
2022-12-15 16:39:40.919
|
Create blogpost vue template in new blog repository
|
## Goal
We would like to create a bare bones blog post template that we can iterate from and apply our design system to. This template should be applied to the few dummy blog posts that exist in our new repository and be displayed on localhost.
## In scope
What is within scope of this request?
- [ ] Create blog post template file
- [ ] Have this template applied to a blog post ( can be loriom ipsum ) that exists in the repository
| 2 |
28,847,821 | 120,488,172 |
2022-12-15 16:38:51.694
|
Create new blog repository
|
## Goal
We would like to create a new project in the Digital Experience group for The Blog.
https://gitlab.com/gitlab-com/marketing/digital-experience
#### Jobs To Be Done
* **Situation**: *When user navigates to our subgroup, there is a project for The Blog.*
* **Motivation**: *We want to create a blank repository the the team the collaborate on*
* **Outcome**: *So we can have team members contribute*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @lduggan
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create blank project in Digital Experience group
- [ ] Ensure DEX team members have access to project (let's use same user levels as Buyer Experience)
- [ ] 1st iteration of [project settings ](https://docs.gitlab.com/ee/user/project/settings/)
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 120,488,145 |
2022-12-15 16:38:11.433
|
Investigate using Nuxt as a tool for blog repository
|
## Goal
We would like to gather documentation and resources for using Nuxt for a blog.
#### Jobs To Be Done
* **Situation**: *We wan't to gather links to docs, blog articles, and example projects for using Nuxt to generate a blog.*
* **Motivation**: *We want to make sure Nuxt can be used for a blog and have resources ready for our engineers to look at.*
---- List of Resources ----
1.
| 2 |
28,847,821 | 117,190,381 |
2022-10-19 16:59:46.479
|
Remove Slippers source code from navigation
|
## Goal
If you look at our /dist html files the navigation includes the full Slippers package, not minified. It's affecting our page load times and our dom size.
We'll need to fix this for www-gitlab-com navigation as well (if it's an issue)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: Affects page load times, SEO scores
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes @mpreuss22
- [ ] No
**How do we measure success?**
- Smaller DOM size
## Page(s)
Which page(s) are involved in this request?
* All Buyer Experience pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @laurenbarker @justin.vetter
- [ ] Informed: Everyone, post update to BE slack channel.
## 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 | 117,189,496 |
2022-10-19 16:40:07.516
|
ENG: Pricing/licensing-faq Refresh
|
## Goal
The /licensing-faq page is a feeder page into the /pricing/ page and currently looks like a handbook page. There is an opportunity to improve this page to be more conversion-focused. We would like to redesign /pricing/licensing-faq/ which will improve user experience.
### Notes
There is currently no slippers component for the accordion. We would like to have this page updated using a BE accordion component now and we will iterate to the slippers component in Q4
#### Jobs To Be Done
* **Situation**: *When users land on the licensing page*
* **Motivation**: *We want to provide them the information they are looking for*
* **Outcome**: *So we can eventually lead them to a free trial *
## Workin Files
- [ ] [Figma design](https://www.figma.com/file/I1RYrS4BtJEvS1rpRJvgBa/Licensing-FAQ-MVC1?node-id=53%3A5419)
**If this is urgent, what is the business need for the urgency?**
- [X] Yes: There is a gap to plan in free trial conversions.
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- Initial MVC for the licensing page that aligns to the new redesign
**How do we measure success?**
- Increased session duration
- Increased clicks to free trial
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No
## Page(s)
Which page(s) are involved in this request?
* `[Licensing Page](https://about.gitlab.com/pricing/licensing-faq/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @fqureshi
- [ ] Consulted: @jhalloran @justin.vetter @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Refresh Licensing FAQ page in BE
- [ ] Remove old page from www
## Not in scope
- [ ]
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 117,113,325 |
2022-10-18 14:51:55.678
|
ENG: Update to CE v. EE install page
|
## Goal
We would like to update the UX for the CE v EE install page
#### Jobs To Be Done
* **Situation**: *When a user goes needs to make a decision between the community or enterprise edition of GitLab...*
* **Motivation**: *We want to guide them to the best option for their needs...*
* **Outcome**: *So we can provide them the best result for their business.*
## Working Files
- [ ] [Figma designs](https://www.figma.com/file/SbTRvhGGPqSVJzuYTPf500/CE-v-EE-MVC3?node-id=17%3A1030)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to deploy updated page`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [x] Yes: `Reach out to Dennis regarding what analytics to add to button clicks`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* [CE v EE](https://about.gitlab.com/install/ce-or-ee/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @takamine-ext
- [ ] Consulted: @fqureshi @jhalloran @justin.vetter `@dennischarukulvanich`
- [ ] 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
| 4 |
28,847,821 | 117,112,816 |
2022-10-18 14:45:27.508
|
/learn page chevron's are not aligned
|
## Goal
Center the chevrons
| 1 |
28,847,821 | 116,921,413 |
2022-10-14 22:33:27.104
|
ENG: Left side anchor nav / colour change to the hover state
|
## Goal
We would like to add a colour change to the hover state to our left-side anchor nav (used on /solution pages) which will improve engagement.
See [prototype](https://www.figma.com/proto/2Mp2QTbudj3q9q8zN0z9h7/hover-test?page-id=0%3A1&node-id=1%3A986&viewport=768%2C840%2C0.17&scaling=min-zoom)
## Page(s)
Which page(s) are involved in this request?
* All instances
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng
- [ ] Informed: @justin.vetter
## In scope
What is within scope of this request?
- [ ] Add a hover state: colour change = `$slp/color/text/300` `#171321`
## 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 | 116,920,406 |
2022-10-14 21:37:08.823
|
[ENG] Homepage | Remove Launch Darkly code from hero
|
## Goal
We would like to remove the LaunchDarkly code around the hero and deploy the variant hero subcopy
#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal is to remove LaunchDarkly code from hero in preparation for next AB test`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `[Homepage](https://about.gitlab.com)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @justin.vetter @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove LD code
- [ ] Deploy Variant subcopy
## 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 | 116,913,230 |
2022-10-14 18:03:17.814
|
UX: Security & Compliance Lightning strike: Compliance page - refresh
|
## Goal
We would like to update the [Compliance](https://about.gitlab.com/solutions/compliance/) landing page to support the [Security & Compliance lightning strike](https://gitlab.com/groups/gitlab-com/marketing/-/epics/3271).
### Project notes
See https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/6521#web-page-updates-chandler-saumya-jennifer
## Workfiles
- [Compliance content doc](https://docs.google.com/document/d/1G9N6ZjbTiZPNBwYji0ZPi821bfTOmML176tcEydwhr8/edit?usp=sharing)
- [Figma file](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=344%3A8535)
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/compliance/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @supadhyaya @chandlergibb
- [ ] Informed: @justin.vetter @fqureshi
## In scope
What is within scope of this request?
- [ ] Figma mock @Tinaliseng
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 116,912,279 |
2022-10-14 17:34:49.135
|
ENG: Topic page template / Related content tab UI update
|
### Describe the Bug
Tabs titles are too close to the active state underline
<details><summary>Current</summary>
</details>
Todo:
1. 16px of space between the copy and the underline
2. Reduce active underline to 24px on each side.
## Page(s)
Which page(s) are involved in this request?
* All instances on /topics
* Example: https://about.gitlab.com/topics/devops/
## 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 | 116,859,157 |
2022-10-13 21:47:34.715
|
Navigation: Change "Customer Case Studies" to "Customer Success Stories"
|
## Goal
We would like to Change "Customer Case Studies" to "Customer Success Stories" in the main navigation which will improve traffic to this section of the site as measured by CTA clicks and visits to the page.
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes `@dsteer`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
## Page(s)
Which page(s) are involved in this request?
* `Main Navigation`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@mpreuss22`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Change "Customer Case Studies" to "Customer Success Stories"
## 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 | 116,858,984 |
2022-10-13 21:40:56.291
|
Remove DevOps Stages section from homepage
|
## Goal
We would like to remove the DevOps Stages section of the homepage which will improve our product marketing messaging as measured by homepage engagement metrics.
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes `@dsteer`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `[Homepage](https://about.gitlab.com)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@mpreuss22`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove this section of the homepage
- [ ] 
## 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 | 116,839,588 |
2022-10-13 15:03:18.213
|
ENG: Solutions / Software Supply chain security - refresh
|
## Goal
We would like to update the [Software Supply chain security](https://about.gitlab.com/solutions/supply-chain/) landing page to support our [Security & Compliance lightning strike](https://gitlab.com/groups/gitlab-com/marketing/-/epics/3271).
## Workfiles
- [Content doc](https://docs.google.com/document/d/1QpfhcnwhkaZvpjid7mwOpg_fw6l6FXeITF7ATMQEs1g/edit)
- [Figma file](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=157%3A5204)
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/supply-chain/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI:
- [ ] Consulted: @Tinaliseng
- [ ] Informed: @justin.vetter @fqureshi
## In scope
What is within scope of this request?
- [ ] Update the existing [Software Supply Chain Security](https://about.gitlab.com/solutions/supply-chain/) 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
| 3 |
28,847,821 | 116,834,201 |
2022-10-13 13:53:52.076
|
Allow broken link checker to fail
|
## Goal
The job is blocking external contributors from contributing.
| 1 |
28,847,821 | 116,786,364 |
2022-10-12 22:19:20.145
|
ENG: Solutions / Change 'Take GitLab for a Spin' copy
|
## Goal
I would like to iterate on the line `Take GitLab for a Spin` which will improve clicks as measured by metrics.
This section has the lowest engagement on the page ([source](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1375#note_1118351358)) so we would like to test an alternative line of copy. I hypothesize that 'Take GitLab for a Spin' is both too vague and too aggressive. I would like to replace the line with `Try Ultimate for Free` which is a more clear and more succinct call to action.
<details><summary>Current</summary>
</details>
<details><summary>Updated</summary>
</details>
### Technical details
The current <NextStep/> component uses a universal yml file for all of the content across the site. We will need to modify the component to look for data coming from the page yml file and have a fallback to use the current universal yml file.
## Page(s)
Which page(s) are involved in this request?
1. All /solution child pages
1. https://about.gitlab.com/solutions
## In scope
What is within scope of this request?
- [ ] Modify the current <NextStep> component to accept page data with a fall back to use the current universal yml file
- [ ] Replace ~~Take GitLab for a Spin~~ with `Try Ultimate for Free` on /solutions and /solution child pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @dennischarukulvanich
- [ ] Informed: @justin.vetter
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 116,783,949 |
2022-10-12 20:53:27.869
|
[ENG]: Bug Features page | Text breaking out of container
|
### Describe the Bug
There is a visual bug where the text is breaking out of the card container on the features page.
<details><summary>Screen Shot</summary>
</details>
### What's my browser?
Share your browser infromation from https://www.whatsmybrowser.org/
## Page(s)
Which page(s) are involved in this request?
* `[Features](https://about.gitlab.com/features)`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 1 |
28,847,821 | 116,774,307 |
2022-10-12 18:28:43.137
|
[ENG] : Pricing Page | Salient bullet design update
|
## Goal
We would like to revisit how the salient bullet points are displayed as the list for premium and ultimate appear to be the same length.
<details><summary>Screen Shots</summary>
Before salient bullet point change:
After salient bullet point change:
</details>
### _We do not want this to go live until AB tests are complete on the Pricing page_
#### Jobs To Be Done
* **Situation**: When users are reviewing the different plans on the pricing page
* **Motivation**: We want to display how much more a user is getting with the ultimate tier
* **Outcome**: So we can help users differentiate the different tiers
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [X] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [X] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- The ultimate salient bullet points should look longer than the premium
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No
## Page(s)
Which page(s) are involved in this request?
* [Pricing Page](https://about.gitlab.com/pricing/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI:
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] [Figma designs](https://www.figma.com/file/uwtK7pFI6KRHeQBL8Pk8RP/Pricing---tier-updates?node-id=476%3A16571)
## 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 | 116,772,865 |
2022-10-12 17:50:08.839
|
Bug: Incorrect logo on blog post
|
## Goal
Somehow our very new logo appears on this blog post from 2015: https://about.gitlab.com/blog/2015/07/03/our-new-logo/
Let's find the old svg re-upload it somewhere new and then update the blog post to point to that new image location.
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Updating old blog post to reference the correct 2015 logo`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `Blog post displays correct logo from 2015`
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/blog/2015/07/03/our-new-logo/
## 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?
- [ ] Find the old logo file
- [ ] Update the blog post to point to correct old logo
## 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 | 116,707,052 |
2022-10-11 21:10:01.484
|
Create sprint changelog
|
## Goal
We would like to create a changelog that is autogenerated at the end of every iteration. We will use add at the bottom of each executive iteration update to direct people to if they'd like to dig deeper.
#### Jobs To Be Done
* **Situation**: *When a iteration is completed, all the items completed are added to changelog.*
* **Motivation**: *We want to create a efficient way to communicate the work completed by the Digital Experience team.*
* **Outcome**: *So we can ensure transparency.*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes @mpreuss22
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Changelog exists`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* Changelog for about.gitlab.com - only Buyer Experience
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @mpreuss22
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create changelog for the Buyer Experience repository
- [ ] Automate changelog to generate at end of iteration cadence
- [ ] Documentation in the handbook
- [ ] Developer docs in repo, /docs
## 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 | 116,696,369 |
2022-10-11 17:49:53.780
|
Create new 'About GitLab' template
|
## Goal
We would like to update create a new template for the [About GitLab](https://about.gitlab.com/company/) page.
### Jobs To Be Done
* **Situation**: *When prospects want to learn more about GitLab as a company.*
* **Motivation**: *We want to ensure the information on the page is current, accurate, and in line with our messaging.*
* **Outcome**: *So we can provide them with the correct information and provide awareness.*
## Page(s)
Which page(s) are involved in this request?
* `[About GitLab](https://about.gitlab.com/company/)`
## 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?
- [ ] Code template from [Design](https://www.figma.com/file/pigc5p3VIgMlp7IopvdFoM/About?node-id=0%3A1): Updating the design to align with our latest 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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 116,685,675 |
2022-10-11 15:45:24.904
|
Update Translated URL Structure and hreflang-tagging handbook
|
## Goal
We would like to ensure the information under Translated URL Structure, hreflang-tagging, and list of localized websites is still accurate (or even relevant)?
#### URLS
* https://about.gitlab.com/handbook/marketing/localization/#translated-url-structure
* https://about.gitlab.com/handbook/marketing/localization/#hreflang-tagging
* https://about.gitlab.com/handbook/marketing/localization/#list-of-localized-websites
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `we are implementing a GDN POC with Smartling, and need to determine what localized sites allready exists and technology around them`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes @laurenbarker
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `Update the handbook with accurate information`
**How do we measure success?**
- `Handbook is updated and list of localized sites is accurate`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @lduggan
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Figure out the history of the handbook page
- [ ] Determine if the information is relevant
- [ ] update the 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
- [ ] Engineering
| 1 |
28,847,821 | 116,675,749 |
2022-10-11 13:51:15.467
|
UX: Add TeamOps section to About page
|
## Goal
We would like to add a section on TeamOps to the About page
#### Jobs To Be Done
* **Situation**: *When prospects want to learn more about GitLab as a company.*
* **Motivation**: *We want to feature the TeamOps page.*
* **Outcome**: *So we can provide provide awareness to the initiative.*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [X] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- section to feature the TeamOps page
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [X] Yes: How many people are clicking on the CTA?
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[About](gitlab.com/about)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @KristinaWeis @Tinaliseng @jhalloran @fqureshi @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 116,425,572 |
2022-10-06 19:22:50.048
|
ENG: Solutions child page template SEO improvements
|
## Goal
We would like to make improvements to the /solutions child template which will improve engagement and conversion as measured by metrics.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/enterprise/
* https://about.gitlab.com/small-business/
* https://about.gitlab.com/solutions/public-sector/
* https://about.gitlab.com/solutions/continuous-software-security-assurance/
* https://about.gitlab.com/solutions/delivery-automation/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI:
* [ ] Consulted: @Tinaliseng `@ncregan` @justin.vetter
* [ ] Informed: @fqureshi
## Working Files
[Suggested worksheet doc for each URL](https://docs.google.com/document/d/1KF5OMF8UR_3Ulv9yRSKLjOgemu6ZZTNewbzYuBKK02s/edit?usp=sharing)
### Scope
* [ ] Use document to update and optimize solutions child template
### Not in scope
- [ ] Update content, add descriptions, optimize javascript
## 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 | 116,418,409 |
2022-10-06 16:28:51.501
|
ENG: Security & Compliance LP | Lightning strike
|
## Goal
We would like to create a `Security & Compliance` landing page that will increase customer trust and confidence as measured by engagement.
## Workfiles
* [Figma mock](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=0%3A1)
### Extra workingfiles
* [Content wireframe](https://docs.google.com/document/d/1UU_TWbY9TWRYCUE2T5jLHXp-uzCWkxPaxg--RP51vb4/edit)
* [Dev Sec Ops page content wireframe](https://docs.google.com/document/d/1UU_TWbY9TWRYCUE2T5jLHXp-uzCWkxPaxg--RP51vb4/edit#)
* [JTBD wireframe](https://www.figma.com/file/vwWJNCcnRQtlOmhDkXm3bW/Security-%26-Compliance?node-id=1%3A10)
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `Lightening strike priority`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to launch the Security & Compliance LP`
**What analytics / data will we need to set-up?**
- [x] Yes: `Standard DEX analytics will need to be added`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Security & Compliance](https://about.gitlab.com/solutions/security-and-compliance)` *new page*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Security & Compliance LP
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 116,418,168 |
2022-10-06 16:24:47.898
|
UX: Security & Compliance Lightning strike: Software Supply chain security refresh
|
## Goal
We would like to update the [Software Supply chain security](https://about.gitlab.com/solutions/supply-chain/) landing page to support our Security & Compliance lightning strike.
### Project notes
Pasted from https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/6521#web-page-updates-chandler-saumya-jennifer
## Workfiles
- [Software supply chain security content wireframe](https://docs.google.com/document/d/1QpfhcnwhkaZvpjid7mwOpg_fw6l6FXeITF7ATMQEs1g/edit)
- [Figma file](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=157%3A5204)
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/supply-chain/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @supadhyaya @chandlergibb
- [ ] Informed: @justin.vetter @fqureshi
## In scope
What is within scope of this request?
- [ ] [Content wireframe](https://docs.google.com/document/d/1PDs1M2REEzsykFPxOgCK6cEy_ssaCTXWltNMTIsIs0U/edit?usp=sharing) @chandlergibb
- [ ] Figma mock @Tinaliseng
- [ ] Engineer (separate issue to come)
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 116,367,397 |
2022-10-05 22:17:01.851
|
Hero Component in Common Folder
|
## Goal
Create a reusable hero component in common folder. We currently do not have one and have been reusing the BySolutions Hero
#### Jobs To Be Done
* **Situation**: *Whenever we need to create a new page or update a template we are using the BySolutions Hero*
* **Motivation**: *Creating a Common hero will improve development time, help track our components and prevent duplicate components in the future*
* **Outcome**: *A top level hero component*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `When the new component is created`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* All pages(now and in the future) requiring the new infinity hero
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@miraclebanks``@mduque-ext`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 116,285,534 |
2022-10-04 22:44:47.340
|
ENG: Remove LaunchDarkly test PricingBorders
|
## Goal
We would like to push the pricing borders live by removing the LaunchDarkly code from the pricing page.
#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: `This needs to be completed before we can run our next test on the pricing page`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `Remove LaunchDarkly code and push variant code only`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `[Pricing](https://about.gitlab.com/pricing)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @meganfilo
- [ ] Consulted: @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove LaunchDarkly code
- [ ] Only show have pricing border variant live
## 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 | 116,283,269 |
2022-10-04 21:29:33.560
|
ENG: Bug Mobile Menu Pricing link
|
## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?
### Describe the Bug
In the mobile menu when you click the actual word "pricing" it 404s, but when you click the white space to the right it takes you to the correct page. It looks like there is some weird rendering issue in the HTML.
### What's my browser?
Share your browser infromation from https://www.whatsmybrowser.org/
Mobile chrome
## Page(s)
Which page(s) are involved in this request?
* Mobile Menu
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 116,281,975 |
2022-10-04 20:48:50.046
|
Add 'TeamOps' in the 'Learn' navigation
|
## Goal
We would like to drive more visitors to the teamops page.
#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 116,270,687 |
2022-10-04 16:28:17.542
|
ENG: Fix render blocking for Google fonts
|
## Goal
We would like to increase our core web vital scores. One of the line items that is hurting our scores is how Google fonts is loaded.
#### Jobs To Be Done
* **Situation**: *When the DOM loads google fonts is blocking page render lowering our core vital score*
* **Motivation**: *We want to update to fix our core vital scores*
* **Outcome**: *So we can show increased core vital score*
#### Please provide more information related to this request
Here are two articles talking about how to resolve this issue
- https://dieppa.co.uk/2020/10/21/eliminate-render-blocking-resources-google-fonts/
- https://www.tutorialjinni.com/eliminate-render-blocking-google-fonts.html
We will need to test to see if we are seeing major font popping with these options, and weigh the benefit of this change.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- Lower Web Core Vital score
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* All
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Change how google fonts is loaded into BE
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 116,267,806 |
2022-10-04 15:37:33.972
|
Regression: Support Template
|
## Goal
There are reports of the Support page not loading properly. This is issues is for defining those issues and resolving them.
### Describe the Bug
- 1350px wide the menu jumps to the left and the scroll gets wonky
- On page load, nothing is displayed in the body, this resolves after 2 seconds and then content displays
- @theo.dp please describe your bug here
### What's my browser?
Share your browser information from https://www.whatsmybrowser.org/
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 116,209,998 |
2022-10-03 19:41:32.671
|
Fix 404's
|
## Goal
Fix all the 404's detected by https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1120
| 1 |
28,847,821 | 116,160,640 |
2022-10-03 05:52:38.524
|
Remove redirect from /teamops to /handbook/teamops
|
## Goal
Remove the redirect in www-gitlab-com from /teamops as the page is about to exist!
| 1 |
28,847,821 | 116,026,298 |
2022-09-29 16:35:38.376
|
[Design] Free Trial Sign-Up Screen re-design
|
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [X] Yes: Request from Ashley
- [ ] No
### Workfiles
* [Figma file](https://www.figma.com/file/DkrMqoi7TStumwGfG19Rt1/Form-A%2FB-test---Ultimate-Free-Trial-Form-refresh?node-id=3%3A773)
* [Figma prototype](uhttps://www.figma.com/proto/DkrMqoi7TStumwGfG19Rt1/Form-A%2FB-test---Ultimate-Free-Trial-Form-refresh?page-id=0%3A1&node-id=3%3A773&viewport=-500%2C665%2C0.41&scaling=min-zoom)
## Page(s)
Which page(s) are involved in this request?
* [Free Trial Sign Up](https://gitlab.com/-/trials/new)
* Only update the logged out version of this page
And use this screen as a starting point
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @s_awezec @fqureshi @justin.vetter @mpreuss22
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Remove 'Skip Trial' link
- [ ] Remove or change illustration
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 116,014,364 |
2022-09-29 13:55:37.399
|
[SPIKE] Research potential pipeline improvements
|
## Goal
A learning and development issue to familiarize myself with GitLab's tooling. The goal is to use this knowledge to create a more robust www-gitlab-com site.
| 4 |
28,847,821 | 115,966,239 |
2022-09-28 22:16:29.698
|
MVC1: Changes to Nav
|
## Goal
We would like to make changes to the Nav as an MVC 1 iteration
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [X] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [X] Yes `@akramer`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
**How do we measure success?**
- Increased or stagnant clicks to Solutions pages
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [X] No
## Page(s)
Which page(s) are involved in this request?
* [Homepage](about.gitlab.com)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [X] DRI: @mpreuss22
- [X] Consulted: @ctsang-ext @Tinaliseng @fqureshi @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Move Solutions under Platform
## 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 | 115,953,935 |
2022-09-28 18:40:03.772
|
/free-trial doesn't work in our review apps
|
## Goal
/fre-trial gives the following error on review apps.
```ERR_TOO_MANY_REDIRECTS```
| 2 |
28,847,821 | 115,942,833 |
2022-09-28 15:36:50.692
|
ENG: Topic Page Template / Add Side Nav
|
## Goal
We would like to add the multi-level side navigation to the Topic pages which will decrease exit rates as measured by metrics.
## Design
- [Slippers Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=9327%3A16896)
Relates to:
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1327
## Page(s)
Which page(s) are involved in this request?
* (List top topic pages for MVC 1 - TODO: @ncregan )
## Scope
- [ ] List of pages and links - TODO @ncregan
- [ ] Apply the [multi-level side nav](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/148) TODO `DEX ENG`
## RCI
- Responsible:
- Consulted: @ncregan @Tinaliseng @dennischarukulvanich
- Informed: @ndubord @justin.vetter
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 115,864,484 |
2022-09-27 15:16:40.186
|
Header & Footer JS package size non BE repo
|
## Goal
I would like to discuss the JS package size for the main nav and footer. In the handbook, blog, and non-BE www pages these two js files are usually the largest load on the page.
When the Nav repo is added to BE our webpack does some smart splitting on what is loaded and when, but not when we just load in the files.
<details><summary>Screen Shot</summary>
</details>
#### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to discuss options on reducing resource load for the packages we manage`
**How do we measure success?**
- `We will look at Core Page scores to determine if reducing filesize will help`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `all non BE pages`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker @ndubord @justin.vetter
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Come up with a plan on how we can reduce Nav package size for non BE pages.
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 115,855,168 |
2022-09-27 13:27:39.118
|
ENG: Update Ultimate-tier link on Free Trial page
|
## Goal
We would like to update the Ultimate-tier link on the /free-trial page
Ultimate-tier link -> https://about.gitlab.com/pricing/ultimate/
#### Jobs To Be Done
* **Situation**: *When a user clicks on the Ultimate-tier link they are taken to the /pricing page*
* **Motivation**: *We want to direct users to the most recent content*
* **Outcome**: *So we can ...*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- End goal is to point users to the correct content
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `[Free Trial](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: @justin.vetter
- [ ] Informed: `@RLeihe268`
## In scope
What is within scope of this request?
- [ ] Update Ultime Tier link
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 115,813,003 |
2022-09-27 00:37:32.200
|
More marketing cleanup in www-gitlab-com
|
## Goal
Part of an on-going effort to migrate the marketing site over to BE. This effort will save us time down the road on regressions/migrations when the www-gitlab-com repository is deleted.
| 2 |
28,847,821 | 115,790,330 |
2022-09-26 14:51:25.312
|
Document visual changes on the website since rebrand
|
From Michael:
- Put together a list of URLs and before and after screenshots of all page refreshes we’ve done since Q2
- Single pager kind of things from the Slack integration to the Features page etc.
- I believe there is a lot of work that leadership is not aware of and I’d like to put together a list with visuals to inform them of how much we’ve done.
| 4 |
28,847,821 | 115,689,412 |
2022-09-23 23:36:57.903
|
Add LaunchDarkly users to DEX handbook
|
Let's add the names of DEX team members who have access to LaunchDarkly to our handbook. Not everyone on our team may have access and this transparency will speed up the process of finding someone that may have access in order to answer questions, grab data, grant additional access, etc.
| 1 |
28,847,821 | 115,686,792 |
2022-09-23 21:30:30.321
|
Release: Overview Partner Program
|
## Goal
We would like to build a new template and apply it to Overview Partners page and a new Benefits for Partners. This new template was created as part of [this issue.](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1107)
- ~~[Figma Link](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=170%3A5667)~~
- [Update Figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=556%3A12097)
For copy:
- Nav: [New GitLab Partner Page Layout - Navigation](https://docs.google.com/document/d/1PLzmWVokewbVWTkT4vPUmQKt46veH0Ia7ohVVBW1EOo/edit#)
- Overview: [New GitLab Partner Page Layout - GitLab Partner Program Overview {new}](https://docs.google.com/document/d/1du1nu8dINnmiyd2CwkFddZbPQ_2dohS0HhO4AWpmh9U/edit#)
- Benefits: [New GitLab Partner Page Layout - Overview & Benefits {new}](https://docs.google.com/document/d/1eX1-we2XqqxBkVe5AIIL4TqVFEwKBcEHiVDu38F7Nmw/edit?usp=sharing)
### Jobs To Be Done
* **Situation**: *We'd like a unified landing page for GitLab partners overview and benefits*
* **Motivation**: *When users need more information we can direct the to the correct spot*
* **Outcome**: *So we can offer them the best service*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/partners/
* https://about.gitlab.com/partners/benefits
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mduque-ext
- [ ] Consulted: @laurenbarker @ctsang-ext @mlebeau
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Releasing new Overview Partners page to production @ https://about.gitlab.com/partners/
- [ ] Creating and releasing a new Benefits for Partners to production @ https://about.gitlab.com/partners/benefits/
- [ ] Updating our navigation as specified in the Figma
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 115,683,801 |
2022-09-23 19:30:19.873
|
ENG: Release Post MVC 1 Rebrand
|
## Goal
We would like to create a new review app link for the engineering work that has been done for the Release Post template from this previous [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1201) and [MR](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/110472)
**The MR should not be merged until we have signoff from all stakeholders**__
### Jobs To Be Done
* **Situation**: *When a customer goes to read the release post ...*
* **Motivation**: *We want to have a similar experience to the rest of the site...*
* **Outcome**: *So we can maintain our brand and make sure our site is accessible.*
## Page(s)
Which page(s) are involved in this request?
* [Example release post](https://about.gitlab.com/releases/2022/07/22/gitlab-15-2-released/)
* [Figma designs](https://www.figma.com/file/GpqMIWNYZW2fC58BHwMbWf/Release-post-MVC1?node-id=2%3A928)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mmanunga-ext
- [ ] Consulted: @fqureshi @jhalloran @justin.vetter @ndubord
- [ ] Informed: `@fseifoddini` `@amittner` `@brhea`
## In scope
What is within scope of this request?
- [x] Skin existing release post with updated brand colors and typography
- [x] Address any existing accessibility issues
## Out of scope
What is out of scope and not part of this iteration?
- Changing the structure of the page
- Hero image
- Anything else
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 115,679,889 |
2022-09-23 17:30:20.343
|
ENG: Free Trial Tab component
|
## Goal
We keep the /free-trial/ page around for SEO purposes and to drive some links to the Self-Managed sign up form. Currently there is no way to link to the page and have the Self-Managed tab automatically selected.
#### Jobs To Be Done
* **Situation**: *When we link to this page driving to the Self-Managed form the user needs to click the tab to fill out the form*
* **Motivation**: *We want to be able to link to this page and have an option to have the Self-Managed tab selected*
* **Outcome**: *So we can drive users directly to the Self-Managed form*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [x] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* `[Free Trial](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: @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update tab component so a direct link can highlight the `GitLab Self-Managed` tab
- [ ] Add accessibility tab targeting to the tab component
## 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 | 115,627,474 |
2022-09-22 22:25:32.830
|
Tracking: Site Search Result Sort dataLayer
|
## Goal
Push the following dataLayer code when the Sort By selection is made on the search result window:<br/>
<img src="/uploads/c5570a4f8a3d0e20d8aef0a170d79ce6/Screen_Shot_2022-09-22_at_3.23.14_PM.png" width="300">
```
dataLayer.push({
'event': 'siteSearchResultSort',
'siteSearchSort': '[dynamic value of most popular, suggested, last updated]',
'siteSearchQuery': '[dynamic searched query goes here]'
});
```
#### Please provide more information related to this request<br/>
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes @laurenbarker
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: Addition to existing Google Analytics data set
**What analytics / data will we need to set-up?**
- [x] Yes: Click tracking within the Site Search section
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* Header on all about.gitlab.com pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @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
| 2 |
28,847,821 | 115,626,268 |
2022-09-22 22:21:30.920
|
Tracking: Site Search Result Filter dataLayer
|
## Goal
Push the following dataLayer code when the Source radio buttons are clicked on:<br/>
<img src="/uploads/72e64a8cfdb1faae3d7ac74d5aa177a7/Screen_Shot_2022-09-22_at_3.16.56_PM.png" width="200">
```
dataLayer.push({
'event': 'siteSearchResultFilter',
'siteSearchFilter': '[dynamic value of about gitlab, handbook, or blog goes here]',
'siteSearchQuery': '[dynamic searched query goes here]'
});
```
#### Please provide more information related to this request<br/>
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes @laurenbarker
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: Addition to existing Google Analytics data set
**What analytics / data will we need to set-up?**
- [x] Yes: Click tracking within the Site Search section
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* Header on all about.gitlab.com pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @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
| 2 |
28,847,821 | 115,625,821 |
2022-09-22 22:06:10.551
|
Tracking: Site Search Result dataLayer
|
## Goal
Objective is to push a dataLayer event when a search is made, along with the searched query.
Push dataLayer on search result load<br/>
<img src="/uploads/78a766243e5f442462784e6379d688b7/Screen_Shot_2022-09-22_at_2.55.15_PM.png" width="500">
```
dataLayer.push({
'event': 'siteSearchResult',
'siteSearchQuery': '[dynamic searched query goes here]'
});
```
Note: The dataLayer should be pushed when the user enters a query in the search field AND when the user clicks on a suggested searched query - both methods will lead the user to the result page as a next step.
#### Please provide more information related to this request<br/>
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes @laurenbarker
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: Addition to existing Google Analytics data set
**What analytics / data will we need to set-up?**
- [x] Yes: Click tracking within the Site Search section
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* Header on all about.gitlab.com pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @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
| 1 |
28,847,821 | 115,625,373 |
2022-09-22 21:43:15.764
|
/solutions/ to pull from content/synced
|
## Goal
Change the features.yml and categories.yml references on /solutions/ from /content/features.yml to content/synced/features and same for categories.
Please also remove the old features.yml/categories.yml files if they're no longer needed.
| 2 |
28,847,821 | 115,590,822 |
2022-09-22 12:43:21.901
|
Plan: Analysts (Design) MVC 2
|
## Goal
We would like to update the Analysts page to include updates [per this comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1384#note_1104043751)
### Jobs To Be Done
TBD
## Page(s)
Which page(s) are involved in this request?
- [Analysts](https://about.gitlab.com/analysts/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] 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
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 115,545,878 |
2022-09-22 02:51:10.735
|
Release: Support Services template
|
## Goal
We would like to release a new Support Services template in the Buyer Experience repository.
This will involve final touches to template.
To release this template, undo the changes made with this [commit](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1097/diffs?commit_id=cceaec7d8a2961f3b4c4c09e913e1bf0d35ee372).
### Jobs To Be Done
Release [the new template ](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1361)in Buyer Experience, migrate content from www-gitlab-com
## Page(s)
Which page(s) are involved in this request?
- [Support Services](https://about.gitlab.com/services/#contactform)
- [Figma](https://www.figma.com/file/2zmj9hb6MBH40d6NMZm8Jw/Professional-Services?node-id=26%3A3)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jariasc-ext
- [ ] Consulted: @ctsang-ext @laurenbarker
- [ ] Informed: @fqureshi
## In scope
What is within scope of this request?
- [ ] Create merge request releasing template to prodcution
- [ ] Tag stakeholders for review in merge reuqest
- [ ] Tag @fqureshi for review in merge request
- [ ] Remove URl from the routes.ignore.js
- [ ] Remove the page from www-gitlab-com
- [ ] Update handbook instructions for how to find and update 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
| 4 |
28,847,821 | 115,544,766 |
2022-09-22 02:07:49.469
|
Release: New Analysts Page
|
## Goal
We would like to release the new Analysts page using the new template built in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1394)
## Page(s)
Which page(s) are involved in this request?
- [Analysts](https://about.gitlab.com/analysts/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: TBD
- [ ] Consulted: @ctsang-ext @laurenbarker
- [ ] Informed: @fqureshi
## In scope
What is within scope of this request?
- [ ] Prepare a MR for stakeholder review and tag @fqureshi for review
- [ ] Release the new Analyst page to production
- [ ] Remove the Analysts page from `www-gitlab-com`
- [ ] Update any references on location of this page and how to update it in the 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
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering).
| 2 |
28,847,821 | 115,544,703 |
2022-09-22 02:02:48.460
|
Create: Analysts Template
|
## Goal
We would like to update the Analysts page using the new template planned in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1384#note_1107954781).
Here is the[ Figma template.](https://www.figma.com/file/7Q7VE1wjbM8iGxloOP0u9b/Analysts?node-id=0%3A1)
### Jobs To Be Done
Create the template in Buyer Experience.
## Page(s)
Which page(s) are involved in this request?
- [Analysts](https://about.gitlab.com/analysts/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] Build the [Figma template](https://www.figma.com/file/7Q7VE1wjbM8iGxloOP0u9b/Analysts?node-id=0%3A1) in Buyer Experience
- [ ] Add this page to BE but disclude it from building in production using routes ignore file. We will release this template in a separate 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
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 115,468,123 |
2022-09-21 01:51:08.604
|
Update /resources/ with the latest DevSecOps survey
|
## Goal
[/resources/](https://about.gitlab.com/resources/) still shows the 2021 DevSecOps survey
| 2 |
28,847,821 | 115,449,707 |
2022-09-20 19:24:11.692
|
Pipeline job to detect 404's
|
## Goal
Detect any broken links on the Marketing site.
## 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
| 8 |
28,847,821 | 115,432,658 |
2022-09-20 14:51:31.099
|
Propose process updates to BE iterations
|
## Goal
Write clear and concise documentation on how the Buyer Experience team uses boards in an iteration.
| 3 |
28,847,821 | 115,291,014 |
2022-09-18 23:12:07.204
|
Fix scripts/data-sync.sh failing on yarn generate
|
## Goal
In the review app, references to synced files break as the synced files get blown away before build.
Reference: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1064
| 2 |
28,847,821 | 115,237,244 |
2022-09-16 18:16:06.326
|
Plan: Analysts (Design)
|
## Goal
We would like to update the Analysts page.
### Jobs To Be Done
TBD
## Page(s)
Which page(s) are involved in this request?
- [Analysts](https://about.gitlab.com/analysts/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @Tinaliseng, @jhalloran
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] 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
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 115,221,018 |
2022-09-16 14:37:36.476
|
Remove features.yml/categories.yml from BE and redirect to the synchronized version
|
## Goal
Follow-up to: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1051
Lets change the references from /content/features.yml to /content/synced/features.yml (and categories.yml)
| 2 |
28,847,821 | 115,170,404 |
2022-09-15 22:20:56.690
|
[Eng] Add a CTA on /learn/ under 'Learn More about Certifications'
|
## Goal
We would like to promote the free trial CTA on /learn/ which will improve Free Trial Conversion.
#### Jobs To Be Done
* **Situation**: *When users visit /learn/ page*
* **Motivation**: *We want to provide them an option to start a free trial*
* **Outcome**: *So we can improve the free trial conversion*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [X] Yes: SaaS Trial CVR continues to trend down from an avg. 0.8% to 0.5% CVR
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [X] Yes @RLeihe268
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- Add CTA
**How do we measure success?**
- Clicks on CTA
**What analytics / data will we need to set-up?**
- [X] Yes: For tracking, the engineer will just need to place the data-ga attributes to the link:
* data-ga-name="free trial"
* data-ga-location="header"
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Learn Page](about.gitlab.com/learn/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @fqureshi
- [ ] Consulted: @mpreuss22 @dennischarukulvanich
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] [CTA Link](https://gitlab.com/-/trials/new?_gl=1%2Aiun8xs%2A_ga%2AMjYyMTI5MzcuMTYyNjk3NTQwMg..%2A_ga_ENFH3X7M5Y%2AMTY2MzY5MTAzNi43Mi4wLjE2NjM2OTEwMzYuMC4wLjA.&glm_content=default-saas-trial&glm_source=about.gitlab.com)
- [ ] [Figma here.](https://www.figma.com/file/xvVvOI4d9kH2oPjpLaLg7o/Learn-%2F-UI-Refresh?node-id=204%3A4444)
## 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 | 115,170,356 |
2022-09-15 22:18:17.714
|
[Eng] Add a CTA on /sales/ in the header section
|
## Goal
We would like to promote the free trial CTA on /sales/ which will improve Free Trial Conversion.
#### Jobs To Be Done
* **Situation**: *When users visit /sales/ page*
* **Motivation**: *We want to provide them an option to start a free trial*
* **Outcome**: *So we can improve the free trial conversion*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [X] Yes: SaaS Trial CVR continues to trend down from an avg. 0.8% to 0.5% CVR
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [X] Yes @RLeihe268
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- Add CTA
**How do we measure success?**
- Clicks on CTA
**What analytics / data will we need to set-up?**
- [X] Yes: For tracking, the engineer will just need to place the data-ga attributes to the link:
* data-ga-name="free trial"
* data-ga-location="\[the placement goes here\]" //either header or body
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Install Page](about.gitlab.com/sales/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @fqureshi
- [ ] Consulted: @mpreuss22 @dennischarukulvanich
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] CTA Link
## 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 | 115,170,269 |
2022-09-15 22:15:50.447
|
[Eng] Add a CTA on /install/ce-or-ee/ below the two boxes
|
## Goal
We would like to promote the free trial CTA on /install/ce-or-ee/ which will improve Free Trial Conversion.
#### Jobs To Be Done
* **Situation**: *When users visit /install/ce-or-ee/ page*
* **Motivation**: *We want to provide them an option to start a free trial*
* **Outcome**: *So we can improve the free trial conversion*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [X] Yes: SaaS Trial CVR continues to trend down from an avg. 0.8% to 0.5% CVR
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [X] Yes @RLeihe268
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [X] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- Add CTA
**How do we measure success?**
- Clicks on CTA
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* `[Install Page](about.gitlab.com/install/ce-or-ee/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @fqureshi
- [ ] Consulted: @mpreuss22 @dennischarukulvanich
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Adding the site footer with the CTA link that leads to https://gitlab.com/-/trials/new?_gl=1%2Aiun8xs%2A_ga%2AMjYyMTI5MzcuMTYyNjk3NTQwMg..%2A_ga_ENFH3X7M5Y%2AMTY2MzY5MTAzNi43Mi4wLjE2NjM2OTEwMzYuMC4wLjA.&glm_content=default-saas-trial&glm_source=about.gitlab.com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 2 |
28,847,821 | 115,168,098 |
2022-09-15 21:10:00.990
|
Smarting GDN Localization Proof of Concept for French, Japanese, and German
|
## Goal
Proof of Concept localized versions of conversion driving pages using the [Smartling Global Delivery Network](https://www.smartling.com/software/global-delivery-network/) have been created on our domain using a sandbox demo from Smartling. We'd like to gain approval from stakeholders on using this service in a production capacity for about.gitlab.com before [signing a contract with Smartling](https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/7033). Proof of Concept URLS to verify are:
**French Localization**
- https://about.gitlab.com/fr-fr/
- https://about.gitlab.com/fr-fr/why-gitlab/
- https://about.gitlab.com/fr-fr/pricing/
**Japanese Localization**
- https://about.gitlab.com/ja-jp/
- https://about.gitlab.com/ja-jp/why-gitlab/
- https://about.gitlab.com/ja-jp/pricing/
**German Localization**
- https://about.gitlab.com/de-de/
- https://about.gitlab.com/de-de/why-gitlab/
- https://about.gitlab.com/de-de/pricing/
We needed to make changes to our DNS to serve these our our doamin, which was coordinated here:
Infrastructure issue for support: https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/16433
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No - but it should be completed by end of FY23Q3.
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes @fqureshi
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
- [x] unsure: I am unsure of the legal requirements for localziation
**What analytics / data will we need to set-up?**
- [x] Yes: @dennischarukulvanich - Please list analytics that will be needed
- [ ] No
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: @laurenbarker
- [x] Consulted: @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Define subdomain and subfolder strategy
- [x] Work with infrastructure in this [issue](https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/16433) to update our DNS
## 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
| 4 |
28,847,821 | 115,161,149 |
2022-09-15 17:58:12.762
|
Release: Free Trial Conversion data in Launch Darkly
|
## Goal
We would like to enable free trial conversion data to be collected by Launch Darkly.
#### Jobs To Be Done
* **Situation**: *When a user clicks on the Free Trial nav button in navigation, data is collected by Launch Darkly for each A/B navigation test variant*
* **Motivation**: *We want to measure free trick click rates of each A/B test variant*
* **Outcome**: *So we can determine a winner based on data*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [x] Yes: We enabled our 1st [A/B test to remove register for the nav](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1356) on 2022-09-15. Since the test is live, we are not collecting correct data, therefore this issue is urgent. If we do not resolve this by 2022-09-16, we will need to stop and restart that A/B test.
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes @laurenbarker @fqureshi
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: unknown
**What is the ultimate end goal vision vs the MVC1 iteration?**
- Free trial clicks are measured in Launch Darkly for variant A and B of the navigation
**How do we measure success?**
- Data is collected and visible through Launch Darkly
**What analytics / data will we need to set-up?**
- [x] Yes: @dennischarukulvanich to verify
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* Buyer Experience
* Launch Darkly
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @miraclebanks
- [ ] Consulted: @laurenbarker @ndubord @jgarc
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Configure in LaunchDarkly
- [ ] Script run in our code
- [ ] Verify data is collected by Launch Darkly
-
## 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
| 2 |
28,847,821 | 115,160,635 |
2022-09-15 17:47:31.564
|
UX: Solutions child page template / design analysis
|
## Goal
We would like to make improvements to the /solutions child template which will improve engagement and conversion as measured by metrics.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/enterprise/
* https://about.gitlab.com/small-business/
* https://about.gitlab.com/solutions/public-sector/
* https://about.gitlab.com/solutions/education/campus/
* https://about.gitlab.com/solutions/continuous-software-security-assurance/
* https://about.gitlab.com/solutions/delivery-automation/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @ctsang-ext
- [ ] Informed: `@supadhyaya` @fqureshi `@chandlergibb`
### Scope
- [ ] Review the UX and design of each page and recommend improvements to the template and/or block components
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 115,148,586 |
2022-09-15 15:06:12.158
|
ENG: Features LP / Stage tabs disappear after clicking 'back'
|
## Describe the Bug
@supadhyaya [reported](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1345#note_1098539975) that when she clicks on a stage and then hits back button, the section with the stages disappears. I am not able to reproduce the bug. Can you have a look?
Here's a video:
- https://drive.google.com/file/d/1xNXgGaWP_WxZbD2V_j3yFp3a4FWODXnr/view?usp=sharing
### What's my browser?
Chrome
## Page(s)
Which page(s) are involved in this request?
* [Features](https://about.gitlab.com/features)
## 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 | 115,080,518 |
2022-09-14 20:00:59.847
|
ENG: Feature cards / Clickable pricing tier pills
|
## Goal
Make it easier for visitors to click through to free trials and pricing from the feature cards.
### Describe the Bug
Currently, users have to have good aim to reach the tooltip link for each tier pill. We would like to make the pill clickable as well.
## Page(s)
Which page(s) are involved in this request?
* /solutions - [review app](https://about.gitlab.com/solutions)
* [/features](https://about.gitlab.com/features/)
## 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 | 115,066,118 |
2022-09-14 16:58:18.679
|
Ability to pre-filter on /learn/
|
## Goal
Have the ability to pre-filter on the /learn/ page, similar to how /events/ works.
#### Please provide more information related to this request
Resource: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/111309#note_1100826333
## Page(s)
Which page(s) are involved in this request?
* `[Learn](https://about.gitlab.com/learn/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @jallen16
- [ ] 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:
- [ ] Engineering
| 2 |
28,847,821 | 115,059,906 |
2022-09-14 15:09:39.805
|
Update Nathan Dubord's readme
|
## Goal
Update my readme page
| 1 |
28,847,821 | 114,980,209 |
2022-09-13 16:47:03.103
|
Migrate comparison pages to Buyer Experience
|
## Goal
We would like to migrate the /devops-tools/ pages over to Buyer Experience.
#### Jobs To Be Done
When viewing the comparison pages, the stage name needs to be "govern" not "protect". We would also like to migrate these pages over to make maintenance easier, and apply our new branding.
#### Please provide more information related to this request
First iteration: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/111298/
Slack thread: https://gitlab.slack.com/archives/CN8AVSFEY/p1663081429262539
## Page(s)
Which page(s) are involved in this request?
* All /devops-tools/ pages that use the new infographic chart.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @jkempton
- [ ] Informed: @mpreuss22
## In scope
What is within scope of this request?
- Add comparison component to latest version of slippers.
- Migrate comparison pages over that use the new component.
## 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
| 8 |
28,847,821 | 114,971,030 |
2022-09-13 15:20:21.701
|
Comparison pages with the new charts appear to be broken
|
## Goal
The recent change from "Protect" to "Govern" has caused the comparison charts to no longer render properly.
## Page(s)
Which page(s) are involved in this request?
* [GitHub vs. GitLab](https://about.gitlab.com/devops-tools/github-vs-gitlab/)
* [Jenkins vs. GitLab](https://about.gitlab.com/devops-tools/jenkins-vs-gitlab/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @jkempton @tywilliams
- [ ] 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:
- [x] Engineering
| 1 |
28,847,821 | 114,898,507 |
2022-09-12 20:48:02.322
|
Update hero banner for Resources page to 2022 DevSecOps Survey
|
## Goal
We would like to update the hero banner on https://about.gitlab.com/resources/ to feature the 2022 DevSecOps Survey.
Request for this update came in as part of [this thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1071#note_1066713318).
#### Jobs To Be Done
* **Situation**: *When a user is looking for resources, our recent DevSecOps survey is featured in the hero.*
* **Motivation**: *We want to promote the survey.*
* **Outcome**: *So we can drive more brand awareness and trust.*
#### Please provide more information related to this request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [x] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [x] Yes @eirinipan
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [x] No: `This is a content update - pure swap for newer content.`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is to update the hero banner from the 2021 DevSecOps Survey to the 2022 version.`
**How do we measure success?**
- `Increased traffic to the 2022 DevSecOps Survey`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [x] No
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/resources/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Update hero content to promote 2022 DevSecOps Survey
- [ ] Find suitable image replacement for hero
## 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 | 114,883,723 |
2022-09-12 17:23:35.344
|
Create: Support Services, new template build
|
## Goal
We would like to create a new Support Services template in the Buyer Experience repository.
### Jobs To Be Done
Build the new template in Buyer Experience, release the code but not to production
## Page(s)
Which page(s) are involved in this request?
- [Support Services](https://about.gitlab.com/services/#contactform)
- [Figma](https://www.figma.com/file/2zmj9hb6MBH40d6NMZm8Jw/Professional-Services?node-id=26%3A3)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: TBD
- [ ] Consulted: @ctsang-ext @laurenbarker
- [ ] Informed: @fqureshi
## In scope
What is within scope of this request?
- [ ] Build the new template in Buyer Experience
- [ ] Create new form component
- [ ] Use the routes.ignore.js file to push this template to production but not release it
## 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 | 114,882,564 |
2022-09-12 16:59:54.964
|
UX: Security & Compliance LP / Lightning strike
|
## Goal
We would like to create a `Security & Compliance` landing page which will increase customer trust and confidence as measured by engagement.
### Project notes
Pasted from https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/6521#web-page-updates-chandler-saumya-jennifer
1. Refresh [DevSecOps](https://about.gitlab.com/solutions/dev-sec-ops/) solution page
1. Refresh [Compliance](https://about.gitlab.com/solutions/compliance/) solution page - [issue here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1487)
1. Refresh: [Software Supply chain security](https://about.gitlab.com/solutions/supply-chain/) solutions page - [issue here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1457)
## Workfiles
- [Content wireframe](https://docs.google.com/document/d/1UU_TWbY9TWRYCUE2T5jLHXp-uzCWkxPaxg--RP51vb4/edit)
- [Dev Sec Ops page content wireframe](https://docs.google.com/document/d/1UU_TWbY9TWRYCUE2T5jLHXp-uzCWkxPaxg--RP51vb4/edit#)
- [Software supply chain security wireframe](https://docs.google.com/document/d/1QpfhcnwhkaZvpjid7mwOpg_fw6l6FXeITF7ATMQEs1g/edit)
- [Compliance](https://docs.google.com/document/d/1G9N6ZjbTiZPNBwYji0ZPi821bfTOmML176tcEydwhr8/edit?usp=sharing)
- [Figma file](https://www.figma.com/file/NvrqYLsDG3A9OpLqmPtFWL/Solutions-Template-%2F-MVC-2?node-id=0%3A1)
## Addition information
#### Please provide more information related to this request - TO DO @supadhyaya
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
**If this is urgent, what is the business need for the urgency?**
- [ ] Yes: `what is the business need for the urgency`
- [ ] No
If the requestor is not the DRI, find out if the DRI is aware of the request / wants to change things.
**Does anyone in leadership have eyes on this project?**
- [ ] Yes `@personshandle`
- [ ] No
**Compliance / legal / accessibility regulations to be aware of?**
- [ ] Yes: `Please describe why`
- [ ] No: `Please describe why`
**What is the ultimate end goal vision vs the MVC1 iteration?**
- `End goal for this MVC iteration is XYZ`
**How do we measure success?**
- `Please describe how success will be measured`
**What analytics / data will we need to set-up?**
- [ ] Yes: `Please describe what analytics will need to be set up`
- [ ] No
## Page(s)
Which page(s) are involved in this request?
* URL TBD
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @supadhyaya @chandlergibb
- [ ] Informed: @justin.vetter
## In scope
What is within scope of this request?
- [ ] [Content wireframe](https://docs.google.com/document/d/1PDs1M2REEzsykFPxOgCK6cEy_ssaCTXWltNMTIsIs0U/edit?usp=sharing)
- [ ] [Layout wireframe](https://www.figma.com/file/vwWJNCcnRQtlOmhDkXm3bW/Security-%26-Compliance?node-id=1%3A10) @Tinaliseng
- [ ] Figma mock @Tinaliseng
- [ ] Engineer (separate issue to come)
## 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
| 6 |
28,847,821 | 114,882,082 |
2022-09-12 16:54:39.981
|
ENG: TeamOps landing page
|
- Design issue: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1259#note_1095420352
- [Figma file](https://www.figma.com/file/EUwvxxmxnTI40hqONO5dWc/TeamOps?node-id=32%3A465)
| 10 |
28,847,821 | 114,823,529 |
2022-09-12 02:45:49.348
|
Document in handbook how to add a video to features.yml
|
Request: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1345#note_1095350984
| 1 |
28,847,821 | 114,766,911 |
2022-09-09 22:58:55.617
|
Release: Remove Launch Darkly Flag for A/B Test - Remove 'register' from the nav
|
## Goal
We would like to remove the A/B test and flag switching between our navigation variations.
This issue is for removing the A/B test and displaying the winner 100%.
### Jobs To Be Done
* **Situation**: *When a user visits our site, 100% get winning variant A*
* **Motivation**: *We want to display the variant that led to more sign ups*
* **Outcome**: *So we can get users to try GitLab*
## Page(s)
Which page(s) are involved in this request?
* Buyer Experience repository
## 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?
- [ ] Removing the feature flag in Launch Darkly
- [ ] Removing feature flag to switch between variation A and B of the navigation in Buyer Experience
- [ ] Removing the loosing nav variation from the navigation repository
- [ ] Notifying this [parent issue that test is over](https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/1)
- [ ] Updating handbook with test winner https://about.gitlab.com/handbook/marketing/digital-experience/engineering-ab-tests/
## 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 | 114,766,855 |
2022-09-09 22:52:50.375
|
Release: Launch Darkly Flag for A/B Test - Remove 'register' from the nav
|
## Goal
We would like to implement a Launch Darkly feature flag to run the [A/B test proposed here](https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/1).
This A/B test will do a 50/50 split between two nav variations - one with the register link and one with out.
This issue is for tracking the work required to build this feature flag switch into the Buyer Experience repository and turning it on.
[A/B Test MR](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1006)
[Handbook Page Update](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/111314)
### Jobs To Be Done
* **Situation**: *When a user visits our site, 50% get variant A of the nav and 50% get variant B*
* **Motivation**: *We want to gather data on register link and effect to other CTAs*
* **Outcome**: *So we can get users to try GitLab*
## Page(s)
Which page(s) are involved in this request?
* Buyer Experience repository
## 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] Create feature flag in Launch Darkly
- [x] User feature flag to switch between variation A and B of the navigation
- [x] Turning on the A/B test
- [x] Notifying this [parent issue that test is running](https://gitlab.com/gitlab-com/marketing/digital-experience/ab-testing/-/issues/1)
- [x] Updating handbook with correct test dates https://about.gitlab.com/handbook/marketing/digital-experience/engineering-ab-tests/
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 114,765,052 |
2022-09-09 21:57:58.208
|
Address v::deep errors on build
|
## Goal
We would like to fix the all the `WARN [@vue/compiler-sfc] ::v-deep ....` errors when running the Buyer Experience project. This warning is slowing down our build and making it difficult to find errors because there are so many v-deep warnings.
### Jobs To Be Done
* **Situation**: *When the site is built locally or for production, we don't see any v::deep warnings in the console*
* **Motivation**: *We want to keep our build clean and manageable for reading errors*
* **Outcome**: *So we can be efficient when fixing build issues*
## Page(s)
Which page(s) are involved in this request?
* building the site locally or for production
## 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?
- [ ] Fix all `v-deep` warnings for `yarn dev`
- [ ] Fix all `v-deep` warnings for `yarn build`
## 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 | 114,764,819 |
2022-09-09 21:48:55.817
|
ENG: Find Alliance - Add new icons
|
## Goal
Change the icons in the page filters to the ones in the [Figma](https://www.figma.com/file/bwbQtDosVskeNxsAry1Y7b/Alliances?node-id=254%3A8165) file after new Slippers release
## Page(s)
Which page(s) are involved in this request?
* `[Find a Alliance](https://about.gitlab.com)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jariasc-ext
- [ ] Consulted: @laurenbarker @ctsang-ext
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Change the icons after a new Slippers version with updated icons
## 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 | 114,764,373 |
2022-09-09 21:35:07.170
|
ENG: Find a Alliance Partner Page - Feedback items
|
## Goal
Solve feedback items on the `Find Alliance Partners` page mentioned [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/982#note_1095473050)
| Comment | In review app | In design |
| ------ | ------ | ------ |
| Can we make sure to show all the body text? |  | c |
| Under Featured Partners", let's remove the extra card (digital ocean) for now |  | none |
| Is it possible to move the caret/arrow closer to the text for the double lined links? |  | none |
| Can we reorder the partner list so that it matches the button list? So instead of starting with "Cloud partners," we start with "API Clients"? |  |  |
| Also can we add headers so it's easier to skim as someone scrolls down? |  |  |
| Fix all horizontal icons so their readable |  |
## Page(s)
Which page(s) are involved in this request?
* `[Find Alliance](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)
- [x] DRI: @jariasc-ext
- [x] Consulted: @laurenbarker, @ctsang-ext
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Fix feedback items from [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/982#note_1095473050)
## 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 | 114,761,124 |
2022-09-09 20:07:20.868
|
UX: Localization Language Selector
|
## Goal
We would like to have a language selector to allow our users to access the website in multiple languages.
### Jobs To Be Done
* **Situation**: *When a user visits a page that has other languages available, a drop down displays the offers choices between them*
* **Motivation**: *We want to communicate to users that a page is available in different laungauges*
* **Outcome**: *So we can increase the effectiveness of our marketing webist*
## Page(s)
Which page(s) are involved in this request?
* [Homepage](about.gitlab.com)
* [Why Gitlab] (https://about.gitlab.com/why-gitlab/)
* [Pricing Page] (https://about.gitlab.com/pricing/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ctsang-ext
- [ ] Consulted: @Tinaliseng @lduggan
- [ ] Informed: @fqureshi @laurenbarker
## In scope
What is within scope of this request?
- [ ] A UX design for the language selector
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [X] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 114,754,937 |
2022-09-09 17:35:21.168
|
Remove /learn/ pages
|
## Goal
As discussed here: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/110922#note_1093272291
| 1 |
28,847,821 | 114,754,832 |
2022-09-09 17:32:20.234
|
Add in-review label/column to iteration boards
|
## Goal
As discussed in: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/edit
Automate the addition of the label when an MR is created
| 2 |
28,847,821 | 114,696,340 |
2022-09-08 22:12:40.855
|
ENG: Update To top button on Learn page
|
## Goal
We need to update the button on the [/learn](https://about.gitlab.com/learn) page as well (remove border & update the purple to 900) per this Slippers [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/issues/202)
## Page(s)
Which page(s) are involved in this request?
* `[Learn](https://about.gitlab.com/learn)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] update the button
- [ ] 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 | 114,695,045 |
2022-09-08 21:26:04.369
|
ENG: KubeCon NA 2022 LP / Capture feedback
|
## Goal
Opening this issue to capture feedback for MVC 1 of the KubeCon NA 2022 LP.
## Page(s)
Which page(s) are involved in this request?
* Not yet deployed
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jgarc `@amandawshen`
- [ ] Informed: @justin.vetter
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 114,689,553 |
2022-09-08 19:20:18.458
|
ENG: Nav | Add DevSecOps and Agile Delivery in the Solutions section of the Nav
|
## Goal
We would like to DevSecOps and Agile Delivery solution pages under the solutions section of the Nav.
### Jobs To Be Done
* **Situation**: *When a user is looking for a solution some of our toped searched pages are not in the nav*
* **Motivation**: *We want to help the user finding the content they are searching for*
* **Outcome**: *So we can give users an easier path to solutions content*
## Page(s)
Which page(s) are involved in this request?
* [DevSecOps](https://about.gitlab.com/solutions/dev-sec-ops/)
* [Agile Delivery](https://about.gitlab.com/solutions/agile-delivery/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `@Tinaliseng`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Adding links to DevSecOps and Agile Delivery solution pages under the solutions section of the Nav
- [ ] Deliverable 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 114,686,148 |
2022-09-08 17:59:29.319
|
ENG: Adding Great Place to Work badge to GitLab careers site
|
## Goal
We would like to add a section to the GitLab careers site that highlights we are Great Place to Work certified which will provide a proof point about what it's like to work here as measured by the ratio of site visits to applications over time.
This section was designed as part of [this issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1267).
Here's the [figma](https://www.figma.com/file/JhFZCIRo8AoWrLIFDEOtL4/Careers?node-id=7%3A399).
Also dropping a mock for easy reference here:
### Jobs To Be Done
* Design a section for our careers page using an existing design pattern to highlight the attached badge and content provided by the talent brand team.
* The idea here is that we want people who visit our careers site to know that we are a Great Place to Work.
* So, they are more likely to apply for a job if there is an open role that's the right fit.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/jobs/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker @drogozinski
- [ ] Informed: Devin to inform People Leadership Group, Ray/Michael to inform marketing as needed
## In scope
What is within scope of this request?
- Designing a small section to highlight our Great Place to Work certified badge and provided copy
- Creating the MR to add that new section seamlessly into the careers site.
- Provided copy: At GitLab, being a great place to work means building a workplace where everyone can contribute and anyone can thrive. We aim to uphold that ideal in every country where we employ GitLab team members.
- Button text: See our employer awards
- Button link: <https://about.gitlab.com/handbook/people-group/employment-branding/content-library/#awards-and-lists-recognizing-gitlab-as-a-great-place-to-work>
## 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 | 114,685,712 |
2022-09-08 17:43:26.673
|
ENG: Solutions/ devops-platform / update header to updated brand
|
### Describe the Bug
Update the main header on [solutions/devops-platfomr](https://about.gitlab.com/solutions/devops-platform/) to match the other /solutions heroes ([example](https://about.gitlab.com/solutions/delivery-automation/))
Change this:
To this:
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/devops-platform/
## 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 | 114,685,321 |
2022-09-08 17:33:09.612
|
ENG: solutions LP / Update "Join GitLab" CTAs
|
## Goal
Update all instances of "Join GitLab" CTAs on /solutions pages. The wording is off-brand and unclear.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/enterprise/
* **Primary**: `Start your free trial`
* **Secondary**: `Talk to an expert`
* 
* https://about.gitlab.com/solutions/compliance/
* https://about.gitlab.com/solutions/dev-sec-ops/
* https://about.gitlab.com/solutions/agile-delivery/
* **Primary**: `Start your free trial`
* **Secondary**: `Learn about pricing`
* 
cc: @dennischarukulvanich please update the above CTAs if you have other suggestions.
## 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
| 2 |
28,847,821 | 114,685,148 |
2022-09-08 17:29:37.783
|
Enable markdown in support copy component - part 2
|
## Goal
This issue is part two of enabling markdown in the support copy component.
### Jobs To Be Done
* **Situation**: *When a update is needed to our support pages, content is supplied using markdown*
* **Motivation**: *We want to make it easier for the support team to self serve updates to these pages*
* **Outcome**: *So we can increase cross functional collaboration*
## Page(s)
Which page(s) are involved in this request?
* TBD update list
* All other content files in [/content/support/](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/support)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mduque-ext
- [ ] Consulted: @laurenbarker @jcolyer
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Enable copy markdown support component to be consumed by the support pages
- [ ] Update all content supplied to the support/copy-markdown.vue component to markdown
## Out of scope
What is out of scope and not part of this iteration?
- Changes to the template
- Changes to any content - other than `HTML` to `MD` in `yml` files.
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 114,617,743 |
2022-09-07 22:15:58.004
|
Document approval flow process in handbook
|
## Goal
We would like to document the marketing site approval process in the handbook. It should include the following:
- What the process is and why it exists
- The four approval flows, from minor to major change
- What the approval labels are
### Jobs To Be Done
* **Situation**: *When anyone is looking for information on what the approval process is and steps, they refer to our handbook*
* **Motivation**: *We want to create a single source of truth for this process*
* **Outcome**: *So we can communicate it out effectively*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/handbook/marketing/digital-experience
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create a new page OR edit an existing handbook page. Your choice - where does this fit in best?
- [ ] Collaborate on this process with Digital Experience following [GitLab's handbook first documentation strategy](https://about.gitlab.com/company/culture/all-remote/handbook-first-documentation/)
- [ ] Announcement in #whats-happening-at-gitlab channel
## 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 | 114,617,649 |
2022-09-07 22:10:26.083
|
Apply approval flow labels to merge request template for Buyer Experience
|
## Goal
We would like to iterate on Buyer Experience merge request templates to reflect the approval flow process documented in our handbook.
### Jobs To Be Done
* **Situation**: *When anyone creates a merge request in Buyer Experience, it describes what label to apply for the approval flow process depending on the type of change.*
* **Motivation**: *To ensure the proper stakeholders review a change to the marketing site.*
* **Outcome**: *So we can ensure changes are reviewed.*
## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/.gitlab/merge_request_templates
## 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?
- [ ] Iterated on existing merge request template with instructions on how to apply a approval flow label and which one.
## 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 | 114,617,046 |
2022-09-07 21:44:57.786
|
Partners: Links to 404 pages
|
## Goal
Partner links to a 404 page: https://about.gitlab.com/partners/technology-partners/
- Microsft Azure
- Oracle Cloud
- Amazee.io
- etc.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/partners/technology-partners/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker
- [ ] Informed: @ctsang-ext
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 114,601,325 |
2022-09-07 18:30:46.523
|
ENG: /features/continuous-integration/ - side nav is missing
|
### Describe the Bug
Left side nav is missing from https://about.gitlab.com/features/continuous-integration/
### What's my browser?
Chrome
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/continuous-integration/
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 114,597,791 |
2022-09-07 17:28:00.393
|
Create approval flow labels
|
## Goal
We would like to create approval flow labels from minor to major change for all Digital Experience repositories and the www-gitlab-com repository. As part of this issue, lets define what those labels are and create them.
### Jobs To Be Done
* **Situation**: *When a change is made to the marketing site, the correct approval label is applied to the merge request*
* **Motivation**: *We want to communicate the level of change via a label*
* **Outcome**: *The goal is for a member of GitLab’s Digital Experience team always to review an MR before it goes live on the Buyer Experience repo or key marketing pages in the www-gitlab-com repo.*
## Page(s)
Which page(s) are involved in this request?
* [Buyer Experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience)
* [Navigation repository](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation)
* [Slippers repository](https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui)
* [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-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?
- [ ] Create group level labels for Digital Experience
- [ ] Create project level labels for www-gitlab-com
## Out of scope
What is out of scope and not part of this iteration?
- Automation or bot work
| 1 |
28,847,821 | 114,538,762 |
2022-09-06 22:33:44.138
|
Contact Page: Marketo Form Fields for Google Analytics
|
## Goal
Related: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1260#note_1086859242
Marketo forms has hidden `<input>` fields to capture the Google Analytics client ID and tracking ID.
**Method** <br/>
This script on Tag Manager fires on DOM Ready across all about.gitlab.com pages, which retrieves the IDs and appends them on the form upon a form submission:<br/>
<img src="/uploads/7a95f17d96e878c4e5b0daa0a56ea94c/Screen_Shot_2022-09-06_at_3.07.34_PM.png" width="600">
**Example:**<br/>
On the https://about.gitlab.com/sales/ page, you can see the `gaclientid__c` and `gatrackid__c` values populate the `<input>` fields upon a form submit: <br/>
<img src="/uploads/4330521db48d740c182b192c7fec5791/qa.gif" width="900">
**Engineering Issue**<br/>
There are two forms on this page: https://about.gitlab.com/company/contact/ with duplicated scripts for each form (not to mention the script on Tag Manager as well). Only the Newsletter script works, the Security one doesn't.
Are there too many duplicated scripts? Or is the Security script not working properly? Also, should I pause the script on Tag Manager from firing on this page?
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/company/contact/
## 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`
## 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 | 114,537,374 |
2022-09-06 21:42:49.828
|
ENG: Alliance Partners Search
|
## Goal
We would like to have an intuitive search on the Alliances Page in order to help the User's to find quick and easy an Alliance Partner
### Jobs To Be Done
* **Situation**: When we arrive to the Alliance Page
* **Motivation**: We want to have a search field with suggestions
* **Outcome**: So we can easily find an Alliance Partner
## Page(s)
Which page(s) are involved in this request?
* [Alliances](https://about.gitlab.com/partners/technology-partners/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] A search input that finds the results from the search criteria or a search input with suggestions from the items in the partners list
## 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.