Keeping the repository lean and clean by removing old content when it is no longer needed helps keeping Magnolia performant. We should implement a place (dashboard) that gives an overview and links to all places where regular repository maintenance needs to be performed. E.g. versions store (MAGNOLIA-9052), tasks, messages.

Questions for discovery

• Identify types of content that profit from regular purging
• What tooling do we need for that? What incubator modules could be promoted?
• Archive such content instead of deleting it? When do we need to? How and where do we archive it?
• How / where would we collate the information about such regular hygiene tasks in Magnolia / the UI?
• How are user profiles affected with SSO (see MGNLSSO-322).
• There's some Groovy  scripts for cleaning up repository content. Optimally the functionality provided by those would be more integrated into Magnolia itself.