Updated 184 broken links to handbook index

After the handbook was split into smaller pages by https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/4939 many of the old links needed updating

source/jobs/ux-lead/index.html.md

@@ -26,4 +26,4 @@ Designers report to the UX/Design Lead.
 * Experience defining the high-level strategy (the why) and creating design deliverables (the how) based on research.
 * Passion for creating visually pleasing and intuitive user experiences.
 * Collaborative team spirit with great communication skills
-* You share our [values](/handbook/#values), and work in accordance with those values.
+* You share our [values](/handbook/values), and work in accordance with those values.

source/jobs/ux-researcher/index.html.md

@@ -21,4 +21,4 @@ The User Experience Researcher reports to the UX Lead.
 * A minimum of 2+ years experience as a user researcher
 * Degree in cognitive psychology, human factors, human-computer interaction, or related field.
 * Collaborative team spirit with great communication skills
-* You share our [values](/handbook/#values), and work in accordance with those values.
+* You share our [values](/handbook/values), and work in accordance with those values.

source/jobs/vp-of-scaling/index.html.md

@@ -25,4 +25,4 @@ title: "Vice President of Scaling"
 - Ability to manage competing company and team priorities in collaborative and cross-disciplinary way.
 - Ability to work well with colleagues both in and outside of the organization, with good judgement, discretion, and tact.
 - Ability to work independently and to undertake supervisory responsibilities as needed.
-- You share our [values](/handbook/#values), and work in accordance with those values
+- You share our [values](/handbook/values), and work in accordance with those values

source/layouts/job_page.haml

@@ -15,7 +15,7 @@
       our culture, our way of life, our story, and what makes us truly unique.
       [vision]: https://about.gitlab.com/strategy
-      [value]: https://about.gitlab.com/handbook/#values
+      [value]: https://about.gitlab.com/handbook/values
       [primer]: https://about.gitlab.com/primer
     = partial "includes/reasons_to_work_for_gitlab"

source/posts/2015-09-14-remote-agile-at-gitlab.html.md

@@ -81,7 +81,7 @@ work as a hard rule and also depends on your skills and responsibilities:
 1. Growth efforts
 1. Other work
-Find this [in our handbook](https://about.gitlab.com/handbook/#gitlab-workflow).
+Find this [in our handbook](https://about.gitlab.com/handbook/communication/#gitlab-workflow).
 ### Known issues

source/posts/2015-12-17-gitlab-release-process.html.md

@@ -38,7 +38,7 @@ Instead of one person assigning tasks to team members, the team members pick up
 The leaders define the direction. They work on the pool and define the milestones. We do work on large features, but these are split up into tasks. Our release priorities are published in our [Direction document in the Handbook](https://about.gitlab.com/direction/), and everyone on the team can see the current milestones we’re tracking against.
-We do have some things which are high priority and which must be worked on first, such as security issues and priority features. After that, it’s a matter of what you want to work on yourself. This process of selecting issues and prioritization is outlined in our GitLab Handbook, under [GitLab Workflow](/handbook/#gitlab-workflow). For example, “Assign an issue to yourself as soon as you start to work on it, but not before that time.” If an issue is assigned to someone, someone is working on it. If it’s not assigned to someone, no one is working on it. If it’s assigned to a milestone, there’s commitment to work on it. This also makes it easier for everyone on the team to collaborate. Having a manager to bring this distributed effort to release is very important.
+We do have some things which are high priority and which must be worked on first, such as security issues and priority features. After that, it’s a matter of what you want to work on yourself. This process of selecting issues and prioritization is outlined in our GitLab Handbook, under [GitLab Workflow](/handbook/communication/#gitlab-workflow). For example, “Assign an issue to yourself as soon as you start to work on it, but not before that time.” If an issue is assigned to someone, someone is working on it. If it’s not assigned to someone, no one is working on it. If it’s assigned to a milestone, there’s commitment to work on it. This also makes it easier for everyone on the team to collaborate. Having a manager to bring this distributed effort to release is very important.
 ## The Release Manager is a role not a person

source/posts/2016-03-04-remote-working-gitlab.html.md

@@ -154,12 +154,12 @@ identify if they'd be a fit for our team.
 If you'd like to work with us at GitLab, please check out the [Jobs][jobs] available.
-[grant]: https://about.gitlab.com/handbook/#travel-grant
+[grant]: https://about.gitlab.com/handbook/incentives/#travel-grant
 [wip]: http://doc.gitlab.com/ce/workflow/wip_merge_requests.html
 [jobs]: https://about.gitlab.com/jobs
 [handbook]: https://about.gitlab.com/handbook
-[communication handbook]: https://about.gitlab.com/handbook/#communication
-[team call]: https://about.gitlab.com/handbook/#team-call
+[communication handbook]: https://about.gitlab.com/handbook/communication
+[team call]: https://about.gitlab.com/hanbook/communication/#team-call
 [manifesto]: https://about.gitlab.com/2015/04/08/the-remote-manifesto/
 [team]: https://about.gitlab.com/team/
 [remotely]: https://about.gitlab.com/2014/07/03/how-gitlab-works-remotely/

source/posts/2016-03-08-gitlab-tutorial-its-all-connected.html.md

@@ -154,7 +154,7 @@ Can't make it? Register anyway, and we'll send you a link to watch it later!
 [group-milestones]: https://gitlab.com/groups/gitlab-org/issues?milestone_title=8.6
 [our monthly release issue]: http://doc.gitlab.com/ee/release/monthly.html#create-an-overall-issue-and-follow-it
 [create-project]: http://doc.gitlab.com/ce/gitlab-basics/create-project.html#how-to-create-a-project-in-gitlab
-[ssot]: https://about.gitlab.com/handbook/#gitlab-workflow
+[ssot]: https://about.gitlab.com/handbook/communication/#gitlab-workflow
 [start-issue]: https://about.gitlab.com/2016/03/03/start-with-an-issue/
 [webcast]: http://page.gitlab.com/mar-2016-gitlab-introduction.html
 [glf-commit]: http://doc.gitlab.com/ee/workflow/gitlab_flow.html#committing-often-and-with-the-right-message

source/posts/2016-03-23-remote-communication.html.md

@@ -83,4 +83,4 @@ It just makes things nicer.
 Have an idea for something we missed? Mention it in comments. Also feel free to
 steal our entire [communications handbook][handbook]. That’s why we put it online!
-[handbook]: https://about.gitlab.com/handbook/#communication
+[handbook]: https://about.gitlab.com/handbook/communication

source/posts/2016-04-08-remote-working-parents.html.md

@@ -121,6 +121,6 @@ Want to leave a comment or ask us something? Feel free! Catch us here or
 [remote-first]: https://zachholman.com/posts/remote-first/
 [productivity]: http://www.inc.com/christina-desmarais/want-productive-employees-let-some-of-them-work-from-home.html
-[handbook]: https://about.GitLab.com/handbook/#communication
+[handbook]: https://about.GitLab.com/handbook/communication
 [focus]: http://thewritelife.com/10-concentration-apps-that-will-help-you-get-down-to-business/
 [twitter]: http://twitter.com/GitLab

source/posts/2016-04-20-feature-highlight-move-issues.html.md

@@ -120,6 +120,6 @@ information.
 [Kamil]: https://twitter.com/ayufanpl
 [Merge request !2831]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2831
-[values]: https://about.gitlab.com/handbook/#values
+[values]: https://about.gitlab.com/handbook/values
 [releasepost]: https://about.gitlab.com/2016/03/22/gitlab-8-6-released/
 [Merge request !2996]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2966

source/posts/2016-04-26-gitlab-employees-on-working-at-gitlab.html.md

@@ -22,7 +22,7 @@ survey to all GitLab team members on a regular basis. The goal of the survey
 is to facilitate an open environment for people to share their thoughts, 
 ask questions, or raise potential concerns. Feedback, even if it is only
 mentioned by one employee, is acknowledged and addressed. Most often, the 
-feedback captured in the survey is addressed in our [Team Call](https://about.gitlab.com/handbook/#team-call). 
+feedback captured in the survey is addressed in our [Team Call](https://about.gitlab.com/hanbook/communication/#team-call).
 ## Five key themes 

source/posts/2016-08-05-feature-highlight-set-dates-for-issues.html.md

@@ -9,7 +9,7 @@ description: "Feature Highlight: Learn how you can leverage issue due dates and
 date: 2016-08-05 10:00:00
 ---
-GitLab has a powerful issue tracker that completely integrates into the GitLab workflow. Our team uses our issue tracker for almost everything, including projects that contain no code. We believe that if anything is significant enough to work on then [it deserves an issue](/handbook/#gitlab-workflow). Before GitLab 8.7, there was no way to communicate that you needed a specific issue to be completed by a specified time. While we had the ability to add milestones to issues and merge requests, there was no way to say "I am working on X and I need to have it completed by Y date." So in GitLab 8.7 we added the ability to set due dates on an issue.
+GitLab has a powerful issue tracker that completely integrates into the GitLab workflow. Our team uses our issue tracker for almost everything, including projects that contain no code. We believe that if anything is significant enough to work on then [it deserves an issue](/handbook/communication/#gitlab-workflow). Before GitLab 8.7, there was no way to communicate that you needed a specific issue to be completed by a specified time. While we had the ability to add milestones to issues and merge requests, there was no way to say "I am working on X and I need to have it completed by Y date." So in GitLab 8.7 we added the ability to set due dates on an issue.
 <!-- more -->

source/posts/2016-08-31-designing-issue-boards.html.md

@@ -14,7 +14,7 @@ Accurate planning and coordination of each release at GitLab is critical to ship
 ## The Proposal
-At GitLab, we believe that the speed of innovation for our organization and product is constrained by the total complexity we've added so far. Creating [boring solutions](/handbook/#boring-solutions) and simplifying our product to its absolute minimum allows us to ship faster and make iterations based on real user feedback. With this in mind, our team began determining basic principles that would help guide us during the creation process of the new Issue Board feature.
+At GitLab, we believe that the speed of innovation for our organization and product is constrained by the total complexity we've added so far. Creating [boring solutions](/handbook/values/#boring-solutions) and simplifying our product to its absolute minimum allows us to ship faster and make iterations based on real user feedback. With this in mind, our team began determining basic principles that would help guide us during the creation process of the new Issue Board feature.
 We knew we wanted the product to be able to:

source/posts/2016-09-13-gitlab-master-plan.html.md

@@ -95,7 +95,7 @@ Want to help GitLab grow? *[We're looking for people to work with us!][careers]*
 [clear-direction]: https://about.gitlab.com/direction/
 [creative-commons]: https://creativecommons.org/licenses/by-sa/4.0/
 [event-recap]: https://about.gitlab.com/2016/09/14/gitlab-live-event-recap/
-[handbook-values]: https://about.gitlab.com/handbook/#values
+[handbook-values]: https://about.gitlab.com/handbook/values
 [idc-study]: https://www.infoq.com/news/2014/01/IDC-software-developers
 [idea-production]: https://about.gitlab.com/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/#from-idea-to-production-with-gitlab
 [issue-boards-post]: https://about.gitlab.com/2016/08/22/announcing-the-gitlab-issue-board/

source/posts/2016-09-26-infrastructure-update.html.md

@@ -51,6 +51,6 @@ Watch the recording or download the slides to see how we're working through our
 <!-- identifiers --> 
 [gitlab]: https://gitlab.com/
-[team-call]: https://about.gitlab.com/handbook/#team-call
-[values]: https://about.gitlab.com/handbook/#values
+[team-call]: https://about.gitlab.com/hanbook/communication/#team-call
+[values]: https://about.gitlab.com/handbook/values

source/posts/2016-11-03-working-at-gitlab-30-days-later.html.md

@@ -15,7 +15,7 @@ Much like [Emily von Hoffmann](https://twitter.com/emvonhoffmann), I too recentl
 One of the most impressive part of the GitLab culture is it's efficiency. Although it is listed as a value, I did not expect it to be so pronuounced. Monthly releases for GitLab CE and EE is just the tip of the iceberg of how much this team can accomplish in a short amount of time. I was amazed at how everything was ready for me before my first day of work. My GitLab email, my slack account, my swag codes and many onboarding items were all setup a few days after I signed my offer letter. I even had my business cards before I started my first day and got to hand them out to my coworkers before I left my previous company!
-The efficiency of the team paired with the fact that everyone is so talented at what they do, truly creates an incredibly productive environment. I cannot agree more with [general guideline #1](/handbook/#general-guidelines):
+The efficiency of the team paired with the fact that everyone is so talented at what they do, truly creates an incredibly productive environment. I cannot agree more with [general guideline #1](/handbook/general-guidelines):
 > Working at GitLab Inc. is cooperating with the most talented people you've ever worked with, being the most productive you'll ever be, and creating software that is helping the most people you've ever reached.
@@ -27,6 +27,6 @@ Unfortunately this wow factor also cultivates a dark side. In a startup culture
 As of a few weeks ago, I've started to block off my lunch time on my calendar. I tend not to prioritize what I need to do until it is on my schedule, so this helps me discipline my time. This may not work for everyone, it definitely keeps me in check.
-In light of all this, it is reliving that the team at GitLab is very supportive of a [healthy work life balance](/handbook/#working-remotely) and will do all they can to make sure everyone is well taken care of. After all, why else would they ask you to take a [minimum of 2 weeks off](/handbook/#paid-time-off) a year for vacation.
+In light of all this, it is reliving that the team at GitLab is very supportive of a [healthy work life balance](/handbook/working-remotely) and will do all they can to make sure everyone is well taken care of. After all, why else would they ask you to take a [minimum of 2 weeks off](/handbook/paid-time-off) a year for vacation.
 Overall, this first month working at GitLab has been a blast. Working on something that impacts many organizations and has a clear [strategic vision](/strategy) is an absolute thrill. If you think you have what it takes to be a GitLabber, check out our [job openings](/jobs).

source/posts/2016-12-05-how-we-stay-connected-as-a-remote-company.html.md

@@ -13,11 +13,11 @@ GitLab is a remote-only company, which means we have the freedom to live where w
 ## Team calls
-Almost every day we have a [team call](https://about.gitlab.com/handbook/#team-call), not just for company updates but to take it in turns filling in the rest of the team about what we’ve been up to that weekend. I’ve been given a tour of team members’ new houses, admired their Christmas decorations, squealed when their pets and kids make an appearance and watched them preparing dinner – glimpses into the personal lives of my colleagues that I’ve never had in any office job. I’ve worked at companies where I didn’t know the names of anyone who worked on a different floor. "There are no floors at GitLab," Douwe said to me on a call, and it's true both literally and metaphorically. Because you’ve chatted with everyone on team calls, everyone feels approachable.
+Almost every day we have a [team call](https://about.gitlab.com/hanbook/communication/#team-call), not just for company updates but to take it in turns filling in the rest of the team about what we’ve been up to that weekend. I’ve been given a tour of team members’ new houses, admired their Christmas decorations, squealed when their pets and kids make an appearance and watched them preparing dinner – glimpses into the personal lives of my colleagues that I’ve never had in any office job. I’ve worked at companies where I didn’t know the names of anyone who worked on a different floor. "There are no floors at GitLab," Douwe said to me on a call, and it's true both literally and metaphorically. Because you’ve chatted with everyone on team calls, everyone feels approachable.
 ## Coffee break calls
-We also have regular one-on-one chats that can be about anything (as long as it’s not work!). Acknowledging that we don’t have a water cooler around which to gather, we make time for shooting the breeze online instead. And it’s kind of cool to have my [coffee break](https://about.gitlab.com/handbook/#coffee-break-calls) with someone on the other side of the world, in an entirely different time zone or season.
+We also have regular one-on-one chats that can be about anything (as long as it’s not work!). Acknowledging that we don’t have a water cooler around which to gather, we make time for shooting the breeze online instead. And it’s kind of cool to have my [coffee break](https://about.gitlab.com/handbook/working-remotely/#coffee-break-calls) with someone on the other side of the world, in an entirely different time zone or season.
 ## Summits

source/posts/2017-01-03-how-to-prepare-for-a-virtual-interview.html.md

@@ -7,18 +7,18 @@ image_title: '/images/blogimages/how-to-prepare-for-a-virtual-interview.jpg'
 description: "Our Global Recruiter shares a few tips on how to get ready for a job interview that's *not* irl."
 ---
-The GitLab interview process, like our company, is remote first. As a result, our recruiting team and hiring managers spend lots of time meeting candidates via [video calls](/handbook/#videocalls). Video chats are an important part
+The GitLab interview process, like our company, is remote first. As a result, our recruiting team and hiring managers spend lots of time meeting candidates via [video calls](/handbook/communication/#video-calls). Video chats are an important part
 of our daily culture and a great way to connect with our teammates, but they can also be a confusing, uncomfortable, and stress-inducing component of an interview. 
 <!-- more -->
-More and more organizations are conducting interviews and meetings using video platforms. At GitLab we use Google Hangouts or Appear.in for most of our [one-on-one calls](/handbook/#video-calls). Whatever platform you’re using, these simple guidelines will help you have a productive web interview and allow you to focus on the role. 
+More and more organizations are conducting interviews and meetings using video platforms. At GitLab we use Google Hangouts or Appear.in for most of our [one-on-one calls](/handbook/communication/#video-calls). Whatever platform you’re using, these simple guidelines will help you have a productive web interview and allow you to focus on the role. 
 Read on for our tips on how to avoid video chat nerves! 
 ## Stage Your Interview Spot
-It’s nice to be in a neutral environment that is a quiet and comfortable for you. That way neither you nor the interviewer gets too distracted by your environment. We encourage you to display your [quirkiness](/handbook/#values) and personality, but for the interview it's best to avoid chaos. For example, we wouldn't suggest taking your interview call in a loud crowded cafe, in a car, or from your bed! These examples may sound extreme, but we have seen it all.
+It’s nice to be in a neutral environment that is a quiet and comfortable for you. That way neither you nor the interviewer gets too distracted by your environment. We encourage you to display your [quirkiness](/handbook/values) and personality, but for the interview it's best to avoid chaos. For example, we wouldn't suggest taking your interview call in a loud crowded cafe, in a car, or from your bed! These examples may sound extreme, but we have seen it all.
 ## Practice Your Positioning
@@ -32,7 +32,7 @@ your interview, and avoid technical snags the day of! It’s also worthwhile to
 ## Do Your Research
-At GitLab, we love when candidates have reviewed our [handbook](/handbook) and know our [values](/handbook/#values). Many of our [interview questions](/handbook/hiring/#interview-questions) can even be found in our [hiring process](/handbook/hiring), making preparation simple. Making a great first impression is not reserved for on-site interviews.
+At GitLab, we love when candidates have reviewed our [handbook](/handbook) and know our [values](/handbook/values). Many of our [interview questions](/handbook/hiring/#interview-questions) can even be found in our [hiring process](/handbook/hiring), making preparation simple. Making a great first impression is not reserved for on-site interviews.
 After you've mastered these tips, it's important to remember that much of the traditional interviewing advice still applies; we encourage you to prepare for a virtual interview the same way you would for an in-person interview. Just because you are taking a call from home doesn’t make it the same as a casual call. Dress appropriately, do your research, and prepare good questions. 

source/posts/2017-01-05-prometheus-and-gitlab.html.md

@@ -7,7 +7,7 @@ image_title: '/images/unsplash/data.png'
 description: "Completing the application lifecycle with monitoring"
 ---
-A little while ago, we presented a first draft of our vision for monitoring within GitLab. We [value transparency](https://about.gitlab.com/handbook/#values), so see below for the recorded video and transcript of the presentation, or view the [slides](https://docs.google.com/presentation/d/12SDArWFfr8fGOZEOqUOwn7NMwfuGKBeS1KLJxtBVyMM/edit?usp=sharing) directly. Please do give us your feedback on any of the linked issues!
+A little while ago, we presented a first draft of our vision for monitoring within GitLab. We [value transparency](https://about.gitlab.com/handbook/values), so see below for the recorded video and transcript of the presentation, or view the [slides](https://docs.google.com/presentation/d/12SDArWFfr8fGOZEOqUOwn7NMwfuGKBeS1KLJxtBVyMM/edit?usp=sharing) directly. Please do give us your feedback on any of the linked issues!
 <!-- more -->