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 | 102,509,526 |
2022-02-16 00:11:03.972
|
ENG: Features - Epic & Issue Boards
|
Epic & Issue Boards: https://about.gitlab.com/stages-devops-lifecycle/issueboard/
| 6 |
28,847,821 | 102,509,351 |
2022-02-16 00:00:17.394
|
ENG: Category Leadership Agile Development
|
## Goal
We would like to create a Category Leadership page for Agile Development.
## Page(s)
Which page(s) are involved in this request?
* 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: `TBD`
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Apply Category Leadership template
- [ ] Apply content
- [ ] Build page in 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
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 102,497,202 |
2022-02-15 17:59:28.449
|
Source Sans Pro is different than www repo
|
Appears the version of Source Sans Pro that nuxt is pulling in is different than the version the www repo is pulling in. Not sure how urgent this is as our font-family will likely change soon and the homepage/pricing page will be migrated over soon.
| 2 |
28,847,821 | 102,438,622 |
2022-02-14 20:31:47.016
|
Fix alignment issue with CTA.vue component
|
Fix regression on [Partners](https://about.gitlab.com/partners/) page
| 1 |
28,847,821 | 102,434,356 |
2022-02-14 18:42:42.037
|
UX: Navigation update - Full header
|
## 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/fPzNDCzZAUlAHuq9iQSFmn/Navigation-Refresh?node-id=93%3A710)
* [Navigation prototype](https://www.figma.com/proto/fPzNDCzZAUlAHuq9iQSFmn/Navigation-Refresh?page-id=93%3A710&node-id=123%3A3344&viewport=303%2C48%2C0.16&scaling=min-zoom&starting-point-node-id=123%3A3344)
* [Navigation link copy and URLs](https://docs.google.com/spreadsheets/d/1ualGLPCyFjEpiskrfAe2ftqoTAw8t56lO1LMzMT7Ojo/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: @mpreuss22 @Tinaliseng @ctsang-ext `@cmestel`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Updated 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
| 8 |
28,847,821 | 102,433,310 |
2022-02-14 18:15:46.651
|
UX: Update customer case studies landing page
|
Relates to https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/5605
## Goal
Copied from the original issue:
> I would like to revamp the customer reference landing page up to current content and brand standards, which will be measured by an increase in the click-through rate to single customer reference pages that have already been revamped and updated.
### Jobs To Be Done
Copied from the original issue:
> * **Situation**: In FY22 Q4
> * **Motivation**: We want to revamp/redesign the customer reference landing page
> * **Outcome**: So that it represents Gitlab well as the first engagement prospective customers have with our customer reference content, improves usability of the overall customer reference online material, and facilitates more engagement with our site.
## 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)
## Documents
- [Planning deck](https://docs.google.com/presentation/d/1odgXn-RUGmZM4hwIF9KKsjnb4jcKgJYwm5gR3wHxcj4/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran @jlparker @lclymer @FionaOKeeffe
- [ ] Informed: `Everyone` @ctsang-ext
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 6 |
28,847,821 | 102,291,366 |
2022-02-11 19:08:17.566
|
Add @gitlab/eslint
| null | 3 |
28,847,821 | 102,291,350 |
2022-02-11 19:07:39.750
|
Explore adding prettier to BE repo
|
## 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
| 2 |
28,847,821 | 102,287,445 |
2022-02-11 17:29:59.524
|
Some HTML is not semantically correct
|
The following discussion from !191 should be addressed:
- [ ] @jgarc started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/191#note_840163309): (+1 comment)
> I went ahead and put this page through https://wave.webaim.org/ and found us to be running into some accessibility issues; I believe most of these are from components pulled elsewhere, and therefore I think are outside the scope of this MR, but I'll try to see if I can call out items that you've directly touched with this change!
| 3 |
28,847,821 | 102,236,655 |
2022-02-10 23:03:28.156
|
ENG: Solutions - By Sector - Public Sector
|
## Goal
We would like to apply the new template to our Public Sector page.
Final template to use will be located in [this Figma file](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=990%3A4681).
## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/public-sector/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mduque-ext
- [ ] Consulted: `@Tinaliseng` `@laurenbarker`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Reusable ENG template for Solutions by Industry/Department pages only applied to the Public Sector page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 6 |
28,847,821 | 102,236,478 |
2022-02-10 22:57:20.695
|
ENG: Features - Continuous Integration
|
## Goal
We would like to build our individual feature pages with the new template which will improve consistency of information as measured by increased GitLab accounts created.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand each of the main features of GitLab's product ...*
* **Outcome**: *so they can decide if we are the right product for their needs.*
## Page(s)
Which page(s) are involved in this request?
* `[Figma File TBD](URL)`
New pages that will use this template:
- Continuous Integration ([Existing page](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/))
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jgarc
- [ ] Consulted: @laurenbarker @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Reusable UX template for individual features pages
## 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
- [x] Engineering
| 2 |
28,847,821 | 102,236,374 |
2022-02-10 22:53:25.916
|
ENG: new page- Why GitLab?
|
[Figma link](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab?node-id=217%3A3754)
Page URL: https://about.gitlab.com/why/
| 8 |
28,847,821 | 102,232,748 |
2022-02-10 20:50:48.385
|
Design a plan to test and verify GTM implementation
|
This is a placeholder issue that will track the issue in https://gitlab.com/gitlab-org/gitlab/-/issues/352529
| 6 |
28,847,821 | 102,232,702 |
2022-02-10 20:49:52.664
|
Add submit event in the combined groups/projects form GTM handling
|
## Goal
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 GTM events for new group and project creation*
* **Outcome**: *So we can measure the free trial*
## 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
We're going to track this as a single event and use contextual info about free trial as suggested [here](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/361#note_845647533).
So the event should now be:
```
dataLayer.push({
'event': 'combinedGroupProjectFormSubmit',
})
```
The URL will have `trial_onboarding_flow=true` in it if the user is coming from a free trial onboarding experience, which we can use to differentiate for trials and regular sign up flows.
## Requirements
What are the requirements for 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
| 6 |
28,847,821 | 102,232,634 |
2022-02-10 20:48:13.544
|
Add GTM to the /users/sign_up/groups_projects page
|
Google Tag Manager didn't get added to `/users/sign_up/groups_projects/new`, which is now in the user sign up path.
This issue will be closed out by https://gitlab.com/gitlab-org/gitlab/-/merge_requests/80348
| 2 |
28,847,821 | 102,221,051 |
2022-02-10 16:51:08.278
|
ENG: Homepage - update security and compliance badges
|
Related to #307.
## Goal
We would like to ensure our security and compliance banner is up to date which will improve our communications as measured by the accuracy of our claims.
## Page(s)
Which page(s) are involved in this request?
* [Homepage](https://about.gitlab.com)
## In scope
Update security and compliance badges on the homepage.
1. Add [ISO/IEC 27001:2013 Certification](/uploads/f413ee4b72019b355199a58c2138608b/ISO_27001_Logo.png)
2. Add [CSA Trusted Cloud Provider](/uploads/b15cb4a9461b170782c49f47bf0480f0/CSA_Trusted_Cloud_Provider_badge.png)
1. Update the copy for <s>SOC2 Certification</s> to `SOC 2 & SOC 3 Certification`
1. Remove Bitsight
*Use the badge files linked above :arrow_heading_up:
| Badge (low res) | Text | Link (open new browser window) |
| ------ | ------ | ------ |
| |SOC 2 & SOC 3 Certification| https://us.aicpa.org/interestareas/frc/assuranceadvisoryservices/serviceorganization-smanagement |
|  |ISO/IEC 27001:2013 Certification| https://www.schellman.com/certificate-directory?certificateNumber=1652216-1 |
||CSA Trusted Cloud Provider|https://cloudsecurityalliance.org/star/registry/gitlab/|
## Final Visual
## Out of scope
What is out of scope and not part of this iteration?
- Changing presentation style of banner
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @mpreuss22, '@JohnathanHunt', '@Julia.Lake', @lduggan (original engineer)
- [ ] 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
| 1 |
28,847,821 | 102,213,972 |
2022-02-10 14:52:35.160
|
IA Refresh - Redirect Mapping
|
To minimize the impact of structural change in the IA refresh we need to set up 301 redirects for deprecated and consolidated pages. We need to match your old URLs with the new ones or relevant alternatives. Without proper redirection, our new/consolidated pages will not get the traffic and PageRank of the old pages, which will affect our search engine rankings.
## Redirecting best practices
- To best preserve search rankings and traffic for better performing pages, it is best to keep the URL structure intact.
- When removing, deprecating or consolidating URLs it is important to redirect to a relevant alternative to preserve the SEO value from backlinks
- Update internal links from the old URLs to the new URLs to prevent internal redirects which impacts crawl budget.
- Check for existing 301 redirects to URLs that will be removed, relocated or consolidated. Updating these to the new URLs will prevent redirect chains and loops which impacts crawl budget.
## Risks
Combining, changing URLs or deprecating pages comes with risks that will affect SEO efforts. If not properly managed we run the risk of:
- Losing SEO value from backlinks attributed to removed or relocated URLs
- Drop in search traffic and rankings. It might take some time for search engines to update their search index.
- Increase in 404 errors, redirect chains and redirect loops.
- Increase in soft 404s error messages in Google Search Console.
### Tasks to be done
- [x] [Create redirect map document](https://docs.google.com/spreadsheets/d/1Oir6thxzoXuumbk5Lh6CBiznE6KOjJXhjQ88svKac68/edit?usp=sharing)
- [ ] Create redirects (old to new) in redirect.yml file
- [ ] Update internal links to reduce internal redirects
| 10 |
28,847,821 | 102,166,838 |
2022-02-09 19:22:22.017
|
Migrate all card components
|
## Goal
Replace card components in the Buyer Experience repo to use the cards from slippers-ui.
**Storybook:** https://gitlab-com.gitlab.io/marketing/digital-experience/slippers-ui/?path=/story/components-card--default
**Usage:** https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/blob/main/src/components/Card/Card.stories.js
| 4 |
28,847,821 | 102,166,463 |
2022-02-09 19:11:05.654
|
IA Refresh Content Audit
|
## Goal
Carry out a content audit to suggest what pages should be kept, deleted, consolidated or redirected in the website refresh. This will be compiled using backlinks, existing website structure and Google Analytics data.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @hsmith-watson
- [ ] Consulted: @ncregan
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Content audit of current marketing pages
## Out of scope
What is out of scope and not part of this iteration?
- Blog posts and releases
- Handbook, Direction, Company and Job Families pages
## Documentation
- [Content Audit Spreadsheet](https://docs.google.com/spreadsheets/d/1fCyFV8gHQrE2EWDZNr801RMJiPTIIG-Wcrvd_sPadSM/edit?usp=sharing)
### Outcomes
Based on the results of the content audit we have four suggested outcomes.
**Leave as is**
No need to delete or redirect. The page has good traffic and a healthy backlink profile. Removing these pages will have a negative impact on traffic.
If deleted we must redirect to an alternative page and 301 redirect to ensure the link equity is maintained.
**Redirect or Update**
The page gets no meaningful traffic but has at least 1 backlink. This needs to be manually reviewed by code owners/departments to ensure nothing of strategic value is removed.
Options:
- Improve SEO by updating the content
- Merge content with similar page and redirect to new location
- Delete page and redirect to alternative
**Manual review**
Pages with OK traffic and little from organic search. This needs to be manually reviewed by code owners/departments to ensure nothing of strategic value is removed.
Options:
- Leave as is
- Improve SEO by updating the content
- Merge content with similar page
- Delete page and redirect to alternative
**Delete Page**
These pages has no meaningful traffic from any source and no backlinks. This needs to be manually reviewed by code owners/departments to ensure nothing of strategic value is removed.
Options:
- Delete page and redirect to alternative
| 10 |
28,847,821 | 102,112,011 |
2022-02-09 04:37:37.573
|
Implement pricing carousel
|
## Goal
Implement carousel into the Buyer Experience repo
## Page(s)
Which page(s) are involved in this request?
* [Pricing](https://about.gitlab.com/pricing)
| 2 |
28,847,821 | 102,111,489 |
2022-02-09 04:17:46.748
|
Update references to /roi/replace
|
## Goal
/roi/replace/ was recently deleted. Update all existing links to /roi/.
| 1 |
28,847,821 | 102,111,387 |
2022-02-09 04:15:13.333
|
Fix <p> styling on comparison pages
|
## Goal
Fix navigation font colors on comparison pages.
## Page(s)
Which page(s) are involved in this request?
* [Self Managed](https://about.gitlab.com/pricing/self-managed/feature-comparison/)
* [SASS](https://about.gitlab.com/pricing/saas/feature-comparison/)
| 1 |
28,847,821 | 102,087,965 |
2022-02-08 18:29:04.829
|
UX: new page Company size - Startups
|
## Goal
We would like to create a new page for Early Stage businesses which will improve our Solutions marketing as measured by more early stage businesses signing up for GitLab accounts.
### Jobs To Be Done
* **Situation**: *When a user from an early stage business looks into using GitLab for their company...*
* **Motivation**: *they want to understand how GitLab works for their specific needs...*
* **Outcome**: *so they can make an informed decision on whether to use our product.*
## Page(s)
Which page(s) are involved in this request?
- `[Figma File TBD](URL)`
Similar to:
- [Enterprise page](https://about.gitlab.com/enterprise/)
- [SMB Page](https://about.gitlab.com/small-business/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] New early stage page
- [ ] New copy and possibly brand assets acquired
## 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
- [x] Illustration
- [x] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 102,087,941 |
2022-02-08 18:28:08.542
|
UX: Support page refresh
|
## Goal
We would like to consolidate our support pages into 1 page which will improve customer's finding the support they need as measured by less support inquiries.
### Jobs To Be Done
* **Situation**: *When a user is looking for help...*
* **Motivation**: *they want to easily find and quickly understand how to solve their problem or get in touch...*
* **Outcome**: *So they can get back to business as usual ASAP.*
## Page(s)
Which page(s) are involved in this request?
- [Support Page 1 - Contact Support](https://about.gitlab.com/support/)
- [Figma designs for Support page](https://www.figma.com/file/xbqYq5HSsiwZXikHpvXnCj/Support-Refresh?node-id=88%3A8051)
- [Support Page 2 - Help Topics](https://about.gitlab.com/get-help/)
- Maybe also [Contact Sales](https://about.gitlab.com/sales/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Support page mocks
## 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
- [x] UX Design
- [ ] Engineering
| 8 |
28,847,821 | 102,087,929 |
2022-02-08 18:27:45.500
|
UX: Template for getting started checklist
|
## Goal
We would like to have a template for getting started checklists, 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 High Fidelity Designs](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=368%3A3068) (WIP - waiting for Jam3 designs)
- [Figma File JTBD](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab?node-id=218%3A4234)
- ~~[Getting started](https://about.gitlab.com/get-started/)~~ Not included because it's not a net new page.
New pages that will use this template:
- SMB/Enterprise quick set up checklist
- CI quick set up checklist
- SCM quick set up checklist
- Build business case for GitLab checklist
- Transition from GitHub or Jira quick set up checklist
- Scaling your GitLab usage quick set up checklist
- Set up support services
## 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
| 4 |
28,847,821 | 102,087,902 |
2022-02-08 18:27:19.780
|
UX: Category Leadership - Template refresh
|
## Goal
We would like to have a consolidated template for our Category Leadership pages which will improve consistency of information as measured by increased GitLab accounts created.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand how GitLab is leading the way in a particular category...*
* **Outcome**: *so they can decide if we are the right product for their needs.*
## Page(s)
Which page(s) are involved in this request?
* `[Figma File TBD](URL)`
New pages that will use this template:
- DevOps ([Existing page 1](https://about.gitlab.com/solutions/devops-platform/), [existing page 2](https://about.gitlab.com/topics/devops/))
- Digital Transformation ([Existing page 1](https://about.gitlab.com/solutions/digital-transformation/))
- Agile Development ([Existing page 1](https://about.gitlab.com/topics/agile-delivery/), [existing page 2](https://about.gitlab.com/solutions/agile-delivery/))
- GitOps ([Existing page 1](https://about.gitlab.com/solutions/gitops/), [existing page 2](https://about.gitlab.com/topics/gitops/))
- Microservices
- DevSecOps
- Security & Compliance
- Cloud Transformation
- Modern Applications
## Files
[Ongoing agenda](https://docs.google.com/document/d/1ielDKrmfHq9QqXH7TNcJXPzAT9I2qkO8vkLN9J6_Blo/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran @hsmith-watson @ncregan @dennischarukulvanich
- [ ] Informed: @fqureshi
## In scope
What is within scope of this request?
- [ ] Reusable UX template for Category Leadership pages (designs by Jam3)
- [ ] JTBD (if deemed necessary)
- [ ] High-fidelity wireframes
## 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,087,863 |
2022-02-08 18:26:14.428
|
UX: Template for Solutions page - by industry / by department
|
## Goal
We would like to have a template for our Solutions `by industry` pages which will improve consistency of information as measured by increased GitLab accounts created. We will use the same template for the `by department` pages.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand what solutions we offer for their industry ...*
* **Outcome**: *So they can decide if we are the right product for their needs.*
## Page(s)
Which page(s) are involved in this request?
* [Figma Template](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A1765)
New pages that will use this template:
**by Industry**
- Finance
- Retail
- Public Sector
- Technology
## Workfiles
* [JTBD Template](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=69%3A2485)
**by Department**
* Engineering
* Product Management
* IT
* QA/Testing
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Reusable UX template for Solutions by industry pages
## 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
| 1 |
28,847,821 | 102,087,850 |
2022-02-08 18:25:51.997
|
UX: Template for Solutions page - by solution
|
## Goal
We would like to have a template for our Solutions pages which will improve consistency of information as measured by increased GitLab accounts created.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand what solutions we offer that could help their business ...*
* **Outcome**: *So they can decide if we are the right product for their needs.*
## Page(s)
Which page(s) are involved in this request?
* [Figma Template](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A722)
New pages that will use this template:
- Delivery Automation
- Continuous Software Security Assurance
- Continuous Software Compliance
## Workfiles
- [Figma JTBD templates](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=69%3A2485)
- [WIP AI spreadsheet](https://docs.google.com/spreadsheets/d/1ualGLPCyFjEpiskrfAe2ftqoTAw8t56lO1LMzMT7Ojo/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Reusable UX template for Solutions pages
## 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
| 1 |
28,847,821 | 102,087,815 |
2022-02-08 18:25:18.009
|
UX: Template for individual feature page
|
## Goal
We would like to have a consolidated template for our individual feature pages which will improve consistency of information as measured by increased GitLab accounts created.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to understand each of the main features of GitLab's product ...*
* **Outcome**: *so they can decide if we are the right product for their needs.*
## Workfiles
Which page(s) are involved in this request?
* [JTBD Template](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=38%3A263)
* [V1 Mock - skinned template](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=173%3A596)
New pages that will use this template:
- Continuous Integration ([Existing page](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/))
- Source Code Management ([Existing page](https://about.gitlab.com/stages-devops-lifecycle/source-code-management/))
- Security Training
- Security Dashboards
- Code Owners
- Code Search
- Roadmaps
- Vulnerability Management
- Epic & Issue Boards
- Merge Trains
- Licenses Compliance
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Reusable UX template for individual features pages
## 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
| 8 |
28,847,821 | 102,087,455 |
2022-02-08 18:15:36.154
|
Deploy script for buyer experience that deletes pages
|
## Goal
We would like to iterate on our deploy script to remove files from GCP if the page was been deleted from the Buyer Experience repository.
### Jobs To Be Done
* **Situation**: *When a page is deleted from the Buyer Experience repository*
* **Motivation**: *We want to delete it form our GCP bucket*
* **Outcome**: *So we can ensure the URL is no longer discoverable*
## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/scripts/deploy#L69
## 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?
- [ ] Iterating on our deploy script to remove files from our GCP bucket
## Out of scope
What is out of scope and not part of this iteration?
- Template or content 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
| 6 |
28,847,821 | 102,027,162 |
2022-02-08 00:03:27.716
|
UX: Content Gathering for IA Refresh
|
## Goal
The experience for buyers on about.gitlab.com is not customer-centric. The Marketing Site is unfocused with too many pages and not enough structure. Starting with a refreshed information architecture that aligns with the awareness, consideration, conversion, marketing funnel prospective customers will be able to engage more fluidly.
Simplifying the experience and increasing the signal we collect from buyer actions will maximize the conversion opportunity our traffic presents.
Full memo: [FY23 Digital Experience Direction](https://docs.google.com/document/d/1LtwKyvWKerqnh6VMnbxgDxuqSb6BfI92Cr7y-2LIJEI/edit)
### Jobs To Be Done
* **Situation**: *When thinking about the information architecture refresh for the marketing site*
* **Motivation**: *we want to understand what content/pages already exist and what needs to be created...*
* **Outcome**: *so we can start working on content creation and editing.*
## Page(s)
Which page(s) are involved in this request?
* [New marketing site IA spreadsheet](https://docs.google.com/spreadsheets/d/1ualGLPCyFjEpiskrfAe2ftqoTAw8t56lO1LMzMT7Ojo/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: @mpreuss22 @cblake @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Understand which pages already exist and link them to the spreadsheet
- [x] If multiple pages exist that could be turned into one, list them all out
- [ ] Create issues for net new content where necessary
- [ ] Create issues for updating or combining content where necessary
- [ ] Formulate a plan to write, edit, and implement content to coincide with the IA refresh timeline
| Page Title | Existing URL or net new | Related content & notes | Already in the buyer repo? |
| ------ | ------ | ------ | ------ |
| Home page | https://about.gitlab.com/ | | |
| Why GitLab? | https://about.gitlab.com/why/ | Related: https://about.gitlab.com/what-is-gitlab/ & https://about.gitlab.com/is-it-any-good/ | |
| GitLab vs GitHub | https://about.gitlab.com/devops-tools/github-vs-gitlab/ | | |
| GitLab vs Atlassian (Confluence)| https://about.gitlab.com/devops-tools/atlassian-confluence-vs-gitlab/ | Related: https://about.gitlab.com/devops-tools/jira-vs-gitlab/ & https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/bdm/ (Jira & Bitbucket rank higher )| |
| GitLab vs Jenkins | https://about.gitlab.com/devops-tools/jenkins-vs-gitlab/ | | |
| GitLab vs CircleCI | https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab/ | | |
| GitLab vs Azure | https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/ | | |
| GitLab vs Artfactory or JFrog? | https://about.gitlab.com/devops-tools/jfrog-vs-gitlab/ | Related: https://about.gitlab.com/devops-tools/jfrog-vs-gitlab/jfrog-artifactory/ | |
| GitLab vs Datadog | https://about.gitlab.com/devops-tools/datadog-vs-gitlab/ | Suggested for APAC | |
| Features | https://about.gitlab.com/features/ | | |
| Feature comparison | https://about.gitlab.com/pricing/self-managed/feature-comparison/ | | |
| Continuous Integration | https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/ | Related: https://about.gitlab.com/stages-devops-lifecycle/continuous-delivery/ & https://about.gitlab.com/snapshots/continuous-integration/| |
| Source Code Management | https://about.gitlab.com/stages-devops-lifecycle/source-code-management/ | Related: https://about.gitlab.com/solutions/benefits-of-using-version-control/ & https://about.gitlab.com/resources/ebook-version-control-best-practices/ & https://about.gitlab.com/solutions/benefits-of-using-version-control/ & https://about.gitlab.com/topics/version-control/version-control-best-practices/ | |
| Security Training | Net new | Related: https://about.gitlab.com/services/education/security-essentials/ | |
| Security Dashboards | Net new | Related: https://docs.gitlab.com/ee/user/application_security/security_dashboard/ | |
| Code Owners | Net new | Related: https://docs.gitlab.com/ee/user/project/code_owners.html | |
| Approval Rules | https://about.gitlab.com/solutions/code-reviews/ | Related: https://docs.gitlab.com/ee/user/project/merge_requests/approvals/rules.html#merge-request-approval-rules | |
| Code Search | Net new | Related: https://docs.gitlab.com/ee/user/search/#code-search | |
| Roadmaps | Net new | Related: https://docs.gitlab.com/ee/user/group/roadmap/#roadmap | |
| Vulnerability Management | Net new | Related: https://docs.gitlab.com/ee/user/application_security/vulnerability_report/ & https://docs.gitlab.com/ee/user/application_security/vulnerabilities/#vulnerability-pages & https://docs.gitlab.com/ee/user/application_security/vulnerabilities/severities.html | |
| Epic & Issue Boards | https://about.gitlab.com/stages-devops-lifecycle/issueboard/ | Related: https://docs.gitlab.com/ee/user/group/epics/epic_boards.html#epic-boards | |
| Merge Trains | Net new | Related: https://docs.gitlab.com/ee/ci/pipelines/merge_trains.html#merge-trains | |
| Licenses Compliance | https://about.gitlab.com/solutions/compliance/ | Related: https://about.gitlab.com/security/ & https://about.gitlab.com/solutions/financial-services-regulatory-compliance/ & https://about.gitlab.com/solutions/hipaa-compliance/ | Yes |
| Solutions | https://about.gitlab.com/solutions/ | | |
| Delivery Automation | [Coming soon...](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/211) solutions/delivery-automation/ | Related: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/delivery-automation/ | |
| Continuous Software Security Assurance | Net new | Related: https://about.gitlab.com/handbook/use-cases/#3-continuous-software-security-assurance | |
| Continuous Software Compliance | Net new | Related: https://about.gitlab.com/handbook/marketing/strategic-marketing/usecase-gtm/compliance/ | |
| The DevOps Platform | https://about.gitlab.com/solutions/devops-platform/ | | Yes |
| Finance | Net new | | |
| Retail | Net new | | |
| Public Sector | https://about.gitlab.com/solutions/public-sector/ | | Yes |
| Technology | Net new | | |
| Education | https://about.gitlab.com/solutions/education/ | Suggested, could also use the campuses page as main URL (very similar) Related: https://about.gitlab.com/solutions/education/campus/ & https://about.gitlab.com/solutions/education/join/| Yes, campuses is also a yes |
| Engineering | Net new | | |
| Product Management | Net new | Related: https://about.gitlab.com/services/education/pm/ | |
| IT | Net new | | |
| QA/Testing | Net new | | |
| Technology Partner | https://about.gitlab.com/partners/ or https://about.gitlab.com/partners/technology-partners/ | | Yes |
| AWS | https://about.gitlab.com/partners/technology-partners/aws/ | | Yes |
| Google Cloud Platform (GCP) | https://about.gitlab.com/partners/technology-partners/google-cloud-platform/ | | Yes |
| RedHat | https://about.gitlab.com/partners/technology-partners/redhat/ | | Yes |
| VMWare | https://about.gitlab.com/partners/technology-partners/vmware-tanzu/ | | Yes |
| IBM | https://about.gitlab.com/partners/technology-partners/ibm/ | | Yes |
| Hashicorp | https://about.gitlab.com/partners/technology-partners/hashicorp/ | | Yes |
| Enterprise | https://about.gitlab.com/enterprise/ | | Yes |
| SMB | https://about.gitlab.com/small-business/ | | Yes |
| Early Stage | https://about.gitlab.com/solutions/startups/ | Should this be called "Start ups"? | Yes |
| DevOps | https://about.gitlab.com/devops-tools/ | | |
| Digital Transformation | https://about.gitlab.com/solutions/digital-transformation/ | | Yes |
| Agile Development | https://about.gitlab.com/solutions/agile-delivery/ | Related: https://about.gitlab.com/solutions/agile-delivery/scaled-agile/ | Yes |
| GitOps | https://about.gitlab.com/solutions/gitops/ | | Yes |
| Microservices | https://about.gitlab.com/topics/microservices/ | Should this be net new? It's the only Topics page pulled in | |
| DevSecOps | https://about.gitlab.com/solutions/dev-sec-ops/ | | Yes |
| Security & Compliance | https://about.gitlab.com/security/ | Related: https://about.gitlab.com/solutions/financial-services-regulatory-compliance/ & https://about.gitlab.com/solutions/hipaa-compliance/ | |
| Cloud Transformation | https://about.gitlab.com/solutions/cloud-native/ | | Yes |
| Modern Applications | Net new | Related: https://about.gitlab.com/handbook/marketing/strategic-marketing/it-groups/build/modernize/ | |
| Stages of the DevOps Lifecycle | https://about.gitlab.com/stages-devops-lifecycle/ | | |
| Manage | https://about.gitlab.com/stages-devops-lifecycle/manage/ | | Yes |
| Plan | https://about.gitlab.com/stages-devops-lifecycle/plan/ | | Yes |
| Create | https://about.gitlab.com/stages-devops-lifecycle/create/ | | Yes |
| Verify | https://about.gitlab.com/stages-devops-lifecycle/verify/ | | Yes |
| Package | https://about.gitlab.com/stages-devops-lifecycle/package/ | | Yes |
| Secure | https://about.gitlab.com/stages-devops-lifecycle/secure/ | | Yes |
| Release | https://about.gitlab.com/stages-devops-lifecycle/release/ | | Yes |
| Configure | https://about.gitlab.com/stages-devops-lifecycle/configure/ | | Yes |
| Monitor | https://about.gitlab.com/stages-devops-lifecycle/monitor/ | | Yes |
| Protect | https://about.gitlab.com/stages-devops-lifecycle/protect/ | | Yes |
| Pricing | https://about.gitlab.com/pricing/ | | |
| Why Ultimate? | https://about.gitlab.com/pricing/ultimate/ | | |
| Why Premium? | https://about.gitlab.com/pricing/premium/ | | |
| Getting Started | https://about.gitlab.com/get-started/ | Related: https://about.gitlab.com/community/moving-to-gitlab/ | Yes |
| Free Trial | https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial | | |
| Install | https://about.gitlab.com/install/ | | |
| CE or EE | https://about.gitlab.com/install/ce-or-ee/ | | Yes |
| Update GitLab | https://about.gitlab.com/update/ | | Yes |
| SMB quick set up checklist | Net new | | |
| Enterprise quick set up checklist | Net new | | |
| CI quick set up checklist | Net new | | |
| SCM quick set up checklist | Net new | | |
| Build business case for GitLab checklist | Net new | Related: https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab/business-decision-makers/ & https://about.gitlab.com/devops-tools/jenkins-vs-gitlab/technical-decision-makers/ & https://about.gitlab.com/devops-tools/jenkins-vs-gitlab/business-decision-makers/ | |
| Transition from GitHub quick set up checklist | https://about.gitlab.com/solutions/github/ | | Yes |
| Transition from Jira quick set up checklist | https://about.gitlab.com/solutions/jira/ | | Yes |
| Scaling your GitLab usage quick set up checklist | Net new | | |
| Set up support services | https://about.gitlab.com/services/ | Related: https://about.gitlab.com/services/catalog/ & https://about.gitlab.com/services/technical-account-management/ & https://about.gitlab.com/services/implementation/ & https://about.gitlab.com/services/education/ | |
| Support | https://about.gitlab.com/support/ | | |
| Get Help | https://about.gitlab.com/get-help/ | | Yes |
| Resources | https://about.gitlab.com/resources/ | | |
| Docs | https://docs.gitlab.com/ | Not in buyer repo | |
| Blog | https://about.gitlab.com/blog/ | | |
| Learn | https://about.gitlab.com/learn/ | | |
| Customer Stories | https://about.gitlab.com/customers/ | | |
| Community programs | https://about.gitlab.com/community/ | | |
| Working remotely | https://about.gitlab.com/company/culture/all-remote/ | | |
| Events | https://about.gitlab.com/events/ | | |
| Company | https://about.gitlab.com/company/ | | Yes |
| Releases | https://about.gitlab.com/releases/ | | |
| Jobs | https://about.gitlab.com/jobs/ | Consider calling this "Careers" | |
| Analysts | https://about.gitlab.com/analysts/ | | |
| Demo | https://about.gitlab.com/demo/ | | Yes |
| Contact Sales | https://about.gitlab.com/sales/ | | Yes |
| Demo | https://about.gitlab.com/demo/ | | |
| Login / Register | https://gitlab.com/users/sign_in | Not in the buyer repo | |
## Out of scope
What is out of scope and not part of this iteration?
- Secondary pages to landing page (ex. Blog posts, Customer case studies, etc.)
- Handbook (other than where we might pull content from)
- Docs (other than where we might pull content from)
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [x] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 10 |
28,847,821 | 101,827,802 |
2022-02-03 15:26:52.139
|
Mermaid Charts Integration
|
## Goal
We would like to integrate mermaid chart functionality into the Buyer Experience repository.
### Jobs To Be Done
* **Situation**: *When we migrate pages to this repository that contain mermaid charts, we can implement them.*
* **Motivation**: Mermaid chart are used extensively in the www-gitlab-com repository.*
* **Outcome**: *So we can increase efficiency for migrating pages to this repository.*
## Page(s)
Which page(s) are involved in this request?
* Example of page the includes mermaid chart: https://about.gitlab.com/company/cadence/
* https://mermaid-js.github.io/mermaid/#/
## 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?
- [ ] Integrating the mermaid chart functionality into this repository
## Out of scope
What is out of scope and not part of this iteration?
- Any work in 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 | 101,769,411 |
2022-02-02 22:25:00.219
|
ENG: Page Update - about.gitlab.com/analysts
|
Related to #240.
## Goal
Design for the Analysts page is ready for engineering.
## Page(s)
Which page(s) are involved in this request?
* [Industry Analyst Research](about.gitlab.com/analysts)
## Workfiles
* [Figma design](https://www.figma.com/file/yhOmOuXxET1rWd9hMHyT8A/Analysts-MVC-1?node-id=0%3A1)
* [Content outline](https://docs.google.com/document/d/1D23GF8KgWHq9IKD_hQNbcElffRPLsAbFzVcu0N9sNC4/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dvilchis-ext
- [ ] Consulted: @rragozzine @Tinaliseng
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Engineering the updated mockup
## Out of scope
What is out of scope and not part of this iteration?
- [ ] Improving UX for page updates
- [ ] User Testing
## Requirements
What are the requirements for this request? Checklist 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 | 101,688,535 |
2022-02-01 21:37:37.398
|
SaaS Revision: Currency Code
|
## Goal
CurrencyCode is visible in the dataLayer code, but GTM is not able to locate it due to the syntax. Moving the currencyCode line in the ecommerce array before the checkout line may help.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/-/subscriptions/new?plan_id=
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpreuss22
- [ ] Consulted: @dennis106
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 101,688,523 |
2022-02-01 21:37:13.085
|
SaaS Revision: Variant
|
## Goal
Premium’s Variant should be “SaaS” instead of “Self-hosted” for the Add To Cart event.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpreuss22
- [ ] Consulted: @dennis106
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 101,688,510 |
2022-02-01 21:36:43.758
|
SaaS Revision: Price
|
## Goal
1. Add Premium’s Price ($288) for the Product Impression and Add To Cart events
2. Update Ultimate’s Price to '1188' for the Product Impression and Add To Cart events since it’s billed annually. This will also match the price on the Checkout event.
3. Price should be in single quote on the Checkout event.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/pricing/
* https://gitlab.com/-/subscriptions/new?plan_id=
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpreuss22
- [ ] Consulted: @dennis106
- [ ] 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
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 101,678,009 |
2022-02-01 16:57:26.119
|
Topics Template Layout Changes
|
We've have looking at the recently migrated CI/CD topics page and we have identified a few changes and issues (listed below) that may have a negative impact on our current and future SEO efforts.
### Topic Navigation Links
All the "More on this topic" links are external and in most cases the link is irrelevant to the topic. Before the switch these were all internal. This can be amended but we need to ensure we preserve all internal links when migrating.
### Heading Heirachy
Headings gives search engines important clues about the page structure and relevancy. headings should be logically structured, starting with a h1 followed by h2's, and subsequent h3's fir related subsections, etc. The current structure isn't in a logical order. Search engines utilse header structures to decipher the informational structure and topical hierarchy of a page.
For example:
- `<h2 class="copy__title" data-v-b44de53e="" data-v-34d03aa1="">Continuous integration and continuous delivery (CI/CD)</h2> `. This should be **H1**.
- `<h3 class="header slp-text-xxl" data-v-b44de53e="" data-v-daaa09f2=""> What is CI/CD? </h3> `. This should be **H2**.
### FAQ schema
The FAQ schema.org markup is missing from the page. This was implemented to make search engine better understand page contents and display the pages in the form of Rich Snippets in SERPs.
### Self referencing canonical path
Self referencing canonical path is missing from this page and other pages that have migrated. This is needed to prevent search engines from indexing URLs with tracking parameters. Search performance is not affected but tracking statistics will be skewed. Search clicks will be wrongly attributed to other marketing activities in Google Analytics or other tracking tools.
| 4 |
28,847,821 | 101,608,194 |
2022-01-31 17:14:54.200
|
Solution page migration - Education section - Join
|
Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/248
## Goal
We would like to migrate `/solutions/education/join` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the solutions template.
### Jobs To Be Done
* **Situation**: *When a user lands on* any page within the `/solutions/education/join` section of the site, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/education/join
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI: `@jariasc-ext`
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Applying the solutions template to this page
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
* Building a new template
* Any work in www-gitlab-com other than removing the page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
* [ ] Copy writing
* [ ] Illustration
* [ ] Custom Graphics
* [ ] Research
* [ ] Data / Analytics
* [ ] UX Design
* [x] Engineering
| 5 |
28,847,821 | 101,608,097 |
2022-01-31 17:13:32.178
|
Solution page migration - Education section - Edu Survey
|
Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/248
## Goal
We would like to migrate `/solutions/education/edu-survey` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the solutions template.
### Jobs To Be Done
* **Situation**: *When a user lands on* any page within the `/solutions/education/edu-survey` section of the site, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/education/edu-survey
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI: `@jariasc-ext`
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Applying the solutions template to this page
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
* Building a new template
* Any work in www-gitlab-com other than removing the page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
* [ ] Copy writing
* [ ] Illustration
* [ ] Custom Graphics
* [ ] Research
* [ ] Data / Analytics
* [ ] UX Design
* [x] Engineering
| 3 |
28,847,821 | 101,607,776 |
2022-01-31 17:07:46.775
|
Solution page migration - Education section - Campus
|
Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/248
## Goal
We would like to migrate `/solutions/education/campus` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the solutions template.
### Jobs To Be Done
* **Situation**: *When a user lands on* any page within the `/solutions/education/campus` section of the site, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/education/campus
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI: `@jariasc-ext`
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Applying the solutions template to this page
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
* Building a new template
* Any work in www-gitlab-com other than removing the page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
* [ ] Copy writing
* [ ] Illustration
* [ ] Custom Graphics
* [ ] Research
* [ ] Data / Analytics
* [ ] UX Design
* [x] Engineering
| 4 |
28,847,821 | 101,494,037 |
2022-01-28 23:20:38.852
|
Navigation Menu Click: Revision
|
## Goal
Add the `data-nav-tab` attribute to all `<a>` tags within the navigation menu. Essentially, items in the main navigation menu already has data-nav-tab, however it seems like there's a different version of the same nav menu that doesn't have the attribute. For example, the nav menu on the Home page has it. The nav menu on this page doesn't have it: https://about.gitlab.com/enterprise/
Please ensure data-nav-tab is placed across all versions of the navigation menu.
## Page(s)
Which page(s) are involved in this request?
- about.gitlab.com/enterprise/
- about.gitlab.com/demo/
- about.gitlab.com/get-started/
- about.gitlab.com/company/
- about.gitlab.com/get-help/
- ...and many more
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpreuss22
- [ ] Consulted: @dennis106
- [ ] 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 | 101,475,231 |
2022-01-28 15:18:30.303
|
Update Buyer Experience components with header tags so pages are rendering header content semantically
|
## Goal
Looking through pages built in our Buyer Experience repo, there are discrepancies in the way we are using heading tags. There are some pages that do not have any h2 tags (they go from h1 to h3) or are completely missing h1 tags. Let's audit what we have and make changes where necessary.
### Jobs To Be Done
* **Situation**: *When someone visits a page built in our Buyer Experience repo*
* **Motivation**: *We want to present header tags correctly / semantically*
* **Outcome**: *So we can improve accessibility and search engine crawling on these pages*
## Examples
Which page(s) are involved in this request?
* [Demo](https://about.gitlab.com/demo/) - no h1
* [Solutions](https://about.gitlab.com/solutions/) - jumping from h1 to h3 tags
## In Scope
- HTML tag updates
## Not in scope
- CSS updates
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 101,416,411 |
2022-01-27 20:33:02.654
|
Safari Cross site scripting console errors
|
## Goal
Investigate if there's an easy solution to prevent console errors from external vendors in safari (screenshot attached)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 101,416,059 |
2022-01-27 20:24:52.221
|
Prevent Cookie banner from appearing in review apps
|
## Goal
We want to disable OneTrust in review apps in order to have a more enjoyable review experience.
### Jobs To Be Done
* **Situation**: *When review apps are deployed for MRs against https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience or https://gitlab.com/gitlab-com/www-gitlab-com*
* **Motivation**: *We want to disable the OneTrust cookie banner from firing*
* **Outcome**: *So we can not have to look at it*
| 2 |
28,847,821 | 101,413,965 |
2022-01-27 19:30:11.916
|
[Transition 50 pages] Child: stages-devops-lifecycle / Monitor
|
## Goal
We want to move https://about.gitlab.com/stages-devops-lifecycle/monitor/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
## Page(s)
- [Monitor](https://about.gitlab.com/stages-devops-lifecycle/monitor/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [ ] Yes
- [x] No
## 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
* [ ] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review
| 1 |
28,847,821 | 101,412,635 |
2022-01-27 18:56:39.461
|
Drift Chatbox shows messages in tab title
|
As per [this issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/264#note_823957805)
Drift chat is still showing (2) New Messages in the title of the tab after being dismissed.
| 1 |
28,847,821 | 101,402,175 |
2022-01-27 16:19:09.839
|
Add a "share to Hacker News" button to the blog
|
## Goal
Our CEO Sid has created a marketing OKR to get 12 blog posts on Page One of Hacker News. One way to accomplish this is to add a "share to Hacker News" button to every blog post.
### Jobs To Be Done
* **Situation**: *When blogs are published, people can easily share to Hacker News, something Sid cares passionately about.*
* **Motivation**: *We want to dramatically increase our mentions on Hacker News.*
* **Outcome**: *So we can keep Sid happy, grow traffic, keep our jobs, market to developers*
## Page(s)
Which page(s) are involved in this request?
* `GitLab Blog - about.gitlab.com/blog`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: `vsilverthorne`
- [x] Consulted: `jcoghlan`
- [x] Informed: `msmolensky`
## In scope
What is within scope of this request?
- [x] Deliverable 1 - A button on the blog to share directly to Hacker News (You can find ready to go code here: https://www.shareaholic.com/website-tools/social-share-buttons/yc-hacker-news)
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Any other blog changes
- 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 | 101,246,591 |
2022-01-25 19:54:53.613
|
Review and update homepage security banner
|
## Goal
We would like to ensure our security and compliance banner is up to date which will improve our communications as measured by the accuracy of our claims.
## 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: @Tinaliseng
- [ ] Consulted: @mpreuss22, @JohnathanHunt, @Julia.Lake
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [x] Review this [Slack message](https://gitlab.slack.com/archives/C010XFJFTHN/p1639175795014500) and update homepage security and compliance banner as needed.
- [x] 
## Out of scope
What is out of scope and not part of this iteration?
- Changing presentation style of banner
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 3 |
28,847,821 | 101,163,873 |
2022-01-24 17:00:55.257
|
/solutions/startups
|
## Goal
We would like to migrate `/solutions/startups/` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the solutions template.
### Jobs To Be Done
* **Situation**: *When a user lands on* `/solutions/startups/`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*
## Page(s)
Which page(s) are involved in this request?
* `[GitHub](https://about.gitlab.com/solutions/startups/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI: ``
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
* [x] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [x] Applying the solutions template to this page
* [x] Building a new component if an acceptable one does not exist
* [x] Creating an additional MR to remove this page from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
* Building a new template
* Any work in www-gitlab-com other than removing the page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
* [ ] Copy writing
* [ ] Illustration
* [ ] Custom Graphics
* [ ] Research
* [ ] Data / Analytics
* [ ] UX Design
* [x] Engineering
| 2 |
28,847,821 | 101,054,369 |
2022-01-21 16:41:50.323
|
Migrate all Typography components
|
## Goal
Convert all the text in the Buyer Experience repo to be wrapped in <SlpTypography> components. When using the component you must select the variant from a predefined list that has been curated by Slippers. The component also automatically adjusts the text size based on screen size and allows us to handle any internationalization efforts in the future. Text needs to read from right to left, text needs to be truncated etc.
| 6 |
28,847,821 | 101,054,362 |
2022-01-21 16:41:33.913
|
Migrate all Button components
|
## Goal
Replace all <SlpButton> components in the Buyer Experience repo to use <SlpButton> from slippers-ui.
**Storybook:** https://gitlab-com.gitlab.io/marketing/digital-experience/slippers-ui/?path=/story/components-button--default
**Usage:** https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/blob/main/src/components/Button/Button.stories.js
**Steps to complete:**
The slippers-ui buttons are globally imported, remove all local imports.
```
import SlpButton from '~/components/button.vue
components: {
SlpButton,
}
```
and update the props (if they've changed). I've removed the dataGaName and dataGALocation props on the button component, I felt they were specific to our product and not all consumers of slippers-ui would need them. I'm open to adding them back, but would prefer if we added them on instantiation.
Once that's done, should be safe to remove button.vue
| 2 |
28,847,821 | 101,054,318 |
2022-01-21 16:40:55.480
|
Replace existing styling with Slippers V1
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[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 | 101,054,278 |
2022-01-21 16:39:50.976
|
Import Slippers V1 into the Buyer Experience project
|
## 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
| 2 |
28,847,821 | 100,943,719 |
2022-01-19 23:59:44.145
|
Follow-up from "Navigation MVC4"
|
The following discussion from gitlab-com/www-gitlab-com!95836 should be addressed:
- [ ] Top banner displayed must result in dropdown offset
- [ ] Dropping in here that when hovering, the carats don't have the same transition as the rest of the dropdown, so they briefly appear first.
> 
- [ ] WAVE accessibility errors
> 
| 1 |
28,847,821 | 100,873,444 |
2022-01-19 01:09:24.412
|
Document Google Analytics Updates
|
## Goal
Create new and/or revise existing handbooks to document the marketing website's **Google Analytics 4** data, specifically:
- Engagement metrics and conversions (how to measure success)
- Tracking methodology (where does the data come from?)
- Dashboard directory (explanation of the visualized data for self-service team members)
## Page(s)
Which page(s) are involved in this request?
* General GA overview (marketing POV): https://about.gitlab.com/handbook/marketing/inbound-marketing/search-marketing/analytics/
* GA to Bigquery data: https://about.gitlab.com/handbook/business-technology/data-team/data-catalog/web-traffic-analysis/
* DEX dataLayer and element attributes: https://about.gitlab.com/handbook/marketing/digital-experience/data-dictionary/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich
- [ ] Consulted: @mpreuss22
- [ ] Informed: @fqureshi @justin.vetter @laurenbarker @RLeihe268
## In scope
What is within scope of this request?
- [ ] Review existing handbook pages about Google Analytics
- [ ] Update handbooks to align with GA4
- [ ] Optional: add new handbooks
- [ ] Optional: archive irrelevant handbooks
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 100,868,918 |
2022-01-18 21:59:50.657
|
[Transition 50 Pages] Child: Topics / Severless
|
## Goal
We want to move https://about.gitlab.com/topics/serverless/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
## Page(s)
- [Serverless](https://about.gitlab.com/topics/serverless/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [ ] Yes
- [x] No
## 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
* [ ] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review
| 2 |
28,847,821 | 100,868,740 |
2022-01-18 21:54:14.954
|
[Transition 50 Pages] Child: Topics / Micro Services
|
## Goal
We want to move https://about.gitlab.com/topics/microservices/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
## Page(s)
- [Microservices](https://about.gitlab.com/topics/microservices/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [ ] Yes
- [x] No
## 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
* [ ] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review
| 1 |
28,847,821 | 100,867,939 |
2022-01-18 21:27:02.894
|
[Transition 50 Pages] Child: Topics / Devops Platform
|
## Goal
We want to move https://about.gitlab.com/topics/devops-platform/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
## Page(s)
Which page(s) are involved in this request?
[Devops Platform Page](https://about.gitlab.com/topics/devops-platform/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [ ] Yes
- [x] No
## 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
* [ ] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review
| 2 |
28,847,821 | 100,867,813 |
2022-01-18 21:25:42.593
|
[Transition 50 Pages] Child: Topics / Version Control
|
## Goal
We want to move https://about.gitlab.com/topics/version-control/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
## Page(s)
- [CI/CD](https://about.gitlab.com/topics/version-control/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [ ] Yes
- [x] No
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: TBD
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
* [ ] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review
| 2 |
28,847,821 | 100,867,434 |
2022-01-18 21:14:26.453
|
[Transition 50 Pages] Child: Topics / DevOps
|
## Goal
We want to move https://about.gitlab.com/topics/devops/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
## Page(s)
Which page(s) are involved in this request?
[DevOps page](https://about.gitlab.com/topics/devops/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [ ] Yes
- [x] No
## 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
* [ ] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [x] Engineering
- [x] UX Review
| 2 |
28,847,821 | 100,872,277 |
2022-01-13 23:23:30.948
|
Add Linter to Buyer's Experience
|
## Goal
We would like to add a Linter to our buyer's experience repo which will improve code consistency as measured by xxx.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jgarc
- [ ] Consulted: `DE ENG`
- [ ] Informed: `@mpreuss`
## In scope
What is within scope of this request?
- [ ] Add linter to buyer's experience
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Alter linting in Slippers
- Alter linting to `www`
## Requirements
What are the requirements for this request? Checklist 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 | 100,612,611 |
2022-01-13 21:00:22.161
|
Turn on GitLab Reviewer Recommender Bot for Buyer Experience
|
## Goal
We would like to implement GitLab Reviewer Recommender Bot into the Buyer Experience repository which will improve efficiency for team members reviewing are deploying code.
### Jobs To Be Done
* **Situation**: *When a MR is created in the Buyer Experience repository it recommends reviewers based on the changes made*
* **Motivation**: *We want to automate the process of selecting reviewers*
* **Outcome**: *So we can improve efficiency*
## Page(s)
Which page(s) are involved in this request?
* The Buyer Experience repository
* Relevant [blog post](https://about.gitlab.com/blog/2022/01/04/the-road-to-smarter-code-reviewer-recommendations/) by Taylor Mccaskin
## 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?
- [ ] Implement Reviewer roulette for the Buyer Experience repository
## Out of scope
What is out of scope and not part of this iteration?
- Any design or template work
- Any work in 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
| 4 |
28,847,821 | 100,537,257 |
2022-01-12 20:45:07.214
|
Add transaction event for enhanced ecommerce for successful subscription purchases
|
## Goal
Track Google Enhanced Ecommerce events in the SaaS purchase flow, based on this specification: https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/f252fc80f1dd6799d19e4d57d6b4c239/Gitlab_GTM_DataLayer_Spec.pdf
### Jobs To Be Done
* **Situation**: *When a customer purchases SaaS subscriptions at `https://gitlab.com/-/subscriptions/new`*
* **Motivation**: *We want to record the transaction `dataLayer` events*
* **Outcome**: *So we can have analytics across the entire purchase flow*
## Page(s)
Which page(s) are involved in this request?
* [New SaaS subscription](https://gitlab.com/-/subscriptions/new)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @tywilliams
- [ ] Consulted: @dennis106
- [ ] Informed: @mpreuss22
## In scope
What is within scope of this request?
- [ ] Transaction `dataLayer` events for SaaS purchases in `gitlab.com`
## Out of scope
What is out of scope and not part of this iteration?
- Checkout events in the `dataLayer`
- Any analytics in `customers.gitlab.com`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 100,215,584 |
2022-01-06 18:37:22.681
|
Silent build fails not displaying in CI/CD
|
## Goal
We would like to display through Nuxt build output in our CI/CD to help diagnose errors and avoid silent build errors.
### Jobs To Be Done
* **Situation**: *When a MR is deployed to `main`*
* **Motivation**: *We want the full output of `yarn generate` in our `build` job*
* **Outcome**: *So we can see exactly where the build failed and avoid silent build errors*
## Page(s)
Which page(s) are involved in this request?
* `.gitlab-ci.yml`
### Examples of past silent build errors
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/123#note_803535037
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/149#note_822804320
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @tywilliams @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Iteration to `.gitlab-ci.yml`
## Out of scope
What is out of scope and not part of this iteration?
- Design, template, or content 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 | 100,213,184 |
2022-01-06 17:29:10.663
|
Update the images used by the pipeline in this project
|
The following discussion from !122 should be addressed:
- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/122#note_803461115): (+1 comment)
> Non blocking for this MR, but I think we should scope work required to create an image specific to our Buyer Experience repository. I'm not sure that tying ourselves to the one used for `www-gitlab-com` is sustainable long term.
We should either:
1. Create a specific image for this repository
1. Move the deploy stage back to using the Google SDK image once it supports the `-z` flag
| 6 |
28,847,821 | 100,038,487 |
2022-01-03 17:45:20.867
|
Solution page migration - Public Sector
|
Related to #191.
## Goal
We would like to migrate `/solutions/public-sector/` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the solutions template.
### Jobs To Be Done
* **Situation**: *When a user lands on* `/solutions/public-sector/`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*
## Page(s)
Which page(s) are involved in this request?
* `[Public Sector](https://about.gitlab.com/solutions/public-sector/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI: `@jariasc-ext`
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Applying the solutions template to this page
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
* Building a new template
* Any work in www-gitlab-com other than removing the page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
* [ ] Copy writing
* [ ] Illustration
* [ ] Custom Graphics
* [ ] Research
* [ ] Data / Analytics
* [ ] UX Design
* [x] Engineering
| 5 |
28,847,821 | 99,646,125 |
2021-12-22 18:53:41.035
|
Learn page migration - Landing
|
## Goal
We would like to migrate `/learn` landing page from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience).
### Jobs To Be Done
* **Situation**: *When a user lands on* `/learn`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*
## Page(s)
Which page(s) are involved in this request?
* `[Learn Landing Page](https://about.gitlab.com/learn/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
* [ ] DRI: `@jariasc-ext`
* [ ] Consulted: `@laurenbarker`
* [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/learn directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
* Any work in www-gitlab-com other than removing the page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
* [ ] Copy writing
* [ ] Illustration
* [ ] Custom Graphics
* [ ] Research
* [ ] Data / Analytics
* [ ] UX Design
* [x] Engineering
| 2 |
28,847,821 | 99,050,342 |
2021-12-15 00:57:39.448
|
Implement New LinkedIn Event-specific tracking using Insight Tag
|
## Goal
LinkedIn recently announced that it has added a new conversion pixel. TLDR version, there is a new pixel based on an insight called an `insights tag` rather than an `event-specific` action. The insight tag is more accurate than the event tag type. [Here is a link to the LinkedIn update](https://www.linkedin.com/help/lms/answer/a425606?accountId=502663326).
### Jobs To Be Done
* **Situation**: When people visit the GitLab website, there are certain conversion events that we would like to track within LinkedIn. Noted the conversion events that we are tracking in the `Pages` section
* **Motivation**: Because we run a number of ad campaigns in LinkedIn, implementing the new tags will help our demand generation team and agency, optimize to performance of a campaign.
* **Outcome**: We would be able to see exactly which conversion events are being completed for a campaign.
## Page(s)
Which page(s) are involved in this request?
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.
* Free Trial conversions - `window.lintrk('track', { conversion_id: 1111306 });`
* Webcast sign ups- `window.lintrk('track', { conversion_id: 1111314 });`
* Thank You Page For Events - `window.lintrk('track', { conversion_id: 2157650 });`
* Demo - `window.lintrk('track', { conversion_id: 1111250 });`
* Gated Asset download- `window.lintrk('track', { conversion_id: 1111282 });`
* Contact Sales - `window.lintrk('track', { conversion_id: 1111290 });`
* Public Sector - `window.lintrk('track', { conversion_id: 1111274 });`
* Newsletter - `window.lintrk('track', { conversion_id: 1111266 });`
* Live Events - `window.lintrk('track', { conversion_id: 1111258 });`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpreuss22 ? (Michael, I Slacked you about this and you said to tag you)
- [ ] Consulted: @mnguyen4
- [ ] Informed: @lstinson @zbadgley
## In scope
What is within scope of this request?
- [ ] Implement LinkedIn insight tags to appropriate conversion events
- [ ] 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
- [x] Data / Analytics: This is to add LinkedIn Insight conversion tags to relevant conversion events on the GitLab website. This allows us to optimize our campaigns that we run in LinkedIn.
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 98,976,264 |
2021-12-14 00:43:34.350
|
Replace form on /demo/ page with 3-minute demo video
|
## Goal
We would like to remove the form on the /demo/ page which will improve user experience per request from leadership. This is related to the following issue (but with simplified scope to only remove the form and display the video): [Proposal for ungated content journeys on the website](https://gitlab.com/gitlab-com/marketing/demand-generation/campaigns/-/issues/1823).
### Jobs To Be Done
* **Situation**: *When someone lands on the /demo/ page*
* **Motivation**: *We want to allow them to watch the 3 minute video without submitting a form*
* **Outcome**: *So we can educate them about GitLab as a DevOps Platform*
## Page(s)
Which page(s) are involved in this request?
* `[/demo/](https://about.gitlab.com/demo/)`
## 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?
- [x] Replace form on /demo/ page with the 3-minute video
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 98,973,203 |
2021-12-13 22:25:39.932
|
Better Devops Tools index page
|
## Goal
We would like to improve the Devops Tools index page so as to:
- Comply with copyright by removing competitor logos
- Make it easier to find specific vendors e.g. using command-F
- Allow for more information to be displayed in the future
### Jobs To Be Done
* **Situation**: *When I go to [Devops Tools](https://about.gitlab.com/devops-tools/)...*
* **Motivation**: *We want to see the names of the vendors instead of the logos*
* **Outcome**: *So we can not sue GitLab, and find specific vendors more easily*
## Page(s)
Which page(s) are involved in this request?
* [Devops Tools](https://about.gitlab.com/devops-tools/)
## Workfiles
* [Figma](https://www.figma.com/file/0avvI8lQ2XgiGbhGEiv2lh/DevOps-Tools-Landscape-1.1?node-id=0%3A1)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `@francispotter`
- [ ] Consulted: `@jfullam @dfrhodes`
- [ ] Informed: ``
## In scope
What is within scope of this request?
- [ ] Redesign the Devops Tools page so there are no vendor logos, but instead the names of the vendors. Do it in a way that doesn't allocate more space (implied importance) to vendors with longer names. One concept has been developed [here](https://12778-remove-competitor-logos-from-the-devops-tools-index-page.about.gitlab-review.app/devops-tools/) but needs some design improvement.
## Out of scope
What is out of scope and not part of this iteration?
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 4 |
28,847,821 | 98,972,938 |
2021-12-13 22:16:13.224
|
Add "add to cart" event to GTM dataLayer for usage tab
|
## Goal
We would like to add the "add to cart" dataLayer event to the view at `https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab` so we can gather analytics in GTM enhanced ecommerce.
### Jobs To Be Done
Implement the product impression event for `https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab` as outlined in the [specification doc](https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/uploads/f252fc80f1dd6799d19e4d57d6b4c239/Gitlab_GTM_DataLayer_Spec.pdf)
## Page(s)
Which page(s) are involved in this request?
* [https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab](https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @dennis106
- [ ] Informed: @mpreuss22
## In scope
What is within scope of this request?
- [ ] GTM dataLayer event on `https://gitlab.com/-/profile/usage_quotas#pipelines-quota-tab`
## Requirements
What are the requirements for this request? Checklist 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 | 98,632,588 |
2021-12-08 00:09:46.612
|
Solutions Template - UX Iteration
|
## Goal
We would like to gather Solution template iterations for the Buyer Experience repository here which will improve efficiency.
### Jobs To Be Done
* **Situation**: *When we notice a style is incorrect on the Solutions template*
* **Motivation**: *We want to document it here*
* **Outcome**: *So we can make MVC changes within MRs and link them all back to this issue*
## Page(s)
Which page(s) are involved in this request?
* All solutions pages built with the Buyer Experience repository
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Itemize the solution template updates
- [ ] Create MVC MRs for each adjustment, apply them to all solutions pages
## Out of scope
What is out of scope and not part of this iteration?
- Any adjustment in Slippers
- Any adjustment in www-gitlba-com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering
| 6 |
28,847,821 | 98,631,403 |
2021-12-07 23:16:38.541
|
DSN: Update marketing navigation 3.0
|
## Goal
We would like to update the navigation to include a "Buy now" button (and maybe a "Register" link) and display buttons always on tablet size, which will improve conversion as measured by increased sales.
### Jobs To Be Done
* **Situation**: *When a user visits our site...*
* **Motivation**: *they want to immediately buy our product...*
* **Outcome**: *so they can start using it right away.*
## Page(s)
Which page(s) are involved in this request?
- Marketing Navigation
- [Figma Designs](https://www.figma.com/file/y2B6qEaGOTDXI1tImIJ5Ct/Navigation-MVC4?node-id=233%3A449)
- [Google Doc Request](https://docs.google.com/document/d/1i9IfkaN6nb8yuzNKET54Kj8qhloo9_fnHg8CTA6NlMU/edit)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: @jgarc @mpreuss22
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Display all buttons on tablet size at all times
- [ ] Include a new "Buy now" button option in the nav
- [ ] Consider adding a "Register" link in the nav so users can sign up for a new account
- [ ] Rethink whether this should be two navs
## 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
| 2 |
28,847,821 | 98,422,601 |
2021-12-03 15:56:54.807
|
Call Bizable script in product via hardcode
|
## Goal
We would like to hardcode Bizable into the product instead of via GTM to have a consistent implementation across our sign up flow platforms. Calling Bizable via GTM also has data loss risk of 5-10%, so hardcoding it into the product eliminates that risk.
[Related thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/19#note_749577421)
### The Code
`<script async='' src='//cdn.bizible.com/scripts/bizible.js'></script>`
## Where would this project happen?
#### Insert here a bulleted list containing any URLs that we'll be updating or creating:
All approved gitlab.com pages in the Trial funnel (not Product pages):
* https://gitlab.com/-/trials/new
* https://gitlab.com/-/trials/select
* https://gitlab.com/users/sign_up
* https://gitlab.com/-/trial_registrations/new
* https://gitlab.com/users/almost_there
* https://gitlab.com/users/sign_up/groups/new
* https://gitlab.com/users/sign_up/projects/new
* https://gitlab.com/users/sign_up/groups_projects/new
* https://gitlab.com/users/sign_up/welcome/trial_getting_started
* Any other Trial funnel page(s)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: `@mpreuss22`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Adding the Bizable script to the pages listed above
## Requirements
What are the requirements for this 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 | 98,365,772 |
2021-12-02 16:59:37.674
|
ENG: Build anchor link functionality for heading titles
|
## Goal
We would like to include the anchor link functionality that displays on hover for section headers in the new repository. Section linking promotes self-service & self-learning which is in line with our all-remote culture. More on [answering with a link here](https://about.gitlab.com/company/culture/all-remote/self-service/#answer-with-a-link) >
### Jobs To Be Done
* **Situation**: *When looking for information GitLab*
* **Motivation**: *I want the ability to copy a link to a specific section*
* **Outcome**: *So I can save it or share it.*
## Page(s)
Which page(s) are involved in this request?
## Workfiles
Use the pajamas link icon instead of the current one
- Link icon svg: 
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @Tinaliseng
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 8 |
28,847,821 | 98,281,687 |
2021-12-02 00:52:10.492
|
Solution page migration - Devops Platform
|
Related to #191.
## Goal
We would like to migrate `/solutions/devops-platform/` from the [www-gitlab-com repository](https://gitlab.com/gitlab-com/www-gitlab-com) into the [buyer experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) and apply the new solutions template.
### Jobs To Be Done
* **Situation**: *When a user lands on* `/solutions/devops-platform/`, the theme is current with our Slippers Design System and built within the buyer experience repository.
* **Motivation**: *We want to migrate 50 pages into the buyer experience repository for FY22 Q4*
* **Outcome**: *So we can work more within the buyer experience repository and less in the www-gitlab-com repository which will increase team efficiency and deliver code faster.*
## Page(s)
Which page(s) are involved in this request?
* `[Accelerating Software Delivery](https://about.gitlab.com/solutions/devops-platform/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dvilchis-ext
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
* [ ] Migrating content from www-gitlab-com into the buyer experience repository as a `yml` stored in the [/content/solutions directory](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content)
* [ ] Applying the solutions template to this page
* [ ] Building a new component if an acceptable one does not exist
* [ ] Creating an additional MR to remove this page from the www-gitlab-com repository
## Out of scope
What is out of scope and not part of this iteration?
* Building a new template
* Any work in www-gitlab-com other than removing the page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 8 |
28,847,821 | 97,767,631 |
2021-11-22 21:29:13.130
|
UX: Pathfactory implementation / Design mock-ups
|
## Goal
I would like to create design mock-ups to explore how and where we can display Pathfactory's Web Tools widget and or carousel.
### Jobs To Be Done
* **Situation**: *When visiting about.gitlab.com*
* **Motivation**: *I want to see content that is relevant to my interest quickly*
* **Outcome**: *So that I can learn about a topic with little effort*
## Page(s)
Which page(s) are involved in this request?
* TBD-WIP
## Workfiles
* Figma - N/A
### Documents
* [GitLab <> Pathfactory agenda](https://docs.google.com/document/d/1YzcqYo4AJjXLEZJsTHkuEwGpjk_XxeBLr41aAjLsV2c/edit?usp=sharing)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran @nikkiroth @mackanic @ncregan
- [ ] Informed: `@mpreuss22` @ndubord
## In scope
What is within scope of this request?
- [ ] Design mock-ups
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 97,761,634 |
2021-11-22 19:34:06.117
|
UX: User research | Why Premium? & Why Ultimate pages
|
## Goal
When making updates to the [Why Premium?](https://about.gitlab.com/pricing/premium/) & [Why Ultimate?](https://about.gitlab.com/pricing/ultimate/) pricing pages, I want to first do research with our end users, so I can better understand how they use the current layout and what changes they would like to see.
### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to easily find information about pricing*
* **Outcome**: *So I can make an informed purchasing decision.*
## Set up
#### What’s being tested?
* [Why Premium?](https://about.gitlab.com/pricing/premium/)
* [Why Ultimate?](https://about.gitlab.com/pricing/premium/)
#### How?
* https://www.usertesting.com/
- [ ] 1. Draft session: Run with 1 user and review
- [ ] 2. Duplicate test and edit (if it needs editing)
- [ ] 3. A/B tests:
- [ ] 3.1 Test 1: 4 participants will complete tasks on the current Why Premium? page.
- [ ] 3.2 Test 2: 4 participants will complete tasks on the current Why Ultimate? page.
#### General Questions
1. Is there anything we want to highlight?
1. Is there anything new we want to add?
1. Is there anything we can remove?
#### Research Questions
* Can users easily find the things they are looking for?
* Are users confused by how content is currently organized?
* Are there any improvements we can make to the current structure of the page?
* Are we using the best terminology?
* Is anything missing that a user would expect to be on the page?
* Is there anything on the page currently that shouldn't be there?
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] 4 user testing sessions [Why Premium?](https://about.gitlab.com/pricing/premium/)
- [ ] 4 user testing sessions [Why Ultimate?](https://about.gitlab.com/pricing/premium/)
## Out of scope
What is out of scope and not part of this iteration?
- Highlights reel
- Analysis and summary
## Requirements
What are the requirements for 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
| 3 |
28,847,821 | 97,761,011 |
2021-11-22 19:17:03.910
|
UX: User research | Features Page
|
## Goal
When making updates to the [Features page](https://about.gitlab.com/features/), I want to first do research with our end users, so I can better understand how they use the current layout and what changes they would like to see.
### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to easily find information about features that are relevant to my needs*
* **Outcome**: *To better understand if GitLab is the right solution for my problems*
## Set up
#### What’s being tested?
* [Features: Current page](https://about.gitlab.com/features/)
* [Features: Figma mock-up](https://www.figma.com/proto/XsnwxTLYPAN0j19vS6iSXm/Features-2.0?page-id=15%3A3641&node-id=37%3A2997&viewport=241%2C48%2C0.45&scaling=min-zoom&starting-point-node-id=37%3A2997)
#### How?
* https://www.usertesting.com/
- [x] 1. Pilot session(s): Run with 1 user and review
- [x] 1.1 [Pilot 1](https://app.usertesting.com/v/4929c951-c8eb-4fe2-a822-9ffa62dfc536?encrypted_video_handle=b8e9bd98-021f-46c5-86ea-6b40f219c6df&shared_via=link) - _failed due to mock-up not loading_
- [x] 1.2 [Pilot 2](https://app.usertesting.com/v/28932e41-4415-4c85-aa57-e3244c8b9a64?encrypted_video_handle=471bacd8-26ac-403a-bb01-7578339d20b5&shared_via=link)
- [ ] 2. A/B tests:
- [ ] 2.1 Test 1: 4 participants will complete tasks for the current live page and repeat the tasks on the new Figma prototype.
- [ ] 2.2 Test 2: 4 participants will complete tasks for the new Figma prototype and repeat the tasks on the current live page.
#### General Questions
1. Is there anything we want to highlight?
1. Is there anything new we want to add?
1. Is there anything we can remove?
#### Research Questions
* Can users easily find the things they are looking for?
* Are users confused by how content is currently organized?
* Are there any improvements we can make to the current structure of the page?
* Are we using the best terminology?
* Is anything missing that a user would expect to be on the page?
* Is there anything on the page currently that shouldn't be there?
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @Tinaliseng
- [ ] Consulted: @jhalloran `engineer - TBD`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] 4 user testing sessions [current page](https://about.gitlab.com/features/)
- [ ] 4 user testing sessions [Figma prototype](https://www.figma.com/file/XsnwxTLYPAN0j19vS6iSXm/Features-2.0?node-id=15%3A3641)
## Out of scope
What is out of scope and not part of this iteration?
- Highlights reel
- Analysis and summary
## Requirements
What are the requirements for 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
| 3 |
28,847,821 | 97,758,666 |
2021-11-22 18:33:53.690
|
ENG: Dynamic breakpoints for navigation different language support
|
## Goal
We would like to investigate if it is feasible to create dynamic breakpoints in the navigation which will improve the experience for users who use GitLab in a language other than English as measured by not having overlapping elements.
Based on [this LogRocket session](https://app.logrocket.com/9jygng/gitlab/s/5-777d1b7e-98ed-4c5e-bd2d-d8db30e1df15/0?t=1637598795696) where the user was using GitLab in a Cyrillic language and many elements of the navigation overlapped making them difficult to read potentially unable to click.
### Jobs To Be Done
* **Situation**: *When a user uses the GitLab navigation...*
* **Motivation**: *they want to be able to easily read and click through all of the elements...*
* **Outcome**: *So that they can get wherever they need to go.*
## Page(s)
Which page(s) are involved in this request?
* Navigation (all pages)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jgarc
- [ ] Consulted: @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Discover if it is possible to create dynamic breakpoints in the navigation as text increases or decreases
- [ ] Find out the difficulty of implementing the fix if it exists
## 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
- [ ] UX Design
- [X] Engineering
| 4 |
28,847,821 | 97,751,084 |
2021-11-22 16:00:17.663
|
DSN: Improve free trial sign up experience
|
## Goal
We would like to X which will improve Y as measured by Z.
### Jobs To Be Done
* **Situation**: *When a user wants to start a free trial...*
* **Motivation**: *They want to have an easy and seamless sign up experience...*
* **Outcome**: *So that they can start using our product quickly.*
## Page(s)
Which page(s) are involved in this request?
* [SaaS Free trial landing page](https://gitlab.com/-/trials/new?glm_content=free-trial&glm_source=about.gitlab.com)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jhalloran
- [ ] Consulted: `@s_awezec` `@gdoud` `@jackib` `@mkarampalas` `@Tinaliseng`
- [ ] Informed: `@kcomoli`
## In scope
What is within scope of this request?
Suggestions that were moved to engineering:
1. Small update to the Country form field selector in order to keep a neutral stance on geo-politics
[Issue](https://gitlab.com/gitlab-org/gitlab/-/issues/349333#note_820089507) & [Figma](https://www.figma.com/file/NxDRjifeVhRIVPFrTzeQdg/Free-Trial-updates?node-id=135%3A15433)
1. Navigation change from "Login" to profile icon - [MR](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/95836)
1. Login page Free Trial breakdown by date [Figma](https://www.figma.com/file/muPxDrFbQdLLI9SAj8EXUK/Free-Trial-CTA-on-Sign-Up?node-id=119%3A10040) & ENG Issue
1. Removed pre-filled username from form field
Suggestions that still need work:
1. "Just do it" best practice [suggestions 1-6](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/213):
1. [ ] **Autofocus on the first field**
1. [ ] **Use specialized mobile keyboards** - label textboxes: email (type=email), telephone numbers (type=tel), URLs (type=url), and numbers (type=num)
1. [ ] **In line validation** - show the error as soon as the user has left the field (rather than on submit), and the error should be specific
1. [ ] **Make labels clickable** - add the input element inside its respective label element
1. [ ] **Let users see their password** - less onerous than requiring them to type it twice and allows the user to see if typed correctly
* [Figma example](https://www.figma.com/file/NxDRjifeVhRIVPFrTzeQdg/Free-Trial-updates?node-id=44%3A6639)
1. [ ] **Use button text to expose the value waiting for users on the other side** - Give the user context for their actions
* On [registration page](https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=free-trial) change "Continue" to "Create account"
* On [start free trial page](https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=free-trial) change "Continue" to "Start free trial"
1. "Just do it" best practice [suggestion 7](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/214)
* **Replace Sign in/up with Login/Register**
1. "Just do it" best practice [suggestion 8](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/215)
* **Move register option to top of login page and vice versa**
1. "Just do it" best practice [suggestion 9](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/216)
**Remember typed values between password attempts** - If the user enters their password unsuccessfully, they should not have to retype their email again. If we allow the user to see their password (https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/213), don’t erase that either – they may want to check to see if they made a typo.
1. "Just do it" best practice [suggestion 10](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/217)
* **Remember email on the “reset password" page**
1. "Just do it" best practice [suggestion 11](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/268)
* **Alternative suggested username** (without pre-filling the form field)
## Out of scope
What is out of scope and not part of this iteration?
- Free trial product experience
## Requirements
What are the requirements for this request? Checklist 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 | 97,511,050 |
2021-11-17 21:51:24.536
|
[Transition 50 Pages] - Pricing
|
## Goal
We want to move https://about.gitlab.com/pricing/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*
## Page(s)
- [Pricing](https://about.gitlab.com/pricing/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [x] Yes
- [ ] No
## 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
* [x] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] Apply [feature pop-up](https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/1536)
##3 Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review
| 4 |
28,847,821 | 97,511,021 |
2021-11-17 21:49:59.546
|
[Transition 50 Pages] - Homepage
|
## Goal
We want to move https://about.gitlab.com to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*
## Page(s)
- [Homepage](https://about.gitlab.com)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [x] Yes
- [ ] No
## 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
* [x] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review
| 4 |
28,847,821 | 97,511,008 |
2021-11-17 21:49:05.432
|
[Transition 50 Pages] - Free Trial
|
## Goal
We want to move https://about.gitlab.com/free-trial/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*
## Page(s)
- [Free Trial](https://about.gitlab.com/free-trial/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [x] Yes
- [ ] No
## 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
* [x] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review
| 4 |
28,847,821 | 97,510,913 |
2021-11-17 21:45:56.022
|
[Transition 50 Pages] - Install
|
## Goal
We want to move https://about.gitlab.com/install/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*
## Page(s)
- [Install](https://about.gitlab.com/install/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [x] Yes
- [ ] No
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: TBD
- [ ] Consulted: @jhalloran @fqureshi @justin.vetter
- [ ] Informed: `Everyone`
## In scope
* [x] Transition page
* [ ] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review
| 8 |
28,847,821 | 97,510,570 |
2021-11-17 21:35:12.138
|
[Transition 50 Pages] - Support
|
## Goal
We want to move https://about.gitlab.com/support/ to our [new site architecture](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/389) which will improve both efficiency and productivity as measured by time to complete issues.
### Jobs To Be Done
* **Situation**: *When working on the Marketing site*
* **Motivation**: *I want to be able to work quickly and efficiently*
* **Outcome**: *So I can accomplish everything in each Digital Experience quarterly plan*
## Page(s)
- [Support](https://about.gitlab.com/support/)
### Has [Slippers UI](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=356%3A18) already been applied?
- [ ] Yes
- [x] No
## 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
* [x] Transition page
* [x] Apply Slippers UI
### Stretch goal
- [ ] None as of now
### Out of scope
- Additional design updates
## Requirements
- [ ] Data / Analytics
- [ ] Engineering
- [ ] UX Review
| 6 |
28,847,821 | 97,424,569 |
2021-11-16 13:36:44.175
|
Add Buy Now Button to Website
|
We have a significant eComm new transaction goal for Q4 FY22, which is 1275 total eComm transactions. In Q3, we achieved 840 transactions. As the Marketing DRI for eComm, I am requesting that Inbound Marketing team create a buy now button that lands a user on the eComm page. This will allow us to directly harvest inbound organic traffic and convert it to a sale. We estimate that buy adding this feature to the website, we can generate an additional 100 eCommerce sales per month.
**Requirements**
[Requirements document for web team review/collaboration is here.](https://docs.google.com/document/d/1i9IfkaN6nb8yuzNKET54Kj8qhloo9_fnHg8CTA6NlMU/edit?usp=sharing)
**Measurement Plan**
[Measurement Plan Document is here.](https://docs.google.com/document/d/11XHQPd4L0_yBGEqgud9gjuSEFeoHffI0z6v7v1dvh0I/edit)
| 8 |
28,847,821 | 96,617,450 |
2021-11-02 19:19:30.218
|
Redirect gitlab.com/pricing To Pricing Page
|
## Goal
I would like to redirect traffic from this page which will improve traffic (and potentially the amount of people who convert) as measured by pageviews and traffic to the checkout page.
### Jobs To Be Done
* **Situation**: *When someone lands on gitlab.com/pricing*
* **Motivation**: *We want to redirect them to about.gitlab.com/pricing*
* **Outcome**: *So they can get to the content they're looking for*
## Page(s)
Which page(s) are involved in this request?
* [404 Pricing Page](https://gitlab.com/pricing)
* [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: @laurenbarker
- [ ] Consulted: `@mpreuss22`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] 301 Redirect
## Requirements
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 | 96,617,300 |
2021-11-02 19:14:44.487
|
Set up social tags site wide for proper sharing
|
## Goal
We would like to set up the correct tagging for social sharing which will improve the display of content shared from GitLab's Marketing site as measured by social engagement.
### Jobs To Be Done
* **Situation**: *When someone shares content to Twitter, Facebook, or LinkedIn*
* **Motivation**: *We want the correct title, image, and body content to display*
* **Outcome**: *So we can make it easy to engage with content on these channels*
## 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?
- [ ] All Marketing site page
## Out of scope
What is out of scope and not part of this iteration?
- Any Handbook pages
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Engineering
| 2 |
28,847,821 | 96,100,628 |
2021-10-25 16:46:11.333
|
ENG: Stages of DevOps lifecycle page MVC1
|
Related to: https://gitlab.com/gitlab-com/marketing/inbound-marketing/marketing-website/-/issues/178
[Figma file](https://www.figma.com/file/4Uy6oP7zWfH1r5wnjlaY7g/Stages-of-the-DevOps-Lifecycle?node-id=0%3A1)
| 3 |
28,847,821 | 101,241,984 |
2021-10-08 17:46:42.053
|
Partner page UI updates / fixes
|
# Goal
Fix inconsistencies and update UI.
## Why
We will be pointing users to [Partners / Google Cloud](https://about.gitlab.com/partners/technology-partners/google-cloud-platform/) from the homepage hero next week. We want visitors to see a fluid and consistent design so they can feel confident about our product.
## Scope
- [ ] Remove confetti from the heading title (positioning is hard to control and there are enough visuals on the page)
- [ ] Swap purple CTA with the outline CTA
- [ ] Update card plate (add stroke) - [Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=2397%3A1400)
- [ ] Remove line that appears behind the cards
- [x] Increase spacing above "Get started with GitLab and GCP joint solutions" to 96px
- [ ] Increase spacing above and below the testimonial to 96px
- [Screen_Shot_2021-10-08_at_10.38.22_AM](/uploads/b3039cb54997953e72681fb5a0a31e15/Screen_Shot_2021-10-08_at_10.38.22_AM.png)
- [Partner_Page_errors](/uploads/67516f07b0b6ea8341c39bc41fbea319/Partner_Page_errors.png)
- [Partner_Page_errors_2](/uploads/b9b37bec94c67b691b0b952490732922/Partner_Page_errors_2.png)
- [ ] Update Body-2 (14px) copy to Body-1 (16px)
- [Screen_Shot_2021-10-25_at_11.33.17](/uploads/62b81bad1f08a5f65819659131cee20a/Screen_Shot_2021-10-25_at_11.33.17.png)
- [Screen_Shot_2021-10-25_at_11.33.55](/uploads/387ab9ee2c13cdf51a9186713b1a330b/Screen_Shot_2021-10-25_at_11.33.55.png)
### Relates to:
Slack thread > https://gitlab.slack.com/archives/G01JH8CA8F3/p1633639300033500
| 3 |
28,847,821 | 95,838,556 |
2021-08-13 16:30:24.363
|
Request: Add Language drop down on Resources page
|
## Before creating an issue
- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.
## Where would this project happen?
#### Insert here a bulleted list containing any URLs that we'll be updating or creating:
- https://about.gitlab.com/resources/
## What does the request INCLUDE?
#### Insert the request here:
* Add a `Language` drop down that will filter the content by language
* Current languages available: Japanese, Korean, French, Italian, Spanish, Portuguese, Russian, German
* Default the `Language` to English
* Why: Currently when we enter new assets on the resources page, they appear in the order added. Defaulting to English will show only the English assets, but still allow users to easily select another language.
* Add language field on yml - https://gitlab.com/gitlab-com/www-gitlab-com/-/edit/master/data/resources.yml
#### Insert here a bulleted list containing links to any relevant resources:
Current languages available:
* Japanese
* Korean
* French
* Italian
* Spanish
* Portuguese
* Russian
* German
## What does the request EXCLUDE?
#### Insert here any items that are out of scope for this iteration:
*Example: Because we need to get this out quickly, we will not be adding new styles, just updating the content.*
## Why would we do this?
#### Insert here why we want to do this:
We are generating more localized content (eBooks, whitepapers, webcasts, etc), but users do not have an easy way to filter for their preferred language on https://about.gitlab.com/resources/.
Most of our localized content has not been added to this page, but we would like to add it.
## Who would be involved?
If you are requesting a deliverable from someone, please create a separate issue with a due date, assign it to that individual, and link it to this issue as a blocker.
Please use the R.A.C.I. framework. This includes RESPONSIBLE individuals who are discipline DRIs, a single person ACCOUNTABLE for the project (usually the requestor), a backup for when they accountable is unavailable, the CONSULTED who have knowledge and feedback to consider but not necessarily implement, and stakeholders who should be INFORMED about the project.
#### Insert here a list of people related to the project AND why you listed them.
*Example: @ brandon_lyon as responsible for engineering, @ jhalloran as responsible for UX, @ tbarr for approval, @ dmor as backup for @ tbarr, @ shanerice for analytics and SEO, @ awithers for copy direction, @ lsayers for legal department awareness*.
## When would you like it done?
If your request has multiple delivery dates, please create an epic with a separate issue for each deadline.
Dates without reason are difficult to prioritize. Without enough lead time we will be unable to meet your deadline.
#### Insert here your requested date AND why:
*Example: Our due date is X. We want to launch this page before a press release on X for a trade show that happens on Y. I have submitted this over a quarter in advance with the hope that it can be prioritized as a quarterly OKR.*
- [x] No deadline requested.
- [ ] YYYY-MM-DD-HH, insert reason.
| 2 |
28,847,821 | 97,121,859 |
2021-08-09 18:27:20.140
|
ENG: Fix card plate inconsistencies
|
## What
Adjust all card plates for a consistent UX.
Using this [blog card](https://gitlab-com.gitlab.io/marketing/inbound-marketing/slippers-ui/?path=/story/components-cards-blog--blog-card) as a base, make sure all other cards have the same plate.
- [ ] Stroke is consistent
- [ ] Drop shadow on default is consistent
- [ ] Drop shadow on hover is consistent
- [ ] Border radius is consisten
DRI:
- @jgarc
- @Tinaliseng
Consulted:
- [x] @jhalloran
| 2 |
28,847,821 | 95,839,875 |
2021-08-06 20:31:24.479
|
Update subtitle on comparison infographic
|
# Relevant URLs
[Tina caught a typo that's hardcoded in the Comparison Infographic component](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/87900#note_645330744).
We need to update the component to fix this, I think we should do the following:
1. Make `Feature maturity comparison against set of industry standards` a prop in the component so it's configurable.
1. Make `Learn more about our scoring methodology` a prop in the component so it's configurable as well.
1. Update the component in `www-gitlab-com` to use it as such.
## Scope/Deliverables
- [x] Make the heading a prop
- [x] Make the scoring language a prop
- [x] Update the implementation in the `www-gitlab-com` repository.
## Requirements
- [ ] Review by UX/UI
- [x] Review by engineering
## Release history:
```
Text
```
| 2 |
28,847,821 | 95,720,854 |
2021-07-26 15:13:55.910
|
ENG: Update All-Remote landing page
|
## Goal
The All-Remote Team would like to bring [our main landing page](https://allremote.info) up to current content and brand standards, which will improve performance as measured by clicks.
### Jobs To Be Done
* **Situation**: *In FY22Q4*
* **Motivation**: *We want to reorganize and update the content of this page*
* **Outcome**: *So it represents GitLab well as the first engagement many people have with our brand; provides a good user experience; and facilitates more engagement with our site.*
## Before creating an issue
- [x] I have reviewed the [Setting yourself up for success](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/website/#requesting-support) section of the website handbook.
- [x] I acknowledge that any content updates should also update [social media content](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/admin/#data-needed-on-pages-in-order-for-links-to-work-on-social-media) such as [images](https://about.gitlab.com/handbook/marketing/corporate-marketing/social-marketing/#social-media-design), titles, and descriptions on relevant pages. Not doing this can negatively impact related campaigns.
## Where would this project happen?
#### Insert here a bulleted list containing any URLs that we'll be updating or creating:
- https://about.gitlab.com/company/culture/all-remote/
## What does the request INCLUDE?
#### Insert the request here:
Update the All-Remote page using [the updated content document here](https://docs.google.com/document/d/1O8DKXTx2_3Jk5cAluuwUelyfd-FCuPpw8EJNz4tMYgQ/edit).
#### Insert here a bulleted list containing links to any relevant resources:
See above
## What does the request EXCLUDE?
#### Insert here any items that are out of scope for this iteration:
Not creating a new page. Not creating any new content. This should use existing assets and resources.
## Why would we do this?
#### Insert here why we want to do this:
Remote work content is a major traffic driver to about.gitlab.com. We are in the top 100 pages on the site, yet we have lower engagement and click rates, lower conversion, and this page is out of date and difficult to parse. We can increase traffic and engagement by improving this page.
This is part of an ongoing effort to improve our all-remote content marketing.
## Who would be involved?
#### Insert here a list of people related to the project AND why you listed them.
DRI: @jessicareeder
Stakeholders: @bbula and @dmurph
## When would you like it done?
If your request has multiple delivery dates, please create an epic with a separate issue for each deadline.
Dates without reason are difficult to prioritize. Without enough lead time we will be unable to meet your deadline.
#### Insert here your requested date AND why:
*Example: Our due date is X. We want to launch this page before a press release on X for a trade show that happens on Y. I have submitted this over a quarter in advance with the hope that it can be prioritized as a quarterly OKR.*
- [ ] No deadline requested.
- [x] Within FY22Q4.
#### Workfiles
* [Figma file](https://www.figma.com/file/ppz12kmHnYJpsvRILxbdi8/All-Remote-UX-Updates?node-id=0%3A1)
| 8 |
28,847,821 | 95,832,858 |
2021-06-08 15:14:21.471
|
Blog post template - Fix anchor links
|
While trying to create a jump menu on the 14.0 breaking changes post that anchor links are not properly rendering/working on new blog posts. More info: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/83720#note_594873900
| 2 |
28,847,821 | 95,837,640 |
2021-05-11 10:00:46.727
|
Mobile Usability - Text too small
|
## Overview
The font size for the page is too small to be legible and would require mobile visitors to “pinch to zoom” in order to read.
**Solution** - After specifying a viewport for your web pages, set your font sizes to scale properly within the viewport.
#### Example Screenshot
URL - https://about.gitlab.com/solutions/benefits-of-using-version-control/
Screenshot taken with [Google Mobile-Friendly Test Tool](https://search.google.com/test/mobile-friendly?id=wkrb6lCQ4qF8Q_TZAa9fTQ).
### Affected URLs
Initial analysis indicates this error is predominantly found on URLs where the content elements such as tables and images are wider than the viewport.
This can be viewed on the about.gitlab.com [Google Search Console page experience report](https://search.google.com/u/1/search-console/mobile-usability/drilldown?resource_id=https%3A%2F%2Fabout.gitlab.com%2F&item_key=CAw).
| 4 |
28,847,821 | 95,837,680 |
2021-05-11 09:53:07.966
|
Mobile Usability - Content wider than screen
|
## Overview
Certain pages appears broken when viewed on a mobile device causing the user to scroll horizontally and vertically to view the content. This seems to be affecting URLs with embedded content such as buttons, images, tables and iframes that are not responsive.
### Example Screenshots
### Solution
To fix this error, make sure the pages use relative width and position values for CSS elements, and make sure images can scale as well.
### Affected URLs
This can be viewed on the about.gitlab.com [Google Search Console page experience report](https://search.google.com/u/1/search-console/mobile-usability/drilldown?resource_id=https%3A%2F%2Fabout.gitlab.com%2F&item_key=CAk).
| 4 |
28,847,821 | 97,576,927 |
2021-03-08 18:01:29.001
|
ENG: Netlify CMS: Migrate DevOps Platform child page to Netlify CMS
|
# Relevant URLs
We recently [fixed a child topics page](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/76751) for `/devops-platform/ten-key-devops-platform-features`, but it's not yet in Netlify CMS.
Need to duplicate our process from the [child topics page migration epic](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/285).
## Scope/Deliverables
- [ ] Move Ten Key DevOps Platform Features into Netlify CMS
## Requirements
- [ ] Review by engineering
## Release history:
```
Move Ten Key DevOps Platform Features into Netlify CMS
```
| 1 |
28,847,821 | 97,572,706 |
2021-02-25 02:46:49.957
|
ENG: <hr> element with single resource type
|
When there is a single resource type on a topics template, a `<hr>` element displays before the content is outputted.
Lets remove the `<hr>` element when there is only 1 resource type.
Example of this exist here:
https://about.gitlab.com/topics/ci-cd/continuous-integration-server/
| 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.