1st step is basically https://www.drupal.org/node/2490136, which is has been implemented in D8.2:
Enable revisions by default when creating a new content type, and also for the article and page content types added by the standard install profile.
It is something that bothers me quite a bit when doing the initial setup of every site since I have to go through the tedious procedure of enabling revisions for existing content types. Then I need to remember to enable it for new custom ones too. It resembles the procedure I was repeating in order to get admin_menu installed and to disable the Overlay and Toolbar modules.
I think that the limitations of the past such as disk space is not a concern any longer, even on the cheapest hosting plans. Performance might be one, but I have not seen any actual benchmarks - only theories that say that keeping many revisions of nodes would slow the site down.
There was a session in DrupalCon Barcelona on September 2015 about it. Here's the screencast: https://www.youtube.com/watch?v=LKQczUM7Qrw
Recent comments
The user fills a form on an Application node, that then flicks off emails, and responds with a Thanks page. Nothing too complex. Just that the deletion of the page providing the expected...
Problem upon submission
Please can you say more about the Rule? What does it do? Does it use any other Rule supporting modules? I presume if you disable the rule and create/save the node then you don't get the...
Problem upon submission
Yeah, so never mind. The issue arose because a page was deleted that had the URL-alias that the Rule was trying to redirect to. Maybe Core could have caught that the URL didn't exist, or...
Problem upon submission