Release post - 2nd iteration

Let's make the release post even better!

• From #1216 (closed): adjust columns for better readability

  • If possible: make "other features" section to fluidly adjust automatically the content of the 2 columns (otherwise we need to adjust them manually to balance the content between both

• From Sid: "Please add a hover text to the new edition badges in this blog post, to expand the abbreviation (mainly EES and EEP, since those haven't been around long enough to be remembered at the top of your head)."

• For HTML5 semantic SEO: adjust divs, sections, and headings to a logical semantic structure. Use <div> inside of a <section> whenever necessary:

  <section>
  <h2>...</h2>
  <p>...</p>
  <h3>...</h3>
  <p>....</p>
  ...
  <div>....</div>
  </section>

  Not:

  <section><h2>...</h2></section>
  <section><p>...</p></section>

All above accomplished here: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/5551

The lastest (current) makes h2 one section, and the actual content of that section another section.

• Align badges perfectly with h2s and h3s

• Suggestion: make p { text-align: justify; } and p code { text-align: left; }

• Highlight the paragraph related to the ids the bagdes link to. If I click the badge "EES", the page scrolls down to "GitLab Products" and Highlights <li id="ees">...</li>:

  

cc/ @dimitrieh @tauriedavis @annabeldunstone @victorwu @luke

changed milestone to %9.1

mentioned in issue #1240 (closed)

assigned to @annabeldunstone

Thanks @marcia, I'm not going to be able to work on this at the moment. Unassigning so someone else can pick it up

removed assignee

Who should lead this? @victorwu? @regisF?

Thanks @marcia . @regisF is PM-ing about.gitlab.com. So he can help with analyzing this and prioritizing any work that needs to be done.

@marcia how did we do the last time? Was it you and @dimitrieh doing all the ground work?

I wonder if we should do this as we build the blog post, as a wip.

@regisF we finished the 9.0 post changing some of the styles in its MR, but we started with a separate MR. I think we should do the latter here, not in the release post MR directly, bc it gets way too overwhelming.

Last time it was me and Dimitrie, yes, then a few commits by FE. But I think the next iterations should be led by you and FE/UX. I can help by commenting here and there, but I can't lead it :)

Then, they'll need to update the release posts handbook with any further change on styling, otherwise we'll get crazy when styling them. It's crucial that the handbook is kept up-to-date. :P

---

The ideal case scenario would be making the styles automated, but for that we'd need some work with haml and yaml to render as we need to.

@marcia so the 100$ question: is this a blocker for 9.1 release post?

I don't think so @regisF, but it was planned for. :) tasks 1 to 4 are the most important ones.

@marcia the problem is that I don't have the bandwidth right now to monitor and follow these changes. Can you check with @jschatz1 if we have any availability for this?

marked the checklist item From #1216 (closed): adjust columns for better readability as completed

mentioned in issue #1320

@regisF actually check with @timzallmann. His FE team is doing marketing now.

marked the checklist item From Sid: "Please add a hover text to the new edition badges in this blog post, to expand the abbreviation (mainly EES and EEP, since those haven't been around long enough to be remembered at the top of your head)." as completed

changed the description

marked the checklist item For HTML5 semantic SEO: adjust divs, sections, and headings to a logical semantic structure. Use <div> inside of a <section> whenever necessary: as completed

changed the description

@marcia Can we close this?

marked the checklist item Align badges perfectly with h2s and h3s as completed

Yes @rspeicher, thanks for the ping! :)

closed