Being able to see what a story's dead/unpublish date is really useful for headless clients for multiple reasons:
Being able to manage data removal from customer driven APIs
Being able to modify UI when a reader interacts with a story that we already know is going to be removed
I recognize that setting/managing the publish/unpublish process is handled by the Content Ops API, and I'm not suggesting that we should allow setting of that value through the Draft API (though that would be useful as well), but being able to easily query that value with the rest of the story data (which includes the story's first published date, story.first_publish_date) would be extremely useful.
Guest
I see -- thanks!
Potentially. The example that springs to mind is when using a built-in bookmark/save feature (I.e. allowing users to bookmark stories to their account). For stories that have a scheduled unpublished date, like wire content, when the user saves that story we can include info in the “thanks for saving!” response that lets them know how much longer the story will be readable for.
Thanks for the suggestion, Lisa.
For item #2, would the unpublish date be leveraged to modify the reader's experience of interacting with that content?
We'll take a look at this workflow.
Thanks