Good question Ann and I'm also interested to hear back from other organizations as to how they approach the archive/retired content scenario. Not everyone may chose to retire content given the high level of content reuse within a Tridion Docs deployment, where truly archiving content will be challenged by the many dependencies on reuse throughout content sets. An approach that RWS recommends is expiring relevant content based on workflow status (i.e. create a new status called Archive or Retired which content can be moved to at the end of its useful life), flagging it as such while retaining its audit trail and history within the repository. This discussion offers some further insights too: https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/19299/is-there-a-way-to-hide-topics-maps-from-users-if-they-have-a-status-of-retired-expired-in-publication-manager-and-web-client. 

Good question Ann and I'm also interested to hear back from other organizations as to how they approach the archive/retired content scenario. Not everyone may chose to retire content given the high level of content reuse within a Tridion Docs deployment, where truly archiving content will be challenged by the many dependencies on reuse throughout content sets. An approach that RWS recommends is expiring relevant content based on workflow status (i.e. create a new status called Archive or Retired which content can be moved to at the end of its useful life), flagging it as such while retaining its audit trail and history within the repository. This discussion offers some further insights too: https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/19299/is-there-a-way-to-hide-topics-maps-from-users-if-they-have-a-status-of-retired-expired-in-publication-manager-and-web-client.