daxitude

Create drafts of WordPress posts/pages/CPTs even after they’ve been published. And when you’re ready, merge the changes back into the original published post.
<h4>Features</h4>
<ul>
<li>Create multiple drafts of already published posts</li>
<li>Merge the changes back into the published post when you’re ready</li>
<li>Uses the published posts’s original post type, so metas, taxonomies, etc all are available in admin screens and can even be modified in the draft and merged back into the original post</li>
<li>Perform a post diff similar to WP’s default revision.php?action=diff with added ability to compare changes in post meta and taxonomies</li>
<li>See a notice when the original post has been updated ahead of a draft</li>
<li>Preview drafts in the post/page/CPT’s natural template</li>
<li>Since drafts all carry the same custom post status, they are organized in the admin’s edit.php with their own status filter (see screenshot-4)</li>
</ul>
This plugin requires javascript.
<h3>How Does it Work?</h3>
Go to a post’s edit screen and click on the “Save a Draft” button in the Drafts of Revisions postbox (make sure you’ve enabled the post type first). The post’s core data, taxonomies, and meta data are all copied into a new post – the draft – as a child of the original post. The draft has a custom post status; it will never show up in any queries for posts. You can create as many drafts as you like.
You can edit a draft’s post content, taxonomies, and meta data as you like and save progress with the native WP “Save Draft” button. You can also preview the draft and compare changes against the parent at any time (even comparing changes in taxonomies and meta data).
When you’re ready to update the parent post, click the Publish button from the draft’s edit page. All post data, taxonomies, and meta data are merged back into the parent post and the draft post is deleted.

Drafts of Post Revisions

Create drafts of WordPress posts/pages/CPTs even after they've been published

Alexandre Froger

Consider the 8 default post statuses that WordPress uses by default: 
* Publish: Viewable by everyone. (publish) 
* Future: Scheduled to be published in a future date. (future) 
* Draft: Incomplete post viewable by anyone with proper user role. (draft) 
* Pending: Awaiting a user with the publish_posts capability (typically a user assigned the Editor role) to publish. (pending) 
* Private: Viewable only to WordPress users at Administrator level. (private) 
* Trash: Posts in the Trash are assigned the trash status. (trash) 
* Auto-Draft: Revisions that WordPress saves automatically while you are editing. (auto-draft) 
* Inherit – Used with a child post (such as Attachments and Revisions) to determine the actual status from the parent post. (inherit)
A typical publishing workflow would be: 
 Auto-Draft > <code>Draft</code> > <code>Pending</code> > <code>Future</code> > <code>Publish</code> 
But what then? <code>Trash</code>? <code>Private</code>? These seem inadapted.
This is where the Unpublished (unpublish) post status provided by this plugin comes into play. 
It allows content publishers to assign a dedicated status to content they desire not to be published, and avoid assigning a semantically inaccurate status.

WP Unpublish

WP Unpublish adds a post status "Unpublished" to your WordPress Posts (Classic Editor).

Drafts of Post Revisions vs WP Unpublish