Commit 985f0ad8 authored by Hanif Smith-Watson's avatar Hanif Smith-Watson
Browse files

Malformed handbook links

parent 990d103e
......@@ -93,7 +93,7 @@
employee_or_customer_facing_app: null
notes: null
saas: null
handbook_link: "[ADP Guide for Pay Date](/handbook/finance/payroll/#pay-date), [ADP Guide for New Hires](/handbook/finance/payroll/#us) and [ADP Tech Stack Guide](handbook/finance/payroll/tech-stack-guide-adp)"
handbook_link: "[ADP Guide for Pay Date](/handbook/finance/payroll/#pay-date), [ADP Guide for New Hires](/handbook/finance/payroll/#us) and [ADP Tech Stack Guide](/handbook/finance/payroll/tech-stack-guide-adp)"
google_group: null
 
- title: Allocadia
......
......@@ -33,7 +33,7 @@ description: "This page defines Self-Managed and provides directions for Self-Ma
* Product Usage
* [Service Ping](https://docs.gitlab.com/ee/development/service_ping/) - Service ping data is sent voluntarily from an Instance. The User and Other Activity is captured as aggregated counts. Since not all customers send service ping data, or send just partial service ping data, there is an [Estimation Algorithm](https://about.gitlab.com/handbook/business-technology/data-team/data-catalog/xmau-analysis/estimation-xmau-algorithm.html) used for a more wholistic view of the overall usage.
* Product Usage data and use cases is further described [here](https://about.gitlab.com/handbook/business-technology/data-team/data-catalog/product-usage-data/).
* The systems overview of how the data is brought into GitLab can be seen [here](handbook/product/product-intelligence-guide/?#systems-overview).
* The systems overview of how the data is brought into GitLab can be seen [here](/handbook/product/product-intelligence-guide/#systems-overview).
## Self-Managed Analysis
 
......
......@@ -483,7 +483,7 @@ Sisense has great [embed docs](https://doc.periscopedata.com/article/embed-api)
 
### Skip unused Dashboard
 
In order to avoid unnecessary dashboard refreshes the option `Skip if unused` must be enabled by default. Sisense checks if the dashboard is used more than 10 minutes in the past 7 days and only if true it will start the scheduled refresh. This saves resources on our platform. Every quarter in the [data health and security audit](handbook/business-technology/data-team/data-management/#quarterly-data-health-and-security-audit) the Data Platform checks if this option is set. If this is not the case it will be switched on.
In order to avoid unnecessary dashboard refreshes the option `Skip if unused` must be enabled by default. Sisense checks if the dashboard is used more than 10 minutes in the past 7 days and only if true it will start the scheduled refresh. This saves resources on our platform. Every quarter in the [data health and security audit](/handbook/business-technology/data-team/data-management/#quarterly-data-health-and-security-audit) the Data Platform checks if this option is set. If this is not the case it will be switched on.
 
### Hardcoded HTML
 
......
......@@ -38,7 +38,7 @@ Our hope is that the GitLab Handbook is something that others want to emulate. T
### What's Next & Why
 
- **[Monorepo refactor:](https://gitlab.com/groups/gitlab-com/-/epics/282)** The [`www-gitlab-com`](https://gitlab.com/gitlab-com/www-gitlab-com/) project is home to multiple sub-sites including the blog, our marketing pages, and the GitLab Handbook which all deploy to the [about.gitlab.com](https://about.gitlab.com) domain. In order to ensure stability, accountability, and efficiency, we are working to separate and isolate these sub-sites into distinct projects within the main project. This will allow us to implement separate CI pipelines for each project, so that changes will only build, test, and deploy the relevant project.
- Digital Experience has [completed their initial rearchitecture](handbook/marketing/digital-experience/marketing-site-rearchitecture-project/), splitting the first batch of marketing pages to the [`gitlab-com/marketing/digital-experience/buyer-experience`](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) project.
- Digital Experience has [completed their initial rearchitecture](/handbook/marketing/digital-experience/marketing-site-rearchitecture-project/), splitting the first batch of marketing pages to the [`gitlab-com/marketing/digital-experience/buyer-experience`](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience) project.
- First step for our team likely involves splitting `/handbook` content from [`www-gitlab-com`](https://gitlab.com/gitlab-com/www-gitlab-com) into a new project and potentially hosting it on a separate domain (i.e. `handbook.gitlab.com`).
- **[Pipeline performance improvements:](https://gitlab.com/groups/gitlab-com/-/epics/255)** Getting the build and deploy time down to a reasonable level is one of the most important things we can do to encourage more collaboration among users already familiar with how to edit the handbook. Recent efforts have reduced the average build and deploy time by over 50% but there are still opportunities for further optimization, mostly around reducing the overall size of the project repository.
- **Evaluate Hugo as a replacement for Middleman:** We have already [ported the internal handbook to Hugo](https://gitlab.com/internal-handbook/internal-handbook.gitlab.io/-/merge_requests/549) and reduced build times by ~100x (from 3min to 16sec). The public handbook is significantly more complex and we will need to develop an incremental migration strategy.
......
......@@ -126,7 +126,7 @@ Note when viewing a deployment failure from the `#announcements` Slack channel,
 
Click on the diagram below to visit the announcement issue for more context and view an uncompressed image:
 
[![Pipeline Reorder](handbook/engineering/releases/gitlab-com-deployment-pipeline.png "pipeline diagram")](https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/2280)
[![Pipeline Reorder](/handbook/engineering/releases/gitlab-com-deployment-pipeline.png "pipeline diagram")](https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/2280)
 
Note the diagram has been upadted as part of increasing rollback availability by removing the [blocking nature of post-deployment migrations](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/585).
 
......
......@@ -151,7 +151,6 @@ Once a Hiring Manager has determined they want to move forward with a candidate,
 
If you would like the Hiring Manager to receive an email when the form has been received, you can go to the job setup for that req, select 'Forms' and edit the individual form you plan to send. The Recruiter, individual CES assigned to the candidate, and CES@gitlab.com will all automatically receive an email when the form is completed.
 
For more information, please visit the [Job Offer Process](handbook/source/handbook/hiring/talent-acquisition-framework/offer-process/) page.
 
### **Step 7: Justification (Engineering Only)**
 
......@@ -167,4 +166,4 @@ If there are any special circumstances regarding a known relocation for the cand
 
### **Step 9: Verbal Offer & Contract**
 
For details about these final stages, please visit the [Job Offer Process](handbook/source/handbook/hiring/talent-acquisition-framework/offer-process/) page.
For details about these final stages, please visit the Job Offer Process page.
......@@ -213,7 +213,7 @@ You will notice two small icons next to the selectors when you go to add one to
#### Building a Custom List
{: #list-creation}
<!-- DO NOT CHANGE THIS ANCHOR -->
You can find a guide for Field Marketing Lists [below](handbook/marketing/account-based-marketing/demandbase/#field-marketing-use-cases) as well.
You can find a guide for Field Marketing Lists [below](/handbook/marketing/account-based-marketing/demandbase/#field-marketing-use-cases) as well.
 
1. Click the database icon in the left-hand navigation menu
1. Select the list type you need under the database menu (Account Lists, Person Lists, Opportunity Lists)
......
......@@ -111,7 +111,7 @@ All Marketo templates will have 2 tokens added to them that the campaign owner s
- The partner MUST HAVE this utm on their link to the landing page otherwise they will not be routed leads
1. Processing Campaign for partner campaings is separate from the typical one. Do not activate both.
1. Processing smart campaign's smart list must reference `FORM 3146: Partners w/ consent+token` or another partner form (translations)
1. Set up asset expiration as [described here](handbook/marketing/marketing-operations/campaigns-and-programs/#step-4b-setting-landing-page--smart-campaign-expiration-asset-expiration), if needed.
1. Set up asset expiration as [described here](/handbook/marketing/marketing-operations/campaigns-and-programs/#step-4b-setting-landing-page--smart-campaign-expiration-asset-expiration), if needed.
1. (no setup needed) Marketo will process..
1. If there is a `Partner CRM ID`
1. Set `Vartopia Partner Account`
......
......@@ -12,7 +12,7 @@ description: "This page contains details regarding the process of verification f
 
## Overview
 
This page contains details regarding the process of verifying applications for [GitLab for Open Source Program](/solutions/open-source/). Because the GitLab for Open Source Program is part of GitLab's [Community Programs](handbook/marketing/community-relations/community-programs/), team members verify applications by using the the seven-step [Community Programs Automation Workflow](/handbook/marketing/community-relations/community-programs/automated-community-programs). See the handbook page on that workflow for details that pertain to all GitLab community programs.
This page contains details regarding the process of verifying applications for [GitLab for Open Source Program](/solutions/open-source/). Because the GitLab for Open Source Program is part of GitLab's [Community Programs](/handbook/marketing/community-relations/community-programs/), team members verify applications by using the the seven-step [Community Programs Automation Workflow](/handbook/marketing/community-relations/community-programs/automated-community-programs). See the handbook page on that workflow for details that pertain to all GitLab community programs.
 
## Program application form
 
......
......@@ -56,7 +56,7 @@ Beginning in FY22 and continuing through FY23, the Community Programs team is ad
 
### Inbound sales requests routing workflows
 
Sales team members receiving inbound requests regarding community programs, should adhere to the following workflow and route leads accordingly, using [Community Programs' email templates](handbook/marketing/community-relations/community-programs/community-program-applications/email-and-zendesk-macros/#zendesk-macros-and-email-templates) if desired:
Sales team members receiving inbound requests regarding community programs, should adhere to the following workflow and route leads accordingly, using [Community Programs' email templates](/handbook/marketing/community-relations/community-programs/community-program-applications/email-and-zendesk-macros/#zendesk-macros-and-email-templates) if desired:
 
| If the lead is inquiring about | Then take this action|
| ------------------------------ | --------------------- |
......
......@@ -215,7 +215,7 @@ The email should answer the following questions in the following order:
1. What is your call to action? What should you do?
1. Where should you go if you need support? If applicable, where do you provide feedback (e.g., forum, issue, other)? If additional updates will be provided, when and how will that information be shared?
 
To request an email, follow directions on [this page](handbook/marketing/marketing-operations/email-management/#request-non-demand-generation-emails)
To request an email, follow directions on [this page](/handbook/marketing/marketing-operations/email-management/#request-non-demand-generation-emails)
 
#### Sample email
 
......
......@@ -149,7 +149,7 @@ dataLayer.push(
```
### Program Asset Expiration
 
Starting in November 2022, teams within Marketo will transition to utilizing the [asset expiration feature](https://experienceleague.adobe.com/docs/marketo/using/product-docs/core-marketo-concepts/programs/working-with-programs/local-asset-expiration.html?lang=en#:~:text=Right%2Dclick%20on%20your%20desired,Choose%20an%20expiration%20date) added to the product in early 2022 as a way to declutter our expired landing pages and no longer relevant smart campaigns. Detailed instructions on this process can be found in our handbook on the [Campaigns and Programs](handbook/marketing/marketing-operations/campaigns-and-programs/) page.
Starting in November 2022, teams within Marketo will transition to utilizing the [asset expiration feature](https://experienceleague.adobe.com/docs/marketo/using/product-docs/core-marketo-concepts/programs/working-with-programs/local-asset-expiration.html?lang=en#:~:text=Right%2Dclick%20on%20your%20desired,Choose%20an%20expiration%20date) added to the product in early 2022 as a way to declutter our expired landing pages and no longer relevant smart campaigns. Detailed instructions on this process can be found in our handbook on the [Campaigns and Programs](/handbook/marketing/marketing-operations/campaigns-and-programs/) page.
 
### Product data in Marketo
 
......
......@@ -10,7 +10,7 @@ This research shadowing process is intended to ensure that stable counterparts h
 
## Shadower process
 
1. Identify the UX Researcher [assigned to your stage group](handbook/product/ux/ux-research/how-uxr-team-operates/#how-ux-researchers-are-assigned). This person will be your contact during this shadow process. Reach out to them and introduce yourself and let them know you’re starting research shadowing.
1. Identify the UX Researcher [assigned to your stage group](/handbook/product/ux/ux-research/how-uxr-team-operates/#how-ux-researchers-are-assigned). This person will be your contact during this shadow process. Reach out to them and introduce yourself and let them know you’re starting research shadowing.
1. Read through pages that are relevant to you and your project(s) within the [UX Research handbook section](/handbook/product/ux/ux-research/). Your researcher can answer any questions you may have.
 
### Problem Validation shadowing
......
......@@ -55,7 +55,7 @@ The [Buyer Experience Group Internal Handbook](https://internal-handbook.gitlab.
| Resource | Areas Covered |
| -------- | ------------- |
| [Deal Desk Handbook](/handbook/sales/field-operations/sales-operations/deal-desk/) | Standard Quote Configuration (new subscription, amend subscription, add-on quote creation, upgrade or product switch during subscription term, renewal, channel deals, true-ups, co-terms, Starter/Bronze End of Availability, SuperSonics, Professional Services), Non-Standard Quotes (Contract Resets, Concurrent Subscriptions, Multi-year Deals, Ramp deals), Alliance Marketplace Private Offers, and more. |
| [Sales Order Processing](handbook/sales/field-operations/order-processing/) | Account and opportunity creation, quote configuration, approvals process, opportunity booking requirements, closing an opportunity. |
| [Sales Order Processing](/handbook/sales/field-operations/order-processing/) | Account and opportunity creation, quote configuration, approvals process, opportunity booking requirements, closing an opportunity. |
| [Internal Support](/handbook/support/internal-support/) | Submitting all requests around licensing, subscription, trials, and grace periods. |
| [Licensing FAQ](https://about.gitlab.com/pricing/licensing-faq/) | Common questions around purchasing, licensing, billing, contacting sales, and more |
| [Finance and Legal Authorization Matrix](/handbook/finance/authorization-matrix/) | |
......
......@@ -51,7 +51,7 @@ Zuora Data to [Salesforce](#salesforce-sales-cloud) via [Zuora CPQ](#zuora-cpq)
 
![Go-To-Market Production SaaS Environments](/handbook/sales/images/gtm-production.png)
 
[Go-To-Market Integrated Environments](handbook/sales/field-operations/sales-systems/gtm-integrated-environments/)
[Go-To-Market Integrated Environments](/handbook/sales/field-operations/sales-systems/gtm-integrated-environments/)
 
### Key Reports / Dashboards
 
......
......@@ -901,7 +901,7 @@ The [Security Assurance sub-department](/handbook/security/security-assurance/)
 
The [Security Engineering sub-department's](/handbook/security/security-engineering-and-research/) focus in FY23 will continue to be in the direction of a proactive security stature. Adoption of additional automation and key technology integrations will help further increase efficiency and effectiveness. After the shift left accomplished last year, our ability to detect and remediate risks pre-production has improved. Building on this capability, improving visibility and alerting on vulnerabilities detected as close to code development as possible will be a new focus. Continued maturity of our infrastructure security, log aggregation, alerting, and monitoring will build upon the increased infrastructure visibility and observability accomplished last year. All of this will contribute towards minimizing risk and exposure in a proactive manner.
 
For FY23 the [Security Operations sub-department](handbook/security/security-operations/) will be committed to a focus on anti-abuse and incident response process maturity. Using established maturity frameworks, the program will focus on utilizing existing technologies with new expanded datasets supported by refined processes resulting in faster time to triage and short time to remediate. Additional focus on gaining a deeper understanding of security incidents, abuse, and causes will drive additional preventative practices. Altogether, this will result in fewer security incidents, less abuse, a more secure, and more reliable service for all GitLab users.
For FY23 the [Security Operations sub-department](/handbook/security/security-operations/) will be committed to a focus on anti-abuse and incident response process maturity. Using established maturity frameworks, the program will focus on utilizing existing technologies with new expanded datasets supported by refined processes resulting in faster time to triage and short time to remediate. Additional focus on gaining a deeper understanding of security incidents, abuse, and causes will drive additional preventative practices. Altogether, this will result in fewer security incidents, less abuse, a more secure, and more reliable service for all GitLab users.
 
Our newest sub-department, [Threat Management](/handbook/security/threat-management/):
FY23 began with the creation of a new sub-department known as Threat and Vulnerability Management. This department will contain our Red Team, Security Research Team, and a newly formed Vulnerability Management team. While the focus of the Red Team and Vulnerability Research teams will not change, the newly formed Vulnerability Management team will take an iterative approach to better understanding and managing vulnerabilities across all of GitLab.
......
......@@ -29,7 +29,7 @@ As a member of the [Security Assurance](/handbook/security/security-assurance/)
* Identifying control weaknesses and gaps (observations)
* Remediation recommendations
* Tracking remediation plans to completion
1. [Continuous Monitoring of GitLab's Security Controls](handbook/security/security-assurance/security-compliance/sec-controls.html) which are mapped to applicable regulatory requirements and security certifications/frameworks we have committed to.
1. [Continuous Monitoring of GitLab's Security Controls](/handbook/security/security-assurance/security-compliance/sec-controls.html) which are mapped to applicable regulatory requirements and security certifications/frameworks we have committed to.
* [User Access Reviews](/handbook/security/security-assurance/security-compliance/access-reviews.html)
* [Business Continuity Plan (BCP)](https://about.gitlab.com/handbook/business-technology/gitlab-business-continuity-plan/) and [Information System Continuity (ISCP)](https://about.gitlab.com/handbook/security/Information-System-Contingency-Plan-ISCP.html) testing
 
......
......@@ -72,7 +72,7 @@ In order to effectively identify, manage, and treat operational risks, GitLab ha
 
The Security Risk Team conducts security operational Risk Identification interviews with individuals operating in at least a Manager capacity/level at GitLab in order to identify security operational risks within their respective departments. Risks identified will always be framed in terms of threat sources and threat events, and then assessed against the likelihood of occurrence and the impact to GitLab if the risk event occurs. Additionally, these risks will be assessed against the current internal controls in place to determine the overall residual risk remaining.
 
For details of the scoring methodology used, refer to the [StORM Methodology](/handbook/security/security-assurance/security-risk/storm-program/storm-methodology.html#risk-factors-and-risk-scoring) page. For guidance on drafting risk language see the [Risk Drafting Guidance](handbook/security/security-assurance/security-risk/storm-program/index.html.md#risk-drafting-guidance) below. Risks will be quality reviewed by the Security Risk Manager or delegate and approval captured via comment in the GRC application.
For details of the scoring methodology used, refer to the [StORM Methodology](/handbook/security/security-assurance/security-risk/storm-program/storm-methodology.html#risk-factors-and-risk-scoring) page. For guidance on drafting risk language see the [Risk Drafting Guidance](/handbook/security/security-assurance/security-risk/storm-program/index.html.md#risk-drafting-guidance) below. Risks will be quality reviewed by the Security Risk Manager or delegate and approval captured via comment in the GRC application.
 
### Step 3: Risk Tracking and Reporting
 
......
......@@ -29,7 +29,7 @@ If the customer needs to go above the 5 users license seats, they would need to
1. Confirm whether the customer still have access to the paid features, if not we should unblock them with a 30 days temporary license.
1. Ask the customer to reach out to aws-sales@gitlab.com.
 
To escalate this request, follow the [ecalate to Sales workflow](handbook/support/license-and-renewals/workflows/working_with_sales.html#general-workflow) if there is already an organization for the customer in SFDC. If the SFDC organization does not exist or you have any questions regarding this the purchase through AWS Marketplace, please reach out to the Alliances team in `#alliances` slack channel.
To escalate this request, follow the [ecalate to Sales workflow](/handbook/support/license-and-renewals/workflows/working_with_sales.html#general-workflow) if there is already an organization for the customer in SFDC. If the SFDC organization does not exist or you have any questions regarding this the purchase through AWS Marketplace, please reach out to the Alliances team in `#alliances` slack channel.
 
- [Example case 1](https://gitlab.zendesk.com/agent/tickets/199133)
- [Example case 2](https://gitlab.zendesk.com/agent/tickets/324283)
......@@ -18,11 +18,11 @@ Below are some common areas for goal setting:
 
##### FRT and Ticket Assignment
 
Contributing towards our [first reply time target](handbook/support/performance-indicators/#service-level-agreement-sla) and [assigning some portion of those tickets](/handbook/support/workflows/working-on-tickets.html#assigning-tickets) are [Support Engineer Responsibilities and Priorities](/handbook/support/support-global-groups/#success-of-their-group-means) in [Support Global Groups](/handbook/support/support-global-groups/).
Contributing towards our [first reply time target](/handbook/support/performance-indicators/#service-level-agreement-sla) and [assigning some portion of those tickets](/handbook/support/workflows/working-on-tickets.html#assigning-tickets) are [Support Engineer Responsibilities and Priorities](/handbook/support/support-global-groups/#success-of-their-group-means) in [Support Global Groups](/handbook/support/support-global-groups/).
 
##### Public and internal comments
 
To [maintain good progress through to resolution on all assigned tickets](/handbook/support/support-engineer-responsibilities.html#3-maintain-good-progress-through-to-resolution-on-all-of-your-assigned-tickets) and [help others maintain progress on their tickets](handbook/support/support-engineer-responsibilities.html#5-help-others-in-your-group-to-maintain-progress-on-their-tickets) engineers must communicate with our customers and collaborate with their peers. Public and internal comments can be an indication of performance, but be careful not to confuse it with the desired result of solved tickets.
To [maintain good progress through to resolution on all assigned tickets](/handbook/support/support-engineer-responsibilities.html#3-maintain-good-progress-through-to-resolution-on-all-of-your-assigned-tickets) and [help others maintain progress on their tickets](/handbook/support/support-engineer-responsibilities.html#5-help-others-in-your-group-to-maintain-progress-on-their-tickets) engineers must communicate with our customers and collaborate with their peers. Public and internal comments can be an indication of performance, but be careful not to confuse it with the desired result of solved tickets.
 
See: [Ticket Baselines](/handbook/support/support-engineer-responsibilities.html#ticket-baseline)
 
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment