Fix top feature markup (13.7)
Why is this change being made?
I noticed that the top feature of the 13.7 release post wasn't centered in the blog post so I tried to figure out why.
Found out that the feature was tagged as primary
, not top
.
Notes that the handbook is inconsistent:
- Here it mentions the
top
feature markup: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-top-feature - Here it doesn't: https://about.gitlab.com/handbook/marketing/blog/release-posts/#top-feature
I wonder if we need 2 sections for each?
Let's fix the markup on 13.7 first and make the handbook update in another MR.
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct 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 in 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 changes relate to any part of the project other than updates to content and/or data files please make sure to ping(this requirement has been removed pending identification of a new DRI for the handbook)@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
Edited by Marcia Ramos