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 | 105,624,002 |
2022-03-28 14:12:56.883
|
ENG: Template for Solutions page - by technology
|
## Goal
This issue is for engineering to ensure the 4 solution by technology pages look acceptable in the refresh branch.
| 4 |
28,847,821 | 105,622,656 |
2022-03-28 13:53:00.500
|
ENG: Main Support page
|
## Goal
We would like to apply a new template the support page.
### Jobs To Be Done
* **Situation**: *The support page does not match are new brand.*
* **Motivation**: *We want to apply a new template.*
* **Outcome**: *So we can be consistent.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/
* [Figma Redesign](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=388%3A12778)
* [Main Support page copy deck](https://docs.google.com/document/d/14QciHeozCNpNg_hAjXhO9J5I5jf6BXS1lx8OO-YYMKY/edit?usp=sharing)
*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @ctsang-ext @jcolyer
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create new template
- [ ] Apply to support page
- [ ] Apply content
- [ ] Ship to production
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 10 |
28,847,821 | 105,622,447 |
2022-03-28 13:49:55.253
|
ENG: Getting Started
|
Work based on https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/344
Designs in https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=241%3A760
## Steps:
- [x] Create a content model based on Figma design with Lorem Ipsum
- [x] Build out semantics
- [x] Use Slippers components where available to fill in design
- [ ] Create custom components as necessary
- [ ] Identify Slippers gaps, cover them, and open issues in Slippers about them.
| 8 |
28,847,821 | 105,620,842 |
2022-03-28 13:27:35.937
|
ENG: Pricing V2 Talk to an expert/Contact sales
|
## Goal
Implement the 2 purple charcoal cards, Talk to an Expert and Contact Sales. This is NOT the "Take the next step" section.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 2 |
28,847,821 | 105,620,744 |
2022-03-28 13:25:27.129
|
ENG: Pricing V2 Pricing FAQ
|
## Goals
Implement FAQ section of the pricing page.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 6 |
28,847,821 | 105,620,623 |
2022-03-28 13:23:40.370
|
ENG: Pricing V2 Add-ons
|
## Goal
Implement the add-ons section of the pricing page. Check with the Jam3 slack channel for changes.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 2 |
28,847,821 | 105,620,499 |
2022-03-28 13:21:47.413
|
ENG: Pricing V2 Features Table
|
## Goal
Implement features table on the pricing page.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 6 |
28,847,821 | 105,620,306 |
2022-03-28 13:18:46.816
|
ENG: Pricing V2 Tiers
|
## Goal
Create the tier carousel
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 6 |
28,847,821 | 105,620,121 |
2022-03-28 13:16:27.013
|
ENG: Pricing V2 Header
|
## Goal
Implement just the header on the Pricing page.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 1 |
28,847,821 | 105,617,797 |
2022-03-28 12:38:30.607
|
ENG: Homepage Awards
|
## Goal
This section was to undergo revisions, whoever the engineer is, please check with @jhalloran before starting!
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 2 |
28,847,821 | 105,617,764 |
2022-03-28 12:37:52.843
|
ENG: Free Trial/Talk to an Expert Component
|
## Goal
Create the Free Trial/Talk to an Export section. This component exists on both the Homepage and the Pricing page
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 2 |
28,847,821 | 105,617,718 |
2022-03-28 12:37:25.721
|
ENG: Homepage Resources
|
## Goal
Implement the resources section of the homepage.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 4 |
28,847,821 | 105,617,664 |
2022-03-28 12:36:45.708
|
ENG: Homepage Quotes
|
## Goal
Create the quote carousel section of the homepage.
Design: https://www.figma.com/file/hKvIRhVlrgXrB1WcyuDBiQ/Home-Page-Refresh-2022-03-29?version-id=1737463174&node-id=2%3A231
| 4 |
28,847,821 | 105,617,616 |
2022-03-28 12:36:03.607
|
ENG: Homepage Customer Logo's
|
## Goal
Create the company logo's section of the homepage.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 1 |
28,847,821 | 105,617,532 |
2022-03-28 12:34:42.122
|
ENG: Homepage Lifecycle
|
## Goal
Create the DevOps lifecycle section of the homepage.
- We're NOT doing the draggable scrub bar this iteration.
The carousel has already been implemented, can re-use that functionality.
Design/Figma: https://www.figma.com/file/hKvIRhVlrgXrB1WcyuDBiQ/Home-Page-Refresh-2022-03-29?node-id=0%3A1
| 6 |
28,847,821 | 105,617,444 |
2022-03-28 12:33:37.782
|
ENG: Homepage Solutions
|
## Goal
Create the solutions section on the homepage.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 4 |
28,847,821 | 105,617,390 |
2022-03-28 12:32:50.281
|
ENG: Homepage Hero
|
## Goal
Create the hero, CTA. banner on the homepage. This includes the carousel feature on the right, the carousel logic has been implemented on the BE site, no need to re-create.
First prototype: https://gitlab.slack.com/archives/C034XUCC1PB/p1648141534252029
| 3 |
28,847,821 | 105,469,326 |
2022-03-25 02:35:04.620
|
CNT: Net new page - Solutions - Software Delivery Automation
|
## Goal
We would like to get content for a net new page which will improve our new site infrastructure as measured by increased trials and adoption.
### Jobs To Be Done
* **Situation**: *When a user enters our site... or when they're searching for continuous software compliance...*
* **Motivation**: *they want to learn how to stay compliant with regulations and policies without slowing down software delivery...*
* **Outcome**: *so they can make an informed choice about whether to try or buy GitLab Ultimate.*
## Page(s)
Which page(s) are involved in this request?
- New page needed
- See Existing page for reference: https://about.gitlab.com/solutions/delivery-automation/
- Related: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/delivery-automation/
- [Jam3 design brief](https://docs.google.com/document/d/1lu9-Izo7j1RG22hlxW4SdJyuepxdUGGbd8CCOvPweRs/edit#)
- [Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=69%3A2485)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @supadhyaya
- [ ] Consulted: @Tinaliseng @KristinaWeis @cblake
- [ ] Informed: @jhalloran @mpreuss22
## In scope
What is within scope of this request?
- [ ] Net new copy for page
## Out of scope
What is out of scope and not part of this iteration?
- TBD
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 105,456,412 |
2022-03-24 20:28:57.789
|
Enable Free Trial url to accept string parameters
|
## Goal
This link (https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org) is used in 100,000s of self managed instances. So we need to get that URL working correctly. Right now - it does not. It works without index.html, but we can't update that link on all the self managed instances. So we need to enable it in the Buyer Experience repository.
### Jobs To Be Done
* **Situation**: The self-managed Epic discovery links to `https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org` which is broken
* **Outcome**: When a user clicks on the epic discovery link from the product, it is properly rendered.
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org
* https://gitlab.com/gitlab-org/gitlab/-/issues/355655#note_887854257
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @a_akgun
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Enable https://about.gitlab.com/free-trial/index.html?return_to=https%3A%2F%2Fgitlab.example.org
## Out of scope
What is out of scope and not part of this iteration?
- slipers UI or www-gitlab-com 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
| 1 |
28,847,821 | 105,400,803 |
2022-03-24 06:28:52.659
|
/sales/ marketo form is getting displayed 3x
|
## Goal
Based on this [slack conversation](https://gitlab.slack.com/archives/CN8AVSFEY/p1648092410352809)
The Marketo form on the /sales/ page is getting displayed 3x
| 1 |
28,847,821 | 105,374,848 |
2022-03-23 19:42:43.542
|
Bump Slippers Version 1.0.6
|
## Goal
Pull in latest slippers-ui code
| 1 |
28,847,821 | 105,369,783 |
2022-03-23 18:02:21.787
|
Add data attributes to nav sign-in button
|
## Goal
GA data dropped for the Sign In link click within the header on about.gitlab.com.
<img src="/uploads/16335cb226181db5785944237e0a38a2/Screen_Shot_2022-03-23_at_11.19.59_AM.png" width="500">
Please add back the `data-nav="login"` attribute to the Sign In button:
<img src="/uploads/0eb3c8f31ebd0d47c871978de1dbb9dd/Screen_Shot_2022-03-23_at_11.09.56_AM.png" width="500">
### Jobs To Be Done
* **Situation**: When users click on the Sign In link
* **Motivation**: We want to place a data-* attribute
* **Outcome**: So we can capture the Sign In click event.
## 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: @dennischarukulvanich
- [ ] Consulted: @mpreuss22
- [ ] 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
- [X] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 1 |
28,847,821 | 105,369,082 |
2022-03-23 17:15:24.829
|
Follow-up from "Removal of 155 stale images"
|
As we remove pages from the `www-gitlab-com`, assets are becoming obsolete. Lets write a script that removes unused assets from the repository. This will have compounding beneficial effects - every pipeline is faster, cloning the repository is faster, and the size the repository becomes smaller.
The first iteration of this script [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101054). Unfortunately, that script takes too long to run through the `www-gitlab-com` repository. For the next iteration of this script, we'll create an array of image filenames and search the repository once. This should reduce the amount of time it takes for the script to complete.
## In scope
What is within scope of this request?
- [x] Iterate on https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/scripts/cleanup-delete-stale-images.sh script that removes unused assets from the www-gitlab-com repository
- [x] Add script to buyer experience repository
---
`@tywilliams` outlined a good strategy to make this faster in the following discussion from gitlab-com/www-gitlab-com!101054:
- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101054#note_882910627): (+3 comments)
> @tywilliams Got any tips for making this script faster?
>
> It seems to go slow due to the size of the repository. It only found 9 images in 1 hour before I had to quit it since I'm about to pack up for the day.
>
> Should I just run it overnight and keep the computer from sleeping?
| 2 |
28,847,821 | 105,365,760 |
2022-03-23 16:41:34.036
|
Page deprecation support for www-101198
|
Time tracking for my support with https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101198
| 1 |
28,847,821 | 105,314,040 |
2022-03-22 22:15:30.339
|
Make sure all links in Buyer Experience are relative links
|
This is a follow up to a request from @mpreuss22 in [Slack](https://gitlab.slack.com/archives/CN8AVSFEY/p1647985950478389?thread_ts=1647985257.315629&cid=CN8AVSFEY):
> is there a way to dynamically set all links to go to pages within this experience? Currently they link out to the live site.
Michael is referring to the review app at [https://refresh.about.gitlab-review.app/](https://refresh.about.gitlab-review.app/). But more generally, this issue will happen to *any* review app, if we use absolute URLs.
Our lives will be a lot easier for local development, review app feedback, and production deployments if we use relative paths across this website.
As an example, an absolute path is: `https://about.gitlab.com/enterprise/`. Whereas the relative path would be `/enterprise/`.
The advantage of using the relative path is that it keeps users on the same root domain as they navigate a particular deployment. It also ensure that we don't accidentally click links and go to different environments in development.
This is the same approach we should take for images (until we get a digital asset management tool, which will change the strategy). Images should refer to relative file paths, and should exist in our repository.
I think the fix for this is for someone to go through and:
1. Search the entire Buyer Experience repository for references to `https://about.gitlab.com`
1. Convert the reference to be a relative link (where applicable - there may be some edge cases that really should always point to production, but I can't think of any off the top of my head)
1. We should consider a linter that will check for this, although truthfully I think that's a hard problem to solve, because sometimes we really truly need to write an absolute path (again, I can't think of when, but we might), and I don't love having linters check every single text file for these kinds of strings. It will slow down our CI. Personally, I would prefer to catch this in code review where we can. But if someone has a better, automated proposal, I'm all ears.
| 2 |
28,847,821 | 105,231,826 |
2022-03-21 20:14:40.137
|
Update release post instructions to new homepage
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 105,100,689 |
2022-03-18 18:06:08.458
|
DataLayer Updates for Contact Sales, Public Sector, and Self-Managed Trials
|
## Goal
DataLayer values for Contact Sales, Public Sector, and Self Managed Trials form submissions were accidentally updated to "Demo" recently. Conversions for these form types dropped on Google Analytics (Goals 11, 12, 20), and are counted towards the Demo conversion instead (Goal 15).
Revert the Marketo form submit dataLayer code back to the original values.
1. **about.gitlab.com/free-trial/**
Update Self Managed form submit dataLayer code back from `demo` to `trial`
2. **about.gitlab.com/solutions/public-sector/**
Update Private Section Contact Sales form submit dataLayer code back from `demo` to `public-sector`
3. **about.gitlab.com/sales/**
Update Contact Sales form submit dataLayer code back, from `demo` to `sales`
### Jobs To Be Done
* **Situation**: When users submit a form
* **Motivation**: We want to capture the event as a dataLayer
* **Outcome**: So we can make analyze leads generated by form type and calculate ROAS across marketing campaigns
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com/free-trial/
* about.gitlab.com/sales/
* about.gitlab.com/solutions/public-sector/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich
- [ ] Consult: @mnguyen4 @jahye1
- [ ] Informed: @mpreuss22 @MihaiConteanu
## Requirements
What are the requirements for this 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 | 105,098,059 |
2022-03-18 17:05:13.401
|
Deprecate remaining reseller items
|
Issue to track time spent on https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100917
| 1 |
28,847,821 | 105,094,982 |
2022-03-18 16:19:25.287
|
Update @gl-website group with www-gitlab-com project maintainers
|
Every community contribution MR submitted to the `www-gitlab-com` repository initiates a GitLab Bot message.
In this message, the @gl-website team is tagged. This group has one active member, @laurenbarker. The other member of the group is @MichaelPreuss, which is not an account. His real account is @mpreuss22.
We need to update this group to include the maintainers of the the `www-gitlab-com` repository and remove the Digital Experience team members.
Here is an example of the bot message:
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100916#note_879874897
| 1 |
28,847,821 | 104,963,258 |
2022-03-17 02:25:55.276
|
Deprecate a fourth batch of non-redirect pages in www-gitlab-com
|
Based on https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0
Deprecates the remaining pages in that spreadsheet. Doing a larger batch to clear 'em all out:
- [x] | https://about.gitlab.com/resellers/pillar-global-solutions/ |
- [x] | https://about.gitlab.com/resellers/project-research/ |
- [x] | https://about.gitlab.com/resellers/releaseteam/ |
- [x] | https://about.gitlab.com/resellers/slexn/ |
- [x] | https://about.gitlab.com/resellers/softmart/ |
- [x] | https://about.gitlab.com/resellers/soporte-libre/ |
- [x] | https://about.gitlab.com/resellers/swnetwork/ |
- [x] | https://about.gitlab.com/resellers/telstra/ |
- [x] | https://about.gitlab.com/resellers/thinknyx/ |
- [x] | https://about.gitlab.com/resellers/tl-consulting/ |
- [x] | https://about.gitlab.com/resellers/twoseed/ |
- [x] | https://about.gitlab.com/resellers/vertical-sysadmin/ |
- [x] | https://about.gitlab.com/webcast/scaling-remote-with-gitlab/ |
- [x] | https://about.gitlab.com/resellers/norseman/ |
- [x] | https://about.gitlab.com/resellers/softworks/ |
| 1 |
28,847,821 | 104,962,163 |
2022-03-17 01:28:45.726
|
Remove third batch of 10 pages from www-gitlab-com (reprise)
|
From https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0
Remove:
- [x] | https://about.gitlab.com/resellers/gitlabhost/ |
- [x] | https://about.gitlab.com/resellers/goldman-information-services/ |
- [x] | https://about.gitlab.com/resellers/hanul-it/ |
- [x] | https://about.gitlab.com/resellers/ig-corporate-solutions/ |
- [x] | https://about.gitlab.com/resellers/lsd-information-technology/ |
- [x] | https://about.gitlab.com/resellers/lyra-infosystems/ |
- [x] | https://about.gitlab.com/resellers/megazone-cloud/ |
- [x] | https://about.gitlab.com/resellers/new-context/ |
- [x] | https://about.gitlab.com/resellers/nous-infosystems/ |
- [x] | https://about.gitlab.com/resellers/onyx-point/ |
| 1 |
28,847,821 | 104,952,533 |
2022-03-16 21:06:07.490
|
Remove batch of 10 pages from www-gitlab-com (this time with feeling)
|
From https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0
- [x] | https://about.gitlab.com/resellers/almtoolbox/ |
- [x] | https://about.gitlab.com/resellers/cxrus/ |
- [x] | https://about.gitlab.com/resellers/deviniti/ |
- [x] | https://about.gitlab.com/resellers/dixit/ |
- [x] | https://about.gitlab.com/resellers/dx-solutions/ |
- [x] | https://about.gitlab.com/resellers/eddr-software/ |
- [x] | https://about.gitlab.com/resellers/emerasoft/ |
- [x] | https://about.gitlab.com/resellers/fierce-software/ |
- [x] | https://about.gitlab.com/resellers/fujitsu-australia/ |
- [x] | https://about.gitlab.com/resellers/git/ |
| 1 |
28,847,821 | 104,951,154 |
2022-03-16 20:46:48.606
|
tabs-menu component mobile regression
|
https://gitlab.slack.com/archives/G01JH8CA8F3/p1647452033097559
| 1 |
28,847,821 | 104,950,738 |
2022-03-16 20:39:45.466
|
Remove batch of 10 pages from www-gitlab-com
|
From https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0
- [x] | https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/license/ |
- [x] | https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/product-gaps/ |
- [x] | https://about.gitlab.com/devops-tools/ibm-apm-vs-gitlab/ |
- [x] | https://about.gitlab.com/devops-tools/jenkins-vs-gitlab/news/ |
- [x] | https://about.gitlab.com/devops-tools/jenkins-x-vs-gitlab/ |
- [x] | https://about.gitlab.com/devops-tools/misc/ |
- [x] | https://about.gitlab.com/devops-tools/misc/tool-template.html |
- [x] | https://about.gitlab.com/devops-tools/missing/ |
- [x] | https://about.gitlab.com/devops-tools/new-template/ |
- [x] | https://about.gitlab.com/devops-tools/tekton-vs-gitlab/ |
| 1 |
28,847,821 | 104,938,189 |
2022-03-16 16:33:20.264
|
Remove batch of 10 pages from www-gitlab-com
|
Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/492
Removing these pages in https://docs.google.com/spreadsheets/d/1sxaZn4IrCxHJhYInOiNJkSX2iiJaEKLp_dqkkmMqiFg/edit#gid=0
- [x] | https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/comparison-methodology/ |
- [x] | https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/evaluation-questions/ |
- [x] | https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/news/ |
- [x] | https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/atlassian-pricing/ |
- [x] | https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/frequently-asked-questions/ |
- [x] | https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/key-features/ |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-BDM.html |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-KeyFeatures.html |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-License.html |
- [x] | https://about.gitlab.com/devops-tools/bitbucket/Bitbucket-Questions-Concerns.html |
- [x] | https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/key-differentiators/ |
| 1 |
28,847,821 | 104,804,939 |
2022-03-14 20:47:43.033
|
Move canonical url into nuxt.config.js
|
## Goal
As per [this conversation](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/292#note_874236654), we should handle canonical url paths in the nuxt.config.js file, rather than in the layout/default.vue file.
| 1 |
28,847,821 | 104,799,754 |
2022-03-14 19:28:05.857
|
CTA component mobile bugs
|
When i was trying to [fix bugs](https://gitlab.slack.com/archives/CN8AVSFEY/p1647044055168979) last Friday evening I found this 
Investigate further
| 1 |
28,847,821 | 104,795,980 |
2022-03-14 18:49:20.415
|
Spike a better solution for handling data in Nuxt pages
|
## Goal
We'd like to manage the content in the Nuxt site in a more consistent, extensible, flexible way.
The pages this matters most for are in the upcoming work. `@mpreuss22` gave us the [rundown of our current commitment in Slack]():
Goal is to deliver 10 amazing, newly designed pages with the rest of the site being on brand, live by April 27th:
Tier 01 (Doing 2nd): 3-4 page templates - Complete new vision, design, and content
* Homepage
* Pricing Page
* Solutions / Features Pages
* Install (stretch)
Tier 02 (Doing 3rd): 6-7 page templates - Well considered new design, significant new content, limited new branded/image/motion assets
* Category Leadership (Currently called Topics)
* Demo
* Enterprise
* SMB
* DevOps Lifecycle Pages
* Getting Started
* Contact Sales
Tier 03 (Doing 1st): - New coat of paint: updated fonts, colours, logos
Everything else: https://docs.google.com/spreadsheets/d/1ualGLPCyFjEpiskrfAe2ftqoTAw8t56lO1LMzMT7Ojo/edit
So to start, I'm going to look at the Tier 01 pages and do the following:
1. See which, if any, we have represented in `content`
1. Take a look at how their page level `.vue` files consume that data
1. Identify common data structures, identify oddities and outliers (stuff that needs special handling)
1. Write up a spec for how we should structure data to be consumed by pages
1. Pitch that spec to @ndubord as a first iteration
Once I do that, I'll write up an interface and try it out on the Homepage. I'll put together more specific issues for each page as I go.
I'm going to timebox this to about a day-and-a-half, and see how far I can get on it. Once I know more, I'll add additional points, add additional issues, etc.
| 3 |
28,847,821 | 104,790,019 |
2022-03-14 16:32:57.631
|
Automate removal of unused assets from www-gitlab-com
|
## Goal
As we remove pages from the www-gitlab-com, assets are becoming obsolete. Lets write a script that removes unused assets from the repository. This will have compounding beneficial effects - every pipeline is faster, cloning the repository is faster, and the size the repository becomes smaller.
## Page(s)
Which page(s) are involved in this request?
* 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: @laurenbarker
- [ ] Consulted: @ndubord
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create script that removes unused assets from the www-gitlab-com repository
- [ ] Remove the unused assets
## Out of scope
What is out of scope and not part of this iteration?
- Asset management in the Buyer Experience repository
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 104,785,332 |
2022-03-14 15:51:36.780
|
ENG: Import new Slippers into BE Refresh branch
|
## Goal
We need to create a new refresh branch to house the updated Slippers styling (lets call it 2.0.0). This 2.0.0 package will need to be imported into the BE refresh branch.
| 6 |
28,847,821 | 104,655,238 |
2022-03-12 06:25:35.724
|
regressions on buyer's experience repository
|
https://gitlab.slack.com/archives/CN8AVSFEY/p1647044055168979
| 1 |
28,847,821 | 104,789,874 |
2022-03-11 23:32:33.509
|
Visit our [Support Page] button does not display on the sales "Talk to an Expert" page
|
This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/
This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.
#### What is/are the relevant URL(s)
[https://about.gitlab.com/sales/](https://about.gitlab.com/sales/)
#### Briefly describe the bug
Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned.
`On the inbound Sales "Talk to an Expert" form fill page, the "Visit our Support Page" button is not displaying. Instead there is code showing rather than the URL button.`
[Screenshot attached]
#### If possible, please specify how to reproduce the bug
`You will see it on the top left of the page`
#### Please provide any relevant screenshots or screencasts
How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/
```
#### What is your window size, browser, operating system, and versions
Please use the following website to determine your browser specifications and provide a link developers can follow:
What is my browser https://www.whatsmybrowser.org
`https://www.whatsmybrowser.org/b/6N8E8`
#### What computing device are you using?
Please list the brand and model (Example: Samsung Galaxy S 10 Plus)
`Mac Mini`
### What type of input are you attempting to use?
Webpage interactivity is often tied to a specific device event.
- [ ] Touchscreen
- [ ] Touchpad
- [X] Mouse click
- [ ] Mouse click and drag
- [ ] Scrollwheel
- [ ] Keyboard
- [ ] Stylus
- [ ] Other (please specify)
#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?
- [X] I tried a fresh incognito window & it had no impact.
- [ ] The problem goes away when using an incognito window.
- [ ] The problem only happens when certain cookies are set to a specific value (please specify below).
#### Please list any browser plugins you have enabled
Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing.
`None`
#### Are you blocking javascript or any other resources?
Javascript is needed for certain website functionality.
- [ ] I AM blocking javascript or other resources.
- [X] I am NOT blocking javascript or other resources.
#### What is your geographic location
Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies.
`USA`
#### What type of network are you connected to?
**Type**
- [ ] Wired
- [X] Wifi
- [ ] Cellular (4G, 5G, etc)
- [ ] Satellite
- [ ] Other
`Insert details here if applicable`
**Location**
- [X] Home
- [ ] Workplace
- [ ] Travel facility (hotel, airport, conference center, etc)
- [ ] Public venue (restaurant, library, cafe, etc)
- [ ] VPN
- [ ] Other
`Insert details here if applicable`
**Hardware**
- [ ] I am behind a network security appliance such as a firewall
- [ ] I am using a pi-hole or other hardware-based traffic blocker
- [ ] Other
`Insert details here if applicable`
<!-- Please do not remove the items below, they are needed to automatically notify the relevant entities -->
/cc @gl-website
<!-- These labels will be automatically applied unless you edit or delete the following section -->
| 1 |
28,847,821 | 104,636,956 |
2022-03-11 19:04:52.642
|
ENG: Navigation update for IA Refresh
|
## Goal
Designs: https://www.figma.com/file/fPzNDCzZAUlAHuq9iQSFmn/Navigation-Refresh?node-id=0%3A1
| 4 |
28,847,821 | 104,629,805 |
2022-03-11 16:26:08.690
|
ENG: Features - Landing Page V1
|
## Goal
When updating the [Features page](https://about.gitlab.com/features/), I want to design a clear and succinct user experience, so potential customers can learn about the Features that GitLab offers.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Features](https://about.gitlab.com/features/)
Figma file: https://www.figma.com/file/XsnwxTLYPAN0j19vS6iSXm/Features-2.0?node-id=15%3A3641
## 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?
- [ ] UX 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:
- [ ] Engineering
| 6 |
28,847,821 | 104,573,535 |
2022-03-10 19:51:22.641
|
Pre-push Hook for linter
|
## Goal
We would like to have a pre-push hook to avoid having lint issues in the pipeline
### Jobs To Be Done
* **Situation**: *When someone does a commit to a Merge Request, sometimes the pipeline fails due to linter issues*
* **Motivation**: *We want to have a pre-push hook to detect linter issues before committing them to the pipeline*
* **Outcome**: *So we can avoid making multiple commits and going back and forth fixing linter issues*
## 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: @jariasc-ext
- [ ] Consulted: @laurenbarker @jgarc
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create a pre-push hook in the Buyer Experience Repo
## Out of scope
What is out of scope and not part of this iteration?
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 104,548,292 |
2022-03-10 12:48:24.069
|
H1 Heading Changed
|
The H1s on /topics pages have been removed and replaced with H2s. H1 headings are a ranking factor for search engines as they use the H1 heading to determine what the page is about.
Affected URLs:
| URL |
|--------------------------------------------------|
| https://about.gitlab.com/topics/ci-cd/ |
| https://about.gitlab.com/topics/devops-platform/ |
| https://about.gitlab.com/topics/devops/ |
| https://about.gitlab.com/topics/gitops/ |
| https://about.gitlab.com/topics/microservices/ |
| https://about.gitlab.com/topics/multicloud/ |
| https://about.gitlab.com/topics/serverless/ |
| https://about.gitlab.com/topics/version-control/ |
| 1 |
28,847,821 | 104,506,839 |
2022-03-09 20:36:51.957
|
Add Script to Webpages to Hide Web Navigation in PathFactory Tracks
|
## Goal
We would like to add a script to some of our webpages, so that we can hide the web navigation header and footer when the page is added to a PathFactory track, in order to improve user experience.
- [Example of a blogpost within a PF track](https://learn.gitlab.com/devsecops-aware/why-implementing-sec)
- [Example of a case study within a PF track](https://learn.gitlab.com/ci-purchase-prac1/goldman-sachs-gitlab)
Additional information about this project can be found [here](https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6077).
### Jobs To Be Done
* **Situation**: *When webpages are added to PathFactory tracks*
* **Motivation**: *We want them to look more organic and to display without the header/foot navigation*
* **Outcome**: *So we can provide a clean, intuitive user experience*
## Page(s)
Which page(s) are involved in this request?
* `All blog posts`
* `All case studies`
* [Pricing page](https://about.gitlab.com/pricing/)
- [x] @eirinipan to confirm that this is an accurate list
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @nikkiroth
- [ ] Consulted: @eirinipan @mpreuss22
- [ ] Informed: @jgragnola @amy.waller
## In scope
What is within scope of this request?
- [ ] Add the following to our web pages (once confirmed above). This will allow the function to hide the header and footer.
// --- Note: The code snippet needs to run after the elements in the script below are loaded. *---
```
<script>
var windowURL = window.location.search;
console.log(windowURL);
if (windowURL.indexOf('menu=hide') > -1 && window.self!= window.top){
document.querySelector('#global-nav ').style.display = 'none';
document.querySelector('.footer.footer').style.display = 'none';
}
</script>
```
## Out of scope
What is out of scope and not part of this iteration?
- Any other changes/edits/requests
## Requirements
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
| 3 |
28,847,821 | 104,502,766 |
2022-03-09 18:51:15.055
|
Follow up: Top Anchored navigation update
|
Top Anchored navigation component should not take the whole width of the page if there are just a few options. It should accommodate to the size of its content.
| 0 |
28,847,821 | 104,500,218 |
2022-03-09 17:47:29.619
|
Request: add child pages to the topic pages
|
## Goal
Go to market campaigns are launching for the quarter and there is new, supporting content that needs to be "made live" but that's not possible at this time.
### Jobs To Be Done
* **Situation**: *When I tried to post these two pages (https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100373 and https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100368) they didn't appear because the child topic pages aren't visible? ...*
* **Motivation**: *We want to support the go to market campaigns ongoing this quarter...*
* **Outcome**: *So we can drive traffic, get leads, convert......*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100373
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/100368
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: `vsilverthorne`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Deliverable 1 - posting those pages and turning that functionality back on
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1 - anything other than the above
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 104,432,669 |
2022-03-09 00:52:58.305
|
Remove duplicate eslint rule
|
Resolve eslint errors that are caused by catch all eslint ignore comments
| 2 |
28,847,821 | 104,430,446 |
2022-03-08 23:29:15.854
|
Update FAQ Schema function to take in and render markdown
|
Related to [485](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/485#note_867644026)
We want the ability for our FAQSchema function in `craftSchema.ts` to take in Markdown from YML files and render appropriate HTML tags.
A use case for this would be the CI/CD topics page's FAQPage schema that [contains unordered lists](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/96884/diffs#975ff1cbc57036d902929f48442254eea9dc1f92_149_0).
+a reminder to check and see if the topics/DevOps FaqPage schema is working in search engines.
| 2 |
28,847,821 | 104,418,214 |
2022-03-08 18:55:16.454
|
ENG: Update customer case studies landing page
|
| Relates to|
| ------ |
| https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/373|
## Goal
We would like to update the customer case studies page to the current content and Slippers UI.
## Page(s)
Which page(s) are involved in this request?
* [Customers](https://about.gitlab.com/customers/)
## Workfiles
- [Figma](https://www.figma.com/file/LvXKj0FACzSabahTD7zA5j/Customer-Stories-Landing-Page?node-id=15%3A3641)
- [Desktop Prototype](https://www.figma.com/proto/LvXKj0FACzSabahTD7zA5j/Customer-Stories-Landing-Page?page-id=15%3A3641&node-id=326%3A5872&viewport=241%2C48%2C0.44&scaling=min-zoom&starting-point-node-id=326%3A5872)
- [Mobile Prototype](https://www.figma.com/proto/LvXKj0FACzSabahTD7zA5j/Customer-Stories-Landing-Page?page-id=38%3A5133&node-id=474%3A7085&viewport=241%2C48%2C0.42&scaling=min-zoom&starting-point-node-id=474%3A7085)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: (insert engineer handle)
- [ ] Consulted: @Tinaliseng
- [ ] Informed: `Everyone` @ctsang-ext
## Out of scope
What is out of scope and not part of this iteration?
- Updates to single customer story pages
- Updates to the homepage customer stories section
## Requirements
What are the requirements for this request? Checklist 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 | 104,396,180 |
2022-03-08 14:35:05.994
|
Add filter to Featured Reports section - MVC2 of /analysts page
|
## Goal
We would like to filter by creator (Forrester, Gartner, IDC) in the Featured Reports section which will improve usability as measured by the control user will have on the rendered content + in time spent looking for information.
### Jobs To Be Done
* **Situation**: I load the /analysts page
* **Motivation**: I want to have a filter in the Featured Reports section
* **Outcome**: So I can filter the reports by creator
## 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: `@mduque-ext`
- [ ] Consulted: `@tinaliseng`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create filter for Featured Reports in the page
## Out of scope
What is out of scope and not part of this iteration?
- Any other work in this or another 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 | 104,117,304 |
2022-03-03 16:50:11.053
|
Homepage - Brag Wall Badge Updates
|
Related to gitlab-com/marketing/inbound-marketing/marketing-website#168.
Hey @Tinaliseng - our Winter 2022 badges just came out, and we've got some awesome new ones (Best ROI and the Top 50/100 ones are probably my fav)
All badges can be found [here](https://drive.google.com/drive/folders/1u9jK3dSbe21DI1nlXz7yAseloYDAziJQ?usp=sharing) in the G-drive, but I also believe you have [login access to G2](https://my.g2.com/gitlab/badges) if you need a different filetype (I uploaded PNG, G2 has SVG)
You can see where I've got an associated issue in my project [here](https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/6098)
Relating this to the first iteration.
ALSO if you still need the [Trust Radius badge link](https://www.trustradius.com/products/gitlab/reviews)
| 2 |
28,847,821 | 103,977,533 |
2022-03-02 16:51:23.379
|
IA Refresh - Add schema.org tags
|
## Goal
We would like to add schema.org tags to 10 key pages which will improve SERP as measured by search rankings for key word/pages.
## Page(s)
Which page(s) are involved in this request?
1. [Homepage](http://about.gitlab.com)
1. [Pricing Page](https://about.gitlab.com/pricing/)
1. [Install](https://about.gitlab.com/install/)
1. Why GitLab
1. Solutions
1. TBD
1. TBD
1. TBD
1. TBD
1. TBD
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @hsmith-watson
- [ ] Consulted: @ndubord @mpreuss22
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Adding appropriate schema.org tags to the above pages
## Out of scope
What is out of scope and not part of this iteration?
- Significant changes to structure of pages that is not already planned
## Requirements
What are the requirements for this 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 | 103,861,555 |
2022-03-01 00:55:37.005
|
Add missing OneTrust tag to /-/trials/select
|
@dennis106 [caught a view that's missing OneTrust](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/200#note_857867397). We should add the OneTrust partial to `ee/app/views/trials/select.html.haml`.
| 2 |
28,847,821 | 103,858,731 |
2022-02-28 22:31:58.245
|
ENG: Create placeholder Get Started page
|
## Goal
Create placeholder Get Started page with associated data in the Buyer Experience repo and merge it into the Refresh branch.
| 2 |
28,847,821 | 103,858,564 |
2022-02-28 22:26:13.562
|
ENG: Migrate /solutions/ landing page
|
## Goal
Migrate the www /solutions/ page to the Buyer Experience repo
| 4 |
28,847,821 | 103,858,419 |
2022-02-28 22:19:18.658
|
ENG: Create placeholder Pricing page
|
## Goal
Create placeholder Pricing page with associated data in the Buyer Experience repo and merge it into the Refresh branch.
| 2 |
28,847,821 | 103,858,330 |
2022-02-28 22:16:18.494
|
ENG: Create placeholder Why GitLab? page
|
## Goal
Create placeholder Why GitLab? page in the Buyer Experience repo and merge it into the Refresh branch.
| 1 |
28,847,821 | 103,858,094 |
2022-02-28 22:07:01.660
|
ENG: Run test AB experiment with Launchdarkly
|
## Goal
Run a live test experiment using LaunchDarkly to prepare for any fast-follow AB testing for Q3 OKR.
| 6 |
28,847,821 | 103,857,964 |
2022-02-28 22:03:13.072
|
ENG: Create re-useable navigation
|
## Goal
Create a Navigation/Footer that can be consumed by both the Buyer Experience repo and the www repo.
| 8 |
28,847,821 | 103,857,788 |
2022-02-28 21:56:58.641
|
Set up Contentful on behalf of Digital Experience
|
I'm going to set up a Contentful account for initial use while we explore it as a proof-of-concept with the Refresh and Information Architecture work going on this quarter.
| 2 |
28,847,821 | 103,849,612 |
2022-02-28 18:23:06.628
|
Investigate Contentful free tier
|
Can we use a free tier Contentful account with a shared login just to stand up the work we're doing in the Buyer Experience in the next couple of months as a proof of concept.
| 2 |
28,847,821 | 103,846,488 |
2022-02-28 16:52:38.242
|
UX: Navigation update - Minimal footer
|
## Goal
We would like to rethink the navigation based on the new buyer repo pages which will improve findability as measured by reduced bounce rate.
### Jobs To Be Done
* **Situation**: *When a user comes to GitLab...*
* **Motivation**: *they want to find the page they are looking for quickly and easily...*
* **Outcome**: *so they can make decisions or learn new information.*
## Page(s)
Which page(s) are involved in this request?
* Navigation
* [Figma designs](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=5021%3A9923)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: @Tinaliseng @ctsang-ext
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Updated minimal footer navigation layout
- [x] UI skin navigation with new brand guidelines
## Out of scope
What is out of scope and not part of this iteration?
- Header navigation
## Requirements
What are the requirements for this request? Checklist 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 | 103,846,462 |
2022-02-28 16:52:27.887
|
UX: Navigation update - Full footer
|
## Goal
We would like to rethink the navigation based on the new buyer repo pages which will improve findability as measured by reduced bounce rate.
### Jobs To Be Done
* **Situation**: *When a user comes to GitLab...*
* **Motivation**: *they want to find the page they are looking for quickly and easily...*
* **Outcome**: *so they can make decisions or learn new information.*
## Page(s)
Which page(s) are involved in this request?
* [Excel with explanations](https://docs.google.com/spreadsheets/d/1D9O84YDXxfjoRhUiwtWySe6Az6pQ2MsjiB6iqhUJHLU/edit?usp=sharing) - see column G for changes and column H for reasoning
* [Figma designs](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/branch/UYZLoPAD4pMunezYiaFhpW/Slippers_foundations?node-id=5021%3A9923)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: @Tinaliseng @ctsang-ext
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Updated footer navigation layout
- [ ] UI skin navigation with new brand guidelines
## Out of scope
What is out of scope and not part of this iteration?
- Header navigation
## Requirements
What are the requirements for this request? Checklist 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 | 103,846,444 |
2022-02-28 16:51:59.127
|
UX: Navigation update - Minimal header
|
## Goal
We would like to rethink the minimal header navigation based on the new buyer repo pages which will improve focus as measured by increased time on page.
### Jobs To Be Done
* **Situation**: *When a user comes to GitLab and they are in a funnel experience...*
* **Motivation**: *they want to be focused on the task at hand...*
* **Outcome**: *so they can make decisions or learn new information.*
## Page(s)
Which page(s) are involved in this request?
* Navigation
* [Figma designs](https://www.figma.com/file/fPzNDCzZAUlAHuq9iQSFmn/Navigation-Refresh?node-id=487%3A5261)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: @Tinaliseng @ctsang-ext
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Updated minimal header navigation layout
- [ ] UI skin navigation with new brand guidelines
## Out of scope
What is out of scope and not part of this iteration?
- Footer navigation
- Content blurbs for navigation items
## Requirements
What are the requirements for this request? Checklist 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 | 103,063,995 |
2022-02-25 16:20:58.012
|
Linked in Event Tracking for Gated Asset download
|
## Goal
Follow up from https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/238.
Here are the conversion tags that we have in LinkedIn that we are looking to get implemented. I am unsure how the conversion tags have been set up in the, so unsure where on the page these need to be added.
* Gated Asset download- `window.lintrk('track', { conversion_id: 1111282 });`
* PathFactory form submit event is hardcoded for GA. Would it be possible to add the LinkedIn conversion event code for Gated Asset right below this line? `ga('send', 'event', 'forms', 'submit', 'PathFactory');` 
### Jobs To Be Done
* **Situation**: *When we want to track Gated Asset downloads*
* **Motivation**: *We want to add LinkedIn conversion codes*
* **Outcome**: *So we can efficiently track the clicks of our users' data*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @dennis106 `
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 103,015,170 |
2022-02-24 20:32:10.017
|
Follow-up from "Resolve "Launch Darkly Integration""
|
The following discussion from !230 should be addressed:
- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/230#note_853364600): (+1 comment)
> **Suggestion:** Provide URL parameters that enable a reviewer to view both versions of an experiment.
>
> For example, in www-gitlab-com you can use `?experiment-review-control` to view the control variant
> and ?`experiment-review-test` to view the test variant.
>
> I'd consider this non-blocking @jgarc ... but we should address it in the next iteration.
NOT IN SCOPE
- [ ] https://docs.launchdarkly.com/home/code/gitlab
| 3 |
28,847,821 | 103,011,750 |
2022-02-24 18:50:50.758
|
UX: Homepage refresh for SKO / Add new brand
|
## Goal
Apply the new brand guidelines provided by Gold Front to a homepage design for the Sales Kick Off.
## Page(s)
Which page(s) are involved in this request?
* Homepage - Fimga mock only (no engineering required)
## Workfiles
- [Figma Mocks](https://www.figma.com/file/CgCuf1LVuEZH8DEijhAzCt/Home-Page-Refresh?node-id=0%3A1)
## Documents
- [Jam 3 Homepage brief](https://docs.google.com/document/d/1lu9-Izo7j1RG22hlxW4SdJyuepxdUGGbd8CCOvPweRs/edit#heading=h.n4tqr0k7lvyy)
- [Brand guides - PDF](https://drive.google.com/file/d/1zbHfV90kxI_PgTUXixEs-6p7F4VAGg7Y/view?usp=sharing)
- [Grand guides - Figma](https://www.figma.com/file/36n655EAUGJPz2DEwrjrOo/2022-GitLab---Brand-Design-Guidelines?node-id=2156%3A29)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran @ctsang @mpreuss22
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 104,785,363 |
2022-02-24 15:10:55.188
|
Create GA View to track Customer Portal and other purchasing flows
|
<!-- Please submit issue with the following format: As a _____ (role in marketing), I would like to ____________(need), so that ________________(reason).-->
<!-- Example: As GTM management, I would like to know that all Trials are MQLing, so that MQL metrics are accurate and we can rely on them for decision making.-->
## As a team focused on customer self-service transactions, I would like a dedicated GA View to provide fast reporting on trial and checkout flows without having to set up custom reports or drill down many levels.
# What we need to know:
## The problem
The Self-Service team would like to track sessions, pageviews, and events (clicks) on the areas of our marketing site and customer portal that our customers use to subscribe and grow. These areas of the site get relatively less traffic compared to marketing and handbook pages, and so are more challenging to report on using the default GA view.
## What specific questions do we need to answer?
- General default GA reporting (Audience, Acquisition, Content, Events) but specific to these parts of the site/customer portal
## What are your must-have's?
These subdomains and pages:
Subdomain:
* customers.gitlab.com
Pages within gitlab.com (regex match):
* /-/subscriptions
* /-/profile/usage_quotas
* /-/usage_quotas
* /trials/
* /pricing/
* /sign_up
* /trial_registrations/
## Do you have any specific metrics, categories or charts in mind?
No, standard GA
## Context
- Audience: Internal GitLab team members, especially Self-Service, Product Intelligence
- When will this likely deliver business value? Immediately
- Due date: ASAP
- Format: GA View
<!-- Please leave the label below on this issue -->
Related to gitlab-com/marketing/marketing-strategy-performance#612.
| 1 |
28,847,821 | 102,954,391 |
2022-02-23 20:28:27.138
|
retire-js-dependency_scanning
|
## Goal
We would like to retire-js-dependency_scanning in the www-gitlab-com pipeline.
### Jobs To Be Done
* **Situation**: *When any MR is merged with master it throws errors*
* **Motivation**: *We want to reduce these errors because the job is depreciated*
* **Outcome**: *So we can improve efficiency*
https://gitlab.slack.com/archives/CVDP3HG5V/p1645467364747489
| 1 |
28,847,821 | 102,890,843 |
2022-02-22 22:14:37.456
|
FAQ Schema
|
## Goal
We would like to enable FAQ schema on the Buyer Experience repository.
### Jobs To Be Done
* **Situation**: *When someone visits a page built with the Buyer Experience repository, FAQ Schema displays if data exists in the `yml` file.*
* **Motivation**: *We want to improve SEO*
* **Outcome**: *This was implemented on topics and solutions pages in www-gitlab-com to make search engine better understand page contents and display the pages in the form of Rich Snippets in SERPs.*
## Page(s)
Which page(s) are involved in this request?
* Topics
* Solutions
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @laurenbarker @hsmith-watson
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Enabling FAQ schema in the buyer experience repository
- [ ] Configuring FAQ schema for existing topic pages
- [ ] Configuring FAQ schema for solution pages
## Out of scope
What is out of scope and not part of this iteration?
- www-gitlab-com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 102,887,402 |
2022-02-22 20:55:48.553
|
CTA.vue component regression - some images wrapped in anchor tags not rendering correctly
|
Some images wrapped in an anchor tag are not rendering within the `cta.vue` component.
This issue impacted the following pages:
[/solutions/public-sector](https://about.gitlab.com/solutions/public-sector)
[/solutions/education](https://about.gitlab.com/solutions/education)
| 1 |
28,847,821 | 102,880,772 |
2022-02-22 17:51:07.515
|
Regression - Border around hero image on Solutions
|
## Goal
We would like to remove the grey border that exists around the hero image on https://about.gitlab.com/solutions/digital-transformation/.
https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/9e554ab3ae6df8c70efd3d41e2a11d7c/Screen_Shot_2022-02-18_at_14.14.02.png
## In scope
What is within scope of this request?
- [ ] Remove border
## Requirements
What are the requirements for this request? Checklist 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 | 102,708,898 |
2022-02-18 21:13:19.153
|
Slp-button / link regression
|
Noticed this on the topics children pages. Not sure if any other pages fall under this scope.
Currently:
Previous:
| 1 |
28,847,821 | 102,703,984 |
2022-02-18 18:49:39.671
|
Add import button GTM events in the combined groups/projects form
|
## Goal
This issue is related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/361, which will be closed with https://gitlab.com/gitlab-org/gitlab/-/merge_requests/81035.
The combined groups/projects form is [now a part of the free trial flow](https://docs.google.com/presentation/d/17e-EyBU7gHIZb_C0LrTfAuncLQW6q4LsuqIQ5qh0FTo/edit#slide=id.g110748f05b3_0_42).
The [old spec](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/uploads/63d466fbba4fca773f6c5a2a356a37c8/Gitlab_GTM_DataLayer_Spec_for_Free_Trial.pdf) had events handled separately for group/project forms. Now we need to combine them.
### Jobs To Be Done
* **Situation**: *When a user goes through the sign up flow*
* **Motivation**: *We want to track the import project GTM events*
* **Outcome**: *So we can measure free trials and other form interactions against Google Analytics data*
## Page(s)
Which page(s) are involved in this request?
* `gitlab.com/users/sign_up/groups_projects/new`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @tywilliams
- [ ] Consulted: @dennis106 @gdoud
- [ ] Informed: @mpreuss22
## In scope
Add the `saasTrialProjectImport` events to those buttons. But as we did in https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/361, we should change this event to `projectImport`, since the form is shown to regular user sign ups as well as trial sign ups.
We can use the `trial_onboarding_flow=true` parameter in the URL to filter against true/false.
I will preserve the other data points and track `'projectImport': '[PLATFORM]'` as we were before for which platform people click.
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [x] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 102,698,895 |
2022-02-18 16:42:56.502
|
Bump slippers-ui import to 1.0.2
|
## Goal
Import latest version of slippers
| 1 |
28,847,821 | 102,650,577 |
2022-02-17 21:56:54.595
|
ENG: /company/culture page is trying to render from Nuxt even though it only exists in www
|
Because we have a /company/culture/all-remote page, Nuxt thinks that [/company/culture](https://about.gitlab.com/company/culture/) is an existing path even though we technically don't have a page for that created in this repository. It currently is rendering the Free Trial CTA when I think it should be rendering the page from www-gitlab-com.
We should be able to add 'content/company/culture' to the route.ignore.js file in our project.
| 1 |
28,847,821 | 102,579,104 |
2022-02-17 00:26:44.425
|
ENG: Get Started - Install
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 5 |
28,847,821 | 102,579,027 |
2022-02-17 00:21:53.969
|
UX: Template for getting started
|
## Goal
We would like to have a template for primary getting started options, which will improve customer onboarding as measured by decreased support inquiries.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand how to begin setting up their GitLab account or other services...*
* **Outcome**: *so they can get started right away and without interruption.*
## Page(s)
Which page(s) are involved in this request?
- `[Figma File TBD](URL)`
- [Getting started](https://about.gitlab.com/get-started/)
New pages that will use this template:
- Get Started
- Free Trial
- Install
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: Carrie Tsang
- [ ] Consulted: @jhalloran @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Reusable UX template for getting started checklists
## Out of scope
What is out of scope and not part of this iteration?
- TBD
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 6 |
28,847,821 | 102,578,282 |
2022-02-16 23:41:21.391
|
ENG: Why GitLab over Artifactory
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 102,578,273 |
2022-02-16 23:40:53.870
|
ENG: Why GitLab over CircleCI
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 102,578,272 |
2022-02-16 23:40:39.578
|
ENG: Why GitLab over Jenkins
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 102,578,267 |
2022-02-16 23:40:24.188
|
ENG: Why GitLab over Atlassian (JIRA/Bitbucket)
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 102,578,264 |
2022-02-16 23:40:13.416
|
ENG: Why GitLab over GitHub
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 102,578,035 |
2022-02-16 23:28:03.085
|
ENG: Pricing - Why Premium?
|
## Goal
We would like to update the pricing tiers template and refresh the Why Premium page
### Jobs To Be Done
* **Situation**: *When a user clicks on the Why Premium page the current layout and content do not match our refresh*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Premium](https://about.gitlab.com/pricing/premium/)
* [Figma](https://www.figma.com/file/gG2foPvh4wW69kYwFVB5Vs/Why-Premium-Refresh?node-id=70%3A2787)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @jhalloran @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Move Premium page to BE repo
- [ ] Update template
## 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
| 8 |
28,847,821 | 102,578,015 |
2022-02-16 23:27:46.253
|
ENG: Pricing - Why Ultimate?
|
## Goal
We would like to use the updated pricing tiers template and refresh the Why Ultimate page
### Jobs To Be Done
* **Situation**: *When a user clicks on the Why Premium page the current layout and content do not match our refresh*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [Ultimate](https://about.gitlab.com/pricing/ultimate/)
* [Figma](https://www.figma.com/file/UAjKpOiXrvAlBT3HUkIgKw/Why-Ultimate-Refresh?node-id=0%3A1)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @jhalloran @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Use the updated pricing tiers template to update the Ultimate page
- [ ] Move Ultimate page to BE repo
## Out of scope
What is out of scope and not part of this iteration?
- Creating the updated pricing tiers template
## Requirements
What are the requirements for this request? Checklist 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 | 102,577,993 |
2022-02-16 23:25:50.451
|
ENG: Category Leadership Stages V1
|
## Goal
V1 means updating to new brand guidelines the following category leadership pages:
* https://about.gitlab.com/stages-devops-lifecycle/manage/
* https://about.gitlab.com/stages-devops-lifecycle/plan/
* https://about.gitlab.com/stages-devops-lifecycle/create/
* https://about.gitlab.com/stages-devops-lifecycle/verify/
* https://about.gitlab.com/stages-devops-lifecycle/package/
* https://about.gitlab.com/stages-devops-lifecycle/secure/
* https://about.gitlab.com/stages-devops-lifecycle/release/
* https://about.gitlab.com/stages-devops-lifecycle/configure/
* https://about.gitlab.com/stages-devops-lifecycle/monitor/
* https://about.gitlab.com/stages-devops-lifecycle/protect/
Additionally, will these pages use the existing content: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/stages-devops-lifecycle
| 4 |
28,847,821 | 102,577,990 |
2022-02-16 23:25:40.490
|
ENG: Category Leadership Monitor
|
## Goal
Apply new brand to current template and content.
| [refresh app](https://refresh.about.gitlab-review.app/stages-devops-lifecycle/monitor/) | https://about.gitlab.com/stages-devops-lifecycle/monitor /|
Related https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/447#note_896434962
## Requirements
What are the requirements for this request? Checklist 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 | 102,577,746 |
2022-02-16 23:12:30.013
|
ENG: Solutions - By Company Size - SMB
|
## Goal
We would like to apply the template to the SMB page.
## Page(s)
Which page(s) are involved in this request?
* https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=737%3A2963
* https://refresh.about.gitlab-review.app/small-business/
* [Content doc](https://docs.google.com/document/d/1QG_kbSlDjuEtpsJ8Wg_li95Mqa4GyOqRdiAUhEgNWgc/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jgarc
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 102,577,707 |
2022-02-16 23:09:30.900
|
ENG + UX Review: Solutions - By Technology - AWS
|
## Goal
We would like to iterate on the AWS partners page on the refresh branch.
Iterating on the AWS partners page will also effect the other partner pages.
### Jobs To Be Done
* **Review App**: https://refresh.about.gitlab-review.app/partners/technology-partners/aws/
* **Production**: https://about.gitlab.com/partners/technology-partners/aws/
* **Outcome**: AWS partners page on the refresh branch is updated with fonts, colors, and new branding.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Updating components in the refresh branch
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 2 |
28,847,821 | 102,577,606 |
2022-02-16 23:06:37.745
|
ENG: Solutions - By Solution - Delivery Automation
|
## Goal
We would like to ensure the delivery automation page is using the new template.
## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/delivery-automation/
* https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A722
## Resources
* [Content issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/580)
*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jariasc-ext
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist 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 | 102,569,492 |
2022-02-16 19:26:02.154
|
Document development process for Slippers and Buyer Experience
|
## Goal
We would like to document the process for using Slippers in the Buyer Experience repository after https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/187.
What is the process for adding a new variable?
What is the process for changing an existing variable?
When do we bump the Slippers version and how do we pull that into the Buyer Experience repository?
### Jobs To Be Done
* **Situation**: *When Digital Experience engineers use Slippers in the Buyer Experience repository, there use documentation available on how the two repositories work together.*
* **Motivation**: *We want to give clear guidance on how to develop with these tools.*
* **Outcome**: *So we can be efficient.*
## Page(s)
Which page(s) are involved in this request?
* Buyer Experience repository
* Slippers repository
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @ndubord
- [ ] Consulted: `Digital Experience team`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Answer questions from teammates in this issues on how to use these tools
- [ ] Creating documentation in the repositories or handbook
## Out of scope
What is out of scope and not part of this iteration?
- www-gitlab-com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 102,509,685 |
2022-02-16 00:16:51.008
|
Feature Branch for Rebrand
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 102,509,654 |
2022-02-16 00:14:19.311
|
ENG: Scaling your GitLab usage quick set up checklist
|
## Goal
We would like to apply the get started checklist template to a "scaling your GitLab usage quick set up checklist" page.
### Jobs To Be Done
* **Situation**: *There isn't a page for users to find information on how to scale their GitLab usage*
* **Motivation**: *We want to make it easy to scale their GitLab usage - upgrade, more CI minutes, more users, ect
* **Outcome**: *So we can improve conversion rates.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/get-started/scaling-gitlab
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Apply get started checklist template
- [ ] Fill with content
- [ ] Deploy to production
- [ ] Depreciate pages with duplicate content and set redircts
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 1 |
28,847,821 | 102,509,605 |
2022-02-16 00:14:00.865
|
ENG: Transition from GitHub
|
## Goal
We would like to apply the get started checklist template to a "transition from GitHub quick set up checklist" page.
### Jobs To Be Done
* **Situation**: *There isn't a page for users to find information on how to migrate from GitHub to GitLab*
* **Motivation**: *We want to make it easy to change from GitHub to GitLab*
* **Outcome**: *So we can improve conversion rates.*
## Page(s)
Which page(s) are involved in this request?
* `/get-started/github/`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Apply get started checklist template
- [ ] Fill with content
- [ ] Deploy to production
- [ ] Depreciate pages with duplicate content and set redircts
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 4 |
28,847,821 | 102,509,601 |
2022-02-16 00:13:47.400
|
ENG: Build business case for GitLab checklist
|
## Goal
We would like to apply the get started checklist template to a "Build business case for GitLab" page.
Goal for this issue: duplicate a page like Enterprise or Small business, and pass off for content to be filled in
### Jobs To Be Done
* **Situation**: *There isn't a page for users to find information on how to build a business case for choosing GitLab*
* **Motivation**: *We want to make it easy to adopt GitLab*
* **Outcome**: *So we can improve conversion rates.*
## Page(s)
Which page(s) are involved in this request?
* Build business case for GitLab
* `/get-started/build-business-case`
*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Apply get started checklist template
- [ ] Fill with content
- [ ] Deploy to production
- [ ] Depreciate pages with duplicate content and set redircts
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 1 |
28,847,821 | 102,509,595 |
2022-02-16 00:13:31.858
|
ENG: SCM quick set up checklist
|
## Goal
We would like to apply the get started checklist template to a "source code management quick set up" page.
### Jobs To Be Done
* **Situation**: *There isn't a page for users to find information on how to set up source code management with GitLab*
* **Motivation**: *We want to make it easy to set up source code management GitLab*
* **Outcome**: *So we can improve conversion rates.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/get-started/source-code-management
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @miraclebanks
- [ ] Consulted: @laurenbarker @fqureshi
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Apply get started checklist template
- [ ] Fill with content
- [ ] Deploy to production
- [ ] Depreciate pages with duplicate content and set redircts
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 1 |
28,847,821 | 120,438,960 |
2022-12-14 23:00:31.213
|
[ENG] BUG /competition page small shift between Monitor & Govern
|
### Describe the Bug
On the [/competition page](https://about.gitlab.com/competition/) in Safari when you toggle between Monitor and Govern you see a small page shift with the table below.
<details><summary>Screen capture</summary>
</details>
### What's my browser?
Safari
## Page(s)
Which page(s) are involved in this request?
* [/competition page](https://about.gitlab.com/competition/)
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.