Improve Marketing landing handbook page: Current Slack channels, team...
Why is this change being made?
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.
Note: Re-created this MR after the handbook migration, original approved MR is in gitlab-com/www-gitlab-com!130670 (closed)
This review and MR is part of the Fix Fridays content review, https://gitlab.com/gitlab-com/marketing/developer-relations/dev-evangelism/de-tmm-meta/-/issues/341
The following problems, and improvement areas are addressed:
General improvements
- Review existing Marketing Slack channels
- Remove outdated channels, add missing channels
- Add guidance to existing channels
- Add automated Slack channels
- Use short Markdown URLs (anchors at the bottom)anywhere applicable, and link them more often in the context of a table for support, etc.
Developer Relations
- Change the name consistently to
Developer Relations
- Remove outdated Code Contributor Program URL
- Replace the outdated questionnaire list with the mission statement (copy from the DevRel handbook)
- Add the Community newsletter to the Newsletter section.
Corporate Communications
- Move Social Marketing back into Corp Communications in the team section, following the org chart.
- Did not rename or move the social marketing handbook -- that will be a separate task for the social marketing team.
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
- 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