[UX] What's New - GitLab Admin Interface for Message Management

Overview

As part of our work for #279 (closed), this is the design issue for the admin interface.

Proposal

Create an area for GitLab team members to create the content for "What's New".

• an admin area to create new messages for Gitlab team members
• permissions around who can create the messages
• a standard structure for the messages
  • Character limits
  • URL for the CTA
  • headline
  • body
  • version it applies to (ex: 12.8, 12.9)
  • packages it applies to (ex: starter, bronze)
  • self-managed or .com
• A way to schedule the messages to display
• A way to edit or delete messages

We should look at the structure of our release posts as an inspiration. Perhaps the best MVC is to be able to consume the data the same way and enforce some ellipsis for long content: https://about.gitlab.com/handbook/marketing/blog/release-posts/#content-blocks

Implementation Details:

• The scheduled date will take precedence over the version for display
• This means we can explore including "expires"

Future Todos

• @timnoah Explore Drag & Drop functionality for ordering the updates.
• @timnoah Explore grouping of updates by Version to aid ordering them.