ENG: Release Post template rebrand MVC1
First pass at rebranding the existing release post template type and styles which will improve continuity and accessibility as measured by reduced drop off.
In scope
What is within scope of this request?
-
Skin existing release post with updated brand colors and typography -
Address any existing accessibility issues
Out of scope
What is out of scope and not part of this iteration?
- Changing the structure of the page
- Hero image
- Anything else
Why is this change being made?
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 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
- 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 #1201
Edited by Margareth Mañunga