Support saving pages representing a new view
The wiki will natively support saving proposed new versions of a page or pages into a "view," so that a change can be seen in normal operation and tested, prior to rolling it out for public consumption. Design a view so that a collection of page changes can be grouped together, and design a way for the view to be accepted or rolled back en masse.
This blueprint has been cancelled. Views will simply be new instances mapped to different urls, and a consistent capture of related information is automatically built in by cached copies of pages updated in the background.
Whiteboard
The main "public" view is the entire wiki actively used. To test a set of changes, save the page as a contributing version of a new view, say, "test-X". The public view still sees previous page versions. Continue to change various pages, saving each under "test-X". When accepting the changes, the public view is updated to point to the new versions of the pages.
Maybe the public page when edited shows "participating in test-X" to warn you that any change needs to be merged into the "test-X" view. Maybe for simplicity "test-X" pages become invalid once a public change occurs underneath, requiring merging to make it valid again.
The invalidation process is a simplification so more complex branching and merging don't overwhelm the simple notion of a wiki.
Since pages are written in a DSL, it is quite likely that easily mergeable "deltas" can be built into the DSL so that any change isn't just a "text diff" but rather a mergeable delta.
Rolling back a view will also generate "invalid" pages when changes occur after the original rollout, where merging of new changes to the public view.