data/applications.yml

@@ -406,13 +406,6 @@
           title: Video walk-through
         - url: http://support.hubstaff.com/gitlab-time-tracking-integration/
           title: Support
-    - title: POEditor
-      content: Collaborative translation platform and localization management software. The integration with GitLab connects the translations in POEditor projects with language files in GitLab repos, simplifying translation management and syncronization.
-      links:
-        - url: https://poeditor.com/
-          title: POEditor
-        - url: https://poeditor.com/help/how_to_translate_a_language_file_from_a_gitlab_project
-          title: GitLab Integration
     - title: GitPitch - Slideshow Presentations for Developers
       content: No more PowerPoint. No more Keynote. Just Markdown. Then Git-Commit.
       links:
@@ -440,13 +433,6 @@
           title: GitLab + JIRA Integration guide
         - url: "https://bigbrassband.com/documentation.html#add_gitlab_server"
           title: GitLab integration documentation
-    - title: Crowdin
-      content: A web-based solution for developers created to streamline the localization process. Easy file sync between GitLab repository and a localization project in Crowdin. Provides translators and managers with an advanced tooling set.
-      links:
-        - url: "https://crowdin.com/"
-          title: Crowdin website
-        - url:  "https://support.crowdin.com/gitlab-integration/"
-          title: GitLab integration documentation
     - title: Zapier
       content: Zapier allows you to connect almost any application to almost any other application, GitLab included.
       links:
@@ -462,6 +448,36 @@
       links:
         - url: https://github.com/svtek/serverless-microsoft-teams-gitlab-connector
           title: Serverless Microsoft Teams Connector
+    - title: Autosync Asana - GitLab by Unito 
+      content: 2-way sync to Asana, connecting assignee, due date, & more. Filter syncs for custom workflows.
+      links:
+        - url: https://unito.io/sync/gitlabcom/asana?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=asana
+          title: Unito.io
+    - title: Autosync Wrike - GitLab by Unito
+      content: 2-way sync to Wrike, connecting assignee, due date, & more. Filter syncs for custom workflows.
+      links:
+        - url: https://unito.io/sync/gitlabcom/wrike?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=wrike
+          title: Unito.io
+    - title: Autosync Basecamp - GitLab by Unito
+      content: 2-way sync to Basecamp, connecting assignee, due date, & more. Filter syncs for custom workflows.
+      links:
+        - url: https://unito.io/sync/gitlabcom/basecamp?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=basecamp
+          title: Unito.io
+    - title: Autosync BitBucket - GitLab by Unito
+      content: Simplify bug management between repos. Powerful filters can sync a few issues or the whole repo!
+      links:
+        - url: https://unito.io/sync/gitlabcom/bitbucket?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=bitbucket
+          title: Unito.io
+    - title: Autosync GitHub - GitLab by Unito
+      content: Simplify bug management between repos. Powerful filters can sync a few issues or the whole repo!
+      links:
+        - url: https://unito.io/sync/gitlabcom/github?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=github
+          title: Unito.io
+    - title: GitLab Issue Sync by Unito
+      content: Simplify bug management between repos. Powerful filters can sync a few issues or the whole repo!
+      links:
+        - url: https://unito.io/sync/gitlabcom/gitlabcom?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=gitlab
+          title: Unito.io
     - title: Cosango GitLab Reports
       content: Small open source app to easily create milestone and time tracking reports in GitLab
       links:
@@ -474,6 +490,15 @@
       links:
         - url: https://GitMate.io/
           title: GitMate.io
+    - title: Relution
+      content: Integrate GitLab with Relution for distributing and managing multiple iOS and/or Android mobile applications built with GitLab CI/CD. You can use Relution to set up Git repositories and CI/CD pipelines for your projects on your GitLab infrastructure.
+      links:
+        - url: 'https://www.relution.io'
+          title: "Relution website"
+        - url: 'https://www.relution.io/en/insights-news/automate-app-projects/'
+          title: "GitLab + Relution integration overview"
+        - url: 'http://repo.relution.io/package/latest/manual.html#development-hub'
+          title: "Relution documentation"
 - title: Continuous Integration
   id: continuous-integration
   applications:
@@ -662,6 +687,11 @@
       links:
         - url: https://www.vivifyscrum.com/
           title: Vivify Scrum
+    - title: Autosync Trello - GitLab by Unito
+      content: 2-way sync to Trello, connecting assignee, due date, & more. Filter syncs for custom workflows.
+      links:
+        - url: https://unito.io/sync/gitlabcom/trello?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=trello
+          title: Unito.io
 - title: Built with GitLab
   id: built-with-gitlab
   applications:
@@ -685,3 +715,21 @@
       links:
         - url: https://www.penflip.com/
           title: penflip.com
+- title: Translation Tools
+  id: translation-tools
+  applications:
+    - title: Crowdin
+      content: 'A web-based solution for developers created to streamline the localization process. Easy file sync between GitLab repository and a localization project in Crowdin. Provides translators and managers with an advanced tooling set.
+      GitLab uses Crowdin to <a href="http://translate.gitlab.com/">add and support multiple languages</a>.'
+      links:
+        - url: "https://crowdin.com/"
+          title: Crowdin website
+        - url:  "https://support.crowdin.com/gitlab-integration/"
+          title: GitLab integration documentation
+    - title: POEditor
+      content: Collaborative translation platform and localization management software. The integration with GitLab connects the translations in POEditor projects with language files in GitLab repos, simplifying translation management and syncronization.
+      links:
+        - url: https://poeditor.com/
+          title: POEditor
+        - url: https://poeditor.com/help/how_to_translate_a_language_file_from_a_gitlab_project
+          title: GitLab Integration

data/contract_types.yml

-- country: Belgium
-  employee_factor: 0.8
-- country: China
-  employee_factor: 0.66
+# Countries with a GitLab entity or payroll established
+# will have an `employee_factor` of 1
+
+# Please list all countries that fit that criteria here
+
+- country: United States
+  employee_factor: 1
 - country: India
-  employee_factor: 0.75
+  employee_factor: 1
+- country: China
+  employee_factor: 1
 - country: Netherlands
-  employee_factor: 0.8
+  employee_factor: 1
+- country: Belgium
+  employee_factor: 1
 - country: United Kingdom
-  employee_factor: 0.8
+  employee_factor: 1
 - country: Germany
-  employee_factor: 0.9
-- country: United States
   employee_factor: 1
 - country: '*'
   contractor_factor: 1.17

data/country_factors.yml

+- country: Belgium
+  country_factor: 1
+- country: China
+  country_factor: 0.66
+- country: India
+  country_factor: 0.75
+- country: Netherlands
+  country_factor: 0.85
+- country: United Kingdom
+  country_factor: 0.85
+- country: Germany
+  country_factor: 1
+- country: United States
+  country_factor: 1
+- country: Israel
+  country_factor: 1.1
+- country: Brazil
+  country_factor: 0.85
+- country: Poland
+  country_factor: 0.8
+- country: Russia
+  country_factor: 0.6
+- country: Portugal
+  country_factor: 0.95
+- country: Ukraine
+  country_factor: 0.65
+- country: Czech Republic
+  country_factor: 0.9
+- country: Mexico
+  country_factor: 0.65
+- country: Chile
+  country_factor: 0.85
+- country: '*'
+  country_factor: 1

data/features.yml

@@ -364,6 +364,7 @@ features:
     gitlab_ce: true
     gitlab_ees: true
     gitlab_eep: true
+    gitlab_eeu: true
     gitlab_com: true
     github_com: false
     bitbucket_org: false
@@ -380,6 +381,7 @@ features:
     gitlab_ce: true
     gitlab_ees: true
     gitlab_eep: true
+    gitlab_eeu: true
     gitlab_com: true
     github_com: false
     bitbucket_org: false
@@ -572,9 +574,9 @@ features:
     gitlab_eep: true
     github_com: false
     github_enterprise: false
-  - title: "Comment on commits in merge requests"
+  - title: "Merge Request Commit Discussions"
     description: "Comment on a commit within the context of a merge request itself"
-    link_description: "Comment on commits in merge requests"
+    link_description: "Merge Request Commit Discussions"
     link: https://docs.gitlab.com/ee/user/discussions/#commit-discussions
     solution: create
     gitlab_ce: true
@@ -587,7 +589,7 @@ features:
     solution: create
     gitlab_ce: true
     gitlab_ees: true
-    gitlab_eep: true    
+    gitlab_eep: true
   - title: "Create merge request from email"
     description: "Create a merge request from email, by sending in the merge request title, description, and source branch name."
     link_description: "Create merge request from email"
@@ -595,7 +597,7 @@ features:
     solution: create
     gitlab_ce: true
     gitlab_ees: true
-    gitlab_eep: true        
+    gitlab_eep: true
   - title: "Lock Discussion"
     description: "Lock down continued discussion in an issue or merge request as a Master role or higher, to prevent further abuse, spam, or unproductive collaboration."
     link_description: "Lock Discussion"
@@ -761,6 +763,7 @@ features:
     gitlab_ce: true
     gitlab_ees: true
     gitlab_eep: true
+    gitlab_eeu: true
     github_enterprise: false
     bitbucket_server: false
   - title: "Run your own software on your instance"
@@ -820,6 +823,7 @@ features:
     gitlab_ce: true
     gitlab_ees: true
     gitlab_eep: true
+    gitlab_eeu: true
     gitlab_com: false
   - title: "IPv6 ready"
     description: "If you host GitLab yourself, IPv6 is supported as long as your underlying provider can support it. GitLab.com on the other hand does not support IPv6 at the moment due to limited provider support."
@@ -1166,6 +1170,7 @@ features:
     gitlab_ce: false
     gitlab_ees: false
     gitlab_eep: true
+    gitlab_eeu: true
   - title: "Import from GitLab.com"
     description: "Import projects from GitLab.com to a private GitLab instance."
     link_description: "Learn more about importing projects from GitLab.com"
@@ -1900,7 +1905,7 @@ features:
       It automatically detects, builds, tests, deploys, and monitors applications.
     link_description: "Read more about Auto DevOps in the documentation"
     link: 'https://docs.gitlab.com/ee/topics/autodevops/'
-    solution: verify
+    solution: configure
     gitlab_ce: true
     gitlab_ees: true
     gitlab_eep: true
@@ -2094,6 +2099,7 @@ features:
     gitlab_ce: false
     gitlab_ees: false
     gitlab_eep: true
+    gitlab_eeu: true
     roi_case: "Allows to reach 99% availability instead of 95%, meaning 15 days of more availability per year, 8 hours per day"
     category: "Uptime & Scale"
     shorthand: "ha_setup"
@@ -2569,7 +2575,7 @@ features:
       GitLab allows easy running of Static Application Security Testing in CI/CD pipelines, checking for vulnerable source code or
       well known security bugs in the libraries that are included by the application. Results are then shown in the MR widget.
       This feature is available also as part of Auto DevOps to provide security-by-default.
-    link: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/3878'
+    link: 'https://docs.gitlab.com/ee/user/project/merge_requests/sast.html'
     solution: security
     gitlab_ce: false
     gitlab_ees: false
@@ -2635,3 +2641,14 @@ features:
     gitlab_eep: false
     gitlab_eeu: true
     include_on_features_page: false
+  - title: "Browser Performance Testing"
+    description: "Easily detect performance regressions for web apps **prior** to merging into master."
+    link_description: Documentation
+    link: 'https://docs.gitlab.com/ee/user/project/merge_requests/performance_diff.html'
+    screenshot_url: 'images/feature_page/screenshots/53-browser-performance.png'
+    solution: monitor
+    gitlab_ce: false
+    gitlab_ees: false
+    gitlab_eep: true
+    gitlab_eeu: true
+    include_on_features_page: true

data/jobs.yml

@@ -4,52 +4,35 @@
 - title: "Executive Assistant"
   description: /jobs/executive-assistant/
-  salary: 53000
+  salary: 97000
+  salary source: Aventador
   apply:
   open: false
 - title: "People Operations Administrator"
   description: /jobs/people-ops-administrator/
+  salary: 76432
+  salary source: Aventador
   apply:
   open: false
 - title: "Accountant"
   description: /jobs/accountant/
-  salary: 62515
+  salary: 93000
+  salary source: Aventador
   apply:
   open: false
-- title: "Account Executive - Mid-Market (East)"
+- title: "Account Executive"
   description: /jobs/account-executive/
-  apply: https://jobs.lever.co/gitlab/865e112a-1acf-4d49-a352-f77ccdf33750
-  open: false
-
-- title: "Account Executive (East)"
-  description: /jobs/account-executive/
-  apply: https://jobs.lever.co/gitlab/fff27ba3-38a9-4755-99cf-26c2bfbe2348
-  open: false
-
-- title: "Account Executive (EMEA)"
-  description: /jobs/account-executive/
-  apply: https://jobs.lever.co/gitlab/d465ac05-13fb-4a0c-8f02-7a70fd2a0acf
-  open: false
-
-- title: "Federal Strategic Account Executive - DOD"
-  description: /jobs/federal-strategic-account-executive/
-  apply: https://jobs.lever.co/gitlab/2e077d5e-3ad2-4be8-956e-9ff28c09bba1
-  open: false
-
-- title: "Federal Strategic Account Executive - Intel"
-  description: /jobs/federal-strategic-account-executive/
-  apply: https://jobs.lever.co/gitlab/3e3dd7ca-aa7f-41e3-8940-8815b99bb704
+  apply:
   open: false
-- title: "Federal Strategic Account Executive - Civilian"
+- title: "Federal Strategic Account Executive"
   description: /jobs/federal-strategic-account-executive/
-  apply: https://jobs.lever.co/gitlab/7dc21a27-6d56-415a-bdd0-a452fbd09cf3
+  apply:
   open: false
-
 - title: "Strategic Account Leader"
   description: /jobs/strategic-account-leader/
   apply:
@@ -62,25 +45,15 @@
 - title: "Accounting Manager"
   description: /jobs/accounting-manager/
-  salary: 78900
-  apply:
-  open: false
-
-- title: "Backend Developer"
-  description: /jobs/developer/
-  salary: 87337
-  apply:
-  open: false
-
-- title: "Backend Lead"
-  description: /jobs/backend-lead/
-  salary: 87337
+  salary: 119010
+  salary source: F1
   apply:
   open: false
 - title: "Billing Specialist"
   description: /jobs/billing-specialist/
-  salary:
+  salary: 67500
+  salary source: F1
   apply: https://jobs.lever.co/gitlab/c80f7c1d-8e4d-491e-8df0-9c4eaba4680c
   open: false
@@ -88,116 +61,51 @@
   description: /jobs/director-backend/
   open: false
-- title: "Build Engineer"
-  description: /jobs/build-engineer/
-  salary: 87337
-  apply: https://jobs.lever.co/gitlab/0b7f460f-fb29-494b-a5b1-21cbb446bcca
-  open: false
-
-- title: "Build Lead"
-  description: /jobs/build-lead/
-  salary: 87337
-  apply:
-  open: false
-
 - title: "Business Development Representative"
-  description: /jobs/business-development-representative/
+  description:
   apply: https://jobs.lever.co/gitlab/73b0dd91-cd87-4845-9918-aeb6e0feec2e
   open: false
-- title: "Sales Development Representative (East & West Coast, US)"
-  description: /jobs/sales-development-representative/
-  salary: 92000
-  apply: https://jobs.lever.co/gitlab/71a6265e-c6ec-462e-86ab-79a0f9995631
-  open: false
-
-- title: "Sales Development Representative (EMEA)"
+- title: "Sales Development Representative"
   description: /jobs/sales-development-representative/
-  salary: 92000
-  apply:
-  open: false
-
-- title: "Sales Development Representative Lead"
-  description: /jobs/sales-development-representative-lead/
-  salary: 92000
-  apply:
-  open: false
-
-- title: "Senior Backend Developer"
-  description: /jobs/senior-developer/
-  salary: 87337
-  apply:
-  open: false
-
-- title: "CI/CD Lead"
-  description: /jobs/ci-cd-lead/
-  salary: 87337
   apply:
   open: false
 - title: "Channel Sales Manager"
   description: /jobs/channel-sales-manager/
-  salary:
-  apply: https://jobs.lever.co/gitlab/d615e4f1-fe69-4cbf-bd72-fefb402793fb
+  apply:
   open: false
 - title: "Community Advocate"
   description: /jobs/community-advocate/
-  salary: 55823
+  salary: 85000
+  salary source: Marketing Compensation Survey
   apply:
   open: false
 - title: "Content Editor"
   description: /jobs/content-editor/
-  salary: 50400
-  apply:
-  open: false
-
-- title: "Content Marketing Manager"
-  description: /jobs/content-marketing-manager/
-  salary: 50400
+  salary: 85000
+  salary source: Marketing Compensation Survey
   apply:
   open: false
 - title: "Controller"
   description: /jobs/controller/
-  salary: 90520
   apply:
   open: false
-- title: "Data and Analytics Architect - Americas"
+- title: "Data and Analytics Architect"
   description: /jobs/data-analytics-architect/
-  salary: 115000
-  apply: https://jobs.lever.co/gitlab/ae5af159-e651-4d2a-a13f-f43896745afd
+  salary: 135000
+  salary source: E-team
+  apply:
   open: false
 - title: "Developer"
   description: /jobs/developer/
-  salary: 87337
-  apply:
-  open: false
-
-- title: "Developer Advocate"
-  description: /jobs/developer-advocate/
-  salary: 70200
-  apply:
-  open: false
-
-- title: "Security Specialist"
-  description: /jobs/security-specialist
-  salary: 87337
-  apply: https://jobs.lever.co/gitlab/fac5198e-20e7-47a4-8b53-e8df48491c8b
-  open: false
-
-- title: "Backend Developer, Edge"
-  description: /jobs/developer-edge/
-  salary: 87337
-  apply:
-  open: false
-
-- title: "Backend Developer, CI/CD Pipelines"
-  description: /jobs/developer-ci-cd/
-  salary: 87337
+  salary: 120000
+  salary source: Aventador
   apply:
   open: false
@@ -206,11 +114,6 @@
   apply:
   open: false
-- title: "Director of Developer Relations"
-  description: /jobs/director-developer-relations/
-  apply:
-  open: false
-
 - title: "Director Federal Sales"
   description: /jobs/director-federal-sales/
   apply:
@@ -226,11 +129,6 @@
   apply:
   open: false
-- title: "Director of Lead Generation"
-  description: /jobs/director-of-leadgen/
-  apply:
-  open: false
-
 - title: "Director of Legal Affairs"
   description: /jobs/director-legal-affairs/
   apply:
@@ -243,151 +141,93 @@
 - title: "Director of Security"
   description: /jobs/director-of-security/
-  apply: https://jobs.lever.co/gitlab/107ea9fc-753f-4b96-b62c-d2358da59cf6
-  open: false
-
-- title: "Edge Lead"
-  description: /jobs/edge-lead/
-  salary: 87337
   apply:
   open: false
-- title: "Federal Solutions Architect - Customer Success"
-  description: /jobs/federal-solutions-architect/
-  apply: https://jobs.lever.co/gitlab/8263aeca-a80c-49dd-a152-bfd8839e8075
-  open: false
-
 - title: "Federal Channel Manager"
   description: /jobs/federal-channel-manager/
   salary:
-  apply: https://jobs.lever.co/gitlab/216da077-5b19-4ef8-b38c-efae1ce17b29
+  apply:
   open: false
-# Ordered alphabetically **by job description URL**
-
 - title: "Field Marketing Manager"
   description: /jobs/field-marketing-manager/
-  salary: 63434
+  salary: 92000
+  salary source: Aventador
   apply:
   open: false
 - title: "Frontend Engineer"
   description: /jobs/frontend-engineer/
-  salary: 83132
-  apply: https://jobs.lever.co/gitlab/15d296bd-b766-4afd-8ee8-48d6fb0b9dba
-  open: false
-
-- title: "Frontend Lead"
-  description: /jobs/frontend-lead/
-  salary: 83132
-  apply:
-  open: false
-
-- title: "Growth Product Manager"
-  description: /jobs/growth-product-manager/
-  salary: 117530
+  salary: 120000
+  salary source: Same as Developer
   apply:
   open: false
 - title: "Implementation Specialist"
   description: /jobs/implementation-specialist/
-  apply: https://jobs.lever.co/gitlab/b1b478c5-446c-4d9c-a920-9c1466f88e36
+  apply:
   open: false
 - title: "Designer"
   description: /jobs/designer/
-  salary: 61000
-  apply:
-  open: false
-
-- title: "Marketing Frontend Engineer"
-  description: /jobs/marketing-frontend-engineer/
+  salary: 107000
+  salary source: Aventador
   apply:
   open: false
 - title: "Marketing Program Manager"
   description: /jobs/marketing-program-manager/
-  apply: https://jobs.lever.co/gitlab/8c4c6599-46bb-472b-afd9-3fb9351ad273
+  salary: 116000
+  salary source: Aventador
+  apply:
   open: false
 - title: "Online Marketing Manager"
   description: /jobs/online-marketing-manager/
-  salary: 83345
-  apply:
-  open: false
-
-- title: "Open Application"
-  description: /jobs/open-application/
-  apply:
-  open: false
-
-- title: "Gitaly Lead"
-  description: /jobs/gitaly-lead/
-  salary: 87337
-  apply:
-  open: false
-
-- title: "Executive Recruiter"
-  description: /jobs/recruiter/
-  apply:
-  open: false
-
-- title: "Performance Lead"
-  description: /jobs/performance-lead
+  salary: 132000
+  salary source: Marketing Compensation Survey
   apply:
   open: false
 - title: "Product Marketing Manager"
   description: /jobs/product-marketing-manager/
-  salary: 87500
-  apply: https://jobs.lever.co/gitlab/219014ac-196e-47d7-90fd-7f3e4033ce46
+  salary: 148000
+  salary source: Marketing Compensation Survey
+  apply:
   open: false
 - title: "Director of Product Marketing"
   description: /jobs/director-product-marketing
-  apply: https://jobs.lever.co/gitlab/d36f3b7c-6754-4624-8835-55b6b5ff8cf7
+  apply:
   open: false
 - title: "Product Manager"
   description: /jobs/product-manager/
-  salary: 117530
-  apply:
-  open: false
-
-- title: "Senior Product Manager, CI/CD Pipelines"
-  description: /jobs/product-manager-ci/
-  salary: 117530
+  salary: 177500
+  salary source: Aventador
   apply:
   open: false
 - title: "Production Engineer"
   description: /jobs/production-engineer/
-  salary: 110295
-  apply: https://jobs.lever.co/gitlab/a9ec2996-b7b6-4d87-aed0-1fc2ce3f8faa
-  open: false
-
-- title: "Production Lead"
-  description: /jobs/production-lead/
-  salary: 110295
-  apply:
-  open: false
-
-- title: "Prometheus Lead"
-  description: /jobs/prometheus-lead/
-  salary: 138000
+  salary: 140000
+  salary source: E-team
   apply:
   open: false
 - title: "Prometheus Engineer"
   description: /jobs/prometheus-engineer/
-  salary: 138000
+  salary: 184000
+  salary source: E-team
   apply:
   open: false
 - title: "Recruiter"
   description: /jobs/recruiter/
-  salary: 71337
-  apply: https://jobs.lever.co/gitlab/21d606b5-cfea-435a-bf79-ded9688e96c6
+  salary: 102698
+  salary source: Aventador
+  apply:
   open: false
 - title: "Regional Sales Director"
@@ -397,105 +237,61 @@
 - title: "Security Engineer"
   description: /jobs/security-engineer/
-  salary: 87337
-  apply: https://jobs.lever.co/gitlab/771fc022-568d-47ae-9f2b-55042e92539d
-  open: false
-
-- title: "Security Lead"
-  description: /jobs/security-lead/
-  salary: 87337
+  salary: 140000
+  salary source: E-team
   apply:
   open: false
-- title: "Support Engineer - EMEA "
-  description: /jobs/support-engineer/
-  salary: 87337
-  apply: https://jobs.lever.co/gitlab/bf6b8d93-e87e-4ba2-a05e-ab36bac0226f
-  open: false
-
-- title: "Support Engineer - APAC "
-  description: /jobs/support-engineer/
-  salary: 87337
-  apply: https://jobs.lever.co/gitlab/5727ca49-b549-4d5e-8789-f30d3b5b1a2e
-  open: false
-
-- title: "Support Engineer - Americas "
+- title: "Support Engineer"
   description: /jobs/support-engineer/
-  salary: 87337
-  apply: https://jobs.lever.co/gitlab/c5bcb75f-e390-44ee-bc3d-b9e4ef0ac55d
-  open: false
-
-- title: "Solutions Architect - Customer Success"
-  description: /jobs/solutions-architect/
+  salary: 120000
+  salary source: Same as Developer
   apply:
   open: false
-- title: "Solutions Architect - Customer Success (EMEA)"
+- title: "Solutions Architect"
   description: /jobs/solutions-architect/
-  apply: https://jobs.lever.co/gitlab/31861843-bf48-4af6-993e-8829ab44daed
-  open: false
-
-
-
-# Ordered alphabetically **by job description URL**
-
-- title: "Support Lead"
-  description: /jobs/support-lead/
-  salary: 87337
   apply:
   open: false
 - title: "Database Specialist"
   description: /jobs/specialist/database/
-  salary: 95000
-  apply: https://jobs.lever.co/gitlab/8b711f1c-d378-4383-a027-bac550aeee6d
-  open: false
-
-- title: "Senior Backend Developer, Distributed Systems Specialist"
-  description: /jobs/specialist/distributed-systems/
+  salary: 124000
+  salary source: Stack Overflow
   apply:
   open: false
 - title: "Issue Triage Specialist"
   description: /jobs/specialist/issue-triage/
-  salary: 87337
+  salary: 120000
+  salary source: Same as Developer
   apply:
   open: false
 - title: "Technical Writer"
   description: /jobs/technical-writer/
-  salary: 65803
-  apply:
-  open: false
-
-- title: "Technical Writing Lead"
-  description: /jobs/technical-writing-lead/
-  salary: 65803
-  apply: https://jobs.lever.co/gitlab/945d2740-cdd1-429f-9e2b-ea84022549c0
-  open: false
-
-- title: "UX Lead"
-  description: /jobs/ux-lead/
-  salary: 85843
+  salary: 102981
+  salary source: Aventador
   apply:
   open: false
 - title: "UX Designer"
   description: /jobs/ux-designer/
-  salary: 85843
+  salary: 120000
+  salary source: Marketing Compensation Survey
   apply:
   open: false
 - title: "UX Researcher"
   description: /jobs/ux-designer/
-  salary: 82000
+  salary: 106610
+  salary source: E-team
   apply:
   open: false
-
 - title: "VP of Engineering"
   description: /jobs/vp-of-engineering/
-  apply: https://jobs.lever.co/gitlab/afc7ce7c-ccc8-4769-983a-617106efc48f
+  apply:
   open: false
 - title: "VP of Partnerships"
@@ -515,18 +311,69 @@
 - title: "Web/UX Designer"
   description: /jobs/web-ux-designer/
-  salary: 85843
-  apply: https://jobs.lever.co/gitlab/2f13eace-2bde-477d-bb58-2eb53997111c
+  salary: 120000
+  salary source: Marketing Compensation Survey
+  apply:
+  open: false
+
+- title: "People Operations Analyst"
+  description: /jobs/people-ops-analyst/
+  salary: 100000
+  salary source: Aventador
+  apply:
+  open: false
+
+- title: "People Operations Specialist"
+  description: /jobs/people-ops-specialist/
+  salary: 88042
+  salary source: Aventador
+  apply:
+  open: false
+
+- title: "People Operations Generalist"
+  description: /jobs/people-ops-generalist/
+  salary: 95308
+  salary source: Aventador
+  apply:
+  open: false
+
+- title: "Marketing Operations Manager"
+  description: /jobs/marketing-operations-manager/
+  salary: 100000
+  salary source: Aventador
+  apply:
+  open: false
+
+- title: "Sales Administrator"
+  description: /jobs/sales-administrator/
+  salary: 72820
+  salary source: Aventador
+  apply:
   open: false
 - title: "People Business Partner"
   description: /jobs/people-business-partner/
-  apply: https://jobs.lever.co/gitlab/d92bc500-ac70-4fa6-b1f7-7413d7226594
+  apply:
+  open: false
+
+- title: "Services Support"
+  description: /jobs/services-support/
+  salary: 82000
+  salary source: Aventador
+  apply:
   open: false
 - title: "Services Support Lead"
   description: /jobs/services-support-lead/
-  apply: https://jobs.lever.co/gitlab/dd2c83dd-66f8-4c5e-bea7-2e16bbeb819d
+  apply:
   open: false
+- title: "Associate Social Marketing Manager"
+  description: /jobs/associate-social-marketing-manager/
+  salary: 76000
+  salary source: Aventador
+  apply:
+  open: false
+
+
   # Ordered alphabetically **by job description URL**

data/pets.yml

@@ -197,6 +197,10 @@
   picture: pickle.jpg
   human: smcgivern
   story: Pickle is a Scottish cat with a love of sitting on keyboards and trackpads, or anything her tin openers are paying attention to instead of her.
+- name: Petunia
+  picture: petunia.jpg
+  human: Celesta Smith
+  story: Petunia is a rescue from Mississippi. She was adopted by Celesta in 2016. Petunia was very ill and was in need of love and attention, however she is now very healthy and loves playing in local dog parks! 
 - name: You?
   picture: ../../gitlab-logo-extra-whitespace.png
   story:  |

data/promo.yml

-text: "GitLab 10.3 Released with Static Application Security Testing and Browser Performance Testing"
+text: "GitLab 10.3 released with Static Application Security Testing, Browser Performance Testing, and much more!"
 link: '/2017/11/22/gitlab-10-3-released/'

data/team.yml

@@ -606,7 +606,7 @@
 - name: James Lopez
   locality: A Coruña
   country: Spain
-  role: <a href="https://about.gitlab.com/jobs/developer/">Developer</a>
+  role: <a href="https://about.gitlab.com/jobs/developer/">Senior Developer</a>
   reports_to: Platform Engineering Manager
   picture: james.png
   twitter: jlopezofficial
@@ -972,8 +972,8 @@
           When she's not typing, you will find her behind the camera, or in a plane, for being behind her camera somewhere else.
 - name: Fatih Acet
-  locality: Istanbul
-  country: Turkey
+  locality: Amsterdam
+  country: Netherlands
   role: <a href="https://about.gitlab.com/jobs/frontend-engineer/">Senior Frontend Engineer</a>
   reports_to: Frontend Engineering Manager
   picture: fatih.png
@@ -991,9 +991,9 @@
               <li><a href="https://docs.gitlab.com/ee/user/project/merge_requests/resolve_conflicts.html">Merge conflict</a> <a href="/jobs/expert/">expert</a></li>
               <li><a href="https://docs.gitlab.com/ee/development/fe_guide/vue.html">Vue.js</a> <a href="/jobs/expert/">expert</a></li>
   story:  |
-          Based on Istanbul, Fatih is a Frontend Engineer who is passionate about delivering solid Frontend code.
+          Fatih is a Frontend Engineer who is passionate about delivering solid Frontend code.
           He loves to see the things he created used by thousands of others.
-          When not working, Fatih likes playing video games and exploring new EDM hits.
+          When not working, Fatih likes spending time with his son and exploring new EDM hits.
           He also believes that one day he will be good at making Latte arts.
 - name: Eliran Mesika
@@ -1581,7 +1581,7 @@
 - name: Emily von Hoffmann
   locality: Sunnyvale, CA
   country: USA
-  role: <a href="https://about.gitlab.com/jobs/content-editor/">Jr. Content Editor</a>
+  role: <a href="https://about.gitlab.com/jobs/associate-social-marketing-manager/">Associate Social Marketing Manager</a>
   reports_to: Content Marketing Manager
   picture: emilyvonhoffmann.JPG
   twitter: emvonhoffmann
@@ -1876,7 +1876,7 @@
   reports_to: CI/CD Lead
   picture: matija.png
   twitter: matteeyah
-  gitlab: cmattrex
+  gitlab: matteeyah
   departments:
     - Engineering
     - Marketing
@@ -3265,8 +3265,8 @@
           Joining December 4th
 - name: Celesta Smith
-  locality: Philadelphia, PA 
-  country: USA 
+  locality: Philadelphia, PA
+  country: USA
   role: <a href="https://about.gitlab.com/jobs/recruiter/">Recruiter</a>
   reports_to: Chief Culture Officer
   picture: celestasmith.png
@@ -3276,11 +3276,11 @@
     - People Operations
   story:  |
           Prior to working at Gitlab, Celesta worked in the staffing world, where she obtained recruiting experience in multiple different fields.
-          Outside of work, you can find Celesta on the tennis court, visiting local breweries, or having a hiking adventure. 
-          Make sure you check out my adorable puppy Petunia on our pets page! 
+          Outside of work, you can find Celesta on the tennis court, visiting local breweries, or having a hiking adventure.
+          Make sure you check out my adorable puppy Petunia on our pets page!
 - name: Michael Hamilton
-  locality: Santa Barbara    
+  locality: Santa Barbara
   country: USA
   role: <a href="https://about.gitlab.com/jobs/sales-development-representative/">Sales Development Representative</a>
   reports_to: Sales Development Representative Lead
@@ -3290,7 +3290,7 @@
   departments:
     - Marketing
   story:  |
-          Prior to working at Gitlab, Michael was developing his sales skills 
+          Prior to working at Gitlab, Michael was developing his sales skills
           at curvature. He loves to rock climb, play with his dog, and build
           awesome things!
@@ -3374,6 +3374,19 @@
   story:  |
           Joining December 18th
+- name: P.H.
+  locality:
+  country:
+  role: <a href="https://about.gitlab.com/jobs/technical-account-manager/">Technical Account Manager</a>
+  reports_to: Director of WW Customer Success
+  picture: ../gitlab-logo-extra-whitespace.png
+  twitter:
+  gitlab:
+  departments:
+    - Customer Success
+  story:  |
+          Joining December 20th
+
 - name: K.O.
   locality:
   country:

source/contributing/index.html.haml

@@ -7,43 +7,66 @@ extra_css:
   - contributing.css
 ---
 .wrapper
-  .contributing-container
-    .contributing-overlay
-      .contributing-content
-        %h1 Contributing to GitLab
-#content
-  .container-contributing
-    .row
-      .col-sm-6
-        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md"}
-          .link-box.single
-            %h4 Contributing Guidelines
-            If you want to contribute to GitLab, make sure to read and follow the contributing guidelines.
-      .col-sm-6
-        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md"}
-          .link-box
-            %h4 Contributing Process
-            Contributors and maintainers should know what to expect from each other in the contribution process.
-            This is described here.
-    .row
-      .col-sm-6
-        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#feature-proposals"}
-          .link-box
-            %h4 Feedback and Feature Proposals
-            Do you have any feedback, a suggestion or want to hear what others have to say? Share in a feature proposal.
-      .col-sm-6
-        %a{href: "/development/"}
-          .link-box.single
-            %h4 Sponsor the development of new features
-            If you want us to implement a certain feature, you can sponsor us to do so.
-    .row
-      .col-sm-6
-        %a{href: "https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=Accepting+Merge+Requests"}
-          .link-box.single
-            %h4 Accepting Merge Requests
-            You can find out if we are accepting merge requests for certain suggested features here.
-      .col-sm-6
-        %a{href: "/handbook/product/technical-writing/community-writers/"}
-          .link-box
-            %h4 Writing technical articles as a Guest Writer
-            Do you have any knowledge you'd like to share with our community? Find out how to write technical articles for the GitLab Docs.
+  .page-illustrated-header-container
+    .container
+      .header-container-content
+        %h1
+          Contributing to GitLab
+  #content
+    .wrapper.container.contributing-content{role: "main"}
+      .block
+        .block-content
+          %h2.block-title Introduction
+          %p.text-center
+            We want to make it as easy as possible for GitLab users to become GitLab contributors, so we’ve created this guide to help you get started. We have multiple tracks to cater to people of varying experience levels.
+          %p.text-center
+            If you’re uncomfortable getting into open source development right away, you may want to consider the Documentation or Translation tracks. Documentation and Translation are both just as important as code, and we'd be happy to have your contributions.
+      
+      .block
+        .block-content
+          %h2.block-title Development
+          :markdown
+            These instructions are for development of GitLab Community Edition specifically. Please note that use of the GitLab Development Kit is currently experimental on Windows. macOS or Linux are recommended for the best contribution experience.
+
+            1. Download and setup the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit), see the [GDK README](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/README.md) for instructions on setting it up and [Troubleshooting](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/troubleshooting.md) if you get stuck.
+            1. Fork the GitLab CE project.
+            1. Choose an issue to work on.
+                * You can find easy issues by [looking at issues labeled Accepting Merge Requests and sorting issues by weight](https://gitlab.com/gitlab-org/gitlab-ce/issues?assignee_id=0&label_name%5B%5D=Accepting%20Merge%20Requests&sort=weight_asc), low-weight issues will be the easiest to accomplish.
+                * Be sure to comment and verify no one else is working on the issue, and to make sure we’re still interested in a given contribution.
+                * You may also want to comment and ask for help if you’re new or if you get stuck. We’re happy to help!
+            1. Add the feature or fix the bug you’ve chosen to work on.
+            1. Open a merge request. The earlier you open a merge request, the sooner you can get feedback. You can mark it as a Work in Progress to signal that you’re not done yet.
+            1. Add tests and documentation if needed, as well as [a changelog entry](https://docs.gitlab.com/ee/development/changelog.html).
+            1. Make sure the test suite is passing.
+            1. Wait for a reviewer. You’ll likely need to change some things once the reviewer has completed a code review for your merge request. You may also need multiple reviews depending on the size of the change.
+            1. Get your changes merged!
+
+            For more information, please see the [Developer Documentation](https://docs.gitlab.com/ee/development/README.html).
+
+      .block
+        .block-content
+          %h2.block-title Documentation
+          :markdown
+            See the [Documentation Styleguide](https://docs.gitlab.com/ee/development/doc_styleguide.html) and [Writing Documentation](https://docs.gitlab.com/ee/development/writing_documentation.html) pages for important information on writing documentation for GitLab.
+
+            1. Visit [docs.gitlab.com](https://docs.gitlab.com) for the latest documentation for GitLab CE/EE, GitLab Runner, and GitLab Omnibus.
+            1. Find a page that’s lacking important information or that has a spelling/grammar mistake.
+            1. Click the "Edit this page" link at the bottom of the page.
+                * Note that this will most likely link you to the GitLab EE repository, most features are available in GitLab CE and you'll likely want to contribute to CE instead. Simply replace `gitlab-ee` in the URL with `gitlab-ce`, e.g. `https://gitlab.com/gitlab-org/gitlab-ee/blob/master/doc/administration/container_registry.md` would become `https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/administration/container_registry.md`.
+            1. Fork the relevant project and modify the documentation in GitLab’s web editor.
+            1. Open a merge request.
+            1. Wait for a review, you may need to change things if a reviewer requests it.
+            1. Get your changes merged!
+
+            For those interested in writing full technical articles, we also have a [GitLab Community Writers Program](https://about.gitlab.com/handbook/product/technical-writing/community-writers/) which includes compensation for writing technical articles.
+
+      .block
+        .block-content
+          %h2.block-title Translation
+          :markdown
+            Please note that GitLab is in the process of being internationalized. Not all pages have been updated to be translatable, and all languages other than English are incomplete. For more information visit [the documentation](https://docs.gitlab.com/ee/development/i18n/translation.html).
+
+            1. Visit our [Crowdin project](https://translate.gitlab.com/) and sign up.
+            1. Find a language you’d like to contribute to.
+            1. Improve existing translations, vote on new translations, and/or contribute new translations to your given language.
+            1. Once approved, your changes will automatically be included in the next version of GitLab!

source/direction/template.html.md.erb

@@ -276,7 +276,7 @@ Moonshots are big hairy audacious goals that may take a long time to deliver.
 ## Scope
-[Our vision](#vision) is to replace disparate DevOps toolchains with a single integrated application that is pre-configured to work by default across the complete DevOps lifecycle.
+[Our vision](#vision) is to replace disparate DevOps toolchains with a single integrated application that is pre-configured to work by default across the complete DevOps lifecycle. Consider viewing [the presentation of our plan for 2018](https://about.gitlab.com/2017/10/11/from-dev-to-devops/).
 ### Inside out scope

source/gitlab-com/index.html.haml

@@ -22,7 +22,7 @@ extra_js:
       %h2
         Below is the GitLab.com hosted SaaS offering, you can host it yourself with our #{link_to 'Products', '/products'}
       %h2
-        We ❤️ open source. Public projects get all Gold plan features for free.
+        We ❤️ open source. Public projects and groups get all Gold plan features for free.
       %br/
       - data.gitlab_com.prices.free_plan do |plan|
         .col-md-4.col-lg-3.col-lg-offset-0.col-md-offset-2

source/handbook/build/index.html.md

@@ -159,32 +159,13 @@ Unless your work is related to the security, all other work is carried out in pr
 ## Resources
-When using any of the resources listed below, same rules apply:
-* Consider the cost and whether anything can be done to reduce the cost.
-* You can boot up as many machines as you need.
-* It is your responsibility to clean up after yourself; if a machine is not used,
-remove it.
-* If you observe any resource that is running for long periods of time,
-ask the person responsible whether the machine is still in use.
-* Prepend your username to any resource you start. Eg. if your name is Jane Doe, resource
-should be named `janedoe-machine-for-testing`.
-
-### GCP
-
-Every team member has access to `testground` project at [Google Cloud Platform](https://console.cloud.google.com/).
-If you don't have access, ask the team lead by creating issue in [Build team issue tracker][issue tracker] and label it `Access Request`.
-
-### Digital Ocean
-
-Every team member has access to [dev-resources project](https://gitlab.com/gitlab-com/dev-resources/) which allows everyone
-to create and delete machines on demand.
-
-### AWS
-
-Team does not have access to AWS accounts. In case you need an AWS
-resource, ask the team lead for access by creating issue in [Build team issue tracker][issue tracker] and label it `Access Request`. Please supply the details
-on what type of access you need.
+General resources available to developers are listed in the
+[Engineering handbook](/handbook/engineering/#resources).
+In the Build team specifically, everyone should have access to the `testground`
+project on [Google Cloud Platform](https://console.cloud.google.com/). If you
+don't have access, ask the team lead by creating issue in
+[Build team issue tracker][issue tracker] and label it `Access Request`.
 ## Cloud Images

source/handbook/revenue-ops/customer-lifecycle/index.html.md → source/handbook/business-ops/customer-lifecycle/index.html.md

 ---
 layout: markdown_page
-title: "Revenue Operations - Customer Lifecycle"
+title: "Business Operations - Customer Lifecycle"
 ---
 ## On this page
@@ -26,7 +26,7 @@ However, there are more granular steps within the above milestones that are used
 | Marketo Qualified Lead | [Lead or Contact] |  MQL |
 | Accepted Lead | [Lead or Contact] |  Accepted |
 | Qualifying | [Lead or Contact] |  Qualifying |
-| Qualified Lead | [Opportunity] | 0 - Pre AE Qualified |
+| Pre Sales Accepted Opportunity | [Opportunity] | 0 - Pending Acceptance |
 | [Sales Accepted Opportunity] | [Opportunity] | 1 - Discovery |
 | Sales Qualified Opportunity | [Opportunity] | 2 Scoping - 5 Negotiating |
 | Customer | [Opportunity] | 6-Closed Won |
@@ -36,6 +36,6 @@ For the definition of the stage please click the record type link.
 When going from Qualifying to Qualified Lead the lead is duplicated to an opportunity, and the lead is set to qualified and not being used anymore.
-[Lead or Contact]: /handbook/revenue-ops/database-management/#lead--contact-statuses
+[Lead or Contact]: /handbook/business-ops/database-management/#lead--contact-statuses
 [Opportunity]: /handbook/sales/#opportunity-stages
 [Sales Accepted Opportunity]: /handbook/marketing/marketing-sales-development/sdr/#criteria-for-sales-accepted-opportunity-sao

source/handbook/revenue-ops/database-management/index.html.md → source/handbook/business-ops/database-management/index.html.md

 ---
 layout: markdown_page
-title: "Revenue Operations - Database Management"
+title: "Business Operations - Database Management"
 ---
 <a name="topofpage"></a>
 ## On this page
@@ -11,7 +11,7 @@ title: "Revenue Operations - Database Management"
 ## Lead Management   
-We follow the steps detailed in the [demand waterfall](/handbook/revenue-ops/customer-lifecycle/#demand-waterfall-) to track the different milestones prospective customers go through as they learn about GitLab and interact with our sales and marketing teams.   
+We follow the steps detailed in the [demand waterfall](/handbook/business-ops/customer-lifecycle/#demand-waterfall-) to track the different milestones prospective customers go through as they learn about GitLab and interact with our sales and marketing teams.   
 ### MQL Definition  
 A Marketo Qualified Lead is a lead that has reached a certain threshold, we have determined to be 90 points, based on demographic, firmographic and/or behavioral information. The [MQL score](https://docs.google.com/a/gitlab.com/document/d/1_kSxYGlIZNNyROLda7hieKsrbVtahd-RP6lU6y9gAIk/edit?usp=sharing) is comprised of various actions and/or profile data that are weighted with positive or negative point values.  
@@ -23,7 +23,29 @@ Any record with a `Person Score` greater than or equal to 50 points will be inse
 Strategic = 5000+ users  
 Large = 751-4999 users   
 Mid-Market = 101-750 users   
-Small-Medium Business (SMB) = 1-100 users    
+Small-Medium Business (SMB) = 1-100 users   
+
+#### How Segments Are Determined
+
+Sales Segmentation can be determined by a few different criteria in Salesforce:
+
+On the lead object, it can be defined by the following fields:
+1. `Number of Developers Bucket` field, which is captured on various web forms including EE trial signups
+1. `How Many Developers Do You Have?` qualifying question, which is asked during the qualification process
+
+On the lead object, the Sales Segmentation will be determined by the larger of the two values. So if the `Number of Developers` field is `>100` but the `How Many Developers Do You Have?` field is `200`, the lead record will be categorized as `Mid-Market`.
+
+On the account object, it can be defined by the following fields:
+1. `How Many Developers Do You Have?` field, which is populated on the opportunity object after lead conversion
+1. `IT + TEDD employees` The sum of IT and [TEDD](https://discoverorg.com/discoverorg-sales-intelligence-platform/data-sets-for-marketing-sales-and-staffing/technology-engineering-design-and-development-tedd-dataset/) employees from DiscoverOrg.
+1. `Number of Licenses` field, which is populated from Zuora and captures the number of licenses that the customer has purchased
+1. Manual override of the `Potential EE Users` field. If you decide to overwrite the `Potential EE Users` field, please note that it must be more than the `Number of Licenses` since a customer cannot have less potential users than they purchased.
+
+Note that the default value for leads and accounts where all of the controlling fields are `NULL` or `0` is `Unknown`.
+
+#### Parent Sales Segmentation
+
+In addition to the current account Sales Segmentation, the Parent Sales Segmentation Field is displayed on the account record as well. The purpose of this field is to show the potential users of the parent account, as it is possible that the current account you are viewing has a potential user count of 100, for example- as it may be a specific location, business unit, or department- but that the parent account may have potential users numbering in the thousands. Please note that the child accounts' Potential EE Users do not roll up to the parent account.
 #### Region/Vertical   
 **Asia Pacific ([APAC](https://docs.google.com/document/d/1Ar0Y49XF0pnvWjhr5-jr0MNKdxfRY2FkS4x9y7KCZw8/edit#))**: Regional Director - Michael Alessio   

source/handbook/revenue-ops/index.html.md → source/handbook/business-ops/index.html.md

 ---
 layout: markdown_page
-title: "Revenue Operations"
+title: "Business Operations"
 ---
 <a name="topofpage"></a>
 ## On this page
@@ -11,14 +11,15 @@ title: "Revenue Operations"
 ## In this section
-- [Customer Lifecycle](/handbook/revenue-ops/customer-lifecycle)
-- [Database Management](/handbook/revenue-ops/database-management)
-- [Reporting](/handbook/revenue-ops/reporting)
+- [Customer Lifecycle](/handbook/business-ops/customer-lifecycle)
+- [Database Management](/handbook/business-ops/database-management)
+     - [Tech Stack Details](/handbook/business-ops/tech-stack/)
+- [Reporting](/handbook/business-ops/reporting)
 ## Purpose   
-Since parts of all three functional groups work closely together and operational management of the database needs to seamlessly move from one functional group to another, this section is a singular reference point for all three teams to find the most up-to-date workflows, routing, rules and definition sets. Overview of workflow and operational processes that overlap the [Sales](https://about.gitlab.com/handbook/sales), [Marketing](https://about.gitlab.com/handbook/marketing) and [Customer Success](https://about.gitlab.com/handbook/customer-success/) teams. A singular repository to track all tools, license allocation, admins and contracts for the combined Marketing & Sales Operations tech stack. Tips, tricks and how to's for the various applications and external resources that will help user be more productive in the business systems.    
+Overview of systems, workflows and processes for the three functional groups - [Sales](/handbook/sales), [Marketing](/handbook/marketing) and [Customer Success](/handbook/customer-success/) - that work closely together. This section is a singular reference point for operational management of the database and where the most up-to-date workflows, routing, rules and definition sets are managed.  Tracking all tools, license allocation, admins and contracts for the combined Marketing & Sales Operations tech stack. Tips, tricks and how to's for the various applications and external resources that will help user be more productive in the business systems.    
 ## Reaching the Teams (internally)   
@@ -27,7 +28,7 @@ Since parts of all three functional groups work closely together and operational
     - [Salesforce](https://gitlab.com/gitlab-com/salesforce/issues) - Salesforce specific needs, issues and questions
     - [Marketing](https://gitlab.com/gitlab-com/marketing/issues) - All issues related to website, product, design, events, webcasts, lead routing, social media and community relations
     - [Customer Success SA Service Desk](https://gitlab.com/gitlab-com/customer-success/sa-service-desk/issues) - your go to place for pre-sales, post-sales, customer training and professional services
-- **Email**: You can send an email to the respective team you wish to reach, please reference the 'Email, Slack, and GitLab Groups and Aliases' for the appropriate alias.  
+- **Email**: Please use the 'Email, Slack, and GitLab Groups and Aliases' document for the appropriate team alias.  
 - **Slack**: A short list of the primary Slack channels used by these respective teams  
     - `#sales`
     - `#marketing`
@@ -38,33 +39,160 @@ Since parts of all three functional groups work closely together and operational
     - `#lead-questions`
-## Tech Stack   
-| Applications & Tools | Who Should Have Access | Whom to Contact w/Questions | Admin(s) |
-| :--- | :--- | :--- | :--- |
-| **Clearbit** | Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR | **JJ Cordz (primary)**<br>Francis Aquino | JJ Cordz<br>Francis Aquino |
-| **DiscoverOrg** | Mid-Market AEs<br>Outbound SDR | **Francis Aquino** | Francis Aquino |
-| **DoGood** | Online Marketing<br>SDR Team Lead | **Nicholas Flynn** | Nicholas Flynn<br>JJ Cordz |
-| **Drift** | Inbound BDR | **Molly Young (primary)**<br>JJ Cordz (integration) | JJ Cordz |
-| **FunnelCake** | Sr Director Demand Gen<br>Marketing OPS<br>Online Marketing |  | JJ Cordz |
-| **Google Analytics** | Sr Director Demand Gen<br>Marketing OPS<br>Online Marketing<br>Product Marketing<br>Content Marketing | **JJ Cordz** | JJ Cordz |
-| **Google Tag Manager** | Online Marketing |  | JJ Cordz |
-| **GovWin IQ** | Sales - Federal | **Francis Aquino** | Francis Aquino |
-| **InsightSquared** | Executives<br>Sales Leadership | **Francis Aquino** | Francis Aquino |
-| **LeanData** | Marketing OPS<br>Sales OPS | **JJ Cordz (primary)**<br>Francis Aquino | JJ Cordz<br>Francis Aquino |
-| **LicenseApp** | Access via GitLab credentials | **Francis Aquino** |  |
-| **LinkedIn Sales Navigator** | Sales Leadership<br>Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR | **JJ Cordz** | JJ Cordz<br>Francis Aquino |
-| **Marketo** | Marketing OPS<br>Online Marketing<br>Content Marketing<br>Field Marketing | **JJ Cordz** | JJ Cordz |
-| **Optimizely** | Online Marketing |  | JJ Cordz |
-| **Outreach.io** | Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR | **Francis Aquino (primary)**<br>JJ Cordz<br>Chet Backman | Francis Aquino<br>JJ Cordz<br>Chet Backman |
-| **Piwik** | Online Marketing |  | Online Marketing Manager |
-| **Salesforce** | Sales Leadership<br>Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR<br>Solutions Architects<br>Marketing OPS | *Not related to quotes or lead routing*: **Francis Aquino**<br><br>*Lead Routing/Scoring/Source*: **JJ Cordz** | Francis Aquino<br>JJ Cordz |
-| **Sertifi** | Account Executives<br>Account Managers | **Francis Aquino** | Francis Aquino |
-| **Terminus** | Online Marketing | **Emily Kyle (primary)**<br>JJ Cordz | JJ Cordz |
-| **Unbounce** | Marketing OPS<br>Online Marketing<br>Content Marketing<br>Field Marketing<br>Design | **JJ Cordz** | JJ Cordz |
-| **WebEx** | Marketing OPS | **JJ Cordz** | JJ Cordz |
-| **Zendesk** | Access via Salesforce | **Lee Matos** | Francis Aquino |
-| **Zoom** | Access via GitLab credentials | **PeopleOPS** | PeopleOPS |
-| **Zuora** | Access via Salesforce | **Wilson Lau (primary)**<br>Francis Aquino (secondary) | Francis Aquino |
+## Tech Stack     
+
+<div class="tg-wrap"><table class="tg">
+  <tr>
+    <th class="tg-k6pi">Applications & Tools</th>
+    <th class="tg-031e">Who Should Have Access</th>
+    <th class="tg-yw4l">Whom to Contact w/Questions</th>
+    <th class="tg-yw4l">Admin(s)</th>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#clearbit">Clearbit</a></strong></td>
+    <td>Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR</td>
+    <td><strong>JJ Cordz (primary)</strong><br>Francis Aquino</td>
+    <td>JJ Cordz<br>Francis Aquino</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#discoverorg">DiscoverOrg</a></strong></td>
+    <td>Mid-Market AEs<br>Outbound SDR</td>
+    <td><strong>Francis Aquino</strong></td>
+    <td>Francis Aquino</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#dogood">DoGood</a></strong></td>
+    <td>Online Marketing<br>SDR Team Lead</td>
+    <td><strong>Nicholas Flynn</strong></td>
+    <td>Nicholas Flynn<br>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong>Drift</strong></td>
+    <td>Inbound BDR</td>
+    <td><strong>Molly Young (primary)</strong><br>JJ Cordz (integration)</td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong>FunnelCake</strong></td>
+    <td>Sr Director Demand Gen<br>Marketing OPS<br>Online Marketing</td>
+    <td></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#google-analytics">Google Analytics</a></strong></td>
+    <td>Sr Director Demand Gen<br>Marketing OPS<br>Online Marketing<br>Product Marketing<br>Content Marketing</td>
+    <td><strong>JJ Cordz</strong></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#google-tag-manager">Google Tag Manager</a></strong></td>
+    <td>Online Marketing</td>
+    <td></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong>GovWin IQ</strong></td>
+    <td>Sales - Federal</td>
+    <td><strong>Francis Aquino</strong></td>
+    <td>Francis Aquino</td>
+  </tr>
+  <tr>
+    <td><strong>InsightSquared</strong></td>
+    <td>Executives<br>Sales Leadership</td>
+    <td><strong>Francis Aquino</strong></td>
+    <td>Francis Aquino</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#leandata">LeanData</a></strong></td>
+    <td>Marketing OPS<br>Sales OPS</td>
+    <td><strong>JJ Cordz (primary)</strong><br>Francis Aquino</td>
+    <td>JJ Cordz<br>Francis Aquino</td>
+  </tr>
+  <tr>
+    <td><strong>LicenseApp</strong></td>
+    <td>Access via GitLab credentials</td>
+    <td><strong>Francis Aquino</strong></td>
+    <td></td>
+  </tr>
+  <tr>
+    <td><strong>LinkedIn Sales Navigator</strong></td>
+    <td>Sales Leadership<br>Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR</td>
+    <td><strong>JJ Cordz</strong></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#marketo">Marketo</a></strong></td>
+    <td>Marketing OPS<br>Online Marketing<br>Content Marketing<br>Field Marketing</td>
+    <td><strong>JJ Cordz</strong></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#optimizely">Optimizely</a></strong></td>
+    <td>Online Marketing</td>
+    <td></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#outreachio">Outreach.io</a></strong></td>
+    <td>Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR</td>
+    <td><strong>Francis Aquino (primary)</strong><br>JJ Cordz<br>Chet Backman</td>
+    <td>Francis Aquino<br>JJ Cordz<br>Chet Backman</td>
+  </tr>
+  <tr>
+    <td><strong>Piwik</strong></td>
+    <td>Online Marketing</td>
+    <td></td>
+    <td>Online Marketing Manager</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#salesforce">Salesforce</a></strong></td>
+    <td>Sales Leadership<br>Account Executives<br>Account Managers<br>Outbound SDR<br>Inbound BDR<br>Solutions Architects<br>Marketing OPS</td>
+    <td>Not related to quotes or lead routing: <strong>Francis Aquino</strong><br><br>Lead Routing/Scoring/Source: <strong>JJ Cordz</strong></td>
+    <td>Francis Aquino<br>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#sertifi">Sertifi</a></strong></td>
+    <td>Account Executives<br>Account Managers</td>
+    <td><strong>Francis Aquino</strong></td>
+    <td>Francis Aquino</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#terminus">Terminus</a></strong></td>
+    <td>Online Marketing</td>
+    <td><strong>Emily Kyle (primary)</strong><br>JJ Cordz</td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#unbounce">Unbounce</a></strong></td>
+    <td>Marketing OPS<br>Online Marketing<br>Content Marketing<br>Field Marketing<br>Design</td>
+    <td><strong>JJ Cordz</strong></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong>WebEx</strong></td>
+    <td>Marketing OPS</td>
+    <td><strong>JJ Cordz</strong></td>
+    <td>JJ Cordz</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#zendesk">Zendesk</a></strong></td>
+    <td>Access via Salesforce</td>
+    <td><strong>Lee Matos</strong></td>
+    <td>Francis Aquino</td>
+  </tr>
+  <tr>
+    <td><strong>Zoom</strong></td>
+    <td>Access via GitLab credentials</td>
+    <td><strong>PeopleOPS</strong></td>
+    <td>PeopleOPS</td>
+  </tr>
+  <tr>
+    <td><strong><a href="/handbook/business-ops/tech-stack/#zuora">Zuora</a></strong></td>
+    <td>Access via Salesforce</td>
+    <td><strong>Wilson Lau (primary)</strong><br>Francis Aquino (secondary)</td>
+    <td>Francis Aquino</td>
+  </tr>
+</table></div>
 [Operations License Tracking & Contract Details](https://docs.google.com/a/gitlab.com/spreadsheets/d/1-W0rmZalDOpTNQf4K50DZ1y3slgmNSrPVPuF6_Hfz6s/edit?usp=sharing) (document can only be accessed by GitLab team members)
@@ -101,7 +229,6 @@ Since parts of all three functional groups work closely together and operational
 ## Other Related Pages
 - [SDR Handbook](/handbook/marketing/marketing-sales-development/sdr/)
-- [Sales Operations](/handbook/sales/sales_ops/)
 - [Marketing Operations](/handbook/marketing/marketing-sales-development/marketing-operations/)   
 - [Customer Success](/handbook/customer-success/)