Add nav and menu documentation to the development overview page
Why is this change being made?
MR!16783 was just implemented which updates to top level menu navigation for the Handbook. There are multiple ways to add links to the menu so documentation is being added to the Docs to support future changes, as discussed in our ext-handbook Slack conversation.
- Add nav and menu documentation to the development overview 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) - 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 -
Handbook: For changes that affect handbook users, but does not need company-wide attention, post in the #handbookSlack 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
-