event status proposal

evs.md

All "stop" and "segment" cards must have a status object. All "stop" views must have the "status" object in the stage block next to the other metadata.

The status object would look like the following:

{
  "status": {
    "code": "post",
    "label": "REPLAY",
    "color": "#969696",
    "message": "The event has ended.  Replay will be available shortly.",
    "start_time": "2015-10-13T17:00:05.138Z",
    "end_time": "2015-10-13T17:50:05.138Z"
  }
}

There will be a fixed array of possible "code" strings and we need to mock examples of each state TBD.

"label": could be a free form string but will likely be a fixed array of labels. "color": will be a hex color or empty string indicating to the UI how to render the label. "message": will be free form string with some tbd character limit. "start_time" and "end_time" are date times that will be used for countdown if the code is "pre" within 48hrs or will be used to display a date range if "pre" and greater than 48 hrs out. Also used to display past date in the "post" phase.

For reference:

Event
   |
   |-- Year
          |
          |-- Stop [status] ---> Stop
                                   |
                                   |-- Stage [status]
                                   |
                                   |-- Schedule
                                            |
                                            |-- Segment [status]
                                            |
                                            |-- Segment [status]