GitLab 9.3 release post

Review Apps link: https://release-9-3.about.gitlab.com/2017/06/22/gitlab-9-3-released/

Release Post

• Blog handbook: https://about.gitlab.com/handbook/marketing/blog/
• Release post handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/

General Contributions

General contributions from the team.

Due date: 06/14 (6th working day before the 22nd)

• Label MR: blog post release
• Add milestone
• Intro
• MVP
• Add cover image image_title (compressed)
• Upgrade barometer
• Top features
• Primary features
• Secondary features (improvements)
• Performance improvements
• Omnibus improvements
• Deprecations
• Documentation links
• Authorship (author's data)

Review

Content review (PMs)

Due date: 06/19 (2nd working day before the 22nd)

• Label MR: blog post release review-in-progress
• General review (PM)
  • Check Features' names
  • Check Features' availability (CE, EES, EEP)
  • Check Documentation links
  • Update data/promo.yml
  • Check all images' size - compress whenever > 300KB
  • Meaningful links (SEO)
  • Check links to product/feature webpages
• Copyedit (Sean P, Rebecca, or Marcia)
  • Title
  • Description
  • Grammar, spelling, clearness (body)
• Final review (Job)

Structural Check

Due date: 06/19 (2nd working day before the 22nd)

• Label MR: blog post release review-structure
• Check frontmatter (entries, syntax)
• Check image_title and twitter_image
• Check image shadow {:.shadow}
• Check images' ALT text
• Videos/iframes wrapped in <figure> tags (responsiveness)
• Add/check <!-- more --> separator
• Add/check cover img reference (at the end of the post)
• Columns (content balance between the columns)
• Badges consistency (applied to all headings)
• Remove any remaining instructions
• Remove HTML comments
• Run deadlink checker
• Update release template with any changes (if necessary)

source/handbook/marketing/blog/release-posts/index.html.md

@@ -247,6 +247,7 @@ Images can be added at will in the description entry. A link to the documentatio
 Features with higher impact, displayed
 in rows after the top feature, with an image next to its text. An image accompanying the description is required.
+A [video](#videos) can also be added to replace the image.
 #### Secondary features (other improvements)
 {:#improvements}
@@ -464,6 +465,21 @@ is displayed responsively.
 Consult the [markdown guide](/handbook/product/technical-writing/markdown-guide/#videos)
 for the correct markdown markup to apply to different sources (YouTube, Google Drive, HTML video).
+For `primary_features`, you can add a video instead of an image, by using the entry `video:`.
+If present, the feature section won't display any images, only the video. Example:
+
+```yaml
+# PRIMARY FEATURES
+  primary:
+    - name: Awesome Feature
+      available_in: [ce, ees, eep]
+      documentation_link: ''
+      documentation_text: "Learn more"
+      video: "https://www.youtube.com/embed/eH-GuoqlweM"
+      description: |
+        Lorem ipsum dolor sit amet, consectetur adipisicing elit. Quae, provident.
+```
+
 ## Technical aspects
 Understand how a release post is formed: