Project Communication

Firstly, thanks for getting involved! Please make sure you are familiar with the project's [Code of Conduct](https://github.com/asyncapi/asyncapi/blob/master/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct).

There are several ways to communicate with the AsyncAPI project:

* Subscribe to our [Newsletter](https://www.asyncapi.com/) to learn about the status of the project.
* GitHub issues - for bugs and feature requests
* GitHub pull requests (PRs) - for fixes or new features already discussed, as per the [contributing guidelines](https://github.com/asyncapi/asyncapi/blob/master/CONTRIBUTING.md#contributing-to-asyncapi)
* The AsyncAPI [Slack workspace](https://www.asyncapi.com/slack-invite)
* The regular meetings:
* See the shared [Google Calendar](https://calendar.google.com/calendar/embed?src=c_q9tseiglomdsj6njuhvbpts11c%40group.calendar.google.com&ctz=UTC).
* More info about meetings is on [our dedicated Meetings view on the website](https://www.asyncapi.com/community/meetings).
* The AsyncAPI [YouTube Channel](https://www.youtube.com/asyncapi)
* Social media:
* [Twitter](https://twitter.com/AsyncAPISpec)
* [LinkedIn](https://www.linkedin.com/company/asyncapi)

Review the linked CODE_OF_CONDUCT.md and CONTRIBUTING.md, then compare the listed communication channels with the current AsyncAPI community pages. The issue does not identify a requested change, target file, or completion condition, so clarify the documentation scope before starting.

Written by the indexing model from the issue text.