Datasets:

giseldo

/

neodataset

like 1

2020-06-29 14:07:39.544

Make Webpage of DIY vs. Single Application - Dev

Development of design issue here: https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/842

2020-06-26 19:06:04.955

Homepage hero swap - June 26

Closes https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/121

2020-06-26 16:44:09.118

Create a speakers section for campaign landing page

Closes https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/92

2020-06-25 23:09:54.223

Test a Marketo form with static html

## Overview #### Briefly describe your request Implement a page where we can test theories related to marketo forms. In particular, https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/1604#note_368531411 #### Describe why this update is being requested: What problem(s) are you trying to solve? What are the goals? 1. Marketo is a third party marketing tool. 2. Third party marketing tools are blocked by privacy strict browsers, adblockers, firewalls, and impacted by cookie consent legislation such as GDPR / CCPA. #### What is/are the relevant URL(s) `https://about.gitlab.com/handbook/marketing/growth-marketing/marketo-test-static/` _________ ## Project Management #### What is the due date AND WHY? Dates without reason are difficult to prioritize. If there is no due date, please be as specific as possible about a timeframe and need. No specific due date but the sooner the better since forms directly impact growth. #### Please identify the directly responsible individual (DRI), stakeholders, and roles |Name|Role| |------|------| | `???` | DRI | | `@brandon_lyon` | Marketing web developer | | `@amy.waller` | Marketo tool lead | | `@shanerice` | Analytics | | `@j.carey` | Analyst | | `@jstava` | Product growth | ____________ ## Audience All visitors to about.gitlab.com ___________ ## Promotion and Measurable Goals #### What are the measurable key performance indicators (KPI)? * `Form completions` * `Self-managed trial signups` _____________ ## Relevant Documents/Information * [Marketo form best practices](https://nation.marketo.com/t5/Product-Blogs/Really-finally-winning-the-Marketo-Forms-vs-Tracking-Protection/ba-p/244434) * [Cookiebot improvements](https://gitlab.com/groups/gitlab-com/-/epics/681). _____________ ## Requestor Checklist * [x] All sections have been filled out * [x] All media and relevant documents have been linked or added * [x] A due date and rationale for the due date has been added * [x] Your team labels have been added

2020-06-25 16:49:07.724

Fix aspect ratio on universal remote video

https://about.gitlab.com/company/culture/all-remote/universal-remote/

2020-06-23 18:49:43.110

Fix broken button on Handbook page

https://about.gitlab.com/handbook/marketing/#content-marketing

2020-06-23 15:14:48.972

Solutions page Hashicorp

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/90

2020-06-23 01:10:44.655

Add promo banner to Google Solution page.

#### What is/are the relevant URL(s) https://about.gitlab.com/solutions/google-cloud-platform/ #### Briefly describe the page/flow Speaks to our partnership with Google Cloud #### What is the primary reason for updating this page? To add a banner that we have a speaking slot at Google Cloud Next On Air and encourage people to register through our link. We get the leads of anyone who registers through this link and the event is free. #### What exactly do you want to change on this page? To add a banner that we have a speaking slot at Google Cloud Next On Air and encourage people to register through our link. The banner should say "Join our session at Google Cloud Next On Air" and link to https://cloud.withgoogle.com/next/sf/?utm_source=google&utm_medium=partnerreferral&utm_campaign=FY20-Q3-global-next-operational-er-nextonair_em_partner&utm_content=GR_1_RegOpen_ERC&utm_term=GitLab&pcn_code=0014M00001h35gDQAQ #### What are the KPI (Key Performance Indicators) Get 50 leads.

2020-06-22 21:45:54.228

Users experiencing refresh loop when loading 13.1 blog post

#### What is/are the relevant URLs or emails? https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/ #### Briefly describe the bug Details from the community members who are experiencing this issue can be found on the HackerNews thread re: the 13.1 release post: https://news.ycombinator.com/item?id=23604638 #### What are the steps to reproduce the bug From AaronFriel: > If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. > Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. > > I let the page run for 30 seconds and: > > * CPU usage on two cores was at 100% > > * 2,943 requests were made for 319 MB of resources over 30.06 seconds > > A staggering rate of 100 requests per second that persists indefinitely - I have no reason to believe the refresh loop is broken at any point. From Earwig: > Same issue here as the original post and similar extensions. I followed the suggestion of clearing cookies for about.gitlab.com and it doesn't help. #### Please provide any relevant screenshots or screencasts Video of related issue that was reported in Slack by @caalberts  #### What is your window size, browser, operating system, and versions * Safari * Firefox * Chrome #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? * (One report) If I open up the page in incognito, I see two requests in the network tab for the page. * (Another report) Incognito appears to be working as expected. #### What is your geographic location * India * Colorado #### What type of network are you connected to? * Unspecified * Wifi Comcast (Colorado) #### What cookie values have been observed by users? * CookieConsent = -1 * The user is not within a region that requires consent - all cookies are accepted. * CookieConsent = -3 * Unknown cause. #### 2020-07-06 Potentially related issue? Upon further investigation, I'm seeing some 301 redirects.

2020-06-22 20:24:12.948

Add Eventbrite registration to Commit Landing page

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/109

2020-06-22 16:30:07.921

Cleanup demo experiment

## Overview #### Briefly describe your request Cleaning up the files named `OLD` and the experiment on the /demo/ page cc @cwoolley-gitlab #### Describe why this update is being requested Assisting the Static Site team with updates to the build process in order to facilitate efficient builds and monorepo projects. #### What is/are the relevant URLs or emails? https://about.gitlab.com/demo/ ## Project Management #### What is the due date and why? If there is no due date, please be as specific as possible about a timeframe and need. `ASAP`, lack of progress is blocking other teams' work. <!-- Please note: Without sufficient lead time we will likely be unable to meet your deadline. Marketing web development is currently an impacted resource. Example: Our due date is XXXX-XX-XX. We want to launch this page before a trade show happens on YYYY-YY-YY. We need a week of lead time to coordinate a press release before the event. --> #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? --> |Name|Role| |------|------| | `@cwoolley-gitlab` | `DRI` | | `@brandon_lyon` | `developer` | ## Requestor Checklist * [x] All sections have been filled out * [x] All media and relevant documents have been linked or added * [x] A due date and rationale for the due date has been added * [x] Your team labels have been added <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-06-22 14:37:40.837

Bug on the trial banner (FE)

<!-- This template is for filing a bug report related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/growth-marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-bug-report --> #### What is/are the relevant URLs or emails? https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/ #### Briefly describe the bug Footer overlays "GitLab Free Trial" banner:  #### What are the steps to reproduce the bug Scroll to the end of the page and look at the "GL trial" banner. It's overlayed by the footer. #### Please provide any relevant screenshots or screencasts <!-- [How to take a screenshot](https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/) --> #### What is your window size, browser, operating system, and versions - macOS Catalina 10.15.5 (19F101) - Chrome Version 83.0.4103.61 (Official Build) (64-bit) - Large screen #### What device are you using MacBook Pro #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? Reproduces on Firefox Developer 78.0b9 (64-bit) #### What browser plugins do you have enabled? Doesn't seem related #### What is your geographic location Doesn't seem related #### What type of network are you connected to? * Wifi at home. <!-- If you do not want to ping the website team, please remove the following cc --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-06-18 21:33:18.953

Add the blocked resource warning to more locations

## Overview #### Briefly describe your request Add the blocked resource warning to the education solutions page.  #### Describe why this update is being requested: Users aren't aware they need to accept cookies to view the form to apply. #### What is/are the relevant URL(s) * https://about.gitlab.com/solutions/education/ * Other pages which are built similarly using shared code (exact URLs unknown) * https://about.gitlab.com/free-trial/self-managed/ * https://about.gitlab.com/demo/ * https://about.gitlab.com/developer-survey/ * https://about.gitlab.com/company/contact/ _________ ## Project Management #### What is the due date and why? If there is no due date, please be as specific as possible about a timeframe and need. ASAP. It's a quick fix and we keep getting asked about this, particularly for German users. #### Please identify the directly responsible individual (DRI), stakeholders, and roles |Name|Role| |------|------| | `@brandon_lyon` | `DRI` | ____________ ## Audience #### Who is primarily looking at this page AND what will they they be doing with it/what do we want them to do? Write specifics AND check off below anything relevant **Specific Details** <!-- Write in specifics. Example: People looking for more info about devsecops", or "potential event attendees vs event sponsors. Want them to sign up for event" --> `SPECIFICS` **Person** [x] Individual (looking for information on GitLab features, events, community, documentation) [x] Person representing company (looking for a solution for DevOps, getting a trial, etc) [ ] PR/Media [ ] Investors/Board members **How much do they know about GitLab?** [x] Very new or first time visiting (most likely came from ads or search) [ ] Has been here a few times [ ] Very familiar (likely looking for documentation, resources, new features, community projects, etc. ) **Special Considerations (check if applicable):** [ ] Government [x] Outside U.S. (primary) [ ] Direct Competitive (ex: OctoCat Campaign} ___________ ## Promotion and Measurable Goals #### What are the measurable key performance indicators (KPI)? * `Form signups` #### Where do you expect traffic to come from? * `Organic` ___________ ## Project Deliverables #### What are the project must-haves? * [x] Blocked resource warning added to the page _____________ ## Requestor Checklist * [x] All sections have been filled out * [x] All media and relevant documents have been linked or added * [x] A due date and rationale for the due date has been added * [x] Your team labels have been added

2020-06-18 17:40:12.629

Link to logo trademark is broken

<!-- This template is for filing a bug report related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/growth-marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-bug-report --> #### What is/are the relevant URLs or emails? <!-- Example: https://about.gitlab.com/something/etc/ --> https://about.gitlab.com/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines #### Briefly describe the bug <!-- Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned. --> I was looking for the logo trademarks as I wanted to link there. From https://about.gitlab.com/press/press-kit/ I clicked on "Trademark information" which then led me to https://about.gitlab.com/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines but the anchor is gone. @dmor My guess is that this was moved into growth marketing now? https://about.gitlab.com/handbook/marketing/growth-marketing/brand-and-digital-design/brand-guidelines/#trademark If yes, please re-assign to fix. #### What are the steps to reproduce the bug <!-- Example (In a bulleted list): * Scroll to the W section of the page * When condition X is true * Hover over Y --> Find any page which links to the anchor: ``` ➜ www-gitlab-com git:(master) grep -r '#gitlab-trademark--logo-guidelines' . ./source/press/press-kit/index.html.haml: = link_to "Trademark information", "/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines" ./source/handbook/finance/Procurement/index.html.md:* [Trademark](/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines) - information regarding the usage of GitLab's trademark ./source/handbook/legal/index.html.md:* [Trademark](/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines) - information regarding the usage of GitLab's trademark ``` <!-- If you do not want to ping the website team, please remove the following cc --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-06-12 15:51:30.815

Blog: Newsletter subscription not possible

<!-- This template is for filing a bug report related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/growth-marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-bug-report --> #### What is/are the relevant URLs or emails? https://about.gitlab.com/releases/categories/releases/ and the other blog categories #### Briefly describe the bug There is an introduction text shown about signing up to the newsletter but no textentry or button is there to actually do it. The text ending with colons suggests there should be any way to progress. #### What are the steps to reproduce the bug * Visit https://about.gitlab.com/releases/categories/releases/ * Try to signup to the newsletter #### Please provide any relevant screenshots or screencasts  #### What is your window size, browser, operating system, and versions * Windows 10, Firefox 77.0.1, 1920x1200px, https://www.whatsmybrowser.org/b/PD973 * Windows 10, Microsoft Edge 44.18362.449.0, 1920x1200px, https://www.whatsmybrowser.org/b/W1IOL #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? * Problem persists on Firefox with disabled Adblockers. * Incognito mode in FF still shows the same behaviour. #### What browser plugins do you have enabled? A lot in Firefox, none in Edge. Relevant FF plugins could be uBlock origin & Privacy Badger #### What is your geographic location Germany #### What type of network are you connected to? * Wired corporate network. /cc @gl-website

2020-06-10 20:14:45.192

AB test pricing

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/-/issues/132 > Product Growth launched the new `/pricing/` page last week. We need to work on getting the new test live with the advantage/benefit language for the tiers.

2020-06-09 23:45:06.357

Terminology update documentation whitelist-blacklist

This is a tracking issue which relates to https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/51812

2020-06-05 12:59:30.834

Web: Demo Landing Page Conversion - MVC 2

## Demo Landing Page Conversion MVC ### Goals Increase Demo landing page conversion rate on about.gitlab.com with collaborative, data-driven MVC. The first attempt did not prove net positive, let's learn from that and try again. ### Audience - Devs prospects new to gitlab at all stages of their careers. ### Requirements Must Have - Co-design an improved and compliant solution - Co-design a conversion-driven MVC that meets or exceeds the design and usability the current state solution. The MVC should be informed by conversion best practices, marketing strategy and brand and website standards. Consider page speed, content and form optimization. - Set KPIs - Set MVC KPIs in order to test the positive and negative impacts of your change - especially marketing KPIs. How might your changes negatively affect experiences and metrics? - Validate performance If testing proves the MVC is positive change, share demonstrable data, merge, and ensure health monitoring and reporting. - Share change events - Document and share change events and results with relevant GitLab teams. - Should Have Could Have Wont Have - Non-cohesive demo experience - Ensure the new landing page experience is aligned to the overall demo workflow (i.e. continuous content and design experience). ### KPIs ### Proposed Tasks - Conversion audit & recommendations (Shane) - KPI's - Planning - MVC Requirements - Iterative Co-Design - Build the page @skarpeles - Test - If success: Merge, monitor and report - Create follow-on issues, as needed. @brandon_lyon @skarpeles @shanerice

2020-06-01 20:31:06.878

Sort/filter options for the release post blog page

### Proposal As the monthly blog post gets longer (more teams shipping more items) it is challenging for users to find what they need. Consider adding an option to the UI for users to sort by section (key features, other features, deprecations, etc) as well as sorting by plan type and/or stage. The default of the page would be to show everything as we now do, but then the user can sort/filter as needed. * What is/are the relevant URL(s): https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/ * What team/dept/company initiatives does this relate to? - Product Marketing * What are the measurable key performance indicators (KPI)? - time on page - clicks on page - feature adoption This suggesting has come cross-functionally from product, marketing, sales and engineering teams at different times. Product stakeholders recommended for design review and or feedback on this one, should you decide to move forward @fseifoddini @sfwgitlab @adawar Recommended Marketing stakeholder @johnjeremiah

2020-05-26 15:27:24.426

Set cookiebot to refresh after accept

#### What problem(s) are we trying to solve? What are the project goals? End users may be unaware that they need to refresh the page after accepting cookies. This used to happen automatically but something may have changed. This is likely impacting Marketo form conversion rate. #### Briefly describe your request Attempt to implement [this fix](https://support.cookiebot.com/hc/en-us/community/posts/360014661313/comments/360001582313). ``` window.addEventListener('CookiebotOnAccept', function (e) { if (Cookiebot.changed) { document.location.reload(); } }); ``` #### What is/are the relevant URL(s) https://about.gitlab.com/* #### What team/dept/company initiatives does this relate to? Improve conversion #### Is there a due date? If so, why? No due date, however ASAP is good. #### Please identify the directly responsible individual (DRI), stakeholders, and roles |Name|Role| |------|------| | `@brandon_lyon` | DRI | | `@sdaily` | Cookiebot | | `@amy.waller` | Marketo | | `@shanerice` | Metrics | <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-05-22 18:01:15.428

Add Value Calculator to the Data Team Handbook to support prioritization and ranking of new Issues, Epics, and Initiatives

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update Update Data Team "How We Work" section to include coverage of the a Value Calculator to aid in work prioritization. Originating Issue: https://gitlab.com/gitlab-data/managers/-/issues/161 <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-05-20 15:00:13.718

Update Data Team Handbook SLOs

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update Update the SLO section of the Data Team handbook to include coverage for Issues and MRs. Origin Issue: https://gitlab.com/gitlab-data/analytics/-/issues/4734#note_340948597 <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-05-19 21:43:01.255

Add video to commit landing page

#### What problem(s) are we trying to solve? What are the project goals? * Communicate event expectations via [this video](https://www.youtube.com/watch?v=iQjMV-Ux8zE&feature=youtu.be). #### Briefly describe your request * Add a video block to the Commit event landing page. #### What is/are the relevant URL(s) * https://about.gitlab.com/events/commit/ #### What team/dept/company initiatives does this relate to? * Unknown. #### Is there a due date? If so, why? * Sooner is better than later but no specific date is connected. #### Who is the audience? * (Primary) Potential event attendees. * Speakers. * Media. * Potential sponsors. #### What are the measurable key performance indicators (KPI)? This phase: * Email subscriptions. * CFP submissions. * Sponsorship info requests. Eventually: * Attendee signups. * Scholarship requests. #### Please identify the directly responsible individual (DRI), stakeholders, and roles |Name|Role| |------|------| | `@Lconway` | DRI | | `@brandon_lyon` | Developer | #### Does this request require a form to capture registrations for a gated asset? - [x] No * Forms on the page are preexisting and already developed with mktg ops. - [ ] Yes * Gated assets require involvement from the MPM team to set up registration processing and tracking for reporting. Please open a [Gated Content Request](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/new?issuable_template=Gated-Content-Request-MPM) for the MPM team. #### Where do you expect traffic to come from? * Linked from https://about.gitlab.com/ * Social media campaign. * Targeted ads. * Email campaigns. #### If applicable, do you have any user journeys, prototypes, content/data? * [Events template figma file](https://www.figma.com/file/frPfePiwZlywXoTkEsw5g1/Email-Web-Design-System---Commit-Example) #### Proposed deliverables * Add a block to the page where there is a video preview <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-05-19 17:49:01.262

Update the issue template for website requests

#### What problem(s) are we trying to solve? What are the project goals? Per @jennyt, we need to check if forms have reporting setup before releasing a page with a form on it. #### Briefly describe your request Update the "website-work-request" issue template with the following details BEFORE the "what are project must-haves" section: > Does this request require a form to capture registrations for a gated asset? * Checkbox for "no". * Checkbox for "yes". * Gated assets require involvement from the MPM team to set up registration processing and tracking for reporting. Please open a [Gated Content Request](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/new?issuable_template=Gated-Content-Request-MPM) for the MPM team. #### Who is the audience? * GitLab team members. #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@jennyT` | DRI | | `@brandon_lyon` | Developer | <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-05-18 15:11:50.077

Update Data Team Handbook Charter

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update Update Data Team Handbook Charter to include our new Mission and other adjustments to help everyone better understand the direction the Data Team is heading, towards providing more complete and scalable solutions. <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-05-15 13:17:03.816

Image broken on Guide to the Cloud resource

#### What is/are the relevant URLs or emails? * https://about.gitlab.com/resources/guide-to-the-cloud/ #### Briefly describe the bug * One of the SVG images doesn't look like it should (it should have a building and aircraft).  #### What is your window size, browser, operating system, and versions * https://www.whatsmybrowser.org/b/4YUV8SF #### What device are you using Macbook 15 2019 <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-05-08 15:41:26.740

Update button text on GitLab for Remote video form

Update button text on form CTA to say "Watch Video". Page is here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7098#note_338454573 Brandon Lyon's comment about adding the button text code is here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7098#note_338454573

2020-05-05 01:07:12.829

New Page for Forrester TEI project

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### Briefly describe the request Create a new page for a new customer project from Forrester, the Total Economic Impact #### What is/are the relevant URL(s) about.gitlab.com/analysts/forrester-tei2020 #### What team/dept/company initiatives does this relate to? Strategic marketing has commissioned a Total Economic Impact report to be used as a sales tool to help customers realize their cost savings in using GitLab for specific use cases. #### Is there a due date? If so, why? Our due date is late May 2020 as we will get the final report from Forrester and have sales training for Sales and a place to direct them to for messaging and links to the tool and other assets. #### What problem(s) are we trying to solve? What are the goals? It's a brand new commissioned report that provides tools for sales and competitive #### Who is the audience? * Sales * Customers * Prospects #### What are the measurable key performance indicators (KPI)? * how many visit the page * downloads of the report * visits to the intereactive tool that Forrester is creating for us #### Please identify the directly responsible individual (DRI), stakeholders, and roles |Name|Role| |------|------| | @cfletcher1 | DRI | | @Tompsett | maintenance and admin | | @rragozzine |maintenance and admin| #### What are the project must-haves? * the web page #### Where do you expect traffic to come from? * social * requesting this be linked to main about.gitlab.com page * use case campaigns #### Please provide any related media files * forthcoming from Forrester, but likely links at this point #### Will you need an opengraph image for social sharing? no, as I still have no idea what that is #### Please create a checklist of deliverables in this phase * create and populate web page #### Please apply your team's label using the dropdown menu below Strategic Marketing, Analyst Relations <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-30 07:22:42.871

Features page: Sticky DevOps stage headers, to discover feature-to-stage assignment faster

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### Briefly describe the request The names of our DevOps stages It would sticky while scrolling over that stage's features For example: `Manage` should remain visible while scrolling over the feature subsections `Users`, `DevOps Reports` and `Value Stream Management` (each a `<h4 class="text-left"`), or when jumping through all `LDAP` mentions with Ctrl+F. #### What is/are the relevant URL(s) https://about.gitlab.com/features/ #### What team/dept/company initiatives does this relate to? <!-- Examples: * Brand and Digital wants to improve growth metrics via [tactical conversion MVCs](https://gitlab.com/groups/gitlab-com/-/epics/242). * [OKR FY 21 Q1 CMO: 20% increase in inbound MQLs](https://about.gitlab.com/company/okrs/fy21-q1/) --> #### Is there a due date? If so, why? No. #### What problem(s) are we trying to solve? What are the goals? <!-- Please specify which goal is the primary goal. Examples: * (Primary) Increase self-hosted conversion rate. * Users can't find what they're looking for. * It's difficult to sign up. * This feature is confusing. * This template is difficult to update. * Reduce cognitive overload. * Improve time-on-site. --> The lifecycle stage headings on [/features](https://about.gitlab.com/features/) (`<a class="item-link" ... <h2>` plus maybe `<p class="subhead"> ...`) can be a long distance apart from where one views the page. This necessitates a lot of scrolling up (often too far, therefore down again) to find the stage name. #### Who is the audience? <!-- Please specify which audience is the primary audience. Examples: * (Primary) Potential event attendees. * Speakers * Media * Potential sponsors --> * GitLab employees looking up the feature-to-stage assignment, for example to then find out a DRI, stable support counterpart or technical writer on [/company/team/org-chart](https://about.gitlab.com/company/team/org-chart/) or [/handbook/product/categories](https://about.gitlab.com/handbook/product/categories/#devops-stages). #### What are the measurable key performance indicators (KPI)? See examples in `checklist of deliverables` below. #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@user1` | DRI | | `@user2` | Conversion | | `@user3` | Design | | `@user4` | Metrics | etc --> #### What are the project must-haves? The `<h2>` stage header must remain in view while scrolling. #### What are the project should-haves? Maybe pinned to the to the top of its respective `<div class="features-description`, below `<header class="navbar"`. <!-- These are important but not necessary for delivery in the current timebox. These are often not as time-critical and may be delayed until a later milestone. (Example should-haves) * New look & feel * Improved navigation * Updated hero section --> #### What are the project could-haves? Instead of pin to top, maybe to the side, tilted by 90˚? <!-- These are desirable but not necessary. (Example could-haves) * Sliders * Animations * "Bells-and-whistles" --> #### What are the project wont-haves? <!-- These are not planned at this time. (Example wont-haves) * A certain section of the page is currently performing well or functioning as intended. Do not change it. * A requested feature is too expensive and not currently a good way to spend limited resources. * A requested feature is impossible given current constraints and existing technology. --> #### Where do you expect traffic to come from? <!-- Examples: * Linked from https://about.gitlab.com/example/ * Social media campaign * Targeted ads --> #### Please provide any related media files <!-- If you are requesting that we place images, videos, etc on a page, please either attach the files to the issue or tell us where they can be sourced: * What subject matter of imagery or videos are you looking for? * Examples: Stock photo of a young person using a phone, screenshot of application name during stage/interaction/screen X, abstract tech background... * The @username of who has related files, what issue they're in, or where they can be found. * For logos, please upload vector files such as svg if possible. If vector files are not possible, please upload transparent png. * If linking a word/spreadsheet/presentation document with images included, please also provide links to the original image sources. * Please note that the more media we have to spend time sourcing, re-sizing, and touching up, the less time we have to work on other items. Media is important but don't forget to weigh its implementation costs. --> #### Will you need an opengraph image for social sharing? <!-- Yes or no, and what could it look like? --> #### If applicable, please provide some example webpages for design guidance. <!-- Please specify why you like each reference. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? <!-- Examples: * Google docs/sheets, Figma prototypes, Mural diagrams. --> #### Please create a checklist of deliverables in this phase - [ ] Update page - [ ] Approved review of changes - [ ] Implement AB test (for example: compare clickthrough rate for `/stages-devops-lifecycle/...` pages vs. each stage's features' docu pages) - [ ] Release - [ ] Evaluate results (for example: higher clickthrough rate to `/stages-devops-lifecycle/...` page due to higher/longer visibility of each stage's header) - [ ] Code cleanup <!-- #### Please apply your team's label using the dropdown menu below Example: "Digital Marketing Programs" --> <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-29 22:29:50.077

Updating candidate sourced KPI to add chart

#### Briefly describe the update <!-- Adding a chart to the candidate sourced KPI --> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-21 22:38:38.920

New Page for 2020 for Gartner MQ for AST

#### Briefly describe the request Create a new web page for a new Gartner Magic Quadrant featuring GitLab #### What is/are the relevant URL(s) https://about.gitlab.com/analysts/gartner-ast20 #### What team/dept/company initiatives does this relate to? Strategic Marketing always requests a web page for a new analyst report where we share information with sales on how to position this document for best advantage and frame GitLab properly in the context of their sales environment. #### Is there a due date? If so, why? The report is expected to come out the week of 2020-04-27. If we can have it that week, that would be good. #### What problem(s) are we trying to solve? What are the goals? * provide information to Sales #### Who is the audience? * sales * customers and prospects * analyst community #### What are the measurable key performance indicators (KPI)? * SEO #### Please identify the directly responsible individual (DRI), stakeholders, and roles |Name|Role| |------|------| | @tompsett | DRI | | @cfletcher1 | Content| | @cblake | Content | | @NicoleSchwartz | Content | #### What are the project must-haves? The web page set up like other web pages on that *.../analysts/* group of pages #### What are the project should-haves? Nothing else really #### Where do you expect traffic to come from? * Sales * Blog posts #### Please provide any related media files We do not have that media yet. It is not released until the analysts release the page. We are not given more than 24 hours notice of this going live. #### Will you need an opengraph image for social sharing? I don't think so, since I have no idea what that is. #### If applicable, please provide some example webpages for design guidance. ../analysts/gartner-aro19 #### Please create a checklist of deliverables in this phase - [ ] create new page in same manner as others in that group Marked confidential because we cannot have anyone know we are anticipating being in this report until it is published. <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-21 16:17:12.572

Create a new Marketo landing page template phase 1

@jgragnola @sbouchard1 FYI I've filed this issue to centralize the landing page requirements we've discussed on zoom, slack, and gathered from various issues. #### Briefly describe the request Create a Marketo landing page template for campaigns. #### What team/dept/company initiatives does this relate to? * [Marketing agility, modular pages via boring project](https://gitlab.com/groups/gitlab-com/-/epics/402#note_327516774) #### What problem(s) are we trying to solve? What are the goals? * (Primary) Make it easier for marketing to create landing pages. * Improve the cohesiveness of the user flow from ads all the way to downloads and PF experiences. * Improve the conversion rate of lead generation forms. * Align about.gitlab landing pages with Marketo landing pages. #### Who is the audience? * (Primary) Users who want to learn more about a targeted subject. * Users who want to browse our content. #### What are the measurable key performance indicators (KPI)? * Form submissions. #### Please identify the directly responsible individual (DRI), stakeholders, and roles |Name|Role| |-|-| |***`@jgragnola`***|***DRI***| |`@sbouchard1`|Conversion| |`@luke`|Design| |`@amy.waller`|Marketo| |`@mnguyen4`|Ads| |`@shanerice`|Metrics| |`@sdaily`|Pathfactory| |`@wspillane`|Social| #### What are the must-haves modules? * Hero * Bullet list * Form * Before & after * Image to showcase a preview of the resource * Trusted by * Value (Pathfactory) * Meta title and opengraph copy. #### What are the should-haves modules? * CTA header * On, off, auto-hide * Opengraph image * Free trial CTA * Social sharing (similar to webcasts) * Speaker module (near hero). * Event interest registration. #### What are the could-have modules? * Calendar * Card list * Icon list * Paragraphs with floated image #### Where do you expect traffic to come from? * Email * Ads * Social #### If applicable, do you have any user journeys, prototypes, content/data? * [Creating a responsive Marketo landing page template](https://www.grazitti.com/blog/create-responsive-landing-pages-in-marketo/) * [Prior issue with mockups for implementing a Marketo landing page](https://gitlab.com/gitlab-com/marketing/corporate-marketing/-/issues/262) * [Figma for cohhesive conversion paths](https://www.figma.com/file/ZXMLi2KANpumss7MXtAgi7/Cohesive-%26-Efficient-Conversion-Paths?node-id=0%3A1) * [Jumpstart Figma file](https://www.figma.com/file/RfId179phVJZ9rgm6aBdys/Jumpstart?node-id=25%3A708) * [Event template figma file](https://www.figma.com/file/frPfePiwZlywXoTkEsw5g1/Email-Web-Design-System---Commit-Example?node-id=0%3A1) * [Event landing page template issue](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/6295) * [Comparison pages Figma](https://www.figma.com/file/4EDH2Zc8bXRjQ4cVL3cdlr/GitLab-vs.-Campaign?node-id=142%3A0) * https://about.gitlab.com/compare/github-actions-alternative/ * https://about.gitlab.com/compare/jenkins-alternative/ * https://about.gitlab.com/just-commit/lower-tco/ * https://about.gitlab.com/solutions/aws/ #### Please create a checklist of deliverables in this phase - [x] Create a responsive Marketo landing page template. - [x] Identify and implement MVC toggleable and editable regions. - [x] Review with stakeholders. - [x] Ensure we have sufficient analytics for performance metrics. * Classnames. * Tracking tags (GTM). * Javascript events. * UTMs. * Pathfactory & email addresses. - [x] Ensure opengraph data works as expected. - [x] Check for mobile usability. * Finger-friendly touch interactions. * Mobile viewport meta tags are present and sized appropriately. - [ ] Browser / SPA icon. - [x] Appropriate font-stack is used. - [ ] Ensure that the new look and feel aligns with upcoming ads & campaigns as well as past ones. * Example: [DevSecOps campaign](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/2592#note_328544950) - [x] Assess if the template is applicable to this [template request](https://gitlab.com/gitlab-com/marketing/corporate-marketing/-/issues/2425) - [x] Create a followup issue for the next phase. #### Saved for later phases * Document how to use the new template. * Preview of "what's inside" * Implement AB testing framework. <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-20 22:48:27.004

A/B Test on Contact Sales Form

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### Briefly describe the request <!-- Example: Create a landing page for a PPC lead generation campaign. --> A/B Test the demo form on /sales #### What is/are the relevant URL(s) https://about.gitlab.com/sales/ #### Please identify the directly responsible individual (DRI) and stakeholders @EWhelchel @Elsje @amimmo @amy.waller #### What team/dept/company initiatives does this relate to? SDR, Sales <!-- Examples: * Brand and Digital wants to improve growth metrics via [tactical conversion MVCs](https://gitlab.com/groups/gitlab-com/-/epics/242). * [OKR FY 21 Q1 CMO: 20% increase in inbound MQLs](https://about.gitlab.com/company/okrs/fy21-q1/) --> #### Is there a due date? If so, why? No specific due date, we would like to get this done to improve lead conversion. <!-- Please note: Without sufficient lead time we will likely be unable to meet your deadline. Marketing web development is currently an impacted resource. Example: Our due date is XXXX-XX-XX. We want to launch this page before a trade show happens on YYYY-YY-YY. We need a week of lead time to coordinate a press release before the event. --> #### What are the project goals? * Improve Form conversion * Improve lead conversion rates, making it easier for sales to reach prospect via #### Who is the audience? Prospects who land on the Demo page. #### What problem(s) are we trying to solve? Increase lead conversion rates, without sacrificing too much of form conversion. Phone number being required should make it easier for SDRs to reach out to prospects. <!-- Example: * Users can't find what they're looking for. * It's difficult to sign up. * This feature is confusing. * This template is difficult to update. --> #### What are the measurable key performance indicators (KPI)? * Form Conversion * Lead Conversion <!-- Examples: * Email subscriptions * Sponsorship info requests * CFP submissions * Attendee signups * Scholarship requests --> #### What are the project must-haves? AB Test on the page for the two forms. <!-- Please try to keep this list as short as possible. This project cannot launch without: (Example must-haves) * Functional signup form * CTA for proposals --> #### What are the project should-haves? <!-- These are important but not necessary for delivery in the current timebox. These are often not as time-critical and may be delayed until a later milestone. (Example should-haves) * New look & feel * Improved navigation * Updated hero section --> #### What are the project could-haves? <!-- These are desirable but not necessary. (Example could-haves) * Sliders * Animations * "Bells-and-whistles" --> #### What are the project wont-haves? <!-- These are not planned at this time. (Example wont-haves) * A certain section of the page is currently performing well or functioning as intended. Do not change it. * A requested feature is too expensive and not currently a good way to spend limited resources. * A requested feature is impossible given current constraints and existing technology. --> #### Where do you expect traffic to come from? Typical traffic to page - no changes <!-- Examples: * Linked from https://about.gitlab.com/example/ * Social media campaign * Targeted ads --> #### Please provide any related media files Embed Code for B test form 2535: I can't get this to paste Let me know if you need the code for the A test. #### Will you need an opengraph image for social sharing? No #### If applicable, please provide some example webpages for design guidance. <!-- Please specify why you like each reference. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? <!-- Examples: * Google docs/sheets, Figma prototypes, Mural diagrams. --> #### Please create a checklist of deliverables in this phase <!-- Examples: - [ ] Place & style marketo form - [ ] Update page - [ ] Approved review of changes - [ ] Implement AB test - [ ] Create heatmaps - [ ] Release - [ ] Evaluate results - [ ] Code cleanup --> - [ ] A/B Test set up - [ ] Create a followup issue for the next phase (monitor results) <!-- #### Please apply your team's label using the dropdown menu below Example: "Digital Marketing Programs" --> <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-20 22:44:42.944

A/B Test on Demo Form for Phone number

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### Briefly describe the request <!-- Example: Create a landing page for a PPC lead generation campaign. --> A/B Test the demo form on /demo #### What is/are the relevant URL(s) https://about.gitlab.com/demo/ #### Please identify the directly responsible individual (DRI) and stakeholders @EWhelchel @Elsje @amimmo @amy.waller #### What team/dept/company initiatives does this relate to? <!-- Examples: * Brand and Digital wants to improve growth metrics via [tactical conversion MVCs](https://gitlab.com/groups/gitlab-com/-/epics/242). * [OKR FY 21 Q1 CMO: 20% increase in inbound MQLs](https://about.gitlab.com/company/okrs/fy21-q1/) --> #### Is there a due date? If so, why? No specific due date, we would like to get this done to improve lead conversion. <!-- Please note: Without sufficient lead time we will likely be unable to meet your deadline. Marketing web development is currently an impacted resource. Example: Our due date is XXXX-XX-XX. We want to launch this page before a trade show happens on YYYY-YY-YY. We need a week of lead time to coordinate a press release before the event. --> #### What are the project goals? * Improve Form conversion * Improve lead conversion rates, making it easier for sales to reach prospect via #### Who is the audience? Prospects who land on the Demo page. #### What problem(s) are we trying to solve? Increase lead conversion rates, without sacrificing too much of form conversion. Phone number being required should make it easier for SDRs to reach out to prospects. <!-- Example: * Users can't find what they're looking for. * It's difficult to sign up. * This feature is confusing. * This template is difficult to update. --> #### What are the measurable key performance indicators (KPI)? * Form Conversion * Lead Conversion <!-- Examples: * Email subscriptions * Sponsorship info requests * CFP submissions * Attendee signups * Scholarship requests --> #### What are the project must-haves? AB Test on each form. <!-- Please try to keep this list as short as possible. This project cannot launch without: (Example must-haves) * Functional signup form * CTA for proposals --> #### What are the project should-haves? <!-- These are important but not necessary for delivery in the current timebox. These are often not as time-critical and may be delayed until a later milestone. (Example should-haves) * New look & feel * Improved navigation * Updated hero section --> #### What are the project could-haves? <!-- These are desirable but not necessary. (Example could-haves) * Sliders * Animations * "Bells-and-whistles" --> #### What are the project wont-haves? <!-- These are not planned at this time. (Example wont-haves) * A certain section of the page is currently performing well or functioning as intended. Do not change it. * A requested feature is too expensive and not currently a good way to spend limited resources. * A requested feature is impossible given current constraints and existing technology. --> #### Where do you expect traffic to come from? Typical traffic to page - no changes <!-- Examples: * Linked from https://about.gitlab.com/example/ * Social media campaign * Targeted ads --> #### Please provide any related media files Embed Code for B test form: I can't get this to paste Let me know if you need the code for the A test. #### Will you need an opengraph image for social sharing? No #### If applicable, please provide some example webpages for design guidance. <!-- Please specify why you like each reference. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? <!-- Examples: * Google docs/sheets, Figma prototypes, Mural diagrams. --> #### Please create a checklist of deliverables in this phase <!-- Examples: - [ ] Place & style marketo form - [ ] Update page - [ ] Approved review of changes - [ ] Implement AB test - [ ] Create heatmaps - [ ] Release - [ ] Evaluate results - [ ] Code cleanup --> - [ ] A/B Test set up - [ ] Create a followup issue for the next phase (monitor results) <!-- #### Please apply your team's label using the dropdown menu below Example: "Digital Marketing Programs" --> <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-15 23:09:04.583

Transition the valuedriver pages to use cases

This is a filler/placeholder issue while @brandon_lyon figures out the details. <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-04-09 12:09:49.686

Blog Post: Show GitLab UI changed over years in pictures (Date TBD/by end of May)

### Proposal I have quite a few screenshots of different old versions of GitLab. When I show it to some GitLab people, they were excited about it. One person suggested I make a blog post out of it. This can be a single blog post or series. With few screenshots per-year and some little text. Or more extended version. Right now its a raw idea. I don't have a good plan yet. Want to check out what people think. Few example of screenshots I have: | Page | Year | Screenshot | |---|---|---| | merge_request| 2012 |  | | dashboard | 2013 |  | | dashboard/issues | 2014 | | | project/tree | 2015 |  | ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#time-sensitive-posts-official-announcements-company-updates-breaking-changes-and-news) - [ ] Added ~"priority" label and supplied rationale in description - [ ] Mentioned `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive - [ ] Add ~"sensitive" label - [ ] Mention `@nwoods` to give her a heads up ASAP - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS` and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-04-06 23:29:41.644

DevOpsTools Comparison Pages - Design

This is issue is related to all design work required to build and launch the new Dev Ops Tool Comparison webpage. You can view the broad stroke estimate and initial planning here: https://gitlab.com/gitlab-com/marketing/product-marketing/-/issues/2266 There is a another issue related to the development of this page here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7052 # Helpful Links * [latest wires](https://www.figma.com/file/4EDH2Zc8bXRjQ4cVL3cdlr/GitLab-vs.-Campaign?node-id=142%3A0) to clarify scope of work * [Initial Estimates in Days](https://docs.google.com/spreadsheets/d/13hrQGM1re7k9LD0LrZYTYj1Qisx5e6aUvV84-CXUKhw/edit#gid=0) (1 work day considered 6.5 hours of work).

2020-04-06 23:27:58.802

DevOpsTools Comparison Pages - Development

This is issue is related to all development work required to build and launch the new Dev Ops Tool Comparison webpage. You can view the broad stroke estimate and initial planning here: https://gitlab.com/gitlab-com/marketing/product-marketing/-/issues/2266 There is a another issue related to the design of this page here: # Helpful Links * [latest wires](https://www.figma.com/file/4EDH2Zc8bXRjQ4cVL3cdlr/GitLab-vs.-Campaign?node-id=142%3A0) to clarify scope of work * [Initial Estimates in Days](https://docs.google.com/spreadsheets/d/13hrQGM1re7k9LD0LrZYTYj1Qisx5e6aUvV84-CXUKhw/edit#gid=0) (1 work day considered 6.5 hours of work). Figma Design Link: https://www.figma.com/file/kQjjTnRL6aFhhvdE4Zd4AO/GitLab-vs.-GitHub?node-id=0%3A1

2020-04-06 16:11:13.682

Moving a new case study to the landing page

Trying to add this new case study: https://about.gitlab.com/customers/axway-devops/ To the top of the landing page, in the place of ESA: https://about.gitlab.com/customers/ Thanks.

2020-03-31 22:40:02.760

2020Q2 update website issue templates and documentation

### Broad goals * Communicate how to work with the marketing Brand and Digital team. * Improve the quality of issues received in the www-gitlab-com repository. ### Pain points * "How do I create a website request?" * "Which template do I use for what?" * Documents are TLDR. ### Specific goals, default issue template * People aren't reading. Replace this copy with a simple "Please select a template from above. Issues without a template are unlikely to be prioritized" * Link to B&D as the repository DRI. * Each template should describe it's use, first thing. * Improve clarity of template titles ("be as explicit as possible"). * Consolidate templates & reduce choice overload. ### Specific goals, other issue templates * Add more sections... * What are the pain points? * What company or team goals/initiatives does this align with? * **What are the deliverables?** * Explore the use of checklists, particularly in the case of deliverables. * **Directly ask for MOSCOW** instead of indirectly asking... * What are the must-haves? * What are the should-haves? * What are the could-haves? * What are the wont-haves? * Consolidate templates & reduce choice overload. * Streamline templates based on organic changes made over time via observation, similar to examples: * Issue description in [this issue](https://gitlab.com/gitlab-com/www-gitlab-com/issues/6294) * "Deliverables" comment in [this issue](https://gitlab.com/gitlab-com/marketing/corporate-marketing/-/issues/1596#note_274860052) * Add more information and requirements around due-dates. * Emphasize the use of phases and MVC. * Add section for requesting opengraph images so this isn't an afterthought. * Consider hiding titles and examples behind comments so that they aren't visible when someone forgets to delete sections. * People often aren't reading. Consider limiting details. * Remove sections which aren't commonly used or at the very least move them towards the bottom of the issue template. * Similarly move the most used sections towards the top. * Make labels as automated as possible. * Only require the most necessary labels, others can be added during grooming. * Reassess which parts should be opt-in vs opt-out. * switch cc pings @ gl-website from opt-out to opt-in. * switch from "manually add labels" to opt-out of labels. * Add breadcrumbs such as "if you require any redesign to this page, you're using the wrong template. Please use X instead [link]." * Consider adding collapsible sections. * Add a label identifying which template was used. Certain templates already have this, many do not. This will help provide metrics around use. ### Deliverables - [x] Updated default issue template. - [x] Updated individual issue templates. - [x] Search documentation for links to old templates and replace with new links. <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-03-30 17:00:46.056

Virtual DevOps Automation Workshops

Per issue https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/2528 and MR https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/44438 Related [Epic](https://gitlab.com/groups/gitlab-com/marketing/-/epics/854) @jennyt has requested the following: #### What is/are the expected URL(s) * /events/virtual-devops-workshops #### Briefly describe the page/flow 1. A landing page that we can send people to for display and selection of virtual workshops. The actual workshops will be on separately created Marketo landing pages. #### If applicable, do you have any user journeys, wireframes, prototypes, content/data? The last time we did something similar was for the 2019 Roadshow https://about.gitlab.com/events/roadshow-2019/ **MVC:** 1. Add an agenda table in place of the speaker section (right side column). <-- `Currently the only item remaining on the request!` This is MVC because the page is text heavy and needs something (image, table) to break it up. 2. Clone the 2019 Roadshow page, rephrase to virtual devops workshops. (jenny did this in the MR) 3. Create a new data/event_virtual_devops_workshop.yml file to populate the data. (brandon did this) **Ideally:** 1. The event selection at the bottom of the page will be on one line across the screen (to prevent scrolling) instead of vertical. 2. Remove the speaker section from this page. (jenny did this in the MR) 3. Add a "who should attend" section. (jenny did this in the MR) 4. Implementing the functionality to automatically pull relevant events onto this page when the individual pages are created. (brandon did this) **Long term:** Brandon recommends we adapt the new event template created recently in the following issue https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/6294, remove irrelevant sections, and add a new component for listing the virtual workshops. #### What is the primary purpose of this page/flow? Generate registrations for virtual workshops #### What are the KPI (Key Performance Indicators) Registration counts #### What information is this page/flow trying to convey? * Existence of virtual workshops * Agenda * Who should attend ### Who is the primary audience? Be specific. * [x] Potential Prospects who have never heard about GitLab * [x] Prospects we're currently selling to * [ ] Non-paying customers * [x] Paying customers * [ ] Authorized resellers * [ ] Community members This workshop is designed for IT Professionals: * Actively evaluating GitLab for their organization * Driving innovation by knowing the full scope of the GitLab tool chain * Planning to increase operations #### Any other audiences? No #### Where do you expect traffic to come from? Marketing emails to database, sales-invited #### Does this page/flow require any forms Yes. @jennyt will assist in providing the relevant registration form. Registration form will be on the individual landing pages for each event. #### Is there a due date? If so, why? Please note that issues with a short deadline and no listed reasons are difficult to prioritize. **2020-03-27**, reasons unknown, deadline already passed. Reason for deadline: The time to set-up and promote a webcast or virtual event is a minimum of 45 days. This event was provided to the MPM team after this deadline. We are able to promote and fill the event, but we require the landing page as quickly as possible. Once the single page is set up with the functionality to pull the individual registration page links, we will not need to repeat this work. <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-03-23 20:43:57.882

Update & to and in location factor targets

This repository primarily relates to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the repository for requests related to docs.gitlab.com, product, or other parts of GitLab. ## Issues should identify The Five W's https://en.wikipedia.org/wiki/Five_Ws who, what, when, where, and why. We also recommended MoSCoW sorting https://en.wikipedia.org/wiki/MoSCoW_method things the issue Must, Should, Could, and Won't do. * Please apply appropriate labels or your issue may not be sorted into appropriate boards. * Please select a template from the top left menu before continuing. Note there is a blank template https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=blank-template pre-populated with labels and @ mentions. If you do not select an appropriate template then your issue might get lost. For more information about our workflows, please reference the handbook for the marketing website https://about.gitlab.com/handbook/marketing/website/ website issue labels https://about.gitlab.com/handbook/marketing/brand-and-digital-design#working-with-issues-groups-and-labels or reference your team documentation. If you are not using a template then please add appropriate labels and @ mentions. Issues lacking known labels may not appear on work boards. ### FAQ: Q: Which template should I use? A: Most people will use the template for bug reports or requesting page updates. Occasionally redesigns, new pages, feature proposals, or new templates are requested. There are also templates for writing various kinds of blog posts including the unfiltered category. The rest of the templates are specific to team, role, or special occasion. Q: When will you get to this issue? A: Your issue will be refined and then prioritized relative to other issues. Marketing's website development team is currently an impacted resource. Q: I have a hard deadline **related to contracts or events**. How do I ensure the issue gets done by then? A: Apply the label "hard-deadline" and assign a due date BEFORE the actual deadline. Leave a comment in the issue or description mentioning that it's time-sensitive and needs to be finished before the date in question if possible. Q: How does marketing's web development team determine priority levels? A: Please see our prioritization documentation https://about.gitlab.com/handbook/marketing/brand-and-digital-design/#prioritization Q: How do I link to an issue template? A: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=name-of-template Q: How do I edit this FAQ? I have another question. A: Submit an issue https://gitlab.com/gitlab-com/www-gitlab-com/issues/new with FAQ in the title and assign it to @ brandon_lyon or another member of the website team https://about.gitlab.com/handbook/marketing/website/

2020-03-23 11:54:12.631

Show the "You're running out of CI minutes" warnings on relevant pages in GitLab

We currently only show the "You're running out of CI minutes" banner warning on the Project overview page. Let's change that so that we'll also show it on Group overview, Projects Dashboard (`/dashboard/projects`), Groups dashboard pages (`/dashboard/groups`). Let's show these banners only to the owner of the group that's running out of CI minutes. We're updating the content and the styling of the banners via gitlab-org/growth/product#1514 ## Proposal | Group overview | Groups dashboard | Projects dashboard | |----------------|------------------|--------------------| |  |  |  | Changes: * Depending on the percentage remaining (30 or 5, see https://gitlab.com/gitlab-org/growth/product/-/issues/1514/designs#banner-warnings-update), show either a warning- or a danger-styled banner on Group overview of the group that is running out of CI minutes. Show it only to group owners. * Depending on the percentage remaining (30 or 5), show either a warning- or a danger-styled banner on Groups dashboard. Show it only to group owners. * Depending on the percentage remaining (30 or 5), show either a warning- or a danger-styled banner on Projects dashboard. Show it only to group owners. Let's use vertical margins of 16 pixels to separate the banner from the main nav and the content of the page.

2020-03-20 14:48:17.689

CSS broken on GitLab Flow page

URL: https://about.gitlab.com/solutions/gitlab-flow/ cc @sbouchard1 @luke @brandon_lyon

2020-03-18 23:49:36.634

Ecosystem Team page in Google results is invalid

When Google searching for `gitlab ecosystem`, the first hit is https://about.gitlab.com/handbook/engineering/development/enablement/ecosystem/, which is a 404:  The correct page is https://about.gitlab.com/handbook/engineering/development/dev/ecosystem/

2020-03-18 14:25:05.954

Pricing page A/B test

Implement [new pricing page](https://gitlab.com/gitlab-org/growth/team-tasks/uploads/1e276f257d2bf72c3a61fec75868fa52/image.png) as experiment. Parent issue: https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/73 MR: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/44494

2020-03-18 14:21:38.134

Implement Snowplow tracking for pricing page A/B test

Utilize the [A/B testing framework](https://gitlab.com/groups/gitlab-com/-/epics/290) for our pricing page test. MR: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/44494 Parent issue: https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/74 I've setup the following snowplow events: Control: <details> <summary markdown="span">On pageload</summary> triggers the event: | property | value | |----------|-------| | category | `pricing_page` | | action | `page_view` | | label | empty | | se_property | `control` | | value | empty | </details> <details> <summary markdown="span">Clicking on the `Sign Up` / `Install` buttons</summary>   triggers these events: | property | value | |----------|-------| | category | `pricing_page` | | action | `cta_click` | | label | `free_saas` or `free_self_managed` | | se_property | `control` | | value | empty | </details> <details> <summary markdown="span">Clicking on the `Buy Now` button</summary>  triggers these events: | property | value | |----------|-------| | category | `pricing_page` | | action | `cta_click` | | label | {{plan_id}} | | se_property | `control` | | value | empty | </details> Test: <details> <summary markdown="span">On pageload</summary> triggers the event: | property | value | |----------|-------| | category | `pricing_page` | | action | `page_view` | | label | empty | | se_property | `group` | | value | empty | </details> <details> <summary markdown="span">Clicking on the `Start now` / `Buy now` buttons to open the modal</summary>  triggers these events: | property | value | |----------|-------| | category | `pricing_page` | | action | `open_modal` | | label | `free`, `bronze-starter`, `silver-premium` or `gold-ultimate` | | se_property | `group` | | value | empty | </details> <details> <summary markdown="span">Clicking on the `Sign-up for free` / `Install GitLab for free` buttons from the modal</summary>  triggers these events: | property | value | |----------|-------| | category | `pricing_page` | | action | `cta_click` | | label | `free_saas` or `free_self_managed` | | se_property | `group` | | value | empty | And `test=jtbd` is added as a URL parameter on the links. </details> <details> <summary markdown="span">Clicking on the `Purchase SaaS` / `Purchase Self-managed` buttons from the modal</summary>  triggers these events: | property | value | |----------|-------| | category | `pricing_page` | | action | `cta_click` | | label | {{plan_id}} | | se_property | `group` | | value | empty | And `test=jtbd` is added as a URL parameter on the links. </details>

2020-03-18 14:17:11.452

Setup testing framework for pricing page test

Utilize the [A/B testing framework](https://gitlab.com/groups/gitlab-com/-/epics/290) for our pricing page test. Parent issue: https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/74

2020-03-04 20:15:55.950

Followup AB test to valuedriver

This issue is a followup for https://gitlab.com/gitlab-com/www-gitlab-com/issues/6595 ## Relevant URL * https://about.gitlab.com/just-commit/reduce-cycle-time/ ## AB testing LaunchDarkly documentation * https://docs.google.com/document/d/1_XztSRs_CMBulZDvrVbSHmCjtOnL0xd6gFUEVo_NxoA/edit?usp=sharing ## Results of prior test found in * https://gitlab.com/gitlab-com/marketing/corporate-marketing/issues/1596#note_299047010 ## Requested deliverables * Switch the main nav so it doesn't have the free-trial CTA (free trial is distracting). * The thank you popup after submit could have free-trial as secondary CTA. * Make sure there is only one CTA. * Remove the "ready to talk" section at the bottom of the page. * Change the download CTA phrase from "Read the Whitepaper" to "Get your Whitepaper". * Suggested copy: any action word that doesn't sound like work (ie not "read") * Try different report screenshots or potentially animations, have a more graphical cover. * Ask Luke for suggestions, we could create a cover, perhaps some synergy of the graphic with the CTA button. * Try moving the bullet points into the purple section before the CTA button (what you will learn is important). * Change the popup title to match the button (Get your whitepaper). * Bump up the font size of and adjust copy to "trusted by 100,000+ organizations worldwide" and make it bigger. * Check with @ mnguyen4 to ensure copy is consistent with what interested them in the first place. ## Valuedriver reference material * https://docs.google.com/presentation/d/1adRX6Vua7LhpZNgG6scqn4uH8Mz3rDVhNGBUU8RFZ2o/edit#slide=id.g7e88ccd42e_0_57 ## Notes: * Please do not run this test for too long so we don't use up our allocated MAU (monthly active users). Last time we ended up with ~ 2000 hits (1,000 each) in ~ 5 days for this particular page which should suffice. * Shane Rice suggested removing the form from the popup and leaving it on the page. That's a good suggestion but for efficiency & time sensitivity I would suggest that as a followup and doing this first.

2020-02-27 16:32:39.221

Unfiltered posts with "featured" appearing on /blog

Before the new /blog design, posts in the `unfiltered` category did not appear on /blog. I think if the post contained `featured: yes` in the frontmatter, it resulted in a blank block on the index page (not ideal, which is why we do have documentation to remove it: https://about.gitlab.com/handbook/marketing/blog/unfiltered/#review) I noticed before a new featured post was published today that an Unfiltered post (where `featured: yes` had been left in the frontmatter) was appearing as the featured post on /blog. Is there a way to prevent this? As mentioned above we do ask people not to include this in the frontmatter but it does happen occasionally.

2020-02-25 12:50:22.349

Update Data Team Workflow Process and Labels

This issue tracks the Update Data Team Workflow Process and Labels. <!-- These labels will be automatically applied unless you edit or delete the following section --> <!-- If you do not want to ping the website team, please remove the following section --> /cc @gl-website

2020-02-24 19:22:36.094

Add Hotjar polls to the about website

Per @sbouchard1 this issue will explore the addition of Hotjar polls to the website as useful way to gather feedback privately in addition to potential use as a KPI. ## Requirements Starting with just one poll for now: - [ ] Discuss with other teams where polls have been used, where we might benefit from their use, tips & tricks, etc. - [ ] Identify [type of poll](https://help.hotjar.com/hc/en-us/articles/115011624547-Creating-Your-First-Poll). - [ ] Identify questions for poll. - [ ] Identify pages where the poll will or won't be served. - [ ] Identify where the poll will live on the page for desktop/tablet/mobile. - [ ] Implement the form. - [ ] Create a followup issue to identify next steps (what do we do with the info gathered, what other polls should we make, create documentation, create an issue template for requesting polls, etc...) ## Note * Need to be careful Hotjar feedback loops do not negatively impact conversion (funnels, etc) * Also need to avoid any conflicts with chat bot (@bethpeterson for awareness) <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-02-21 21:30:39.544

Migrate only/except CI to rules

Many of our CI jobs in .gitlab-ci.yml use the only/except(advanced) feature described here: https://docs.gitlab.com/ee/ci/yaml/#onlyexcept-advanced This feature is marked as "an alpha feature, and it is subject to change at any time without prior notice!" Only/Except is [planned to be deprecated](https://docs.gitlab.com/ee/ci/yaml/#onlyexcept-basic). Either-way, I think we should migrate all of our CI jobs to use rules instead of the only/except feature. Rules allow for more complex pipelines and will set us up for a monorepo build process. https://docs.gitlab.com/ee/ci/yaml/#rules See also [original issue for rules](https://gitlab.com/gitlab-org/gitlab/issues/27863)

2020-02-13 20:44:28.557

[new webpage] - Topic page - /version-control

### [COPY](https://docs.google.com/document/d/1T2_3fEZfGPY_1TvpHGYz0Ku_MR7lsO-hMdMvdej4tT4/edit#) #### What is/are the expected URL(s) /topics/version-control/ Does this match existing strategies? **Yes** Has keyword research been done? **Yes** #### Briefly describe the page/flow This is a topic page to provide awareness-level information. It mirrors the [agile delivery](https://about.gitlab.com/agile-delivery/) page. #### If applicable, do you have any user journeys, wireframes, prototypes, content/data? I have a [google doc with a wireframe and content](https://docs.google.com/document/d/1T2_3fEZfGPY_1TvpHGYz0Ku_MR7lsO-hMdMvdej4tT4/edit) (it's still in the planning stage). it'll be similar to this [doc for the agile delivery page](https://docs.google.com/document/d/1UxcdvnRAIKVPln-Fgo_LHKwc8mMQ-QDXGjacO2pqbhU/edit#) #### What is the primary purpose of this page/flow? - increase awareness - drive people to the pathfactory path #### What are the KPI (Key Performance Indicators) - number of sessions #### What other purposes does this page/flow serve, if any? - capture emails for campaign funnels #### What information is this page/flow trying to convey? - what is scm - what are the benefits ### Who is the primary audience? Be specific. - prospective customers - developers - devs learning about scm #### Where do you expect traffic to come from? - organic search - blog posts #### Please provide some example websites for design guidance. - https://about.gitlab.com/agile-delivery - https://about.gitlab.com/devops

2020-02-10 20:01:53.650

Document kramdown abbreviation syntax in handbook

As documented in https://gitlab.com/gitlab-com/www-gitlab-com/issues/4762, usability of acronyms is limited when the definition is made in place on a long document. Kramdown already supports a [lightweight markup for abbreviations](https://kramdown.gettalong.org/syntax.html#abbreviations) but it is fairly opaque to the user. ## Proposal Update the handbook to include specific usage of the Kramdown abbreviation syntax until we can build a more automated solution as recommended in #4762

2020-02-10 19:50:08.952

Improve styling of acronyms

## Problem to solve The display of acronyms defined in the handbook [using Kramdown's abbreviation syntax](https://kramdown.gettalong.org/syntax.html#abbreviations) could use some help. Currently, there is a combination of a dotted border and underline. The styling should make the abbreviation stand out but remain consistent with the rest of the site. Current display on the handbook:  ## Proposal Update the styling to remove the double dashed/dotted border. Start by removing the unstyled user agent text-decoration and then evaluate the legibility of the user-defined style.

2020-02-03 12:07:37.340

Create a message in #handbook if master is broken for the handbook

## Problem to solve When the master pipeline fails for a handbook build, the user has often left the page and completely changed context. It can be hours or days before they return to fix the error. ## Proposal Create an alert in the #handbook Slack channel if the master pipeline fails.

2020-01-31 18:52:35.209

Investigate feature flag AB testing tools

Relates to https://gitlab.com/gitlab-com/www-gitlab-com/issues/6151 and https://gitlab.com/groups/gitlab-com/-/epics/290 This issue will investigate if we can use LaunchDarkly as an A/B test tool and attempt implementation. Always be thinking MVC. - [x] Sign up for trial accounts and create simple tests to familiarize yourself with the tools. - [x] Assess what (if any) additional items are required for implementation. - [x] Implement a test to verify the chosen tool is functioning as expected and evaluate the efficacy of the tool. - [x] Ensure necessary tracking is in place (analytics, heatmaps, and test significance). - [x] Ensure this plays nicely with cookiebot. - [x] Document relevant processes and responsibilities related to the new tool(s). Related to the documentation item, here's a video about [managing feature flags at full scale](https://www.youtube.com/watch?v=uFW4SSRtkUU). <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-01-31 08:03:28.873

List Categories in Order of Maturity on Maturity page

As per this issue, https://gitlab.com/gitlab-com/Product/issues/722, we need to update the code that generates the categories on the [Maturity page](https://about.gitlab.com/direction/maturity/) so that categories are list in order of maturity.

2020-01-28 10:07:12.621

Create a dashboard in Periscope for blog pipeline metrics

We need to create a pipeline metrics dashboard in Periscope specifically to the blog child pipeline. The dashboard should be based on the existing one for all of the website: https://app.periscopedata.com/app/gitlab/561277/WIP:-www.gitlab.com-Pipeline-Metrics This issue is dependent on https://gitlab.com/gitlab-com/www-gitlab-com/issues/6355

2020-01-27 20:28:08.225

Upgrade www-gitlab-com repo to Ruby 2.6.5

Upgrade the `www-gitlab-com` repo to Ruby 2.6.5, to match the recent upgrade of the `gitlab-org` repo. Based on a [slack question](https://gitlab.slack.com/archives/C8HG8D9MY/p1579047921205700), there doesn't appear to already be an issue for this. This should be straightforward. Looking at the history of `.ruby-version`, it looks like only a couple of changes were needed for the last upgrade.

2020-01-24 21:17:58.353

Provide a quicker way to open the Web IDE from a Handbook page

## Problem to solve Handbook pages offer a quick way to view the source file in the repository or open the source file immediately in the web IDE.  However, this functionality is found in the last 40px of the page, below the footer, and over 900px removed from the content itself. Users would benefit from a more easily accessible way to transition from reading to editing handbook content. ## Proposal Building off the work in #6027 we should add two buttons to the popover when text is highlighted on a handbook page. One icon to open the file in the file browser. Another to open it in the web IDE. Something like this:  ## Implementation details * The twitter/social sharing options should be visually separated from the editing options in order to distinguish between the intent for each * We should not remove the links from the bottom of the page ## What comes next? * The web IDE button should take the user to the exact line of code that matches their selection

2020-01-22 19:15:11.470

Create separate Middleman instance for blog

## Who The Static Site Editor Group and Brand and Digital Design team are working together to create monorepo structure for www-gitlab-com. ## What We are creating a distinct Middleman build for just the blog. By isolating the blog into separate middleman build, we can start to develop blog centric features for just this part of the site. ## Why We are doing this so the blog becomes isolated from other parts of the website and deployment time are reduced. This is also a required step toward creating a true monorepo structure for www-gitlab-com ## When Based on the [Monorepo Approval issue](https://gitlab.com/gitlab-com/www-gitlab-com/issues/6213) and timeline for deliverables, we need to complete this by Feb 3rd ## References * ["how to share assets with multiple sites and allow "local" overrules?" - middleman issue](https://github.com/middleman/middleman/issues/1902)

2021-04-12 16:44:13.915

Blog: Security findings from DevSecOps survey 2021 - May 18

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [ ] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal This blog will go over some of the findings for security in the DevSecOps survey (google doc link shared with me privately https://docs.google.com/document/d/1DdKiGl_1PUSdwPk-go5HaN8AiVncJz2-Zjx5QwYfBKc/edit?usp=sharing) The CTA will be to the developer report, and this blog _could_ also be used for supporting the GTM-CICD? Not sure, since this isn't really about GitLab as a security solution but just reporting on the results from the community. Maybe awareness level. ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@cbuchanan` | requestor | | `@vsilverthorne`| editor | | `@vsilverthorne` | approver (optional) | ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [x] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [x] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-04-08 18:23:15.954

Standard for helper indicators in KPI/RPI charts

We need to come up with a standard to represent helper indicators for KPI/PIs. Examples * Number of bugs in timing KPIs * Cost/user and % of rev indicators ### Proposal Taking into account https://about.gitlab.com/handbook/engineering/quality/performance-indicators/#average-age-of-open-s1-bugs * Instead of 2 lines intersecting it would be best to have 1. A bar chart to represent age => purple to indicate primary indicator 1. A red line for target age => KPI/PI target 1. Area chart represent number of open bugs per month => grey? to indicate supplemental indicator * Using purple to designate primary indicator as a constant formatting * Grey color for supplemental indicator #### Mockup  @lmai1 @davis_townsend for your review and feedback kindly :slight_smile:

2021-04-07 22:04:42.522

Enterprise page feature list has repeated bullet points

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) `https://about.gitlab.com/enterprise/` #### Briefly describe the bug Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned. `See the screenshot below for details. Two sections of the feature list have duplicate bullet points.` #### Please provide any relevant screenshots or screencasts How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/  <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-04-06 15:54:04.118

Blog post: Learn JSON superpowers with jq and automate GitLab workflows (April 19)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [ ] Drive traffic to our website - [ ] Convert traffic into leads - [ ] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal - Updating a post Michael wrote for his personal blog for the GitLab blog. - Based on his comment on #trending channel in Slack: https://gitlab.slack.com/archives/C01P65FC56X/p1615993387003400 - Based on this blog post: https://dnsmichi.at/2021/03/17/learn-json-superpowers-with-jq-automate-gitlab-personal-access-token-management/ @dnsmichi please note that the blog post shouldn't just be a copy/paste of what you originally wrote, but instead should take the content and adapt the information, tone, and writing so it fits in the GitLab blog. I'll be your reviewer so ping me (@skassabian) with any questions or lmk if you need more time. ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@person` | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-04-03 07:14:53.886

Update Ruby from 2.7 to 3.0 to use on dev

We need to continuously keep updating the build/test environments of the repository itself. Relates to gitlab-org&5149 (initiative upgrading Ruby 2.7 to 3.0 in GitLab product) ### cf. - Similar update on build/test: #10917

2021-03-29 21:52:44.837

Blog post: Slippers blog template review (May 3)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [ ] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal <!-- What do you want to blog about? Add your description here. If you are making an announcement, please open an `announcement` request issue in the Corporate Marketing project instead: https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements --> The [digital experience team](https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/) recently launched the [new Slippers blog template](https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/1146) for the marketing blog. I have two main points I'd like to write about, and I'd be happy to take feedback on which direction to pursue, or if it makes sense to write two separate posts, or if one post could contain both points. 1. We used GitLab's [iteration value](https://about.gitlab.com/handbook/values/#iteration), along with GitLab's tool to [promote an issue to an epic](https://docs.gitlab.com/ee/user/group/epics/manage_epics.html#promote-an-issue-to-an-epic) to iterate on an issue we realized was too large in scope by [promoting it to the blog post template epic](https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/296). Once we did this, we were able to also [collaborate](https://about.gitlab.com/handbook/values/#collaboration) more effectively. I'd like to highlight how GitLab's iteration and collaboration values are embodied by the GitLab product's technical capabilities. 1. We had a problem where existing CSS was conflicting with the Slippers design system, and since we didn't have the header/footer ready yet, we couldn't just disable them all. So we used the [shadow DOM](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM) to encapsulate CSS entirely, along with [templates and slots](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_templates_and_slots) to write semantic HTML in erb or HAML templates as desired, all tied together with [custom elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements). In addition to the values piece, I'd like to showcase how we used Web Components to solve challenges in a way that allowed us to iterate quickly. We have lots of the content [written as documentation](https://gitlab.com/gitlab-com/www-gitlab-com/blob/0c3b195ee49d4283fcb8330f987b3c039d0f2cff/doc/slippers-blog-template.md#L22), which could be rewritten in an approachable way for the blog. ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@tywilliams` | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [x] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-03-23 19:15:42.945

How can we shift accessibility left? (June 3)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [x] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal When of the major shortcomings of accessibility in software development is that it is something tacked on at the end of the software development lifecycle. By shifting accessibility left, as in, thinking about building accessible software at the first stage of the SDLC, can be a game-changer for accessible software development. This blog post talks about what accessible software development looks like and how companies like GitLab – a product built for developers, by developers, to help developers build better software – can look like. ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@person` | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-03-22 22:27:21.144

Feature Unfiltered Post: How we tested a feature that affected GitLab

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> <!-- Add a link to the original Unfiltered blog post and @ mention the author --> How we tested a feature that affected (almost) all parts of GitLab https://about.gitlab.com/blog/2021/03/17/collaborating-on-a-cross-stage-feature/

2021-03-17 21:22:04.355

Blog post: YAML tips for CI/CD (July 6)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [x] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal Our first blog post about YAML tricks to speed up pipelines was so popular we're thinking of doing a follow-up post that explores different tips for developers on how to use YAML for CI/CD. @cbuchanan @dnsmichi do you have any ideas for team members who might know a lot about this topic that can write a blog post or can be interviewed? ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@person` | requestor | | `@person`| editor | | `@person` | approver (optional) | **Note @skassabian will be OOO this week so please assign to an alternative editor, such as @bmatturro or @mackanic** ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-03-17 17:43:05.179

Blog Post: How does open source relate to accessibility? (April 14)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [x] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal I'd like to explore how accessibility in software development relates to the open source community. Open source software is designed so everyone can contribute (and ideally, use) software, and accessibility in software development is about building and designing software to be inclusive to users of differing abilities. ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@person` | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-03-17 16:55:46.895

Brandon write a blog post

The goal is to represent our team by contributing more content. Possible topics on Brandon's mind include home office networking, custom keyboards, time management, writing documentation, etc.

2021-03-15 00:54:53.601

Update merging during broken `master` process

This issue is tracking progress on https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/77343. Post-merge checklist: - [x] Add a note to the Engineering Week in Review about the change. - [ ] Update our [code review](https://docs.gitlab.com/ee/development/code_review.html) process and links to the new process.

2021-03-09 17:50:33.641

Feature Unfiltered Post: Slippers design system

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> <!-- Add a link to the original Unfiltered blog post and @ mention the author --> https://about.gitlab.com/blog/2021/03/05/starting-from-the-start-slippers-design-system/ @smcguinness1 thanks for writing this blog post! Moving to the main blog.

2021-03-08 12:03:39.760

Feature Production-Grade Infrastructure and DevSecOps in Under Five Minutes on blog

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> Feature https://about.gitlab.com/blog/2021/02/24/production-grade-infra-devsecops-with-five-minute-production/ on main blog (FYI @skassabian)

2021-03-02 17:32:59.150

Draft: Iteration and code reviews - prt 3 (Mar 18)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [x] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal <!-- What do you want to blog about? Add your description here. If you are making an announcement, please open an `announcement` request issue in the Corporate Marketing project instead: https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements --> ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@person` | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate weekly milestone (e.g. `Fri: Mar. 5, 2021`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-03-02 17:19:52.503

Draft: How and why to use patch files for code review - prt 2 (Mar 15)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [x] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal <!-- What do you want to blog about? Add your description here. If you are making an announcement, please open an `announcement` request issue in the Corporate Marketing project instead: https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements --> ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@person` | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate weekly milestone (e.g. `Fri: Mar. 5, 2021`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-02-25 21:24:13.306

Git default branch name change blog post

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) The Inbound Marketing team prioritizes requests that drive results and meet our [goals of generating organic traffic and inquiries](https://about.gitlab.com/handbook/marketing/inbound-marketing/#goals). Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [ ] Drive traffic to our website - [ ] Convert traffic into leads - [ ] Thought leadership/share expertise - [ ] Build relationships with potential customers - [ ] Drive long-term results (please explain below in your proposal) - [x] Announcement - https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/3211 - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal <!-- What do you want to blog about? Add your description here. If you are making an announcement, please open an `announcement` request issue in the Corporate Marketing project instead: https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements --> ## Roles and Responsibilities | Person | Role | | ------ | ------ | | `@person` | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate weekly milestone (e.g. `Fri: Mar. 5, 2021`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (approve, backlog, deny) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-02-24 20:28:29.516

Reduce youtube iframe ad tracking network requests

This is an attempt to reduce network calls related to youtube iframes and adsense. <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-02-24 16:07:34.308

Adjust MTTP KPI to only count working days

Original Issue Link: https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12524 > Currently MTTP shows the time MRs take to reach production, measured across the entire month however this gives an inaccurate view because we intentionally don't deploy on weekends. >We should adjust https://app.periscopedata.com/app/gitlab/764878/MTTP-KPI-Dashboard?widget=10055732 to only count working days within a month to give a true measure of MTTP. >@davis_townsend do you think we could make this change?

2021-02-24 10:56:23.372

Feature "Redesigning our docs"

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> Feature https://about.gitlab.com/blog/2021/02/12/redesigning-our-docs/ on main blog.

2021-02-24 02:10:21.559

Update Ruby from 2.7 to 3.0 to use on build/test

We need to continuously keep updating the build/test environments of the repository itself. Relates to gitlab-org&5149 (initiative upgrading Ruby 2.7 to 3.0 in GitLab product) ### Prerequisites - [x] gitlab-org/gitlab-build-images!372 ### TODO - [x] !75872 - [x] !78849 - [x] !79022 - [x] !79284 - [x] !79480 - [x] !79484 - [x] !79491 - [x] [middleman/middleman#2460](https://github.com/middleman/middleman/pull/2460) - [x] [middleman/middleman#2462](https://github.com/middleman/middleman/pull/2462) - [x] !78850 ### cf. - Previous update: !73459

2021-02-22 20:21:11.146

Blog update: Add GitOps tag to relevant blog posts

I added a "gitops" tag to the blog handbook and now need to add the tag to past published, relevant blog posts: - https://about.gitlab.com/blog/2020/12/17/gitlab-for-cicd-agile-gitops-cloudnative/ - https://about.gitlab.com/blog/2020/07/14/gitops-next-big-thing-automation/ - https://about.gitlab.com/blog/2020/04/17/why-gitops-should-be-workflow-of-choice/ - https://about.gitlab.com/blog/2019/11/18/gitops-prt-3/ - https://about.gitlab.com/blog/2019/11/12/gitops-part-2/ - https://about.gitlab.com/blog/2019/11/04/gitlab-for-gitops-prt-1/ - https://about.gitlab.com/blog/2019/10/28/optimize-gitops-workflow/

2021-02-22 20:21:07.887

DE ENG: Marketo privacy subprocessors form

## This issue relates to https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/4263#note_513238603 URL: https://about.gitlab.com/privacy/subprocessors/#sign-up Steps to reproduce: Submit the form. Observed: Page reloads and sends to /pricing/ Expected: For says "thank you for submitting" with no page redirect.  <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-02-22 14:28:24.660

Feature Unfiltered post: Meet Pipeline Editor

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> Opening to consider featuring the following Unfiltered post: https://about.gitlab.com/blog/2021/02/22/pipeline-editor-overview/

2021-02-19 17:07:47.878

Handbook update: Add GitOps tag

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update I realized we should probably add a 'gitops' tag to the [Blog Handbook](https://about.gitlab.com/handbook/marketing/blog/#tags). I'm not sure how to do add a tag, could we work on this during our next 1:1 @rebecca? <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-02-09 07:06:09.978

Update bundler from 1.17.x to 2.1.4 on Ruby 2.7

Update bundler in `Gemfile.lock` from 1.17.x to 2.1.4 (the default version of Bundler bundled in Ruby 2.7.2) after !73459 and !74347.

2021-02-04 11:24:10.586

Feature Unfiltered post: This SRE attempted to roll out an HAProxy config change. You won't believe what happened next...

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> Review https://about.gitlab.com/blog/2021/01/14/this-sre-attempted-to-roll-out-an-haproxy-change/ for featuring on main blog.

2021-02-01 16:10:54.507

Blog post: Roundup of debugging stories - 2021-03-31

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Roundup of the best stories coming out of https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/4077. Inspired by https://boleary.dev/blog/2021-01-27-the-purse-caper-debugging-can-be-hard.html. ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2021-01-21 04:50:25.141

Create "What is cloud native continuous integration" web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing how to implement continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/cloud-native-continuous-integration #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [ ] Copy complete - [Draft](https://docs.google.com/document/d/1LbUehBdSfaelENMsxW6PriuVrt0xpoAg9iGIobOQPEk/edit?usp=sharing) - [ ] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-01-13 20:57:37.458

Improve findability of different release information about GitLab

Problem: We have too much information about releases in different places, and we might not have the SEO optimized. Example: I did a Google search for "GitLab Releases" and ended up on [this page](https://about.gitlab.com/releases/), which is a really poor customer experience. @timnoah and I compared what we saw when we did the same Google search, and had different results: My result:  His result: 

2021-01-13 04:08:20.730

Marketing site Event list sorting incorrect in some cases when event date is a range

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) `https://about.gitlab.com/events/` #### Briefly describe the bug The Event list sorting does not always work correctly for events where the date is a date range. In development, you need to be running the marketing site (not the handbook) to view the `/events` page. #### If possible, please specify how to reproduce the bug In `events.yml` define an event with `date:` as a range. `date: December 30 - January 4, 2021` or `date: December 30 - January 4, 2022` or `date: December 30 - December 31, 1999` In all cases GitLab::Homepage::Event `sort_date` will parse `December 30` as `December 30, 2021` (the current year). <!-- Please do not remove the items below, they are needed to automatically notify the relevant entities --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-01-11 17:38:04.016

Privacy policy page is bugged

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) `https://about.gitlab.com/privacy/` #### Briefly describe the bug Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned. `@sdaily reported. The page looks unstyled and has broken formatting.` #### If possible, please specify how to reproduce the bug `Visit the page` #### Please provide any relevant screenshots or screencasts How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/  #### What is your window size, browser, operating system, and versions Please use the following website to determine your browser specifications and provide a link developers can follow: What is my browser https://www.whatsmybrowser.org `https://www.whatsmybrowser.org/b/4YUV8SF` #### What computing device are you using? Please list the brand and model (Example: Samsung Galaxy S 10 Plus) `Macbook pro 15" 2019` #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? - [x] I tried a fresh incognito window & it had no impact. - [ ] The problem goes away when using an incognito window. - [ ] The problem only happens when certain cookies are set to a specific value (please specify below). #### Please list any browser plugins you have enabled Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing. `N/A` #### What is your geographic location Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies. `California. Other locations have reported this as well.` #### What type of network are you connected to? **Type** - [x] Wired - [ ] Wifi - [ ] Cellular (4G, 5G, etc) - [ ] Satellite - [ ] Other `Insert details here if applicable` **Location** - [x] Home - [ ] Workplace - [ ] Travel facility (hotel, airport, conference center, etc) - [ ] Public venue (restaurant, library, cafe, etc) - [ ] VPN - [ ] Other `Insert details here if applicable` **Hardware** - [x] I am behind a network security appliance such as a firewall - [ ] I am using a pi-hole or other hardware-based traffic blocker - [ ] Other `Insert details here if applicable` <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-01-08 12:32:53.821

Blog post: How to balance iteration with stability in engineering (Aug 17)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Based on discussion with ZJ re: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10021. Transcript: https://docs.google.com/document/d/1mduHzWXoaXo09Q6R4-oU9QPjR4AZwOzN22Nb4I7v6Kc/edit?usp=sharing ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2021-01-08 12:30:15.482

Blog post: Why you should be doing engineering demos

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Resources: * https://gitlab.com/gitlab-org/gitaly/-/blob/master/.gitlab/issue_templates/Demo.md * https://about.gitlab.com/handbook/engineering/development/demos.html * From interview with ZJ: https://docs.google.com/document/d/1TtqTcqXk27CQeGlPgn-nPGl127KiER8YVGyfV_QywDc/edit?usp=sharing Inspired by conversation from https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10021. ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2021-01-04 19:43:35.458

ENG: Investigate upgrading to Ruby 3 for the www repo

https://www.ruby-lang.org/en/news/2020/12/25/ruby-3-0-0-released/

2020-12-29 23:40:19.596

Update agile delivery topics/solutions pages

The Agile Delivery Solutions page is linked under Agile Delivery on the topics page. In this [MR](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/70991), we removed agile delivery from the monorepo, and it's showing as nested under the `topics` folder. But when you go to the [topics](https://about.gitlab.com/topics/) live page, it still links to about.gitlab.com/solutions/agile-delivery I'm not sure why it would still be linking to the solutions page after the changes we made. Thank you for taking another look at this!

2020-12-28 23:35:25.302

Create "What is a continuous integration server" web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing how to implement continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/continuous-integration-server #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [ ] Copy complete - [Draft](https://docs.google.com/document/d/1LbUehBdSfaelENMsxW6PriuVrt0xpoAg9iGIobOQPEk/edit?usp=sharing) - [ ] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->