Move technical blueprint into handbook

Why is this change being made?

This moves the content created in gitlab-com/gl-infra/scalability!90 into the handbook and onto the team page. As discussed in gitlab-com/gl-infra/scalability!90 (comment 1878914225), the handbook and team page is the right location for this type of documentation.

A related change is gitlab-com/gl-infra/scalability!93, which removes the content from the scalability repo.

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

• Move technical blueprint into handbook

Relates to discussion in gitlab-com/gl-infra/scalability!90 (comment 1878914225)

---

added HandbookContent label

assigned to @abrandl

mentioned in commit gitlab-com/gl-infra/scalability@c8f2085d

mentioned in merge request gitlab-com/gl-infra/scalability!93

handbook-codequality.json not present... using markdownlint-cli2-codequality.json only

️ Pipeline Failure - Linting Errors

One of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes you'll find the code quality report above which can link you to where the error is in your code. Additionally below you'll find a table of the errors. The table has links to the markdown lint rules so you can find more information on how to fix the issue(s).

Rule	File	Line	Error	Help
MD012	content/handbook/engineering/infrastructure/team/scalability/observability/technical_blueprint.md	41	Multiple consecutive blank lines [Expected: 1; Actual: 2]	️
MD026	content/handbook/engineering/infrastructure/team/scalability/observability/technical_blueprint.md	56	Trailing punctuation in heading [Punctuation: ':']	️
MD026	content/handbook/engineering/infrastructure/team/scalability/observability/technical_blueprint.md	73	Trailing punctuation in heading [Punctuation: ':']	️
MD026	content/handbook/engineering/infrastructure/team/scalability/observability/technical_blueprint.md	84	Trailing punctuation in heading [Punctuation: ':']	️

If you need more help please reach out on Slack in #mr-buddies or #handbook.

changed the description

marked the checklist item Provided a concise title for this [Merge Request (MR)][mr] as completed

marked the checklist item Added a description to this MR explaining the reasons for the proposed change, per [say why, not just what][say-why-not-just-what] as completed

added 1 commit

• 6255f7db - Fix markdown linting issues

Compare with previous version

mentioned in merge request gitlab-com/gl-infra/scalability!90

@lmcandrew @stejacks-gitlab Could you please approve/merge?

No content change, just moving stuff over and I thought the ownership/responsibilities overview could still live on the front page.

requested review from @lmcandrew and @stejacks-gitlab

approved this merge request

marked the checklist item Assign reviewers for this MR to the correct [Directly Responsible Individual/s (DRI)][dri] as completed

started a merge train

removed this merge request from the merge train because pipeline did not succeed. Learn more.

added 6 commits

• 6255f7db...d5e311b1 - 4 commits from branch main
• 95650645 - Move technical blueprint into handbook
• 3bb9d649 - Fix markdown linting issues

Compare with previous version

enabled automatic add to merge train when the pipeline for ebaafb21 succeeds

added this merge request to the merge train at position 2

merged

mentioned in commit b21ad495

@rnienaber FYI - blueprint is now in the handbook.