Quetzalli

I am not a designer but I am here to give my opinion and agree with @derberg about keeping the TOC. 🙃 It is industry standard to have TOCs in...

@mcturco LGTM 🚀🚀🚀

Hey @jonaslagoni, this sounds like a great new doc for sure! I can see the huge value of explaining how different versioning strategies work within AsyncAPI. Are you willing to...

Let me know if you need my help in the docs, I'm happy to help out! This sounds like a really great new project ✨✨✨

> I'm going to copy paste a message I wrote on AsyncAPI Slack for another folk who created another diagram. https://asyncapi.slack.com/archives/C0230UAM6R3/p1655219125760849?thread_ts=1655137152.791769&cid=C0230UAM6R3 @smoya Thank you for remembering to copy your feedback...

> I'm wondering if it would lake sense to already add to this diagram, or maybe another version, the component that is called `Producer/Consumer`, because the things is that it...

> so what I mean is that maybe in concept document it would be worth having 2 diagrams, one simple, and one more complex. So maybe one diagram with just...

Question ✌🏽 @nelsonmic, other than adding a 2nd diagram with a written explanation of it, are you up to speed on other feedback in this PR? 😀 Do you need...

Great @nelsonmic! Don't forget to use `mermaidJS` syntax in your next diagram drafts, since [we have finished voting, and that tool got the most votes](https://github.com/asyncapi/website/issues/849). 😀

> Heyy @alequetzalli 😀 , I have made changes in `AsyncAPI in numbers` section. please review it. > > I have resolved and made all the changes requested Lukasz ....