diff --git "a/7764.csv" "b/7764.csv" deleted file mode 100644--- "a/7764.csv" +++ /dev/null @@ -1,10847 +0,0 @@ -issuekey,created,title,description,storypoints -29688087,2020-01-17 00:50:48.022,Update templates for website merge requests,"Relates to &232 and #6109 - -Goals: - -* Automatically add relevant details if possible (labels, pings, etc) -* Improve clarity of issues -* Reduce grooming time -* Ensure that all issues contain the [The Five W's](https://en.wikipedia.org/wiki/Five_Ws) : who, what, when, where, why, and how. -* Request [MoSCoW](https://en.wikipedia.org/wiki/MoSCoW_method) information when possible. - -Implementation Details: - -- [ ] Update the default MR template. -- [ ] Explore the use of checklists in MR templates.",1 -29682716,2020-01-16 19:21:38.595,Make sure that we Capture Advanced Search in our feature and feature comparison pages,"This was raised in the PM & Engineering meeting agenda. -https://docs.google.com/document/d/1D9rW65d4w0UwSRw_0jJMRk5wAxdhAd4ynrHLbMMwIjo/edit#bookmark=id.nif5uubi5a0 - -> It is under Advanced Global Search https://about.gitlab.com/features/ - -> Sid: We need it to be added to the feature comparison page, let’s check if there are other items missing. - -> Sid: Which plan is it in? Can't find on https://about.gitlab.com/pricing/gitlab-com/feature-comparison/ => Add here. - -### Tasks - -- [ ] Add elastic search to the feature comparison page -- [ ] Check if there is anything else that is missing from the feature comparison page",1 -29644971,2020-01-15 21:17:03.379,Propose new IA for Brand and Digital Handbook,"## Goals -Propose new IA for Brand and Digital Handbook content, including existing content and foreseeable content updates. May require migrating Brand and Digital content currently spread across other team pages to a new, centralized [Brand and Digital Handbook location](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/). - -* Some content will apply to entire Brand and Digital team, such as shared labels, whereas other content will be specific to Brand or Design -* Embrace Handbook IA conventions and only stray with strategic intent -* Solve for integration with other handbook sections and pages (i.e. cross-links) -* Make it easy for users looking for content in old locations to find that content in its new location (i.e. cross-links) -* Optimize IA and content for stakeholders AND our team -* Avoid duplicate content wherever possible -* Announce change via appropriate channels - -## Proposed tasks -* [x] Team - Identify existing Brand and Digital content -* [x] Shane & TBD Partner - Facilitate collaborative IA exercise in Mural or Figma, using digital post-its to represent existing and foreseeable content simply, and then organizing that content into a site map with arrows representing cross-links. -* [x] @skarpeles - create a spreadsheet of which topics each person should handle -* [x] Team review -* [x] Implement in follow-on Issues/MRs - -## How to contribute - -If you have additional ideas or comments about what's mentioned in this description, please add them to this issue! -* Start a new thread for your idea/topic -* Keep comments relevant to the thread they're in -* As these discussions evolve, the brand team will review and add approved suggestions to the description and mark the thread with a :white_check_mark: - -## Mural Board - -Link to Mural board of visual page hierarchy: https://app.mural.co/t/gitlab2474/m/gitlab2474/1579534915496/530305c8bd3e3e1831f08ad402b46926283f805c - -## Spreadsheet of Pages -Spreadsheet of pages to complete, and who is responsible for each: https://docs.google.com/spreadsheets/d/1_QCkndT-6mR0wfuGxiLrFeWHG5RyTN6rYdR3cJHOEsw/edit#gid=0 - -## Google Doc of Content Migration -https://docs.google.com/document/d/1Tt9kODKAcecCvXsc6msu5j4yr448c0S8I3Mgffp4NNE/edit - -@luke @brandon_lyon @skarpeles @monica_galletto @vicbell ",1 -29494181,2020-01-10 19:20:50.351,Cache `node_modules` for www-gitlab-com pipelines,"# UPDATE NOTE: This MR will not be implemented. After looking at the initial numbers, the amount of additional time taken by the additional cache push/pull (~18500 files in `node_modules`, about ~8 seconds to push and ~8 seconds to pull) would eat up most of the gains caused by eliminating the `yarn install` (which takes ~20 seconds). This seems to indicate that the Yarn/NPM network download time is normally very fast (probably due to CDN/etc, and yarn optimizations), almost as fast as downloading and unzipping the files from disk. https://gitlab.com/gitlab-com/www-gitlab-com/issues/6358 still offers opportunities to do this caching via docker, though. - -We currently don't put the downloaded node_modules in the cache, like we do for the bundler vendor directory containing gems. This would probably be an easy and quick win to save 20-30 seconds, and also reduce the possibility of flaky builds (if the download happens to fail for network/etc issues - I'm not sure if we are using a local pass-through caching proxy or not) - -POTENTIAL IMPROVEMENT: Small, probably 20-30 seconds for jobs which need this. - -PROS: -* Easy to implement, low risk, same as we are already doing for gems",1 -29437529,2020-01-09 10:26:51.545,Disable all remaining unnecessary jobs in pipeline when merging to master,"Similar to https://gitlab.com/gitlab-com/www-gitlab-com/issues/6161 we should disable all remaining quality and spec related jobs when running a pipeline against master, because they are guaranteed to have already run as part of a Merge Request. - -The only jobs to run for a merge to master should be build and deploy.",1 -29358963,2020-01-07 08:35:44.768,Disable unnecessary jobs in pipeline when merging to master,"As discussed in https://gitlab.com/gitlab-com/www-gitlab-com/issues/5983#note_267627509 we currently run the code_quality and dependency_scanning jobs for both MRs and merges to master. - -Since no direct commits to master is allowed and MRs can't be merged until the pipeline passes it is sufficient to only run these two jobs on the MR pipeline. - -This will [improve pipeline speed](https://app.periscopedata.com/app/gitlab/561277) by eliminating jobs on master which only need to run once for each commit, and should have already been run as part of a merge request. - -See also more similar follow-on work in https://gitlab.com/gitlab-com/www-gitlab-com/issues/6190",1 -29336665,2020-01-06 15:52:03.947,Propose an A/B Testing Framework for about.gitlab.com (Spike),"## Goals -Propose an A/B testing framework for testing conversion MVCs on about.gitlab.com so we can iterate, learn and increase conversions faster - and with more apples to apples data than comparing time periods. - -## Requirements -* **Collaborate with appropriate stakeholders on MVC A/B test solution** - -## Proposed Tasks -* Collaborate to identify potential requirements -* Set MVC requirements -* Collaborate on brainstorming technology solutions (consider build vs. buy) -* Propose a solution - -## Follow-on Issue -Create an A/B testing framework for testing conversion MVCs on about.gitlab.com so we can iterate, learn and increase conversions faster - and with more apples to apples data than comparing time periods. -* Co-design, develop and test solution on conversion MVC - -@brandon_lyon @laurenbarker -@shanerice @jjcordz -@s_awezec @jackib",3 -29315321,2020-01-06 05:36:36.472,Demo Landing Page Conversion MVC," -## Goals -Increase Demo landing page conversion rate on about.gitlab.com with collaborative, data-driven MVC. - -## 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 -Design KR: Increase Demo landing page conversion rate by 50%. - -Current State Benchmark: Conversion rate is 9.5% (23,821 unique pageviews QTD; 2,272 unique submit events) - - -## Proposed Tasks -* [ ] WIP: Conversion audit & recommendations (Shane) -* [x] KPI's -* [ ] Planning -* [ ] MVC Requirements -* [x] Iterative Co-Design -* [x] Build the page @skarpeles -* [x] Test -* [ ] If success: Merge, monitor and report -* [ ] Create follow-on issues, as needed. - -@brandon_lyon @skarpeles -@shanerice @jjcordz - -",4 -29310187,2020-01-05 23:28:12.894,Home Page Conversion MVC," -## Goals -Increase Home page conversion rate on about.gitlab.com with collaborative, data-driven MVC. - -## Requirements - -* **Co-design an informed 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. -* **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 - - -## Proposed Tasks -* [x] @sbouchard1 Conversion audit & recommendations -* [ ] @shanerice KPI's -* [ ] Planning -* [ ] MVC Requirements -* [ ] Iterative Co-Design -* [ ] Development @skarpeles -* [ ] Test -* [ ] If success: Merge, monitor and report -* [ ] Create follow-on issues, as needed. - -@brandon_lyon @skarpeles -@shanerice @jjcordz - -",4 -29244082,2020-01-02 18:01:24.330,GitHub and Azure DevOps links should go to sections on comparison pages,"### Acceptance Criteria: - -The logos on https://about.gitlab.com/devops-tools/ should link to related tabs on the resulting page. - -- [x] Clicking on the ""Azure devops"" logo under the ""create"" column should link to `https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab.html#create` -- [x] URL hashes should be manually navigable, ie typing in the URL manually links to that spot. - -For now this will only apply to two rows: GitHub and Azure. - -### Problem Statement: - -``` -via @tbarr - -The GitHub and Azure DevOps logos link to this page: https://about.gitlab.com/devops-tools/github-vs-gitlab.html or this page: https://about.gitlab.com/devops-tools/azure-devops-vs-gitlab.html - -The logos in the Comparison chart should deep-link into the section that is relevant. For example, if you click on the GitHub logo under PACKAGE, it should take you to: https://about.gitlab.com/devops-tools/github-vs-gitlab.html#package - -There also seems to be a problem that even if you paste that link, it doesn't take you to package until you click. - -cc @mskumar -```",2 -28955401,2019-12-20 15:55:24.511,Add CTA to Global Website Nav,"## Goals -Increase online conversions by adding a call-to-action (CTA) element to the about.gitlab.com global nav. - -## Requirements - -Must have -* **Stand out CTA element** - Next to the GitLab logo, the CTA is a stand out element on the global nav. -* **Co-design an informed 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. -* **Stand out CTA element** - Pick CTA to try (will impact KPIs) -* **Set KPIs** - Set MVC KPIs in order to test the positive and negative impacts of your change - especially marketing KPIs. For example, if changing other elements is required to fit the new CTA, how might that negatively impact other experiences and metrics? -* **Validate performance** If testing proves the MVC is positive change, share demonstrable data, merge, and implement health monitoring and reporting. -* **Share change events** - Document and share change events and results with relevant GitLab teams. - -Should have -* **Ability to opt-out of CTA** - For example, an important content funnel where the primary goal is the content download. - -## Tasks -* [x] @shanerice KPIs (add 5,600 `/free-trial/` pageviews per month) -* [x] WIP: Co-design -* [x] Dev -* [ ] @shanerice @brandon_lyon Test - - -@s_awezec @matejlatin -@brandon_lyon @shanerice @jjcordz @skarpeles",4 -28649592,2019-12-14 01:18:33.903,Add tests and validation logic to greenhouse integration,"The Greenhouse integration code is brittle. It has broken all builds on `www-gitlab-com`- see slack thread below. - -Per @stanhu 's suggestion, it needs to be improved and tests need to be added. In particular: https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/helpers/jobs_helpers.rb - -cc @brandon_lyon - -### Slack thread - -
- Conversation on slack - -From this thread in slack: https://gitlab.slack.com/archives/CETG54GQ0/p1576276480021000 - -Thread -is-this-known - - -Thread -is-this-known - - -Brandon Lyon 1 hour ago -Scrolling through the error, it seems to happen around `block in show_childs' on public/jobs/apply/index. I'll take a peek at the code and see if I notice anything unusual to do with child elements. (edited) - - -Brandon Lyon 1 hour ago -Looks related to the partial builds process, at least that's the test that's failing ( build_proxy_resource ) - - -Brandon Lyon 1 hour ago -Yeah something to do with the data being pulled from greenhouse possibly. The job apply template appears to source its data through jobs_listing.rb which sources the data from the greenhouse_io gem - - -Brandon Lyon 1 hour ago -I'm trying to run the test locally to see if it fails or passes from my machine -:thank-you: -1 - - - -Brendan 1 hour ago -A property to toggle wouldn’t be super hard. I can take a swing at that -:dancingpenguin: -1 - - - -joshua 1 hour ago -We can’t break our jobs site though - - -Brandon Lyon 1 hour ago -Yeah the test fails on my local machine in the same spot - - -Brendan 1 hour ago -Is the jobs site working? - - -Brandon Lyon 1 hour ago -On another tangent, the job listing library hasn't been updated in 4 months so that's probably not the file responsible. The job page template hasn't been updated in weeks so I don't think that's it either. - - -Brandon Lyon 1 hour ago -It looks like there's a difference between jobs appearing in greenhouse and jobs appearing on-site at the moment. I'm not sure what the cause is for the difference. - - -William 1 hour ago -Local build also fails for me in the same spot - - - -Brandon Lyon 1 hour ago -I've exhausted my investigatory skills and knowledge of the site. It's probably time to call in more knowledgeable people. The failing line numbers in question appear to be around one of these two spots but I'm not sure which: -https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/jobs/apply/template.html.haml#L37 -https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/jobs/apply/template.html.haml#L48 (edited) - - -Brandon Lyon 1 hour ago -Actually I do have a theory I can test first. - - -William 1 hour ago -I’m looking at the same 2 lines… looks like Tony from ROIDNA built the template https://gitlab.com/gitlab-com/www-gitlab-com/commit/601c8ccbf90c813adcc047270ebbef32ca832f1c -@stanhu @rspeicher any thoughts on troubleshooting the show_childs method? - -GitLabGitLab -Resolve ""Jobs Page Update Supporting Subcategory Listings"" (601c8ccb) · Commits · GitLab.com / www-gitlab-com -Source for https://about.gitlab.com/ - - -Brandon Lyon 43 minutes ago -My theory didn't pan out - - -stanhu 42 minutes ago -sounds like res.first is nil for some reason. Let's see if we can run this locally - - -Brandon Lyon 41 minutes ago -code name sounds like first result nil? - - -Darren Murph:car: 38 minutes ago -(Thanks all who are working on this by the way, much appreciated :collaboration-value: ) -:collaboration-value: -1 - - - -Brandon Lyon 30 minutes ago -The show_childs method has the following options -def show_childs(data, item, arr, show_list, depth, dept_id, result, teams) - (edited) - - -stanhu 29 minutes ago -I think I have a fix. I don't completely understand the data, but we're just getting a single blank array under the engineering department job listing for one of the listings (edited) -:yay: -2 -:bulb: -1 -:star2: -1 - - - -Brandon Lyon 27 minutes ago -I suspected the data but wasn't sure how to test it. Although in retrospect I probably could have looked at greenhouses documentation to figure out their API and tried postman. (edited) - - -stanhu 27 minutes ago -whatever child ID 4034708002 is - - -Darren Murph:car: 27 minutes ago -When it’s all said and done, sounds like we’ll chalk it up to excessive greenhouse gas emissions mucking things up -:lol: -1 - - - -Brandon Lyon 26 minutes ago -Out of curiosity would the fix be in job_helpers.rb? - - -William 26 minutes ago -I suspect that there’s either a bug in greenhouse, or a job was posted where there’s an expected/required field and it was omitted. (edited) -:100: -1 - - - -Brandon Lyon 25 minutes ago -Interesting, going to the URL manually says that job is not found -https://boards.greenhouse.io/gitlab/jobs/4034708002 - - -stanhu 22 minutes ago -not sure if that's an actual job ID - - -stanhu 22 minutes ago -Ironically, it's barfing on child_id 4034708002 -for https://boards.greenhouse.io/gitlab/jobs/4465197002 -boards.greenhouse.io -Backend Engineer, Static Site Editor -Remote -:rolling_on_the_floor_laughing: -2 - - - -Brandon Lyon 21 minutes ago -ah gotcha - - -joshua 20 minutes ago -It knows - - -stanhu 19 minutes ago -pushing up a merge request now. This code needs serious improvements and testing :slightly_smiling_face: - - -stanhu 19 minutes ago -I think this is Greenhouse's way of saying we need to hire someone to maintain this page - - -Brandon Lyon 17 minutes ago -I pinged peopleops to see if they have any ideas because the greenhouse listing does look a bit different from some others - - -stanhu 16 minutes ago -https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/36883/diffs -GitLabGitLab -Fix broken Greenhouse job generation (!36883) · Merge Requests · GitLab.com / www-gitlab-com -Child ID 4034708002 did not exist, and the code did not handle this properly. -Author -Stan Hu -Assignee -Stan Hu -:thank-you: -2 - - - -William 8 minutes ago -Looks like it choked on rubocop - I committed the suggested fix - -
",2 -28639095,2019-12-13 17:50:04.691,Remove use of alt-link and ensure homepage displays appropriate category links,"From [scaling agenda](https://docs.google.com/document/d/1nMJzrDfG7C14WP5v7P226oPFuXkwqIk7bdIT8ai0DNU/edit#bookmark=id.yqcc4osgu9vm): - - -> KENNY EricB Sid: Can we ensure that every shipped feature in the table on https://about.gitlab.com/ links to the docs? Usability testing linked to https://about.gitlab.com/direction/verify/usability_testing/ so please test others. -> EricB: I’ll take this one for the team and get a MR out today -> Here’s the MR: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/35049 -> EricB: I’ve asked Todd B to merge as it changes our homepage -> Reverted in https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/36826 -> Kenny: We need to adjust the logic for how the link is selected on the homepage to select Product link first, then docs, then vision based on availability and remove the use of the alt-link. -> Also give error if it is no longer planned but there is no docs link. -> Kenny: Thumbs up, I’ll add the lint. - -## Tasks -* [x] Banish Alt_Link - https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/36915 -* [x] Add CI Check on categories.yml file - https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/37335",1 -28332457,2019-12-11 22:01:26.769,Update Periscope handbook page with Data Team issue template usage,This issue tracks the work done to the handbook for the related issues,1 -28287210,2019-12-10 20:40:43.305,Increase width of org chart,"### Problem to solve - -As GitLab grows more layers of management, our fixed width org chart page is cutting off certain individuals. - -### Further details - -![image](/uploads/4b07470c82bd298959e4258d43a0d74d/image.png) - -### Proposal - -Increase the width of the org chart page or allow it be side scrolled.",1 -28276378,2019-12-10 15:24:45.661,Add tweet button when highlighting text in the handbook,"### Problem to solve - -In order to increase reach of the GitLab handbook, we should make it easy to tweet out highlighted text. - -### Proposal - -When a user highlights text, let's pop up a twitter button. When a user clicks that button it takes them to a separate page to tweet out the quote with a link back to the handbook page where the text was. [Medium](https://medium.com/darklang/how-dark-deploys-code-in-50ms-771c6dd60671) has a similar feature. - -![image](/uploads/2bc4afa929f2ff19479ad66ccd1cc1a3/image.png) - -### Implementation details - -The share link to use is, `https://twitter.com/intent/tweet?url=$URL&text=$text&hashtags=$tags`, where: -1. `$url` is a URI encoded string of the handbook page the user is currently on -1. `$text` is a URI encoded string of the text the user has selected -1. `$tags` is a comma separated list of the hashtags to add to the tweet. Propose defaulting to `gitlab,handbook`",3 -28151002,2019-12-09 20:48:59.595,"Create handbook page which documents all steps in the existing handbook build, test, and deploy process","### Problem to solve - -It is hard to understand which steps are happening in the build, test, and deploy process of the handbook. - -### Proposal - -Let's document the steps as a handbook page.",2 -27056389,2019-11-14 15:34:05.000,Remove the feature flag for upstream date updates,Remove the feature flag for epic upstream dates update from https://gitlab.com/gitlab-org/gitlab/blob/master/ee/app/services/epics/update_dates_service.rb#L23,1 -29981332,2019-11-07 16:30:03.630,Investigate open source static site editors for use with the GitLab handbook,"### Problem to solve - -Editing the handbook for non-tech users is harder than it needs to be. Static site editors provide more WYSIWYG editing experiences. - -### Proposal - -TBD",1 -26539898,2019-10-31 21:06:56.308,AUP Layout change and minor update,"### Description - -Currently section 3 of the [Gitlab Website Terms of Service](https://about.gitlab.com/terms/#gitlab_com) is not formatted in a way that is easy to read and does not include the term `Spam`. - -Checklist when modifying an existing page: - -- [ ] What is the goal of changing the page? -- [ ] What metrics are we trying to affect? -- [ ] How will we decide if the change was successful or not? -- [ ] Would we revert the changes if we decided that it was not a success? -- [ ] Make sure events are reflected in Google Analytics/Marketo if the page is changed -- [ ] Make sure redirection is done if we change the page so email newsletters do not contain dead link - -### Proposal -Update the AUP to make it easier to read and include the term `Spam`. - -Proposed change/format below: - -### Acceptable Use of Your Account and the Website - -By accepting this Agreement you agree not to use, encourage, promote, or facilitate others to use the Website or your account in a way that is harmful or disruptive to others (""Acceptable Use""). - -Examples of harmful or disruptive use include, but are not limited to: -* engaging in illegal or fraudulent activities. -* infringing upon others' intellectual property rights. -* distributing harmful or offensive content that is defamatory, obscene, abusive, an invasion of privacy or harassing. -* the distribution of malicious/commercial Spam -* violating the security or integrity of any computer, network or communications system. -* taxing Gitlab resources with activities such as cryptocurrency mining. -* conducting [external scans](https://about.gitlab.com/security/#external-testing) of any kind against GitLab.com infrastructure without written permission from GitLab. - -Furthermore, account name squatting is prohibited by GitLab. Account names on GitLab are administered to users on a first-come, first-serve basis. Accordingly, account names cannot be held or remain inactive for future use. Any attempts to purchase, solicit, or sell account names in any form may result in the permanent suspension of the account. GitLab reserves the right to remove, rename, or close inactive accounts at its discretion. - -If you believe that an account is in violation of these terms, please visit our [Abuse Reports](https://docs.gitlab.com/ee/user/abuse_reports.html) page for reporting instructions. -### Links / references - -https://about.gitlab.com/terms/#gitlab_com - -cc @gl-website -cc @jhurewitz @cciresi",1 -26165001,2019-10-21 15:24:44.282,How to update CTAs in existing blog posts,"Gang, we've promoted Brooklyn and London and now need to push SF but we have a whole lot of blog posts with CTAs to finished events. It would be nice to see if we could find a way to automatically update the CTAs to reflect current priorities. @gl-website @brandon_lyon cc @erica",2 -26089422,2019-10-18 16:21:26.043,Wide tables are causing page display issues for the about.gitlab.com on mobile," - - - - -### What is/are the relevant URLs or emails? - -Any page with a table wider than a mobile device, e.g.: - -* https://about.gitlab.com/handbook/engineering/security/vulnerability_management/ -* https://about.gitlab.com/handbook/product/product-management/#product-management-career-development-framework -* https://about.gitlab.com/devops-tools/azure_devops/azure-devops-overview/ - -### Briefly describe the bug - -Pages with wide tables cause the responsive mobile view to be wider than the header, and thus scroll horizontally - -### What are the steps to reproduce the bug - -* Use a on a narrow mobile device, e.g. iPhone X. -* Go to a page which has a wide table. E.g. one of URLs above - -### What is the observed behavior? Be specific. - -* Zoom out/scroll to the right, see grey area -* Scroll down to table, and see that it is the cause of the too-wide behavior - -### What is the expected behavior? Be specific. - -* Table is sized to device width, and page is not scrollable horizontally. - -### Please provide any relevant screenshots - -![mobile_rendering](/uploads/2442980a31d45f72e0e0019c71ab7959/mobile_rendering.png) - -For reference - here is what Desktop looks like: - -![Screen_Shot_2019-10-18_at_12.31.10_PM](/uploads/1a3b73f049fa857af705d3abff4e4891/Screen_Shot_2019-10-18_at_12.31.10_PM.png) - -### What is your window size, browser, operating system, and versions - -Safari 13, iOS 13.1 414px by 896px - -Also tested on an Android device - -### What device are you using - -* iPhone 11 pro max -* iPhone X in Chrome developer tools responsive emulator",2 -25706100,2019-10-08 01:25:51.758,Add Periscope Charts to Engineering Productivity PIs,"We should add Periscope charts to the Engineering Productivity team KPIs - -The following was added with https://gitlab.com/gitlab-com/www-gitlab-com/commit/f192317d7669dd70fc9b70b4d8219245af4472b7 - -``` -periscope_data: - chart: 6114177 - dashboard: 463858 - embed: v2 -```",1 -25127034,2019-09-23 17:54:15.208,Add External Pipeline for Marketing Site,"### Problem to solve - -Local development of this repo is slow and cumbersome. Production build times for Middleman are also slow. - -### Proposal - -Let's move frontend asset builds out of Middleman and into an `external_pipeline`. This will allow Middleman to do what it does best - compile the HTML. - -For our `external_pipeline`, lets have it complete the following tasks: -- preprocess scss -- minify css -- minify js -- bundle js -- sourcemaps -- copy web fonts, icons -- image resizing and processing* (depending on speed) -- browser reload (local dev) - (local dev) - -### What does success look like, and how can we measure that? - -Faster local development for developers. - -Faster deployment times. Reduced publishing time for blog, handbook, and marketing webpages. - -### Iterative Approach -1. Process Stylsheets with Webpack first, introducing build to system -1. Monitor and fix edgecases -1. Add javascript bundling to Webpack second -1. Monitor and fix egecases -1. Migrate rollup to Webpack for vue component bundles -1. Monitor and fix edgecases -1. Add image process to Webpack - - -cc @gl-website",8 -24977120,2019-09-19 07:51:58.581,Add a Collapse All / Expand all button to the company org chart,"Add a button at the top of the org chart that allows the user to toggle between collapsing/expanding all the nodes by clicking on the button. - -Default org chart state should be to be fully expanded. - -Button text: -- If all nodes are expanded: Collapse all -- If any node is collapsed: Expand all - -Reference: https://gitlab.slack.com/archives/C3MAZRM8W/p1568416800345400?thread_ts=1568366463.339100&cid=C3MAZRM8W",1 -23937187,2019-08-19 20:53:10.463,Finish aligning PIs with Job Families (Infrastructure::Delivery),"While working on #5041, I noticed we don't seem to have specific specialties defines for Backend Engineer, Delivery and Engineering Manager, Delivery. - -We need to sort out said roles and link their appropriate PIs.",2 -23359700,2019-07-31 18:42:37.555,FY20-Q3 Infrastructure IACV OKR: Raise GitLab.com Availability from 96.64% to a consistent 99.95% => 0%,"* [ ] Key result: MTTD, MTTR, MTBF, and MTTP PIs to be at OK health and a minimum of level 2 maturity `=> 0%, comment` -* [ ] Key result: 100% of services have fully defined and observable service levels, error budgets, and capacity planning `=> 0%, comment` -* [ ] Key result: 50% of services running on Kubernetes `=> 0%, comment`",8 -23265646,2019-07-29 13:56:19.921,Add Plan team section to Product,"# Why - -* There is a Plan engineering team section, but not holistic plan team section to collaborate on cross-functional processes. - -# What - -* Add page and create first pass content.",1 -23161389,2019-07-25 14:14:08.763,What is accessibility testing and why is no one doing it?," - -### Proposal - -Assigned to @skassabian as this was the jumping off point for her survey on accessibility. I'm on unclear on time frame but put June 2020 as a placeholder. - -### Checklist - -- [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - - [ ] 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)",3 -21879252,2019-06-13 14:25:16.421,Encode devops stages parent/child structure in either categories.yml or stages.yml,"With the process of building our dashboards and label migration. We should store the single source of truth on devops stage parent-child structure in the handbook project. - -Context: - -* https://gitlab.com/gitlab-org/quality/triage-ops/issues/172#mapping -* https://quality-dashboard.gitlap.com/groups/gitlab-org/stages - -Comments from the dev metrics meeting. - -> Jason: Idea is to encode this in data in the handbook. => Lyle: isn’t it categories.yml and stages.yml. => Jason: There is no label field. We should extend it.",3 -77860388,2019-04-18 17:15:53.908,Quality Engineering KPI - Build bug first triage (with stage/group and severity) metric into Periscope,"### Overview - -Measure our speed to triage new issues. We currently have ~400 new issues every week in CE/EE. We need to go through all of them and identify valid issues and high severity bugs. - -## Measurement definition - -The duration from issue creation to partial triage time for all gitlab-org/quality/team-tasks~2278648 issues in `gitlab-org/gitlab`. This will be visualized as a Time Series chart showing the average duration by month. - -Next steps: -- [x] Define an automated mechanism to detect first triage of a GitLab team member. - starting with description in https://gitlab.com/gitlab-org/quality/team-tasks/issues/136#note_211116724 -- [ ] Define measure mechanism and establish threshold. -- [ ] Fan-out triaging to all of engineering. First triage is mostly on the Quality Dept Eng Prod team. -- [ ] Expand this into first scheduled milestone. - -We need to build this in Periscope and respect/update https://about.gitlab.com/handbook/engineering/quality/performance-indicators/. - -Once finalized, the chart should go into https://app.periscopedata.com/app/gitlab/516343/Quality-KPIs.",3 -20078014,2019-04-15 16:21:48.461,Remove Stage Dependency on Competitor Field,"@atkach1 Can you take this on? - -Please remove the field dependency on the Competitor object. - -Right now, Competitor is controlled by the Stage field, when it should not. However, we do want a validation rule in place for any deal in Stage 2 or higher that requires a Competitor, except for Web Portal deals.",1 -20053287,2019-04-15 07:24:30.956,Geo blog post: what we've learned about FDW,"We could write a nice technical blog post about how we use FDW, how we set it up, which challenges we encountered, and what we did to improve performance. Also writing about our ActiveRecord model could be interesting. - -But since we seem to be moving away from it, it might be better to just list the lessons we've learned from it. - -cc `@geo-team`",3 -19272292,2019-03-19 23:49:48.496,update python style guide,related to issue: https://gitlab.com/gitlab-data/analytics/issues/1003,1 -19089877,2019-03-13 23:24:20.905,"Geo: Write blog post ""How to install GitLab 11.9 with Geo on AWS"" tutorial","- [ ] Follow up https://gitlab.com/gitlab-org/gitlab-ee/issues/7360#note_150168367: - ->>> -I had an idea. Do we need some kind of initiative like DigitalOcean seems to have for writing tutorial-style blog posts? Similar to https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-gitlab-on-ubuntu-18-04. - -`How to install GitLab 11.9 with Geo on AWS` sounds attractive. - -We can only do so much to make our docs apply generally *and* add cloud-provider-specific exceptions *and* keep them up-to-date. I'd like to avoid making our general docs more confusing with too much specificity. But without specificity, the sysadmin needs to learn how the whole system works. - -Blog posts like this acknowledge this problem. They are hyper-specific. They go out-of-date, but the type of people installing GitLab should understand that, and should be able to adapt these tutorials to their purposes until a better one comes along that bumps the old one down the Google results. - -Would a blog post resolve this issue? ->>>",3 -17658350,2019-01-25 10:57:29.376,Designing with a vision in mind," - -### Proposal - -Write about how we set our vision for the things we design, how it adapts through time but most importantly, how it guides us towards better solutions. - -### Checklist - -- [ ] Due date and milestone added for the desired publish date -- [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#time-sensitive-posts-official-announcements-company-updates-breaking-changes-and-news) - - [ ] Added ~""priority"" label - - [ ] Mentioned `@rebecca` to give her a heads up ASAP",2 -17281234,2019-01-11 21:12:16.144,"""GitLab workflow"" link at the ""Engineering workflow"" page seems to be dead","The [engineering workflow page](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/handbook/engineering/workflow/index.html.md) refers to the ""GitLab workflow"" (at [this line](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/handbook/engineering/workflow/index.html.md#L103) and more). - -But the corresponding link `/handbook/communication/#gitlab-workflow` is dead - no such anchor at the [""Communication""](https://about.gitlab.com/handbook/communication/) page of the handbook. - -What was meant by this link? Should this reference be removed or updated with anything else?",1 -16199303,2018-11-28 22:35:11.373,Add additional categories to the Monitor Comparison,Add additional categories to the Monitor Comparison,10 -16198959,2018-11-28 22:01:47.714,IBM Monitor Competitor Page,IBM APM Monitor Competitor Page,10 -16165368,2018-11-27 23:58:17.118,Broadcom (CA) APM Monitor Competitor Page,Broadcom (CA) APM Competitor Page,10 -16163761,2018-11-27 21:22:47.098,Datadog Monitor Competitor Page,Datadog Monitor Competitor Page,10 -14983229,2018-10-16 09:11:51.873,Geo blog post: Repository verification,"Write an article explaining the thinking process behind the Repository Verification feature. - -Ideally should cover: -- Problem it solves -- Reasoning and thinking process that leads us to the decision to make it the way it is -- Evolution since the first iteration -- Performance vs Accuracy -- Visual representation of important parts of the algorithm",5 -14707232,2018-10-05 02:27:48.729,Manually select related posts,"Add a setting to the blog front matter so that related posts can be chosen manually. - -The setting should be `related:` and take a comma-separated list of one, two, or three relative URLs. - -Depends on https://gitlab.com/gitlab-com/www-gitlab-com/issues/2450 - -cc @rebecca",2 -14707104,2018-10-05 02:13:27.278,Show title on previous and next posts,"At the bottom of a blog post are ""next"" and ""previous"" links: - -![image](/uploads/a5cd29478d3db1c8e397628c51147b50/image.png) - -Update so that they include the title of the blog post. - -## Todo -- [ ] Make a mockup of what the previous/next button should look like -- [ ] Implement the logic to add the title -- [ ] Build the CSS to make the buttons match the mockup - -cc @rebecca",2 -14621265,2018-10-02 07:51:56.648,Add an email signature example to the tools-and-tips page,"### Description - -In the `tools-and-tips` section I want to add an email signature example to make it easier for the reader to setup a GitLab email signature. - -Checklist when modifying an existing page: - -- [ ] What is the goal of changing the page? -**To make it easier for the reader to setup a GitLab email signature.** -- [ ] Would we revert the changes if we decided that it was not a success? -**Yes** - -### Proposal -![Screenshot_2018-10-02_at_09.47.44](/uploads/a85d888730506c258bb248bda5d74643/Screenshot_2018-10-02_at_09.47.44.png) - -### Links / references -https://about.gitlab.com/handbook/tools-and-tips/#email-signature",1 -14620587,2018-10-02 07:25:33.152,Fix spelling errors on tools-and-tips page,"### Description - -I found some spelling errors while reading throigh the `tools-and-tips` section of the handbook. - -Checklist when modifying an existing page: - -- [ ] What is the goal of changing the page? -**To fix spelling errors** -- [ ] How will we decide if the change was successful or not? -**Check for spelling errors** -- [ ] Would we revert the changes if we decided that it was not a success? -**Yes** - -### Proposal -stereoids -> steroids - -manpulations -> manipulations - -dirctory -> directory - -### Links / references -https://about.gitlab.com/handbook/tools-and-tips/",1 -5988498,2017-07-05 23:48:49.195,Borken image of DT on Team Page due to filename extension,Saved as .jpg but entered as .png. doh!,1 -5444968,2017-05-18 23:53:38.973,GitLab Issue,"Hello World! :wave: - -This is my issue's description, written in markdown (GitLab Flavored Markdown). - -### This is an `

` - -> _Let's quote someone here_ - -Add a task list: - -- [ ] Task 1 -- [ ] Task 2 - -Mention merge requests (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1784) and issues (https://gitlab.com/gitlab-org/gitlab-ee/issues/2101) and hover over them to see their titles. - -Invite users to collaborate with `@mentions`: @marcia ",3 -2589860,2016-06-23 14:36:37.432,Communicate between Programmers.,"* For medium sized issues there will always be a frontend or backend. -* For bigger issues there should be a whole team. UX, Frontend, Backend, Product -* If you are starting on a new feature that is sizable you should expect at least a FE and BE programmer. If for some reason there isn’t than make sure you ask why there isn’t. If it is a bigger (direction/large customer) issue then expect a whole team. -* Make a call with your team when you start. -* Communicate throughout the whole process. So that when the MR comes in there will be less questions in the end. Questions can be brought up in the beginning and during the process.",1 -2340172,2016-06-01 16:13:57.663,Add Apply button to description on job,"Currently to apply to a job you can't do it to a description. Add the apply button to the description. - -cc @JobV @markpundsack @iamphill @annabeldunstone ",1 -1469501,2016-04-11 08:57:01.694,404 error on GitLab Features PDF,"Twitter: http://www.twitter.com/ccellar/status/718398387238924289 - -Clicking on the `Download the feature comparison table as a PDF` link on the bottom of the about.gitlab.com/features page returns a 404 error",1 -1227378,2016-02-18 01:47:53.837,Feature to Feature Comparison to BitBucket,"Looking to establish a page or section on gitlab.com with an apples-to-apples comparison between GitLab EE and Atlasssian products. The goal is to have a more direct comparison to features and the advantages we hold over Atlassian. The current comparison here(https://about.gitlab.com/comparison/#gitlab-vs-bitbucket-server) is a bit outdated according to conversations with prospects, and does not highlight the feature-to-feature comparisons in depth. - -The goal is for the sales team to be able to send a link(s) to prospects/customers considering BitBucket so they can clearly see the differences in more detail. I've talked with Job about this this morning and he is putting a few things together to update the website. Thoughts are always welcome! @ChadMalchow @AshleyS @jwrede @ronstroschein @sytses @malessio @balameb @JobV ",7 -1111849,2016-01-29 18:56:47.369,Remove 3d card flip,"@JobV - -Let's remove the 3d card flip from the profile cards and replace it with an actual link to a user's card. - -> deprecated feature!",3 -995533,2016-01-05 18:50:24.135,Changing Enterprise Trial Duration from 30 days to 14 days,"Hey Ashley, - -Can you please reduce the number of days for trails to 14? Thanks!",7 -984482,2016-01-01 18:55:51.941,Document merge request review workflow (endbosses),"We should write in handbook that we have endbosses now, and that each merge request should be reviewed by an endboss. - -We should also document how to choose an endboss: -https://gitlab.slack.com/archives/development/p1451384205002259",1 -69754853,2020-08-12 09:44:23.978,Release post tier badge text is misaligned,"#### What is/are the relevant URLs or emails? - -Any release page, e.g.: https://about.gitlab.com/releases/2020/07/22/gitlab-13-2-released/ - -#### Briefly describe the bug - -The tier badges' texts are misaligned. - -#### What are the steps to reproduce the bug - -1. Visit any release page, e.g.: https://about.gitlab.com/releases/2020/07/22/gitlab-13-2-released/ -1. Look at the tier badges under a feature headline - -#### Please provide any relevant screenshots or screencasts - -![Screenshot_from_2020-08-12_10-33-40](/uploads/e5f772c69afd65ef91fa70ab17d097a1/Screenshot_from_2020-08-12_10-33-40.png) - -#### What is your window size, browser, operating system, and versions - -Tested in Firefox 79.0 and Chromium Version 84.0.4147.105 (Official Build) snap (64-bit) on Ubuntu 20.04.1 LTS - -#### Possible fix - -The badges have a fixed width of `60px`, which is not enough to contain the longer strings like `ULTIMATE`. Two possible fixes: - -1. Rely on a `display: table` layout more for these badges, without setting a fixed width on each badge -1. Use `display: grid` :tada: - - -/cc @gl-website - -",1 -69740173,2020-08-11 21:51:38.477,Newsletter subscription form white text white background," - -#### What is/are the relevant URLs or emails? - - - -https://about.gitlab.com/events/commit/ - -#### Briefly describe the bug - - - -The newsletter subscription form has white text over a white background and therefore is practically invisible. It technically still functions but this bug is likely be a barrier to use. - -#### Please provide any relevant screenshots or screencasts - -![Greenshot_2020-08-11_14.49.11](/uploads/5aaa60cbd519210c1e075b48778ab9ab/Greenshot_2020-08-11_14.49.11.png) - -#### What is your window size, browser, operating system, and versions - - - -https://www.whatsmybrowser.org/b/4YUV8SF - -#### What device are you using - - - -Macbook Pro 15"" 2019 - -#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? - - - -N/A - -#### What browser plugins do you have enabled? - - - -N/A - -#### What is your geographic location - - - -California - -#### What type of network are you connected to? - - - -Home cable - -",1 -69669963,2020-08-10 23:33:35.585,Adjust pricing page popups take3," -## Overview - -This is related to https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/-/issues/212#note_389216039 - -#### Briefly describe your request -What is going to be added/removed, etc. - - -`Add more style emphasis to the links, continuing work from` https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8584 - -#### Describe why this update is being requested: -What problem(s) are you trying to solve? What are the goals? - - - -* `Users would like a quick look ""does this tier have the features I need for a specific category/topic?""` -* `The quicker a user sees what they want, the more likely they are to buy.` - -#### What is/are the relevant URL(s) -`https://about.gitlab.com/pricing/` - -_________ - -## 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. -`2020-08-13. We're reusing code but adding some CSS so it should be quick.` - - -#### Please identify the directly responsible individual (DRI), stakeholders, and roles - - - -|Name|Role| -|------|------| -| `@tbarr` | DRI | -| `@sytses` | Primary stakeholder | -| `@rreich` | Project facilitator | -| `@brandon_lyon` | Marketing developer lead for this week's MVC | -| `@shanerice` | Development partner, testing/analytics/seo, guidance/coordination | -| `@skarpeles` | Marketing developer lead during prior iterations | -| `@jstava` | Growth group stakeholder | - - ____________ - -## 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** - -`Users who are ready to buy but need to know which version to purchase` - -**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) -- [x] Has been here a few times -- [ ] Very familiar (likely looking for documentation, resources, new features, community projects, etc. ) - -**Special Considerations (check if applicable):** - -- [ ] Government -- [ ] Outside U.S. (primary) -- [ ] Direct Competitive (ex: OctoCat Campaign} - -___________ -## Promotion and Measurable Goals - -#### What are the measurable key performance indicators (KPI)? -* `Same performance metrics currently measured on that page` - - -#### Where do you expect traffic to come from? -* `The usual` - - -## Relevant Documents/Information - -* [Pricing capabilities YML](https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/uploads/33772b260e9c36753dba3dc778a1b8f0/pricing_capabilities.yml). -* [Related merge request with relevant code](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/58002). - -## Project Deliverables - -#### What are the project must-haves? - - - -* [ ] Reusing work from the [previous iteration](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8584) -* [ ] Add styles to the links to attempt to improve engagement. - -#### What are the project could-haves? - - - -* [ ] A/B test implemented. - -## 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",1 -69668521,2020-08-10 21:57:58.092,Commit event sponsors update August week 1,"Ongoing work related to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/164 - -This MR adds the following logos to the sponsor section: - -* Accurics -* Epsagon -* ServiceNow -* Drupal",1 -69553366,2020-08-07 17:35:52.475,Disable the design test on pricing page,Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/289,1 -69479787,2020-08-05 20:55:09.568,Generate Release Notes in GitLab Releases," - -### Problem to solve - -Gitlab users want to easily find/read release notes relevant to them, such as tier, the stages they use or specific items of interest (upgrades, deprecations and removals) in release announcements. Gitlab team members (such as Marketing and Sales) want to successfully find/share relevant release notes with Gitlab users and prospects. - -The following pages deliver Gitlab's release notes organized in various ways, forcing internal and external Gitlab users to reference various pages to collect the information they seek: - -- **Release Post Marketing Blog""**: https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/ -- **Gitlab Releases""** https://about.gitlab.com/releases/ archived ==> https://web.archive.org/web/20200714130736/https://about.gitlab.com/releases/ -- **GitLab upcoming releases""** https://about.gitlab.com/upcoming-releases/ -- **Upcoming features for paid tiers""** https://about.gitlab.com/direction/paid_tiers/ -- **X-Y Preview""** https://about.gitlab.com/releases/gitlab-com/ -- **Gitlab releases""** https://gitlab.com/gitlab-org/gitlab/-/releases/v12.10.0-ee - -### Intended users - -Current users, prospects, internal Gitlab team members - -### Proposal - -Improve and leverage Gitlab's in product Release feature https://gitlab.com/gitlab-org/gitlab/-/releases to serve as the ""go to"" SSOT for both SaaS and Self-hosted release notes, such that it can essentially replace the need for the various pages listed above. - -**Benefits** - -- Deliver a better user release notes experience internally/externally -- Boost process efficiency by decoupling the requirements of ""release notes"" from a ""marketing blog post"" -- Enable Product team to focus on feature/supporting content success -- Enable Marketing to focus on how, when and where else to best expose the release notes as part -- Enable Sales to clearly communicate via one thorough/sortable SSOT for existing and potential customers - -**Requirements:** - -To successfully replace the various release pages listed above, the Release feature https://gitlab.com/gitlab-org/gitlab/-/releases needs to: - -| | Requirement | | -|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | Display or provide quick access to content blocks that currently only surface in the [Release Post Marketing Blog](https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/) | - primary features
- secondary features (inclusive of recurring release notes such as Omnibus, Chart and Runner improvements)
- bugs
- performance improvements
- upgrades
- removals
- deprecations
- Issue to follow: https://gitlab.com/gitlab-org/gitlab/-/issues/234009 | -| 2 | Individual items should link through to: | - changelogs
- documentation
- epics
- issues
Issue to follow: https://gitlab.com/gitlab-org/gitlab/-/issues/217145 | -| 3 | The page should be sortable / filterable by: | - version
- plan type
- stage
- category
Issue to follow: https://gitlab.com/gitlab-org/gitlab/-/issues/234007 | -| 4 | Be continually up to date with features as they become available for SaaS (similar to or link to... https://about.gitlab.com/releases/gitlab-com/) | Epic to follow: https://gitlab.com/groups/gitlab-org/-/epics/4160 | -| 5 | Include a way to highlight ""Upcoming"" features for Self-hosted, which currently happens on https://about.gitlab.com/releases/gitlab-com/ but is hard to discern | Epic to follow: https://gitlab.com/groups/gitlab-org/-/epics/4160 | -| 6 | Include a way to search release notes |
- Issue to follow: https://gitlab.com/gitlab-org/gitlab/-/issues/227178 | -| 7 | Include a way to still be able to pull content blocks and generate the Marketing release post blog in it's current format |
- Issue to follow: https://gitlab.com/gitlab-org/gitlab/-/issues/234009 |",8 -69427832,2020-08-04 20:16:02.673,What are Versioned Tests and why should you use them?," - -### Proposal - -Versioned tests are listed as one of the highlighted features of GitLab CI/CD, but it doesn't look like we use that term or have fully explained what that looks like and what that means. I would like to make a post that talks about versioned tests and what they are, what they do, how to set them up, and why they're a good feature. - -This is for the CI Use Case Campaign. Publish date is not time-sensitive, anytime in Q3 is fine. - -### Checklist - -- [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - - [ ] 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/#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](http://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 `@TinaS`, 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 `@KimLock` and `@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) -- [x] 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)",2 -69374021,2020-08-03 17:03:38.023,Adjust pricing page popups," -## Overview - -This is related to https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/-/issues/212#note_389216039 - -#### Briefly describe your request -What is going to be added/removed, etc. - - -`Update the popups per direction from management, following this spreadsheet` - -https://docs.google.com/spreadsheets/d/1P58q76cyAqgyAUM5P-WaCdcmXkNQWNML3mKAmabTadk/edit#gid=2024575769 - -#### Describe why this update is being requested: -What problem(s) are you trying to solve? What are the goals? - - - -* `Users would like a quick look ""does this tier have the features I need for a specific category/topic?""` -* `The quicker a user sees what they want, the more likely they are to buy.` - -#### What is/are the relevant URL(s) -`https://about.gitlab.com/pricing/` - -_________ - -## 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. -`2020-08-07` - - -#### Please identify the directly responsible individual (DRI), stakeholders, and roles - - - -|Name|Role| -|------|------| -| `@tbarr` | DRI | -| `@sytses` | Primary stakeholder | -| `@rreich` | Project facilitator | -| `@brandon_lyon` | Marketing developer lead for this week's MVC | -| `@shanerice` | Development partner, testing/analytics/seo, guidance/coordination | -| `@skarpeles` | Marketing developer lead during prior iterations | -| `@jstava` | Growth group stakeholder | - - ____________ - -## 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** - -`Users who are ready to buy but need to know which version to purchase` - -**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) -- [x] Has been here a few times -- [ ] Very familiar (likely looking for documentation, resources, new features, community projects, etc. ) - -**Special Considerations (check if applicable):** - -- [ ] Government -- [ ] Outside U.S. (primary) -- [ ] Direct Competitive (ex: OctoCat Campaign} - -___________ -## Promotion and Measurable Goals - -#### What are the measurable key performance indicators (KPI)? -* `Same performance metrics currently measured on that page` - - -#### Where do you expect traffic to come from? -* `The usual` - - -## Relevant Documents/Information - -* [Pricing capabilities YML](https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/uploads/33772b260e9c36753dba3dc778a1b8f0/pricing_capabilities.yml). -* [Related merge request with relevant code](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/58002). - -## Project Deliverables - -#### What are the project must-haves? - - - -* [ ] Replace the ""compare features"" links on the bottom of the pricing matrix with links from each item on the feature list where the popup is [filtered to that specific feature](https://docs.google.com/spreadsheets/d/1P58q76cyAqgyAUM5P-WaCdcmXkNQWNML3mKAmabTadk/edit#gid=2024575769). -* [ ] Remove the popup graphic, title, and description paragraph. -* [ ] Popup buttons are moved below the feature list. - -![interstitial_round3](/uploads/c390d0a80b0c2a6b4b53a8e6e57b8063/interstitial_round3.png) - -#### What are the project could-haves? - - - -* [ ] A/B test implemented. - -## 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",5 -69372467,2020-08-03 16:07:06.912,Investigate using a serverless app to process Marketo forms,"`@jeanduplessis` recently pointed out a potential way to process Marketo forms without a server is via a serverless application such as Lambda. This would allow us to combine the best of both worlds, our static website and a dynamic server. We should investigate and see if this is something we could potentially use to fix our Marketo privacy issues. - -Due to cost and time required, before we do this we should try other solutions first: - -* https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/-/issues/256 -* https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/214 - -",10 -69305752,2020-07-31 16:38:34.806,Commit event sponsors update July week5,"Ongoing work related to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/164 - -This MR adds the following logos to the sponsor section: - -* mabl -* Oracle -* DataDog",1 -69237754,2020-07-30 15:05:07.858,Update default MR template,"## Please update the default MR template - -``` - - - -## Why is this change being made? - - - -## Author Checklist -- [ ] Provided a concise title for the MR -- [ ] Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency] -- [ ] Assign this change to the correct DRI - - If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager. - - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack]. - - If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping `@gl-static-site-editor` in a comment for a review and merge. For example changes to `.gitlab-ci.yml`, JavaScript/CSS/Ruby code or the layout files. -```",1 -69142279,2020-07-28 21:11:27.885,Remove JS files from blog post and move blog post to correct directory,"#### What is/are the relevant URLs or emails? -This blog post does not have a current URL because it is in the depreciated `source/posts` directory. The blog post also references javascript files uploaded directly to its image directory. -``` -source/images/blogimages/gitlab-daily-tools/Handy GitLab actions.user.js -source/images/blogimages/gitlab-daily-tools/GitLab filters.user.js -``` -Having javascript files located in the image directory will confuse linters and filters. - -#### Where is the blog post located -https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/source/posts/2019-11-26-gitlab-daily-tools.html.md - - -/cc @gl-website - -",1 -69119383,2020-07-28 12:12:51.717,Team map not loading in Safari,"#### What is/are the relevant URLs or emails? - -https://about.gitlab.com/company/team/ - -#### Briefly describe the bug - -Team map not loading in Safari. - -#### Please provide any relevant screenshots or screencasts - -![image](/uploads/383afca895ff6b22b513e8b8d7651d38/image.png) - -#### What is your window size, browser, operating system, and versions - -Mojave 10.14.5 and Safari 13.1.1 - -#### What device are you using - -Macbook Pro",2 -69066803,2020-07-27 20:31:34.705,Phase 2 Website Update - search,"``` - -BL notes to self: - -* The parts left for me are outlined in a comment near the bottom - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8470#note_422300928 - - -``` - -This template if for the Marketing Growth Team for their Phase 2 Webpage updates - -Title this issue: Phase 2 Website Update - (Page Name) - -[Phase 2 Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23) - -## Metadata for page -- **Intent:** -- **Goal:** -- **Who is code owner:** -- **SME Group:** - -## Adjustments to be made: -These adjustments are from this audit round - -- [x] Add metadata -- [ ] Swapping content or content links -- [ ] Adding pathfactory link -- [ ] Adjusting SEO -- [x] Adding CTA buttons -- [ ] Adjusting copy on CTA buttons -- [x] Adjusting old/erroneous messaging -- [ ] Improve mobile optimization -- [ ] Clean up alignment -- [ ] Adjust color schemes -- [x] Swap out old assets - - -## Relevant Links: -- [Page Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23) -- [Survey](https://docs.google.com/forms/d/1GsZ4IoIAeLssROY_JfoWuOFPWyO5M4ykgYBNhD5sU8o/edit) - -## Roles and Responsibilities - -| Role | DRI | -| ------ | ------ | -| Project DRI | @rreich | -| Marketing Analytics | @shanerice | -| Content/Messaging | @erica| -| Web Dev | @skarpeles | -| Brand/Design | @luke | -| GM Stakeholder | @dmor | - -## Production -**Project DRI** -- [x] Add design to design tab -- [ ] Decide on audit items and check-off -- [ ] Assign to relevant Team Leads for visibility -- [ ] Make relevant WIP MRs -- [ ] Add this issue to the page epic description -- [ ] Close issue once set of MRs is complete - -**Team Leads** -You may make comments in the design tab for tracking, but conversations on updates should be kept to the relevant MRs",1 -69047497,2020-07-27 19:09:14.553,Phase 2 Website Update - community/index,"This template if for the Marketing Growth Team for their Phase 2 Webpage updates - -Title this issue: Phase 2 Website Update - (Page Name) - -[Phase 2 Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23) - -## Metadata for page -- **Intent:** -- **Goal:** -- **Who is code owner:** Growth Marketing -- **SME Group:** Community Team - -## Adjustments to be made: -These adjustments are from this audit round - -- [x] Add metadata -- [ ] Swapping content or content links -- [ ] Adding pathfactory link -- [x] Adjusting SEO -- [x] Adding CTA buttons -- [x] Adjusting copy on CTA buttons -- [x] Adjusting old/erroneous messaging -- [ ] Improve mobile optimization -- [x] Clean up alignment -- [ ] Adjust color schemes -- [x] Swap out old assets - - -## Relevant Links: -- [Page Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23) - -## Roles and Responsibilities - -| Role | DRI | -| ------ | ------ | -| Project DRI | @rreich | -| Marketing Analytics | @shanerice | -| Content/Messaging | @erica| -| Web Dev | @skarpeles | -| Brand/Design | @luke | -| GM Stakeholder | @dmor | - -## Production -**Project DRI** -- [x] Add design to design tab -- [x] Decide on audit items and check-off -- [x] Assign to relevant Team Leads for visibility -- [x] Make relevant WIP MRs -- [x] Add this issue to the page epic description -- [ ] Close issue once set of MRs is complete - -**Team Leads** -You may make comments in the design tab for tracking, but conversations on updates should be kept to the relevant MRs",1 -69045016,2020-07-27 18:57:10.331,Change all mentions of WIP to Draft in Blog Handbook," - -#### Briefly describe the update - -WIP prefix for merge request has been depreciated in favor of using Draft instead. - -This was documented here https://gitlab.com/gitlab-org/gitlab/-/issues/228685 - -Let's change all documentation in the handbook related to creating abd publishing blog posts to use the new prefix. - -This will apply to the following pages: -https://about.gitlab.com/handbook/marketing/blog/ -More TBD - - -",1 -69032896,2020-07-27 17:13:37.143,Phase 2 Website Update - what-is-gitlab/index,"This template if for the Marketing Growth Team for their Phase 2 Webpage updates - -Title this issue: Phase 2 Website Update - (Page Name) - -[Phase 2 Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23) - -## Metadata for page -- **Intent:** About GitLab the company -- **Goal:** Learn more about GitLab the company -- **Who is code owner:** Growth Marketing -- **SME Group:** Corporate Marketing - -## Adjustments to be made: -These adjustments are from this audit round - -- [x] Add metadata -- [x] Swapping content or content links -- [ ] Adding pathfactory link -- [ ] Adjusting SEO -- [x] Adding CTA buttons -- [x] Adjusting copy on CTA buttons -- [x] Adjusting old/erroneous messaging -- [ ] Improve mobile optimization -- [ ] Clean up alignment -- [ ] Adjust color schemes -- [ ] Swap out old assets - -## Relevant Links: -- [Page Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23) - -## Roles and Responsibilities - -| Role | DRI | -| ------ | ------ | -| Project DRI | @rreich | -| Marketing Analytics | @shanerice | -| Content/Messaging | @erica| -| Web Dev | @skarpeles | -| Brand/Design UX Desktop and Mobile | @sbouchard | -| Brand/Design Dev | @mpreuss22 | -| GM Stakeholder | @dmor | - -## Production -**Project DRI** -- [x] Add design to design tab -- [x] Decide on audit items and check-off -- [x] Assign to relevant Team Leads for visibility -- [x] Make relevant WIP MRs -- [x] Add this issue to the page epic description -- [x] Close issue once set of MRs is complete - -**Team Leads** -You may make comments in the design tab for tracking, but conversations on updates should be kept to the relevant MRs",4 -68959758,2020-07-24 19:07:54.145,Investigate deferring the load of below-the-fold images in marketing site,"Can we dramatically improve performance by deferring the load of below-the-fold images and third-party