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/posts/2017-01-22-gitlab-8-16-released.html.md

@@ -40,7 +40,7 @@ where GitLab CEO Sid gave a keynote on the past, current and future of GitLab:
   <iframe src="https://www.youtube.com/embed/xGxLi3PtxHM" frameborder="0" allowfullscreen="true"> </iframe>
 </figure>
-This was an internal presentation meant for our team members. We share it because transparency is [one of our values](https://about.gitlab.com/handbook/#values). It is not a formal announcement, for example we're still evaluating the subscription plans for GitLab.com.
+This was an internal presentation meant for our team members. We share it because transparency is [one of our values](https://about.gitlab.com/handbook/values). It is not a formal announcement, for example we're still evaluating the subscription plans for GitLab.com.
 If you don't have the time to watch the full video, have a look at
 [44:48][sid-challenge], where Sid gives a challenge to the present team:

source/posts/2017-01-31-around-the-world-in-6-releases.html.md.erb

@@ -9,7 +9,7 @@ description: 'Two GitLabbers spent 6 months visiting and working with 49 differe
 twitter_image: '/images/tweets/around-the-world-in-6-releases.png'
 ---
-Two GitLabbers, [Robert](/team/#rspeicher) and [Douwe](/team/#DouweM), took our ["the company will cover travel costs to visit colleagues"](/handbook/#travel-to-visit-team-members) policy and ran with it, spending six months visiting and working with 49 different colleagues in 20 cities, in 14 countries, on five continents. Read on for the who, what, why, and where.
+Two GitLabbers, [Robert](/team/#rspeicher) and [Douwe](/team/#DouweM), took our ["the company will cover travel costs to visit colleagues"](/handbook/spending-company-money/#travel-to-visit-team-members) policy and ran with it, spending six months visiting and working with 49 different colleagues in 20 cities, in 14 countries, on five continents. Read on for the who, what, why, and where.
 <!-- more -->
@@ -21,11 +21,11 @@ _Can you catch a glimpse of the limited-edition GitLab branded socks?_
 ## Background
 One of the great things about [remote work at GitLab](/2015/04/08/the-remote-manifesto/) is that it doesn't just mean "work your regular 9-to-5 job from home," but rather "work however you like, wherever you like, whenever you like."
-We don't believe in fixed [working hours]((/handbook/#working-hours)), prefer [asynchronous communication](/handbook/#communication) for most things, encourage people to take as much [time off](/handbook/#paid-time-off) as they need to run errands or just take a break from work, and the main thing we expect from our people is [results](/handbook#values).
+We don't believe in fixed [working hours]((/handbook/paid-time-off/#working-hours)), prefer [asynchronous communication](/handbook/communication) for most things, encourage people to take as much [time off](/handbook/paid-time-off) as they need to run errands or just take a break from work, and the main thing we expect from our people is [results](/handbook/values).
 On the other hand, we realize that one of the downsides of remote work is that, while you may see your colleagues every day in chat and video calls, you will likely not have the chance to physically hang out with them more than once or twice a year at a summit or conference.
-One of the things we do to help our team members [connect and stay connected](/2016/12/05/how-we-stay-connected-as-a-remote-company/) uses that advantage to combat the downside: we encourage everyone to [travel to visit and work with other team members](/handbook/#travel-to-visit-team-members), wherever they may be, and will cover any travel costs to get there.
+One of the things we do to help our team members [connect and stay connected](/2016/12/05/how-we-stay-connected-as-a-remote-company/) uses that advantage to combat the downside: we encourage everyone to [travel to visit and work with other team members](/handbook/spending-company-money/#travel-to-visit-team-members), wherever they may be, and will cover any travel costs to get there.
 (It's in the handbook, so it's true!)
 ## The Trip
@@ -63,19 +63,19 @@ Not shown is the week between Sydney and Amsterdam that we spent in [New Zealand
 [![Map](/images/blogimages/around-the-world-in-6-releases/map.png){: .shadow}](/images/blogimages/around-the-world-in-6-releases/map.png)
-About halfway through the trip, GitLab CEO [Sid](/team/#sytses) realized the tremendous positive impact the trip was having on all of the people visiting, being visited, and following along through our team calls, and the ["the company will cover travel costs to visit colleagues"](/handbook/#travel-to-visit-team-members) policy [was born](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/3735) to encourage more people to make trips like this in the future.
+About halfway through the trip, GitLab CEO [Sid](/team/#sytses) realized the tremendous positive impact the trip was having on all of the people visiting, being visited, and following along through our team calls, and the ["the company will cover travel costs to visit colleagues"](/handbook/spending-company-money/#travel-to-visit-team-members) policy [was born](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/3735) to encourage more people to make trips like this in the future.
 Now that the trip is concluded and we've had a few weeks to reflect, I'd like to share with you some of the things we've learned during this trip.
 In the near future, we will also publish a follow-up to ["GitLab in Action"](/2016/08/24/gitlab-in-action/), covering our travels through Latin America, Europe, Asia, and Oceania in more detail.
 ## Insight 1: GitLab feels like one big team of friends
-One of the first things we realized on this trip relates to one of our core values at GitLab: [Kindness](/handbook/#kindness).
+One of the first things we realized on this trip relates to one of our core values at GitLab: [Kindness](/handbook/values/#kindness).
 Each and every one of the people we met up with, some of whom didn't even know we were coming until just days before we arrived, welcomed us with open arms and made us feel at home in these strange cities and countries.
 Many of them invited us into their homes, introduced us to their significant others and/or [pets](/team-pets), and took us into town to show us their favorite places to see, work, eat, or have a drink.
-Because of the glimpses we have had into each other's lives through the daily company-wide [team call](/handbook/#team-call) and the dozens of chat channels about interests and hobbies, it immediately felt like we were hanging out with a friend, not just "someone from the internet," or "this person I work with." While early conversations often related to our single biggest shared interest – GitLab and work at GitLab – this quickly became just one of the many things we talked about.
+Because of the glimpses we have had into each other's lives through the daily company-wide [team call](/hanbook/communication/#team-call) and the dozens of chat channels about interests and hobbies, it immediately felt like we were hanging out with a friend, not just "someone from the internet," or "this person I work with." While early conversations often related to our single biggest shared interest – GitLab and work at GitLab – this quickly became just one of the many things we talked about.
 Interestingly, this was true regardless of whether they were in our department and we had already worked with them a lot, or if they did something totally different and we had never conversed before. ["There are no floors in GitLab"](/2016/12/05/how-we-stay-connected-as-a-remote-company/), and even though we have multiple [functional groups](/team/structure), GitLab feels like one big team.
@@ -95,9 +95,9 @@ Seen from Taipei, the European workday starts at around 4pm, and the American wo
 Being the kind, helpful people we are, we chose the former, and as those things go, before we knew it the clock struck 12 and we had been working for 15 hours straight.
-Turns out it's really hard to stick to regular working hours when most of the people you work with are half a world away. In the end, we did what Jen-Shin had already found as working best for him: we shifted our workday a number of hours to better align with Europe. Other people work in the morning, take a break for a few hours to do whatever it is people do, and work some more in the evening. [Working hours are flexible](/handbook/#working-hours), so everyone finds something that works for them. Of course, as more people from the APAC region join the team, and as our people get more evenly distributed among timezones, much of this issue will resolve itself automatically.
-Another example of an issue our APAC team members face is the inconvenient timing of the daily company-wide [Team Call](/handbook/#team-call): 8:30am in San Francisco, 5:30pm in Amsterdam, but 12:30am in Taipei. Of course the agenda is in a shared document, but not being able to hear or react live to the stories people share about their lives, or to share your own with the rest of the team, makes you feel like you miss out, and – in a sense – like you are being left out. To help with this, we have started [recording all of our team calls](https://gitlab.com/gitlab-com/peopleops/issues/1) including the "what did you do this weekend?" bit, and have a dedicated [APAC Team Call](/handbook/#team-call) for those in that region and anyone else who wants to join, to give them the same regular opportunity to share stories about their lives, and to talk with colleagues about something other than work.
+Turns out it's really hard to stick to regular working hours when most of the people you work with are half a world away. In the end, we did what Jen-Shin had already found as working best for him: we shifted our workday a number of hours to better align with Europe. Other people work in the morning, take a break for a few hours to do whatever it is people do, and work some more in the evening. [Working hours are flexible](/handbook/paid-time-off/#working-hours), so everyone finds something that works for them. Of course, as more people from the APAC region join the team, and as our people get more evenly distributed among timezones, much of this issue will resolve itself automatically.
+Another example of an issue our APAC team members face is the inconvenient timing of the daily company-wide [Team Call](/hanbook/communication/#team-call): 8:30am in San Francisco, 5:30pm in Amsterdam, but 12:30am in Taipei. Of course the agenda is in a shared document, but not being able to hear or react live to the stories people share about their lives, or to share your own with the rest of the team, makes you feel like you miss out, and – in a sense – like you are being left out. To help with this, we have started [recording all of our team calls](https://gitlab.com/gitlab-com/peopleops/issues/1) including the "what did you do this weekend?" bit, and have a dedicated [APAC Team Call](/hanbook/communication/#team-call) for those in that region and anyone else who wants to join, to give them the same regular opportunity to share stories about their lives, and to talk with colleagues about something other than work.
 Bottom line is, hearing about these issues from a distance is one thing, but being there and experiencing it yourself is totally different.
@@ -133,7 +133,7 @@ This trip has been one of the most, if not _the_ most, rewarding experiences of
 We would like to thank all of the people we visited for welcoming us with open arms into their cities and, in many ways, their lives. You (and everyone else at GitLab) are welcome in our homes anytime.
-We would like to thank GitLab for making these things possible through [the way we work](/handbook/), for actively encouraging trips like this by covering a [significant portion of the cost](/handbook/#travel-to-visit-team-members), and ultimately for having built a company with a [culture](/culture/) and [team](/team/) like no other.
+We would like to thank GitLab for making these things possible through [the way we work](/handbook/), for actively encouraging trips like this by covering a [significant portion of the cost](/handbook/spending-company-money/#travel-to-visit-team-members), and ultimately for having built a company with a [culture](/culture/) and [team](/team/) like no other.
 Stay tuned for our follow-up to ["GitLab in Action"](/2016/08/24/gitlab-in-action/), covering our travels through Latin America, Europe, Asia, and Oceania in more detail!

source/strategy/index.html.md

@@ -28,7 +28,7 @@ Everyone can contribute to digital products with GitLab, to GitLab itself, and t
 3. To ensure that **everyone can contribute to GitLab itself** we actively welcome contributors. We do this by having quality code, tests, documentation, using popular frameworks, offering a comprehensive [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit), and a dedicated [GitLab Design Kit](https://gitlab.com/gitlab-org/gitlab-design). We use GitLab at GitLab Inc., to drink our own wine and make it a tool we continue to love. We celebrate contributions by recognizing a Most Valuable Person (MVP) every month. We allow everyone to anticipate, propose, discuss, and contribute features by having everything on a public issue tracker. We ship a new version every month so contributions and feedback are visible fast. To contribute to open source software people must be empowered to learn programming. That is why we sponsor initiatives such as Rails Girls and [Lean Poker](http://leanpoker.org).
-4. To ensure that **everyone can contribute to our organization** we have open business processes that allow all team members to suggest improvements to our handbook. We hire remotely so everyone with an internet connection can come work for us and be judged on results, not presence in the office. We offer equal opportunity for every nationality. We are agnostic to location and create more equality of opportunity in the world. We engage on Hacker News, Twitter, and our blog post comments. And we strive to take decisions guided by [our values](https://about.gitlab.com/handbook/#values).
+4. To ensure that **everyone can contribute to our organization** we have open business processes that allow all team members to suggest improvements to our handbook. We hire remotely so everyone with an internet connection can come work for us and be judged on results, not presence in the office. We offer equal opportunity for every nationality. We are agnostic to location and create more equality of opportunity in the world. We engage on Hacker News, Twitter, and our blog post comments. And we strive to take decisions guided by [our values](https://about.gitlab.com/handbook/values).
 ## Goals
@@ -72,7 +72,7 @@ We realize our competitors have started earlier and have more capital. Because w
 4. First time right: last to market so we get it right the first time, a fast follower with taste.
-5. Values: make decisions based on [our values](https://about.gitlab.com/handbook/#values), even if it is inconvenient.
+5. Values: make decisions based on [our values](https://about.gitlab.com/handbook/values), even if it is inconvenient.
 6. Free SaaS: to make GitLab.com the most popular SaaS in 2020 it should be largely free.
@@ -107,4 +107,4 @@ Our quarterly Objectives and Key Results are [publicly visible in our Lattice go
 ## Why public
-Our strategy is completely public because transparency is one of our [values](/handbook#values). We're not afraid of sharing it because as Peter Drucker said: "Strategy is a commodity, execution is an art.".
+Our strategy is completely public because transparency is one of our [values](/handbook/values). We're not afraid of sharing it because as Peter Drucker said: "Strategy is a commodity, execution is an art.".