Removing Markdown Mention Team Planning on Project Management Direction Page

Why is this change being made?

We are looking to move Markdown related work, and the technical expert Brett Walker, from Group Project Management to Group Knowledge. Extensive conversations have been had on this within Plan Stage (Approved by both EMs, GPM, and additional parties), and more information can be found in this Issue.

As part of this we need to remove Markdown as a mention under the Team Planning category which falls under Group Project Management. We are not moving it to another category at this time, as there are informal discussions on either creating a new category that contains the rich text editor, plain text editor, and Markdown work, or to simply bundling them under a single Label (or several associated labels).

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
  • 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 _overview.html.md.erb

---