Make a grid of story states about mapstory

[jonpmarino]

@glynnis in response to your questions, I'd say:

• yes, a user can unpublish a story
• If a user makes changes to a published story, to me it makes sense to unpublish while editing, and then republish when finished. this presumably would maintain the mapstory URL and story #...thus not messing with any external embeds of that story that have occurred.
• yes, user can discard any story they create on mapstory.org...whether its in draft or published form.
  Question...what is the difference between a draft and an unpublished story? are they not the same thing? or if not, does it make sense to think of them the same way? If so, we'd have 2 states: 1) Draft (or 'unpublished') and 2) Published Story. Published means its visible in the search. Draft means its visible for me on my profile with a clear DRAFT indication, and that's it.

[glynnis]

• Also consider: how do we communicate to the user that a draft or published story uses layers that have had updates? Do we let the user pin their story to a particular commit on a layer?

[glynnis]

Notes from a whiteboard session a few months ago that I found while clearing off my phone :) stashing here in case it's useful when this gets picked up again.

[emilyashley]

Reminder to address save fail recovery in this workflow.

There are many ways a save can fail (and I'm sure we'll keep finding new ones) We might want to address how to recover from a mapstory save failure in a way that keeps as much story, chapter, and layer data as possible

@Coop56 suggested we should only lose whatever it is we've changed since the last save if a save fails, not everything.

Address which of these states is the 'last save' to revert to? (for each available state)