Slack read-only view avaliable on a public location

Our slack channel is very useful, contains good instructions, hints and updates, yet it is only avaliable if you are a member of the channel. It this way it creates an artificial barrier to the timely updates and knowledge base that the channel is. The idea is to have history (or at least part of the history) of the slack channel avaliable on a public facing page.

The issue does not name any files, tests, or entry points. First clarify which Slack history should be public and where the public-facing page belongs, then investigate the repository structure and available Slack or documentation integrations. Done means an agreed, accessible read-only history or archive is available without Slack membership.

Written by the indexing model from the issue text.