Add newsletter issue URL and fix formatting of engagement channels
Why is this change being made?
I was reviewing the guidelines for adding an announcement for team members to the company newsletter, and could not find the most current newsletter issue mentioned in the handbook. After research in my inbox, I found a link to a newsletter issue in the latest newsletter, which unveiled the issues location in https://gitlab.com/gitlab-com/internal-communications/newsletter/-/issues
This MR adds the issue list to the handbook to help team members contribute to the company newsletter more efficiently.
I also spotted that the list formatting is not correct, and applied a new list formatting, including the collaboration emoji to highlight the to contribute blocks better.
| Before | After |
|---|---|
 |
 |
Context for the announcement:
Author Checklist
-
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 bysection 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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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
-
Edited by Michael Friedrich