Draft: Release Post template - Brand refresh (post release) pt 2
Why is this change being made?
We would like to update the release post template to be better inlined with our refreshed brand. Closes #1060
Changes made:
| Element | Figma | Current |
|---|---|---|
| Gitlab Release H1 |  |
------ |
| Split H1 and H2 copy in header |  |
 |
| Update share icons |  |
 |
| Ref Buttons icon update |  |
 |
| Truncate and reposition previous and next pages |  |
 |
| Questions or comments section |  |
 |
| Add button to GitLab Forum option |  |
 |
| Invert comments and "last call" section |  |
 |
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.
-
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Closes #1060 (closed)
Edited by Margareth Mañunga