I'm a big friend of Slack, Discord & Co. I use both communication tools daily, know their strengths and weaknesses. These types of tools are necessary for quick and easy communication in the team. Like a chat. I don't want to miss it in project teams.
The problem of the tools, however, is the accessibility and retrievability of information. Slack and Discord use their channels to group the information, the search functionality try to filter the data. For team members it is usually difficult to find important information over the history of communication. In addition, Discord has no threads.
Experience shows that in addition to Discord and Slack, a board or wiki is needed for keeping the information about the project.
### Knowledge sharing
Is there news and announcements? Write on the board. A problem in Developer Chanel is solved, write it on the board. You have a usable code snippet, write it on the board. You have thoughts or ideas, write it on the board. For the others.
Manifest and document everything on the board, which is needed more than once. There will always be more people looking for the same solution. It's easier to look on the board than ask in the channel.
### Keep it public
Two things why a public board is particularly accessible for beginners:
1. Users do not have to register to get information. The content is public.
2. Google will index the board threads, so anybody would get the problem solutions directly over search engines.
And that's the basic idea of Arweave: _Arweave makes data permanent, public and accessible._