Add ability to stage changed content for publication
Andrew Linfoot
Right now, if a user edits published content, the changes go live immediately. Frequently, an editor may want to change an already published piece of content, and want to save their changes to either preview or finalize their content and publish at a later date.
Two related issues, #320 and #608 could then allow users to preview unpublished/staged content prior to publishing.
Wout Mertens
Not sure how to implement this as part of Keystone - isn't this more an implementation problem?
Right now I just use a publish flag…
Revisions would mean saving versions, which is a very deep change.
Wout Mertens
I just now realized there is a history schemaplugin, which saves the changes that were done to a document in another list.
Something similar could be used to copy changed documents into a NAME_to-review list (together with a summary of changes), and once those documents get saved with a "publish now" flag (by someone with the proper permissions), they are copied back to the actual list.
In other words, you wouldn't be able to save to the list directly, it would always be a two-step process.
Matan Kadosh
In my opinion this has a lot to do also with the revision feature request.
The content editor might want to preview a revision, as well as saving a draft as a revision and view it from there
Robert Jensen
Implemented this myself with a second mongoose connection, but would be really nice to have built-in!