Add an alias for Building High Performing Teams

Why is this change being made?

The levelup course Building High Performing Teams: Orientation includes a link to https://about.gitlab.com/handbook/leadership/build-high-performing-teams/.

Before you jump into the course, we'd really recommend taking a look at the Building High Performing Teams handbook page to get a bit more context on what it means as a whole.

This page is no longer on about.gitlab.com, and there is a redirect to the equivalent page on handbook.gitlab.com, but the content has been moved to a section on the leadership page, so currently users end up on a page that doesn't exist: https://handbook.gitlab.com/handbook/leadership/build-high-performing-teams/

What is the best way to fix this?

We should update the levelup course to link directly to https://handbook.gitlab.com/handbook/leadership/#building-high-performing-teams

This is something the Learning and Development could look into.

What else can we do?

This MR adds an alias on the leadership page https://handbook.gitlab.com/handbook/leadership/, to redirect requests for https://handbook.gitlab.com/handbook/leadership/build-high-performing-teams/ (a 404) to https://handbook.gitlab.com/handbook/leadership/ (AFAIK we can't use aliases to link directly to the #building-high-performing-teams heading in that page.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update file high-performing-teams.md

---