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 | 125,697,119 |
2023-03-23 18:52:20.666
|
[ENG] Localized Navigation
|
## Goal
We would like enable our navigation to be translated when serving German, French, and Japanese localized pages.
#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.
## Which page(s) are involved in this request?
* All localized pages in the Buyer Experience repository
## In scope
What is within scope of this request?
- [ ] German translations using Google Translate for navigation
- [ ] Japanese translations using Google Translate for navigation
- [ ] French translations using Google Translate for navigation
- [ ] Enabling navigation to serve translated versions
- [ ] Shipping localized navigation to localized pages in Buyer Expeirence
- [ ] Verifying in production it's working correctly
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: 'Engineer'
- [ ] Consulted: `@laurenbarker`
- [ ] Informed: `Everyone`
| 6 |
28,847,821 | 125,694,753 |
2023-03-23 16:59:13.018
|
Follow-up from "Add automated schema markup blog posts"
|
The following discussion from gitlab-com/www-gitlab-com!121760 should be addressed:
In Scope
- remove datemodified field
- update blog url field
- TBD
| 2 |
28,847,821 | 125,692,776 |
2023-03-23 16:47:41.624
|
[ENG] Replace homepage hero images with svg's
|
## Goal
SVG's are smaller and scale better than png's, see if we can track down the source design files for the following assets and export as svg's.
1. https://about.gitlab.com/_nuxt/image/41d978.png
2. https://about.gitlab.com/_nuxt/image/20508c.png
3. https://about.gitlab.com/_nuxt/image/59ca91.png
### New images
[Home-svgs.zip](/uploads/88c40466073afd16a6209a37f0b5b4af/Home-svgs.zip)
| 1 |
28,847,821 | 108,033,251 |
2022-05-04 19:08:32.524
|
GA4: Properties
|
## Goal
Architect GA4 properties. The concept of "views" from GA Universal no longer exists. Map out existing GAU properties and views to the new GA4 property-level structure.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 108,033,068 |
2022-05-04 19:02:20.269
|
GA4: Ecommerce dataLayer
|
## Goal
Update the existing checkout and transaction dataLayers to include the new GA4 dataLayer syntax. We will be parallel tracking ecommerce events into both Universal GA and GA4 until EOY '22, which is why we need both dataLayer events.
New dimensions:
1. Recently, the namespace id was passed into dimension 36 for each transaction. This will be `item_category3` within the GA4 dataLayer.
2. Users can reach the Checkout page from about.gitlab.com/pricing/ or gitlab.com (group billing section). We need to distinguish where the user came from. Adding the referrer (previous page's hostname) into a new variable would allow us to see the marketing site's impact on users entering checkout. This will be `item_category4` within the GA4 dataLayer.
**Checkout**
Update the existing Checkout dataLayer script to include the new GA4 syntax. Lowercase values.
```
<script>
dataLayer.push({ ecommerce: null });
// existing Universal GA code
dataLayer.push({
'event':'EECCheckout',
'currencyCode': 'USD',
'ecommerce': {
'checkout':{
'actionField': {'step': 1},
'products': [{
'name': 'GitLab Premium',
[...]
}]
}
}
});
// new GA4 code
dataLayer.push({
event: 'begin_checkout',
ecommerce: {
currency: 'USD',
items: [
{
item_id: '[product id]', //0001 for ultimate, 0002 for premium
item_name: '[product name]', //ultimate, premium
item_category: '[product category]', //devops, cicd
item_category2: '[saas or self managed]',
item_category3: '[namespace id]',
item_category4: '[previous page's hostname]', //about.gitlab.com or gitlab.com
price: [product price annual], //228.00, 1188.00
quantity: [product amount] //1, 200
}
]
}
});
</script>
```
**Transaction**
Update the existing Transaction dataLayer script to include the new GA4 syntax. Lowercase values.
```
<script>
dataLayer.push({ ecommerce: null });
// existing Universal GA code
dataLayer.push({
'event':'EECtransactionSuccess',
'ecommerce': {
'currencyCode': 'USD',
'purchase': {
'actionField': {
'id': [...]
},
'products': [{
[...]
}]
}
}
});
// new GA4 code
dataLayer.push({
event: 'purchase',
ecommerce: {
transaction_id: '[transaction id]',
value: [revenue],
tax: [tax],
currency: 'USD',
items: [{
item_id: '[product id]', //0001 for ultimate, 0002 for premium
item_name: '[product name]', //ultimate, premium
item_category: '[product category]', //devops, cicd
item_category2: '[saas or self managed]',
item_category3: '[namespace id]',
item_category4: '[previous page's hostname]', //about.gitlab.com or gitlab.com
price: [product price annual], //228.00, 1188.00
quantity: [product amount] //1, 200
}]
}
});
</script>
```
Guide:
https://developers.google.com/analytics/devguides/collection/ga4/ecommerce
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich @tywilliams
- [ ] Consulted: @mpreuss22
- [ ] Informed: @justin.vetter
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 6 |
28,847,821 | 108,033,031 |
2022-05-04 19:01:22.724
|
GA4: Translate Event Names
|
## Goal
Translate the events (category, action, label) from Universal GA to GA4 event syntax (event name, event parameter), including custom dimensions.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 2 |
28,847,821 | 108,033,005 |
2022-05-04 19:00:23.563
|
GA4: Basic Configuration
|
## Goal
Based on the GA4 properties outlined on this issue: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/859
Configure GA4 properties with essential events (ie. pageviews).
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 3 |
28,847,821 | 108,032,988 |
2022-05-04 18:59:26.005
|
GA4: OneTrust Google Consent Mode
|
## Goal
Google Consent Mode enables the machine learning modeling features within GA4, Google Ads, and Campaign Manager to fill in the data gap for users who opt out via OneTrust cookie consent.
Step by step implementation guide: https://community.cookiepro.com/s/article/UUID-d81787f6-685c-2262-36c3-5f1f3369e2a7?language=en_US
1. Place the default gtag script _before_ the Google Tag Manager and OneTrust scripts across all pages.
```
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'analytics_storage': 'denied',
'ad_storage': 'denied',
'functionality_storage': 'denied',
'region': ['EU', 'UK', 'PE', 'RU'],
'wait_for_update': 500
});
gtag('consent', 'default', {
'analytics_storage': 'granted',
'ad_storage': 'granted',
'functionality_storage': 'granted',
'wait_for_update': 500
});
</script>
<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXX');</script>
<!-- End Google Tag Manager -->
<!-- OneTrust Cookies Consent Notice start -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js" type="text/javascript" charset="UTF-8" data-domain-script="XXXXXX" ></script>
<script type="text/javascript">
function OptanonWrapper() { }
</script>
<!-- OneTrust Cookies Consent Notice end -->
```
2. Enable Google Consent Mode on OneTrust settings for each Geolocation Rules. Publish. This will dynamically update the consent values from the gtag script (code above ^^^) base on the actual user's consent.
3. Remove OneTrust autoblocking from the Google Tag Manager script. Hold off on this task for now. I'll need to ensure all tags within GTM have consent mode first.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [x] DRI: @dennischarukulvanich
- [ ] Consulted: @mpreuss22 @laurenbarker @justin.vetter @jburton
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 108,032,970 |
2022-05-04 18:59:03.865
|
Single pages accessibility audit (demo, ten, enterprise, etc)
|
## Goal
Run Axe Devtools report and fix failures on the following pages:
- [x] customers
- [x] demo
- [x] enterprise
- [x] fifteen
- [x] free-trial
- [x] get-help
- [x] get-started
- [x] home
- [x] livestream
- [x] pricing
- [x] sales
- [x] small-business
- [x] ten
- [x] terms
- [x] update
### 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 | 108,032,759 |
2022-05-04 18:56:38.672
|
Company page(s) accessibility audit
|
## Goal
A scan of the page with [axe DevTools](https://www.deque.com/axe/devtools/) yields the following results that should be addressed.
## Page(s)
Which page(s) are involved in this request?
* [Company](https://about.gitlab.com/company/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `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
- [x] Engineering
| 2 |
28,847,821 | 107,886,835 |
2022-05-02 18:31:20.226
|
Hero logo placement on mobile
|
### Describe the Bug
Logo placement is awkward on mobile
Current layout:
Update to:
## Page(s)
Which page(s) are involved in this request?
* All hero pages - Example: https://about.gitlab.com/small-business/ and https://about.gitlab.com/enterprise/
* [Figma file for reference](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=1787%3A7553)
## Requirements
What are the requirements for this request? Checklist 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 | 107,885,247 |
2022-05-02 17:48:22.547
|
Benefits block: Image disappears when interacting with the accordion
|
### Describe the Bug
Image disappears when interacting with the accordion.
Watch loom video:
https://www.loom.com/share/377b0963545c4770b83d6b3cca69d05c
### What's my browser?
Chrome
## Page(s)
Which page(s) are involved in this request?
* [Enterprise](https://about.gitlab.com/enterprise/)
* [Small Business](https://about.gitlab.com/small-business/)
Maybe more
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 107,876,764 |
2022-05-02 14:29:54.788
|
UI Fixes SMB - Showcase component spacing
|
## Goal
We would like to improve the spacing between sections to allow for breathing room.
Fix this bug https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/820#note_945131372
### Describe the Bug
Not a bug, just an update. Please increase the spacing between sections to 96px
## Page(s)
Which page(s) are involved in this request?
* [Solutions/small-business](https://about.gitlab.com/small-business/)
## Requirements
What are the requirements for this request? Checklist 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 | 107,563,009 |
2022-04-29 16:17:33.076
|
Bug: Footer: Solutions --> Education = wrong page, should direct to Campus
|
## Goal
The Solutions --> Education = goes to the wrong page, should direct to [Campus](https://about.gitlab.com/solutions/education/campus/).
It goes here now --> https://about.gitlab.com/solutions/education/
It should go --> https://about.gitlab.com/solutions/education/campus/
Also the frame around the left GitLab for Education Box is missing.
### Jobs To Be Done
* **Situation**: *When a clicks on Education in our footer...*
* **Motivation**: *We want to direct them to the campus page...*
* **Outcome**: *So we can make sure they are seeing the most relevant content.*
## Page(s)
Which page(s) are involved in this request?
* Footer
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jariasc-ext
- [ ] Consulted: @jhalloran @c_hupy @laurenbarker
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 107,558,219 |
2022-04-29 14:48:29.922
|
Pull Quote carousel is missing chevron/arrow icon on button
|
### Pages in scope
Any page that uses the pull-quote component (ex: [Sales](https://about.gitlab.com/sales/))
### Components in scope
`/components/pull-quote.vue` is missing the arrow that was on the next button. We should add back, or replace, what ever was at this path previously: (line 77) `/nuxt-images/icons/arrow.svg`
We should also add a label that describes what the button will do once clicked, and then hide the image from screen readers.
Ex:
```
<button
v-if="data.multiple_quotes"
class="quote-button"
@click="increaseIndex"
aria-label="Read next quote"
>
<img src="/nuxt-images/icons/arrow.svg" alt="" aria-hidden="true" />
</button>
| 1 |
28,847,821 | 107,558,201 |
2022-04-29 14:48:08.103
|
Fix remaining side menu overlap and positioning issues
|
This was recently fixed on the Stages DevOps Lifecycle page. ([MR](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/543))
### Components in scope
`/components/side-menu/side-menu.vue`
`/components/anchor-dropdown.vue`
### Pages in scope
[Get Help](https://about.gitlab.com/get-help/)
[Support](https://about.gitlab.com/support)
Desktop: Side menu should stop and/or disappear when it reaches the bottom of the main content. It should not continue scrolling to the footer.
Mobile: The anchor dropdown component replaces the side menu. The positioning of it should be adjusted so it does not cover up the heading of the page and is not overlapped by the nav.
| 2 |
28,847,821 | 107,442,873 |
2022-04-28 22:44:17.456
|
ENG | Tracking: Remove OneTrust Events
|
## Goal
OneTrust automatically sends events to Google Analytics from the cookie banner script. These events are labeled as an interaction event on Google Analytics, which is skewing bounce rate and creating a "not set" landing page. This can happen when an interaction event fires before or without a pageview. Typically, we would set the event as non-interaction on Google Tag Manager. However, these events are coming directly from OT, so we cannot adjust the event.
<img src="/uploads/bcc10f7d50780ead590588969ab818ea/Screen_Shot_2022-09-08_at_11.51.42_AM.png" width="600">
Per this [OneTrust guide](https://www.cookiepro.com/integrations/google-analytics/), we can disable OT from sending events to GA by placing this data attribute to the cookie banner script:<br/>
`data-ignore-ga='true'`
<img src="/uploads/6ed68923c5990dee05e324c69a106b47/Screen_Shot_2022-09-08_at_12.31.41_PM.png" width="800">
## Page(s)
Which page(s) are involved in this request?
* All the pages with OneTrust (gitlab.com, about, customers, docs, page, learn, etc.)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: Someone
- [ ] Consulted: @dennischarukulvanich
- [ ] Informed: @laurenbarker @justin.vetter
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 107,411,334 |
2022-04-28 17:48:58.149
|
H1 Heading Removed
|
The H1 heading is missing from the URLs highlighted in the table below. The `H1` has been replaced by `H2`.
H1 headings are a ranking factor for search engines as they use the H1 heading to determine what the page is about. On top of that, H1 headings help your visitors to quickly understand the topic of the page.
| URL | H1 (NEW) | H1 (OLD) | H1 (CHANGE) | H1 (LAST CHANGED ON) |
|----------------------------------------------|----------|----------------------------------------|-------------|----------------------|
| https://about.gitlab.com/demo/ | | See GitLab in action | removed | 4/27/2022 |
| https://about.gitlab.com/install/ce-or-ee/ | | Which GitLab edition is right for you? | removed | 4/27/2022 |
| https://about.gitlab.com/sales/ | | Talk to an Expert | removed | 4/27/2022 |
| https://about.gitlab.com/solutions/startups/ | | GitLab for Startups | removed | 4/27/2022 |
| 2 |
28,847,821 | 107,404,274 |
2022-04-28 16:46:21.604
|
Navigation 1.0.21 - www
|
## Goal
Import be-navigation 1.0.21 into the middleman www repo.
| 1 |
28,847,821 | 107,310,532 |
2022-04-27 16:42:43.672
|
Incorrect meta title and description for SCM page
|
Revert the existing meta data to the previous. The SCM is ranked in the top 3 results in Google for "source code management" and will be impacted negatively if the title tag isn't reverted.
The title tag is now a duplicate of another page and the meta description is the default description generated by the website.
**Previous**
- Title: `Source Code Management`
- Description: `Source code management enables coordination, sharing, and collaboration across an entire software development team. GitLab supports teams to rapidly collaborate and iterate on new features and deliver business value.`
**Current**
- Title: `GitLab The One DevOps Platform`
- Description: `Code, test and deploy with GitLab. Everyone can contribute!`
| 1 |
28,847,821 | 107,305,847 |
2022-04-27 15:42:19.489
|
Customer Case Study -https://about.gitlab.com/customers/ - Case studies are not showing up
|
## Goal
We would like to view all the customer case studies that are uploaded in the case study page
### Jobs To Be Done
* **Situation**: When all case studies are uploaded in the parent case study page
* **Motivation**: We want to view and filter them
* **Outcome**: So we can support the sales team
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/customers/
Uploaded case studies dated (2022-03-21) are not showing up on the page under filters etc. Also there has been an additional upload of case studies under the original date (2022-02-22) and these are not coming up. Can someone please look into this, it could be a bug?
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: @FionaOKeeffe
## In scope
What is within scope of this request?
- [ ] 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 | 107,297,281 |
2022-04-27 14:22:43.073
|
A11y > Navigation unusable by keyboard
|
## Problem
**Navigation is unusable by keyboard.**
- While it's possible to open a parent nav item with the keyboard, it is not possible to access any of the expanded navigation links or even close the menu, making the rest of the page useless as the focus moves behind an open navigation panel.
- Navigation isn't coded correctly. It uses an unordered list `<ul>` with buttons `<button>` as the child elements, but only list items are allowed so this also fails markup validation.
- The **Support** dropdown can't be closed via keyboard, which also prevent focus from moving efficiently.
## Solution
- Use correct HTML semantics.
- Ensure all functionality can be done via keyboard.
- Ensure focus order is correct.
- Ensure elements don't obscure other elements that can receive focus.
## MVC 1
First iteration MVC can be seen in this [merged MR](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/24).
## What has been done
- All unordered lists have been updated to only include list items as direct children elements.
- Focus attributes of the footer section have been updated to be inaccesible whenever the Menu is open.
## What still needs to be done
- Although the links on the footer are hidden whenever the nav menu is open, as a user I cannot reach the submenus directly afterwards as the focus incorrectly goes to the top of the browser to start the page again. [This behavior can be seen here](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/24#note_966838793).
- The **Support** dropdown can only be closed by clicking `Support` again or navigating the whole menu. We would need to add a `Close` button inside that dropdown to have an actionable element with which we could close it with the keyboard.
## MVC2
For the MVC2, an npm package [was tested here ](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/34) but failed to work on production so it was rolled back and focus trap was implemented from scratch [here](https://gitlab.com/gitlab-com/marketing/digital-experience/navigation/-/merge_requests/45).
## What has been done
The focus trap was created in the `navigation-desktop-menu.vue` file using DOM references. The npm packages for the focus trap have been removed from the repo. Focus trap should be working as expected now.
## What still needs to be done
- When `Close` button is clicked, focus should go to the latest focused nav item instead of the Support buttton (first button on page).
| 5 |
28,847,821 | 107,294,006 |
2022-04-27 13:43:18.504
|
Replace logo on blog pages
|
Related MR: https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/6311
Related thread: https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/epics/106#note_926020262
| 1 |
28,847,821 | 107,287,894 |
2022-04-27 12:03:35.600
|
/stages-devops-lifecycle has overlap in the footer
|
### Describe the Bug
On https://about.gitlab.com/stages-devops-lifecycle/ , when the screen is wide enough, there is overlap on the right side, especially noticeable in the footer.
### What's my browser?
Tested on Firefox and Chrome
## Page(s)
Which page(s) are involved in this request?
* [Unify the DevOps lifecycle with GitLab | GitLab](https://about.gitlab.com/stages-devops-lifecycle/)
## Screenshot
## Requirements
What are the requirements for this request? Checklist 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 | 107,255,436 |
2022-04-27 02:36:37.131
|
Markdown not rendering on features page
|
## Goal
There is a markdown render issue as shown an image below
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* [SAST Features](https://about.gitlab.com/features/?stage=secure)
* [Page Page](https://about.gitlab.com/features/?stage=package)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 107,255,297 |
2022-04-27 02:30:56.566
|
Monitor links navigate to wrong location
|
## Goal
Incident management link takes you to the wrong location.
Should take you to https://docs.gitlab.com/ee/operations/incident_management/
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* `[Monitor](https://about.gitlab.com/stages-devops-lifecycle/monitor/)`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering
| 1 |
28,847,821 | 107,248,567 |
2022-04-26 23:02:33.264
|
Tracking: Navigation Menu
|
## Goal
Google Tag Manager isn't able to detect clicks within the "be-navigation" navigation menu.
**Example:**<br/>
When I click on Resource > Blog on the [Install page](https://about.gitlab.com/install/) with the "be-navigation" menu,
GTM thinks my click element is `nav > be-navigation`, instead of the `<a>` tag:
<br/><br/>
When I click on the same Resource > Blog link on the Home page, GTM detects the correct `<a>` tag.
<br/>
<br/>
Is there some JS blocking GTM from targeting the correct` <a>` tag?
## Page(s)
Which page(s) are involved in this request?
* Any page with the be-navigation nav menu, ie: https://about.gitlab.com/install/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich
- [ ] Consulted: @mpreuss22
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 107,248,491 |
2022-04-26 22:56:17.286
|
QA Blog
|
**UI Fixes for the Blog LP:**
1. Update "Sign up for GitLab's twice monthly newsletter" from H3 to H4 (23px/32lh)
2. Remove the second repeated line "Sign up for GitLab's twice monthly newsletter"
3. Have the "Subscribe" button the width of the email form
| Existing | Figma |
| ------ | ------ |
|  |  |
| 2 |
28,847,821 | 107,248,471 |
2022-04-26 22:54:55.925
|
Homepage Hero Video continues to play after lightbox is closed
|
## Goal
Prevent video from playing after Lightbox has been closed.
### 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 | 107,243,988 |
2022-04-26 20:40:25.810
|
Fix invisible links Copy/CopyMedia - Solutions
|
## Goal
We would like to fix invisible links in Copy or CopyMedia component.
https://refresh.about.gitlab-review.app/solutions/cloud-native/
### 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
- [x] Engineering
| 1 |
28,847,821 | 107,238,280 |
2022-04-26 17:48:09.072
|
ENG: Update Get free trial link on home hero and CTAs
|
## Goal
Update the Get free trial links on the home hero and CTA components from `/free-trial` to `https://gitlab.com/-/trials/new?glm_content=default-saas-trial&glm_source=about.gitlab.com`
## Page(s)
Which page(s) are involved in this request?
* All pages CTA
* Home page
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 107,238,041 |
2022-04-26 17:39:22.503
|
QA: SCM page
|
**UI Fix: ** Update all text that is currently font-weigh 700 (all the headers) to font-weight 600 (semi-bold) on [SCM page](https://refresh.about.gitlab-review.app/stages-devops-lifecycle/source-code-management/)
| 1 |
28,847,821 | 107,233,067 |
2022-04-26 15:44:43.024
|
Free Trial page stuck in redirect loop in review apps.
|
`/free-trial/` is stuck in a redirect loop, but only on review apps. It works fine on local dev servers, local static builds, and in production.
| 4 |
28,847,821 | 107,232,366 |
2022-04-26 15:34:33.431
|
Why GitLab Hero CTAs
|
## Goal
@meganfilo @jhalloran on the Why GitLab hero the secondary button (What is GitLab) is using the wrong style and missing the triangle icon (see homepage for example of how it should be).
| 1 |
28,847,821 | 107,226,877 |
2022-04-26 14:26:34.452
|
ENG: Horizontal scroll component performance update
|
The `horizontal-scroll-bar.vue` currently uses dynamic values in the `left` position property to move the bar as the user scrolls. This can lead to the browser making a lot of calculations on every event trigger, which can lead to performance issues for some users as the DOM gets redrawn each time.
This can be prevented by using the `transform: translateX()` property and value which occurs on a separate layer than the layout, which means the DOM will not be redrawn.
| 2 |
28,847,821 | 107,175,373 |
2022-04-25 21:12:06.955
|
Require code owner approval
|
## Goal
We would like to require a code owner approval for protect branches in the Buyer Experience repository.
### Jobs To Be Done
* **Situation**: *A merge request needs to be approved before merging to a protected branch.*
* **Motivation**: *We want to ensure that any change deployed to the marketing site is approved before it goes live.*
* **Outcome**: *So we can ensure control over the marketing site.*
## Page(s)
Which page(s) are involved in this request?
* https://docs.gitlab.com/ee/user/project/protected_branches.html#require-code-owner-approval-on-a-protected-branch
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/.gitlab/CODEOWNERS
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpreuss22
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Iterate on CODEOWNERS and who owns what parts of the project
- [x] Adjust project settings in Buyer Experience project
| 2 |
28,847,821 | 107,151,567 |
2022-04-25 16:33:58.668
|
Homepage hero carousel progress bars
|
## Goal
- For each image in the carousel, have a progress bar representing it's state
- Transition each image with a fade-in
### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*
## Page(s)
Which page(s) are involved in this request?
* home (refresh)
| 3 |
28,847,821 | 107,075,951 |
2022-04-23 20:25:02.756
|
Follow-up from "ENG: Solutions - By Sector - Public Sector""
|
The following discussion from !433 should be addressed:
- [ ] @mduque-ext started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/433#note_921322831): (+1 comment)
> @dennischarukulvanich tagging you in this MR which has [the public sector page](https://feature-quotes-carousel.about.gitlab-review.app/solutions/public-sector/).
>
> Could you please take a look and make sure we are not missing important Analytics stuff that should be in place? Thank you very much in advance!
We would like to address feedback received concerning the GA tags and Analytics elements that should be in place for the `/solutions/public-sector` page
Pages involved:
`/solutions/public-sector`
**@dennischarukulvanich original feedback for the Public Sector Page:**
Update all `data-ga-location` values to align with section name. The reason for this is to distinguish identical links. For example, there are 2 "hardened" links under solutions block and value prop.
* [x] hero
* [x] benefits
* [ ] quotes carousel
* [x] solutions block
* [ ] value prop
* [x] case studies
* [x] resource cards
Update "Start your free trial" CTA button:
* [x] `data-ga-name="free trial"`
Under "Security. Efficiency. Control.", add data-ga-name/location to each Learn More link.
* [x] `<a data-ga-name="reduce security learn more" data-ga-location="benefits">`
* [x] `<a data-ga-name="free up learn more" data-ga-location="benefits">`
* [x] `<a data-ga-name="modernize learn more" data-ga-location="benefits">`
Add these data attributes to each toggle div section:
* [x] `<div data-inbound-analytics="public-sector-leap-target" data-toggle-group="example: Reduce security and compliance risk" data-ga-toggle="expand or collapse" class="accordion"`
Add data attributes to the "Trusted by government" carousel per slide
* [x] `<div data-ga-carousel="example: public-sector us army" class="quotes-carousel__quote">`
Update "Off-line Environment" learn more link:
* [x] `data-ga-name="offline environment"`
Add attributes to "Low to High Environment":
* [x] `data-ga-name="low to high" data-ga-location="quotes carousel"`
Add attributes to "GitLab meets NIST SSDF 1.1 guidance" and "hardened"
* [x] `data-ga-name="gitlab meets nist" data-ga-location="value prop"`
* [x] `data-ga-name="hardened" data-ga-location="value prop"`
* [x] I noticed the "All Case Studies" link has an `<a>` tag nested inside another `<a>` tag. Not sure if this is a mistake, but Google Tag Manager will target the inner `<a>` tag, so the data-attributes will need to go on both `<a>` tags.
* [x] Same as above for the case study learn more links.
* [x] Also, need to update data-ga-name from "learn more" to include the customer's name, ie. "us army cyber school learn more".
Add data attributes to the "View all resources" link:
* [x] `data-ga-name="view all resources" data-ga-location="resource cards"`
| 1 |
28,847,821 | 106,984,639 |
2022-04-21 16:54:50.072
|
Missing Open Graph Tags
|
Some Open Graph tags are missing from the URLs in the Buyer Experience repo.
With Open Graph, you get full control over how your posts look when they're shared on social media platforms like Facebook. Adding Open Graph markup code to HTML makes it easy to set an attractive visual, title and description for your page.
Open Graph helps you improve the way your content looks, which leads to a higher click-through rate.
#### Missing Tags
- `og:url`
- `og:title`
- `og:image`
- `og:type`
| 2 |
28,847,821 | 106,984,331 |
2022-04-21 16:46:25.475
|
ENG: Horizontal scroll bar component
|
We need a component to use for sections horizontal scroll sections on mobile to hint to the viewer that there is content to the right.
Example: [Figma link](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=1174%3A8136)
| 4 |
28,847,821 | 106,939,248 |
2022-04-21 00:40:31.183
|
ENG: Why GitLab mobile styling updates
|
### Scope of changes
- [ ] Add horizontal scroll to three card section on mobile
- [ ] Add horizontal scroll for case studies on mobile
- [ ] Animation section: headers should be left aligned on mobile
- [ ] Customer logos: 'Trusted by' should be on its own line with logos lining up 3 per row on mobile
| 2 |
28,847,821 | 106,931,308 |
2022-04-20 19:39:06.035
|
ENG: Apply intro text component to Delivery Automation
|
## Goal
We would like to iterate on the [solutions intro component](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/649) and apply it to https://refresh.about.gitlab-review.app/solutions/delivery-automation/.
## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/delivery-automation/
* [Solutions Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11) with full layout for Automated Software Delivery
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/refresh/components/solutions/by-solution/by-solution-intro.vue
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mmanunga-ext
- [ ] Consulted: @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Iterate on the solutions intro component to match Figma
- [ ] Apply the updated component to `/solutions/delivery-automation/` for the `refresh` branch
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 106,916,679 |
2022-04-20 14:42:12.778
|
Deprecate and Redirect Solutions/Feature pages
|
After auditing the content of the website for the upcoming Marketing IA site refresh we identified `/solutions/` and `/stages-devops-lifecycle/` pages that could be deprecated, redirected or remain.
In the new structure some solutions and stages pages will remain or be moved to newly created folders. The remaining pages will be deprecated and redirected to an alternative page but I want to ensure that no page of strategic value is unnecessarily culled.
[List of pages to kept, redirected or deprecated.](https://gitlab.slack.com/files/U014T1XSKT6/F0371BSQGTE/solutions_-_ia_refresh)
| 2 |
28,847,821 | 106,870,718 |
2022-04-20 00:14:19.188
|
ENG: Refresh app is failing to load javascript
|
## Goal
The refresh review app is failing to load javascript. Because of this pages arn't loading correcting.
For example:
- https://refresh.about.gitlab-review.app/ - image caresoul not displaying
- https://refresh.about.gitlab-review.app/features/ - first paint is empty
- https://refresh.about.gitlab-review.app/pricing/ - CTA bottom module blank ( think this all pages )
- https://refresh.about.gitlab-review.app/solutions/public-sector/ - hero is blank
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @tywilliams
- [ ] Consulted: @justin.vetter
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 106,870,371 |
2022-04-19 23:47:37.243
|
ENG: Why GitLab Feature Table
|
[Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=981%3A5769)
| 4 |
28,847,821 | 106,840,476 |
2022-04-19 15:09:31.794
|
ENG: Migrate Continuous Delivery from www-gitlab-com
|
## Goal
We would like to migrate the Continuous Delivery page to the Buyer Experience repository and use the new template for the child stages dev ops lifecycle pages.
### Jobs To Be Done
* **Situation**: *When a user lands on https://about.gitlab.com/stages-devops-lifecycle/continuous-delivery/ it is using the same template as https://about.gitlab.com/stages-devops-lifecycle/enablement/*
* **Motivation**: *We want to have this page built in the Buyer Experience repository.*
* **Outcome**: *So we can be consistent with where pages are built for the stages devops lifecycle section of the website.*
## Page(s)
Which page(s) are involved in this request?
* Live -> https://about.gitlab.com/stages-devops-lifecycle/continuous-delivery/
* Current location -> https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/stages-devops-lifecycle/continuous-delivery/index.html.haml
* Move content here -> https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/stages-devops-lifecycle
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mmanunga-ext
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Migrate content to BE repo and create yml file for it
- [ ] Apply the template used for other child stages-dev-ops lifecylce pages
- [ ] Create MR to remove page from www-gitlab-com
## Out of scope
What is out of scope and not part of this iteration?
- Changing the template
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 106,795,084 |
2022-04-18 20:39:25.747
|
ENG: Update order of Stages DevOps Lifecycle
|
## Goal
“Manage” is something that would happen at the end not the beginning of the dev ops lifecycle. Therefore, we'd like to update the order of stages when they appear on the site, placing "Manage" at the end.
This includes the following places in https://refresh.about.gitlab-review.app/:
- [ ] Homepage section - "For every stage of the DevOps Lifecycle"
- [ ] Navigation - Why GitLab > "The DevOps Lifecycle"
- [ ] Features - https://refresh.about.gitlab-review.app/features/
### Jobs To Be Done
* **Situation**: *When a user encounters a "Stages Dev Ops Lifecycle" section on the marketing site, the manage stage is last*
* **Motivation**: *We want to be concise on the order of stages in the Dev Ops Lifecycle.*
* **Outcome**: *So we can be consistent and a leader in the category.*
## Page(s)
Which page(s) are involved in this request?
* Any page built by the Buyer Experience repository
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: TBD
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 106,786,295 |
2022-04-18 17:00:16.192
|
ENG: Why GitLab content updates
|
### Scope
Iteration 3 of Why GitLab
- New hero
- New cta / devops stages section
- Update content throughout the page to match [Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05)
- Accordion section styling updates
- Cards section styling updates
| 4 |
28,847,821 | 106,784,692 |
2022-04-18 16:34:45.827
|
Why GitLab: Comparison Graph
|
Design isn't totally finalized yet, but it seems that we're going with something in [this direction](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=981%3A5770).
I'll take this on this iteration. I'll try to get it done before Thursday for release stuff, but if not I should be able to wrap by the end of the week regardless.
| 6 |
28,847,821 | 106,732,613 |
2022-04-17 00:19:44.051
|
ENG: Refactor Why GitLab hero
|
The current iteration of the Why GitLab hero is, while responsive, not anchored at the center of the screen at all sizes.
Refactor the component so that it anchors correctly, update content, and continue to look into different ways of implementing the gradient background (CSS vs background image)
| 4 |
28,847,821 | 106,665,593 |
2022-04-14 19:17:15.472
|
Why GitLab Analytics updates
|
Relates to #638
From this [comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/393#note_913406026):
> **New MR**
> SCM Learn More link
`data-ga-name="scm learn more" data-ga-location="body"`
CI/CD Learn More link
`data-ga-name="cicd learn more" data-ga-location="body"`
GitOps Learn More link
`data-ga-name="gitops learn more" data-ga-location="body"`
(Our Customers Have Spoken) See More
`data-ga-name="customers see more" data-ga-location="body"`
View All Case Studies
`data-ga-name="case studies view all" data-ga-location="body"`
> **Comparison**
See GitLab vs button
`<button class="next-comparison-button" data-ga-name="see gitlab vs [name of brand, ie. atlassian]" data-ga-location="why-compare">`
See more details
`data-ga-name="[name of brand, ie. Atlassian] details" data-ga-location="why-compare"`
The div container per Brand
`<div class="slp-container" data-inbound-analytics="[name of brand, ie. atlassian] compare">`
Need this to see how visible each brand is, and how many clicks per brand to gauge interest. Ex) 100 users saw the Atlassian comparison, 10 clicks on See More = 10% click rate for Atlassian.
| 2 |
28,847,821 | 106,661,391 |
2022-04-14 17:35:41.164
|
Add stock images to solutions hero and no-image hero component
|
This is a follow up issue to build a no-image hero component: https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=871%3A2092
As part of this issue, please also update the hero image on the following pages ([thread](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/389#note_911631595
)):
* [Public Sector 1](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=816%3A1668)
* [Startups 2](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=833%3A1908)
* [Enterprise 1](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=833%3A1881)
* [No image 4](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=871%3A2092)
----
The following discussions from !389 should be addressed:
- [ ] @mduque-ext started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/389#note_910636846): (+2 comments)
> @laurenbarker Here's the Hero for Solutions component created and applied to all solutions pages (except the ones using the `by-solution-hero` that Javi did). It has configuration for 1 or 2 buttons and rounded or rectangle image.
>
> Should we use a placeholder image for pages which don't have an image or sould we have an option in this component to handle pages w/o image in the Hero section (such as [agile delivery](https://about.gitlab.com/solutions/agile-delivery/))?
>
> What do you think?
- [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/389#note_910664686): (+5 comments)
> @Tinaliseng Are the hero image styles in [this figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11) ready to build? Miguel is out Thursday and Friday this week, so I'd like to get this MR deployed tomorrow if possible.
>
> I'll be going through all these page as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/666) as well, so we'll have more review cycles here.
| 1 |
28,847,821 | 106,644,968 |
2022-04-14 13:42:24.929
|
Deprecate or Redirect Event pages
|
After auditing the content of the website for the upcoming Marketing IA site refresh we identified `/events/` pages that could be deprecated.
[Events page deprecate list](https://docs.google.com/spreadsheets/d/1ZgCOSiIkAK8Kj_NXizFUE74uMDn5piNuo8wz9RIwOJI/edit#gid=0)
| 2 |
28,847,821 | 106,611,326 |
2022-04-13 22:44:30.626
|
Fix sticky nav in refresh branch
|
The sticky nav in the refresh branch has white on white links.
1. https://refresh.about.gitlab-review.app/solutions/education/
2. https://refresh.about.gitlab-review.app/analysts/
Fix these links so they're visible and use the correct colors.
It also seems the stickiness is starting at the wrong part with the navigation. I'm going to check with @ndubord to make sure it plays nice with the nav.
| 2 |
28,847,821 | 106,603,080 |
2022-04-13 19:15:37.872
|
ENG: Footer updates
|
Related to #616
From this [comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/341#note_911860714):
> Hi @meganfilo! We have updates for the footer - let me know if we need to create another issue. here is the [figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=5021%3A9923) link and a link [an excel](https://docs.google.com/spreadsheets/d/1D9O84YDXxfjoRhUiwtWySe6Az6pQ2MsjiB6iqhUJHLU/edit#gid=0) that explains what is is changing.
| 1 |
28,847,821 | 106,602,850 |
2022-04-13 19:08:34.391
|
Add cache bust to Nuxt favicons
|
Related to https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/631
Now that we have [fixed the 404 files](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/102323), some users may have cached assets with the broken favicon in their browsers.
This will resolve over time, but we can also cache bust the old favicon with a query string at the end of the assets. I will also check to see if Nuxt has a conventional way to do this - most CSS/JS files with Nuxt get a cache bust at build time, but these are hardcoded strings, so we may have to do it the old fashioned way.
| 1 |
28,847,821 | 106,599,650 |
2022-04-13 18:07:23.692
|
Deprecate and Redirect Community URLs
|
Deprecating `/community/` pages no longer required for the website IA refresh.
| 1 |
28,847,821 | 106,598,282 |
2022-04-13 17:25:44.180
|
ENG: 'No-Image' fallback library - Resource cards
|
## Goal
We would like to have a set of fallback images to choose from when a resource card doesn't have an associated image. These should live somewhere in our repo.
## Page(s)
Which page(s) are involved in this request?
* Any page that displays resource cards.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @Tinaliseng @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Set of fallback cards
- [ ] Somewhere for them to live
## What's involved
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 106,597,938 |
2022-04-13 17:19:09.956
|
CODEOWNERS and deployment permissions during release week
|
## Goal
We would like to define ownership permissions for the Buyer Experience repository the week of our big release. There are alot of moving parts and there is a high risk of something breaking if it's not synced correctly with our release branch.
### Jobs To Be Done
* **Situation**: *When a MR is deployed to the Buyer Experience main or refresh branches the week of 4/27 it is reviewed and deployed by our team*
* **Motivation**: *We want tighter ownership of our codebase during the big reveal*
* **Outcome**: *So we can ensure a smooth launch of the new site architecture and brand release*
## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @gitlab-com/marketing/digital-experience
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Define process for adding member as a maintainer to our Buyer Experience repository
- [ ] Iterate on our CODEOWNERS
- [ ] Document in the handbook
## Out of scope
What is out of scope and not part of this iteration?
- www-gitlab-com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [x] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 1 |
28,847,821 | 106,553,794 |
2022-04-13 00:59:26.436
|
ENG: GitLab 15 landing page
|
## Goal
We would like to build a GitLab 15 landing page.
### Jobs To Be Done
We need a GitLab 15 a landing page at about.gitlab.com/fifteen. This landing page will use the existing GitLab 10 template that exists in the Buyer Experience repository. Changes to this template will be:
- Create new template for GitLab 15 that applies the "fresh coat of paint" to GitLab 10 template
- Fullwidth hero image - Sync with @amittner to get the asset
- [Content doc](https://docs.google.com/document/d/1tnLr8oOty02s_bg6F626Crt4J7B1P-GcunLKnJYPxjU/edit#)
- Stretch goal - add countdown timer component
## Resources
* [Buyer Experience Template for about.gitlab.com/ten ](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/main/pages/ten.vue)
* https://about.gitlab.com/ten/
* https://about.gitlab.com/gitlab-14/
* [Figma file for a simpler version](https://www.figma.com/file/PRnQFROp9rDgKvfix9WA5E/14.0-Release-Landing-Page?node-id=49%3A95)
* [content doc](https://docs.google.com/document/d/1tnLr8oOty02s_bg6F626Crt4J7B1P-GcunLKnJYPxjU/edit#)
## 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?
- [ ] Build new landing page at /fifteen
- [ ] Start with existing template used for /ten
- [ ] Confirm assets and content
## Out of scope
What is out of scope and not part of this iteration?
- anything 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
- [x] UX Design
- [x] Engineering
| 4 |
28,847,821 | 106,553,725 |
2022-04-13 00:54:36.885
|
ENG: Update press kit with new assets
|
## Goal
We would like to update the press kit with the new brand assets.
### Jobs To Be Done
* **Situation**: *When a user accesses the press kit they get updates assets*
* **Motivation**: *We want to align with our 4/27 launch*
* **Outcome**: *So we can by consistent with our brand*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/press/press-kit/
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/press/press-kit/index.html.haml
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mmanunga-ext
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update the existing press kit page in the www-gitlab-com repository with new brand assets
## Out of scope
What is out of scope and not part of this iteration?
- Migrating anything for the press kit to the buyer experience repo
## Requirements
What are the requirements for this request? Checklist 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 | 106,547,472 |
2022-04-12 19:52:15.757
|
Turn off OneTrust in review app
|
OneTrust is taking up to 12 seconds to load and then fail to load on the review apps for Buyer Experience.
My hypothesis is that's because OneTrust is not configured to work in our review environments, which means it takes a long time to try and connect to the OneTrust server, never gets what it needs, and ends up bailing out.
I don't think we need OneTrust in review apps. I would prefer to have it to emulate prod environment, but if it's not configured for this at the moment, I'd rather just disable it in review apps so we don't artificially slow down those pages.
Fortunately, this is not an issue that makes its way to production, because OneTrust is correctly configured for `about.gitlab.com`, so this is a pretty low priority thing. I just want to clean it up before a lot of folks are walking through the refresh branch and wondering why it's so slow.
Once I remove it, I will triple-check that it's still loading in production, where we absolutely need to have it.
| 1 |
28,847,821 | 106,541,058 |
2022-04-12 17:05:41.761
|
ENG: Ensure all existing topic pages have new coat of paint
|
## Goal
We would like to review all existing topic pages and ensure they have the fresh quote of paint - fonts, colors, and logo.
## Page(s)
Which page(s) are involved in this request?
* All topic pages that exist in the Buyer Experience repository - https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/topics
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 106,540,991 |
2022-04-12 17:03:58.271
|
ENG: Ensure all existing solutions pages have new coat of paint
|
## Goal
We would like to ensure all existing solution pages have the fresh coat of paint
## Page(s)
Which page(s) are involved in this request?
* https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/tree/main/content/topics
## In scope
What is within scope of this request?
- [ ] Make sure all existing solution pages have the fresh coat of paint
## Requirements
What are the requirements for this request? Checklist 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 | 106,540,981 |
2022-04-12 17:03:35.194
|
UX: Review Solutions by Industry
|
## 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 | 106,540,897 |
2022-04-12 16:59:50.790
|
ENG: Create new resource component - Solutions
|
## Goal
We would like to build the new resources component.
## Page(s)
Which page(s) are involved in this request?
* https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11
## Requirements
What are the requirements for this request? Checklist 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 | 106,540,556 |
2022-04-12 16:53:35.390
|
UX: Review Solutions by Solutions/ Use Case
|
DRAFT
## Goal
We would like to X which will improve Y as measured by Z.
- [Refresh Branch](https://refresh.about.gitlab-review.app/)
## Page(s)
Which page(s) are involved in this request?
* 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 | 106,540,459 |
2022-04-12 16:51:48.322
|
UX: Review Solutions by Company Size
|
DRAFT
## Goal
We would like to X which will improve Y as measured by Z.
- [Refresh Branch](https://refresh.about.gitlab-review.app/)
## 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 | 106,539,737 |
2022-04-12 16:31:24.284
|
ENG: Apply new hero to all Solutions
|
## Goal
We would like to apply the new hero to all existing Solutions pages.
[Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A1765)
### Jobs To Be Done
* **Situation**: *When a user lands on any existing solutions page*
* **Motivation**: *The hero is skinned to the new template*
* **Outcome**: *So we can ensure an existing experience*
## Page(s)
Which page(s) are involved in this request?
* /solutions/*
## 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?
- [ ] Apply new hero to all existing solutions 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:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 106,539,732 |
2022-04-12 16:31:12.590
|
UX: Resources - Learn page
|
## Goal
We would like to update the Learn page, which will improve findability and brand recognition, as measured by reduced drop off.
### Jobs To Be Done
* **Situation**: *When a customer visits the Learn page ...*
* **Motivation**: *they want to easily find and consume content that will help them improve...*
* **Outcome**: *so they can grow with GitLab as a product.*
## Page(s)
Which page(s) are involved in this request?
* [Learn 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: @jhalloran
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update UX as needed
- [ ] Skin in new brand refresh designs
## 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 | 106,539,340 |
2022-04-12 16:21:02.976
|
UX: Review Solutions navigation experience
|
## Goal
We would like to review the experience of navigating to all items under "solutions" from the primary nav.
- [Refresh Branch](https://refresh.about.gitlab-review.app/)
## 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 | 106,535,558 |
2022-04-12 15:21:58.436
|
ENG: Solutions by Sector - Education
|
## Goal
We would like to apply this template from Jam3 to our Education solutions page.
## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/education/
* [Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=645%3A1765)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `TBD`
- [ ] Consulted: @justin.vetter
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Apply the new template to the education page
## Out of scope
What is out of scope and not part of this iteration?
- www-gitlab-com
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 2 |
28,847,821 | 106,530,417 |
2022-04-12 13:57:22.582
|
ENG: Create Show Case component
|
## Goal
We would like to create a reusable case studies component as designed here: https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=7200%3A13980
This will include updating the current place holder component (`by-solution-features`) used on the Delivery Automation solutions page.
### Jobs To Be Done
* **Situation**: *When we want to use the case studies component for a solutions page it is available*
## 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?
- [ ] Build a reusable case studies component for solutions 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:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 3 |
28,847,821 | 106,530,230 |
2022-04-12 13:54:36.937
|
ENG Create Side Nav component - Solutions
|
## Goal
We would like to build a reusable side nav component as designed here: https://www.figma.com/file/vIL4om4wEuV0lQFHC4avJT?node-id=1117:6720#176945666
### Jobs To Be Done
* **Situation**: *Create this component so it's available to apply to a solutions page that uses the new template*
* **Motivation**: *We want to move fast*
* **Outcome**: *So we can migrate a couple solutions pages to the new template*
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @jgarc
- [ ] Consulted: @laurenbarker
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Create the component in the refresh branch
## Out of scope
What is out of scope and not part of this iteration?
- Applying it to any page - We'll need a solutions page in the full template to use.
## Requirements
What are the requirements for this request? Checklist 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 | 106,524,828 |
2022-04-12 12:54:25.879
|
ENG: Create ValueProp component - Solutions
|
## Goal
We would like to have a ValueProp component in the refresh branch with new styles that can be reused in our Solutions pages.
[Figma](https://www.figma.com/file/nWIOpmuMp7RZXmfTj6ujAF/Slippers_foundations?node-id=6963%3A13367)
## Page(s)
Which page(s) are involved in this request?
* Public Sector
* Delivery Automation
* Future solutions pages
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: `GitLab Handle`
- [X] Consulted: `@laurenbarker`
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Deliverable 1
- [ ] Deliverable 2
## Out of scope
What is out of scope and not part of this iteration?
- Not in scope 1
- Not in scope 2
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 2 |
28,847,821 | 106,524,801 |
2022-04-12 12:54:05.822
|
ENG: Create Benefits component - Solutions
|
## Goal
We would like to have a Benefits component in the refresh branch with new styles that can be reused in our Solutions pages.
Apply this component to the Delivery Automation and Public Sector solutions pages in the **refresh branch**.
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/refresh/content/solutions/delivery-automation.yml
- https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/blob/refresh/content/solutions/public-sector.yml
Figma Resources:
- Here is the [full Figma ](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11)file for those pages.
- Here is the [Slippers Foundation Figma](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11) for this component
## Page(s)
Which page(s) are involved in this request?
* https://refresh.about.gitlab-review.app/solutions/delivery-automation/
* 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: @mmanunga-ext
- [X] Consulted: `@laurenbarker`
- [ ] 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?
- www-gitlab=com work
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 2 |
28,847,821 | 106,367,406 |
2022-04-09 03:25:10.592
|
ENG: pricing page SaaS/SM Modal.
|
## Goal
We would like to update the pricing modal in the refresh branch to align with new designs.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpenagos-ext
- [ ] Consulted:
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Update modal to align with [Figma design](https://www.figma.com/file/4CkayJDu97uNEWBOlgABwE/Pricing-Refresh-2022-04-01?node-id=220%3A5757)
## Requirements
What are the requirements for this request? Checklist 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 | 106,275,914 |
2022-04-07 20:04:08.574
|
Why GitLab: Case Studies
|
[Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)
This was started as part of #623 but the design been changed to match the Homepage case studies section.
** Note: Save the existing Case Studies component code, as we may need to reuse it in the future
With that said, we can probably steal the Homepage case studies code (or use the component entirely if it fits our needs!).
Update case_studies content in why.yml if needed.
| 2 |
28,847,821 | 106,275,851 |
2022-04-07 20:01:31.027
|
Why GitLab: Section w/three cards
|
[Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)
### Scope
- Add content to Why.yml
- Create card component (doesn't look like this has been created yet)
- Add the header, See more link, and three cards to Why page (feel free to create a separate component for the whole section!)
| 4 |
28,847,821 | 106,275,734 |
2022-04-07 19:57:23.930
|
Why GitLab: Accordion / Company Logo section
|
We should copy some of the code from our accordion or faq component for this.
[Figma](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)
### Scope
- Add content Why.yml
- Create component and add to Why page
- Ensure analytics tags are added. See the [comment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/638#note_903425202) in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/638) for more information.
| 8 |
28,847,821 | 106,275,630 |
2022-04-07 19:52:58.589
|
Why Gitlab: Slider component
|
This is the same as the component being built in this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/588). We can find a way to collaborate, or if the team working on this component doesn't get to it before we do, we can start it!
[Figma file](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab-Refresh-2022-04-05?node-id=458%3A8579)
| 8 |
28,847,821 | 106,265,389 |
2022-04-07 16:01:35.766
|
ENG & SEO: URL structure for solutions content neighborhood
|
## Goal
We would like to define the URL structure for the solutions content neighborhood.
### Jobs To Be Done
* **Situation**: *When build out the solutions content neighborhood *
* **Motivation**: *We want to know the URL structure *
* **Outcome**: *So we can organize our routes, templates, and data efficiently.*
## Page(s)
Which page(s) are involved in this request?
* Buyer Experience repository`
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @jhalloran @mpreuss22
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] URL structure of solutions by solution
- [ ] URL structure of solutions by industry
- [ ] URL structure of solutions by department
- [ ] URL structure of solutions by technology
- [ ] URL structure of solutions by company size
- [ ] URL structure of solutions by technology
## Out of scope
What is out of scope and not part of this iteration?
- Building anything
## Requirements
What are the requirements for this 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
- [x] UX Design
- [x] Engineering
| 1 |
28,847,821 | 106,196,705 |
2022-04-06 17:40:46.251
|
Free Trial page is not available in review apps
|
The Free Trial page is not reachable in review apps due to too many redirects. Lets fix that.
The following discussion from !349 should be addressed:
- [ ] @dennischarukulvanich started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/349#note_901750085): (+3 comments)
| 1 |
28,847,821 | 106,195,749 |
2022-04-06 17:16:26.038
|
Page anchors creating internal redirects
|
Our SEO Auditing tools have detected an increase in internal redirect links caused by missing trailing slash `/` on anchored links. The pages identified all have a drop down menu when viewing on a mobile device.
Everytime a search engine bot encounters a redirect it decreases our crawl budget. This may run out before search engines can crawl updated or newly created pages we want to get indexed.
### Pages affected
- https://about.gitlab.com/stages-devops-lifecycle/
- https://about.gitlab.com/support/
- https://about.gitlab.com/get-help/
### Page source example
(snippet from https://about.gitlab.com/stages-devops-lifecycle/)
```
<div class="side-menu" data-v-24faf1f9 data-v-1e8cac17>
<!---->
<ul class="side-menu__list" data-v-24faf1f9>
<li class="side-menu__item" data-v-24faf1f9>
<div class="side-menu__item__container" data-v-24faf1f9>
<a href="/stages-devops-lifecycle#manage" data-ga-name="manage" data-ga-location="header" class="side-menu__link" data-v-24faf1f9>Manage
</a>
<div class="side-menu__line" data-v-24faf1f9></div>
</div>
<!---->
</li>
<li class="side-menu__item" data-v-24faf1f9>
<div class="side-menu__item__container" data-v-24faf1f9>
<a href="/stages-devops-lifecycle#plan" data-ga-name="plan" data-ga-location="header" class="side-menu__link" data-v-24faf1f9>Plan
</a>
<div class="side-menu__line" data-v-24faf1f9></div>
</div>
```
The link URL should be `<a href="/stages-devops-lifecycle/#manage"`
| 2 |
28,847,821 | 106,187,850 |
2022-04-06 15:33:43.034
|
Create Direct Link to Pricing Page FAQs
|
## Goal
I have done research into salient events towards conversion of our product. Expanding the pricing page FAQs was **highly predictive** at my initial pass, so much so I believe it would be worthwhile to create a direct link to the FAQs on the pricing page. This would enable customers to be able to share it easier with others and also arrive at this important state easier.
- Ex: `https://about.gitlab.com/pricing?FAQs/`
### Jobs To Be Done
* **Situation**: We do not have a direct link to the pricing page FAQs
* **Motivation**: Try to improve the number of purchases of our product
* **Outcome**: Create a direct link to the pricing page FAQs to drive traffic directly to these important locations on our pricing page to increase purchase rates.
## Page(s)
Which page(s) are involved in this request?
* [Pricing Page](https://about.gitlab.com/pricing/)
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @mpreuss22
- [x] Consulted: @mpreuss22
- [x] Informed: @mpreuss22
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 1 |
28,847,821 | 106,164,817 |
2022-04-06 11:07:16.382
|
404 Error page in XMLSite
|
There is a 404 error page in the buyer experience XML sitemap file.
**URL:** https://about.gitlab.com/undefined/
**Sitemap:** https://about.gitlab.com/buyer-experience/sitemap.xml
```
<url>
<loc>https://about.gitlab.com/undefined/</loc>
</url>
```
The XML Sitemap should only contain URLs we wish for search engines to index. URLs in our sitemaps should be clean - i.e. sitemaps should only include URLs that are HTTP status 200 (OK), indexable, canonical and unique. If search engines find 'dirt' in sitemaps, such as 404 pages, they may stop trusting the sitemaps for crawling and indexing signals.
| 1 |
28,847,821 | 106,112,207 |
2022-04-05 14:20:58.215
|
Favicon 404ing
|
## Goal
Favicon is 404ing on BE repo pages.
- Looks like assets in the /ico/ folder are not getting built on production
| 4 |
28,847,821 | 106,058,861 |
2022-04-04 20:18:57.459
|
ENG: Migrate support child pages
|
## Goal
We would like to migrate all Support subpages to the Buyer Experience repository.
https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/sites/uncategorized/source/support
### Jobs To Be Done
* **Situation**: *We need all support pages to exist in a single place*
* **Motivation**: *We want to make it efficient for managing content*
* **Outcome**: *So we can be efficient*
## Page(s)
Which page(s) are involved in this request?
* All child pages that exist in this directory: https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/master/sites/uncategorized/source/support
## 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?
- [ ] Create all child support pages
- [ ] Remove child support pages from 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 | 106,057,811 |
2022-04-04 19:54:21.001
|
Support: controls and ownership
|
## Goal
We would like to add introduce appropriate controls and ownership to the support page.
### Jobs To Be Done
* **Situation**: *When an change is made to the support page*
* **Motivation**: *We want to ensure content owners approve the change*
* **Outcome**: *So we can make adjustments to the text as required*
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/support/
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @laurenbarker
- [ ] Consulted: @jcolyer @mpreuss22
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] [Add codeowners feature](https://docs.gitlab.com/ee/user/project/code_owners.html) to Buyer Experience repository
- [ ] Place @jcolyer and @tcooney as owners of support page content
- [ ] Add @jcolyer and @tcooney as project maintainers
- [ ] Remove existing support page from www-gitlab-com to ensure SSoT for content
## Requirements
What are the requirements for this request? Checklist 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 | 106,044,635 |
2022-04-04 15:30:20.080
|
Move hardcoded Bizible script into the head tag
|
## Goal
We would like to move the Bizible tag implemented on trial and signup pages to the head tag, which should ensure the tag fires first and [referral information is not missed as advised by Adobe](https://experienceleague.adobe.com/docs/bizible/using/bizible-tracking/setting-up-tracking/adding-bizible-script.html?lang=en).
### Jobs To Be Done
* **Situation**: *When a trial or signup page is loaded*
* **Motivation**: *We want to track that view, with referral information captured in Bizible*
* **Outcome**: *So we can attribute marketing and particularly paid demand gen activity to new trial and signups*
## Page(s)
Which page(s) are involved in this request?
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)
* https://customers.gitlab.com/customers/sign_in
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @miraclebanks
- [ ] Consulted: @laurenbarker @jahye1
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Adding the Bizable script to the pages listed above towards the bottom of the head tag
NOTES:
- [Adobe implementation doc](https://experienceleague.adobe.com/docs/bizible/using/bizible-tracking/setting-up-tracking/adding-bizible-script.html?lang=en)
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [X] Data / Analytics
- [ ] UX Design
- [X] Engineering
| 4 |
28,847,821 | 106,037,480 |
2022-04-04 14:10:19.754
|
Update pricing 400 CI/CD minutes link
|
## Goal
Make the FAQ hyperlink for 400 CI/CD minutes per month consistent with the other usage limits.
| 1 |
28,847,821 | 106,026,543 |
2022-04-04 11:40:11.020
|
Pricing Page schema.org markup
|
**Schema Type:** Product - https://schema.org/Product
**URL:** https://about.gitlab.com/pricing/
**Markup**
```
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Product",
"name": "DevOps Platform",
"description": "A DevOps platform combines the ability to develop, secure, and operate software in a single application so everyone involved in the software development process -- from a product manager to an ops pro -- can seamlessly work together to release software faster.",
"audience": "Ops Pro,Security, Testers, Product Managers, Product Designers, Finance, The Legal Team",
"sku": "",
"mpn": "",
"brand": {
"@type": "Corporation",
"name": "GitLab",
"logo": "https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo.png"
},
"offers": [{
"@type": "Offer",
"name": "DevOps Platform - Free Plan",
"Price": "0.00",
"priceCurrency": "USD"
},{
"@type": "Offer",
"name": "DevOps Platform - Premium Plan - Billed Annually",
"Price": "228.00",
"priceCurrency": "USD"
},{
"@type": "Offer",
"name": "DevOps Platform - Ultimate Plan - Billed Annually",
"Price": "1188.00",
"priceCurrency": "USD"
}
]}
</script>
```
| 1 |
28,847,821 | 106,017,359 |
2022-04-04 09:37:50.726
|
Homepage Schema.org markup
|
**Schema type:** Corporation Schema (https://schema.org/Corporation) - updating existing Organization schema to Corporation Schema
**URL:** https://about.gitlab.com/ only
The ticker symbol is the biggest difference between Organization schema and corporation schema
New Fields Added:
- tickerSymbol
- Description
- Slogan
- Awards
- KnowsAbout
```
{"@context":"https://schema.org",
"@type": "Corporation",
"name":"GitLab",
"legalName":"GitLab Inc.",
"tickerSymbol":"GTLB",
"url":"https://about.gitlab.com",
"logo":"https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo.png",
"description" : "GitLab is The DevOps platform that empowers organizations to maximize the overall return on software development by delivering software faster and efficiently, while strengthening security and compliance. With GitLab, every team in your organization can collaboratively plan, build, secure, and deploy software to drive business outcomes faster with complete transparency, consistency and traceability.
GitLab is an open core company which develops software for the software development lifecycle with 30 million estimated registered users and more than 1 million active license users, and has an active community of more than 2,500 contributors. GitLab openly shares more information than most companies and is public by default, meaning our projects, strategy, direction and metrics are discussed openly and can be found within our website. Our values are Collaboration, Results, Efficiency, Diversity, Inclusion & Belonging , Iteration, and Transparency (CREDIT) and these form our culture.",
"foundingDate":"2011",
"founders":[{"@type":"Person","name":"Sid Sijbrandij"},
{"@type":"Person","name":"Dmitriy Zaporozhets"}],
"slogan": "Our mission is to change all creative work from read-only to read-write so that everyone can contribute.",
"address":{"@type":"PostalAddress","streetAddress":"268 Bush Street #350","addressLocality":"San Francisco","addressRegion":"CA","postalCode":"94104","addressCountry":"USA"},
"awards": "Comparably's Best Engineering Team 2021, 2021 Gartner Magic Quadrant for Application Security Testing - Challenger, DevOps Dozen award for the Best DevOps Solution Provider for 2019, 451 Firestarter Award from 451 Research",
"knowsAbout": [
{
"@type": "Thing",
"name": "DevOps"
},
{
"@type": "Thing",
"name": "CI/CD"
},
{
"@type": "Thing",
"name": "DevSecOps"
},
{
"@type": "Thing",
"name": "GitOps"
},
{
"@type": "Thing",
"name": "DevOps Platform"
}
],
"sameAs":["https://www.facebook.com/gitlab",
"https://twitter.com/gitlab",
"https://www.linkedin.com/company/gitlab-com",
"https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg"]}</script>
```
| 1 |
28,847,821 | 105,917,033 |
2022-04-01 23:00:10.300
|
Tracking: Vimeo Video
|
## Goal
Vimeo video dataLayer events (load, play, progress, complete) are not firing on certain pages (ie. Home, Demo). The configuration on Google Tag Manager appears to be setup properly. I think the culprit is from this JS error on the Home page:
<br/>
<img src="/uploads/bc0156e623619e8c4dafeb9ffb9af8a1/Screen_Shot_2022-04-01_at_3.55.57_PM.png" width="600">
<br/>
I do not see the JS error on other pages where Vimeo is firing data properly (ie. /company/history/)
<br/>
<img src="/uploads/cd9b454dc830d7d29b93b3c07a7b1699/Screen_Shot_2022-04-01_at_3.53.06_PM.png" width="600">
### Jobs To Be Done
* **Situation**: When Vimeo video loads...
* **Motivation**: We want to ensure dataLayer events from Vimeo are firing on video load, play, progress, and complete...
* **Outcome**: So we can analyze video engagements, specially on the Home page since it's the first media a user sees.
## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com
* about.gitlab.com/demo/
* etc.
## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)
- [ ] DRI: @dennischarukulvanich
- [ ] Consulted: @mpreuss22
- [ ] Informed: @ndubord
## Requirements
What are the requirements for this 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
| 6 |
28,847,821 | 105,902,577 |
2022-04-01 16:36:15.849
|
ENG: Additional updates to Why GitLab? page
|
Follow up to #363.
[Figma link](https://www.figma.com/file/3a8RLDtpMQGzeujk7wAdj2/Why-GitLab?node-id=485%3A6505#174109306)
## Work done as part of this issue
This page is probably best if approached by building the individual sections
- [x] Hero (Megan)
- [x] Small CTA section ('GitLab is unlike anything...') w/ two buttons and image (Tyler)
- [x] GitLab vs. xxxx section (GitHub, Atlassian, JFrog) (Megan)
- [x] Take the next step CTA section. This CTA component is possibly being built as part of this [issue](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/593). Not sure if it will be the exact layout though!
| 10 |
28,847,821 | 105,832,914 |
2022-03-31 16:25:12.813
|
Fix blog card images
|
Blog card images on the All-Remote page are not contained within the card.
| 1 |
28,847,821 | 105,829,037 |
2022-03-31 15:06:52.079
|
ENG: Solutions - By Solution -Hero
|
## Goal
Create the for the `no-image` Hero section in Solutions- By Solution pages.
Includes the Hero Section with gradient background and the infinity image and also de responsive behavior.
First prototype -> https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=446%3A11
## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/solutions/delivery-automation
* https://about.gitlab.com/solutions/continuous-software-security-assurance
* https://about.gitlab.com/solutions/continuous-software-compliance
* 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: @jariasc-ext
- [ ] Consulted: @laurenbarker, @jhalloran
- [ ] Informed: `Everyone`
## In scope
What is within scope of this request?
- [ ] Solutions - By Solution - Hero Section
## Out of scope
What is out of scope and not part of this iteration?
- Any other section
## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:
- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering
| 4 |
28,847,821 | 105,781,867 |
2022-03-30 19:51:10.105
|
ENG: Blog refresh
|
Based on the meeting documented in https://docs.google.com/document/d/19WfMAXKmZ47baUMwUStFSveOufb03x7aUCf42CuU76g/edit#, we really need to make sure the Blog landing page and blog posts get the refresh styles coming through with the rebrand.
This issue will track that work, and may be promoted to an epic if need be.
At a high level, here's what I think needs to happen:
- [x] Update the fonts on landing page
- [x] Update the fonts on blog posts
- [x] Grab Inter fonts from Google Fonts
- [x] Remove old colors on landing page
- [x] Update new colors on landing page
- [x] Remove old colors on blog posts
- [x] Update new colors on blog posts
- [x] Isolate changes by pulling them out to a separate style sheet and loading it in those templates (just cleanup work, really)
- [x] Check for substantial regressions and fix them
### Changes from @jhalloran on 2022-04-04
Figma file: https://www.figma.com/file/HdsUOq4gDMjaI1kkhwUWNN/Blog-LP-Refresh?node-id=5%3A1421
I'll come through and enumerate those as well.
Then I'll loop in @mpreuss22 and @jhalloran to make sure I'm on the right track. Finally I'll reach out to @vsilverthorne to let her know what's getting impacted (there should be no workflow change - just a change in the output of these pages).
I'm going to start from https://gitlab.com/gitlab-com/marketing/digital-experience/slippers-ui/-/merge_requests/168, which is the brand update in the Slippers repository, and identify what changes I can make over in https://gitlab.com/gitlab-com/www-gitlab-com to match those.
MR for this will be at https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101723 to start. I think we can get this done in one.
#### Blog landing page
- [x] Change "Subscribe" title to "sign up for GitLab's twice-monthly newsletter"
- [x] Add form field label for "Enter your email address" (Requested in https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6274)
- [x] Add "abc@xyz.com" placeholder text (Requested in https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6274)
- [x] Add title copy to search bar "Search the blog"
- [x] Update search placeholder copy to "search"
- [x] Add YouTube social option (figma file says LinkedIn, but we already had that)
- [x] Add hover states
#### Blog post template
- [x] Add a label for the newsletter field and update placeholder text (Requested in https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/6274)
- [x] Match the landing page social icons
- [x] Fix the SVG fill on the social icons to be `#171321`
- [x] Add hover state to CTA
| 6 |
28,847,821 | 105,781,746 |
2022-03-30 19:48:49.105
|
ENG: Create new footer
|
[Figma design](https://www.figma.com/file/33yxdO2kvMwvgjPlfjvxL0/Footer-refresh?node-id=56%3A871)
| 6 |
28,847,821 | 105,702,174 |
2022-03-29 17:16:39.643
|
ENG: Solutions - By Company Size - Start Up
|
## 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.