Update links for all migrated sections

content/handbook/company/okrs

1. [Diversity, Inclusion & Belonging]({{< ref "values#diversity-inclusion" >}}): [A focus on gender parity]({{< ref "people-success-performance-indicators#diversity---women-at-gitlab" >}}),

[Team Member Resource Groups]({{< ref "erg-guide#definition-of-the-tmg---team-member-groups" >}}), [other initiatives]({{< ref "/handbook/company/culture/inclusion#what-we-are-doing-with-diversity-inclusion--belonging" >}})

1. [Collaboration]({{< ref "values#collaboration" >}}): [Kindness]({{< ref "values#kindness" >}}), [saying thanks]({{< ref "values#say-thanks" >}}), [intentionally organize informal communication]({{< ref "/handbook/company/culture/all-remote/informal-communication" >}}), [no ego]({{< ref "values#no-ego" >}})

1. [Total Rewards]({{< ref "compensation#gitlabs-compensation-principles" >}}): [Competitive market rates for compensation]({{< ref "compensation#competitive-rate" >}}), [Equity compensation](https://about.gitlab.com/handbook/stock-options/), [global benefits (inclusive of office equipment)](https://about.gitlab.com/handbook/finance/expenses/#-office-equipment-and-supplies)

1. [Total Rewards]({{< ref "compensation#gitlabs-compensation-principles" >}}): [Competitive market rates for compensation]({{< ref "compensation#competitive-rate" >}}), [Equity compensation](/handbook/stock-options/), [global benefits (inclusive of office equipment)](/handbook/finance/expenses/#-office-equipment-and-supplies)

1. [Work/Life Harmony]({{< ref "/handbook/company/culture/all-remote/people#worklife-harmony" >}}): [Flexible workday]({{< ref "/handbook/company/culture/all-remote/guide#non-linear-workday" >}}), [Family and Friends days]({{< ref "family-and-friends-day" >}})

1. [Remote Done Right]({{< ref "workplace" >}}): [One of the world's largest all-remote companies]({{< ref "workplace#all-remote-flywheel" >}}), [prolific inventor of remote best practices]({{< ref "workplace#vision" >}})

Unlike typical companies, part of the mandates of our Security, Infrastructure, and Support Departments is to contribute to the development of the GitLab Product. This follows from these concepts, many of which are also behaviors attached to our [core values](/handbook/values/):

* [Dogfooding](/handbook/values/#dogfooding)

* [Everyone can contribute](https://about.gitlab.com/company/mission/#everyone-can-contribute)

* [Everyone can contribute](/handbook/company/mission/#everyone-can-contribute)

As such, everyone in the department should be familiar with, and be acting upon, the following statements:

## Introduction

The GitLab team handbook is the central repository for how we run the company. Printed, it consists of over

[2,000 pages of text](https://about.gitlab.com/handbook/about/#count-handbook-pages). As part of our value of being

[2,000 pages of text](/handbook/about/#count-handbook-pages). As part of our value of being

transparent the handbook is [open to the world](https://gitlab.com/gitlab-com/content-sites/handbook/), and we welcome

feedback. Please make a [merge request](https://gitlab.com/gitlab-com/content-sites/handbook/merge_requests) to suggest

improvements or add clarifications. Please use [issues](https://gitlab.com/gitlab-com/content-sites/handbook/issues) to

ask questions.

For a very specific set of [internal](https://about.gitlab.com/handbook/communication/confidentiality-levels/#internal)

For a very specific set of [internal](/handbook/communication/confidentiality-levels/#internal)

information we also maintain an [Internal Handbook](https://internal-handbook.gitlab.io/)

## Handbook Contents

One common concern newcomers to the handbook express is that the strict documentation makes the company more rigid.

In fact, writing down our current process in the handbook has the effect of empowering contributors to propose change.

As a result, this handbook is far from rigid. You only need to look at the [handbook changelog](https://about.gitlab.com/handbook/CHANGELOG.html) to see the evidence. Every attempt is made to document guidelines and processes in the handbook. However, it is not possible to document every possible situation or scenario that could potentially occur. Just because something is not yet in the handbook does not mean that it is allowed. GitLab will review each team member's concern or situation based on local laws to determine the best outcome and then update the handbook accordingly. If you have questions, please discuss with your manager or contact the [People Success](https://about.gitlab.com/handbook/people-group/) team.

As a result, this handbook is far from rigid. You only need to look at the [handbook changelog](https://about.gitlab.com/handbook/CHANGELOG.html) to see the evidence. Every attempt is made to document guidelines and processes in the handbook. However, it is not possible to document every possible situation or scenario that could potentially occur. Just because something is not yet in the handbook does not mean that it is allowed. GitLab will review each team member's concern or situation based on local laws to determine the best outcome and then update the handbook accordingly. If you have questions, please discuss with your manager or contact the [People Success](/handbook/people-group/) team.

## Handbook Interpretation

We've gathered *some* information about the handbook here, but there's still more elsewhere.

- [Handbook usage](https://about.gitlab.com/handbook/handbook-usage/)

- [Evolution of the handbook](https://about.gitlab.com/handbook/ceo/#evolution-of-the-handbook) on the [CEO page](https://about.gitlab.com/handbook/ceo/)

- [Handbook usage](/handbook/handbook-usage/)

- [Evolution of the handbook](/handbook/ceo/#evolution-of-the-handbook) on the [CEO page](/handbook/ceo/)

- [Changelog](https://about.gitlab.com/handbook/CHANGELOG.html)

- [Handbook editing examples](https://about.gitlab.com/handbook/practical-handbook-edits/)