To save space or reduce duplication, only the settings that were changed (diffs) could be stored when saving a new revision. When filtering the settings when rendering the site, this would require walking back through the previously-applicable revisions and finding ones that include that setting to apply. A case where this would be useful is if the user who saved a revision did not have the capability to change a setting, and so that setting might be omitted from the revision. Otherwise, the new subset settings could just be merged on top of the previously active settings to make sure all have values.
To save space or reduce duplication, only the settings that were changed (diffs) could be stored when saving a new revision. When filtering the settings when rendering the site, this would require walking back through the previously-applicable revisions and finding ones that include that setting to apply. A case where this would be useful is if the user who saved a revision did not have the capability to change a setting, and so that setting might be omitted from the revision. Otherwise, the new subset settings could just be merged on top of the previously active settings to make sure all have values.