I have had a discussion with some colleagues who currently use Twiki and are evaluating Confluence. Currently pages cannot be 'frozen' to prevent future modification.

Scenario: a monthly status page contains dynamically generated information from other sources. eg a jira issue list. After 6 months we want to see the first report, but it is executing the jiraissues list again and shows current data.

I use the jiraissues macro as an example, but any dynamically retrieved value (eg metadata, SQL etc) could equally be used. I wonder how hard it would be to for example 'save' the post-rendered page content that could be retrieved and rendered 'as was' rather than 'as is'.

Such 'frozen pages' could be available in a similar way to page revisions.

Tinylink support could could also be extended to support not only 'frozen pages' but also revisions, allowing 'permanent tinylinks to always resolve given content at a point in time.