Replace Live with LiveBlog and DeadBlog

[oliverlloyd]

What?

Replaces Design.Live with Design.LiveBlog and Design.DeadBlog

Why?

Because there are two distinct styles for live blogs, those that are live or active, and historical live blogs that are no longer live or active.

And also because at the moment, liveblogs are represented by CAPI using booleans and we want to bring these articles into the model.

CAPI LiveBlog

{
  designType: 'Article',
  config: {
    isLiveBlog: true,
    isLive: true,
  }
}

CAPI DeadBlog

{
  designType: 'Article',
  config: {
    isLiveBlog: true,
    isLive: false,
  }
}

Dead?

The nomenclature of 'DeadBlog' exists already in Frontend where it is used for Cards and whilst 'dead' is a bit morbid it's the correct antonym for 'live'.

LiveBlog

DeadBlog

[oliverlloyd]

DeadBlog

[liywjl]

I have never really though much about the antithesis of LiveBlog so the name DeadBlog sounded a bit odd at first. But the more I think about it, the more I am coming around to it.

I like the name 👍

[Akhaides1881]

I think this can work well. with oracle I'm not sure if it is compatible.

[oliverlloyd]

I think this can work well. with oracle I'm not sure if it is compatible.

Hey @Akhaides1881 👋 thanks for the comment! However, I think you might have meant to be looking at a different Guardian repo, I see your account is under https://github.com/Seven-Guardians? We certainly don't use Oracle around here (or at least not that I know of!).

Welcome, nonetheless 😄