Update README with new logo banner

[mcturco]

Reason/Context

This is to replace the old AsyncAPI logo in this repo's README with the banner attached below that represents the new branding.

Here are a few guidelines for this change as well:

1. Make sure you are using Markdown syntax only
2. Be sure to remove the old logo as well as the old title of the repo as this image will replace both elements
3. Make sure you link this image to the website: https://studio.asyncapi.com
4. If there is any description text below the repo title, let's make it left-aligned if it isn't already, so as to match the left-alignment of the content in the new banner image

Download the image file:
github-repobanner-studio.png.zip

---

Banner preview

Please note that this is only a preview of the image, the contributor should download and use the above zip file

[fmvilas]

Doesn't Studio have its own logo? 🤔 May be worth putting it here instead of this banner?

[mcturco]

@fmvilas I was wondering the same thing but wasn't sure... Yeah I guess now that you bring it up, it would be fine since the asyncapi mark is still in the studio logo.

Do we like something like this? Let me know if we should change the description (cc @magicmatatjahu)

[magicmatatjahu]

@fmvilas @mcturco

In the description of the repository we have:

Visually design your AsyncAPI files and event-driven architecture.

We don't only visualize AsyncAPI, but also do other things (that's why we talk also about design of EDA). But maybe Fran has another (better) suggestion for the description.

[mcturco]

@magicmatatjahu Sounds good! I have updated the text to your suggestion and also provided an alternate layout. But of course, if we have a better description suggestion I can update it, no problem.

I think Option 2 is more impactful for the Studio, but it will require more scrolling for the user (something that might not be a huge deal for GH README?)

Option 1

Option 2

[magicmatatjahu]

@mcturco Awesome, thanks! I prefer that 1 option and you described why:

I think Option 2 is more impactful for the Studio, but it will require more scrolling for the user.

😄 @fmvilas What do you think?

[fmvilas]

I actually like the second option better 😄 I don't care to scroll tbh.

[mcturco]

I actually like the second option better 😄 I don't care to scroll tbh.

Yeah I think I like the layout of the second option better. It is better visual hierarchy. I think for a Readme file its not that big of a deal to scroll a bit more, and this option isn't that much taller. It's similar to the one we have on the org Readme, and I think that one works well.

[magicmatatjahu]

We can go with the second option.

[mcturco]

Great! I have updated the assets in the issue comment at the top, so this issue is ready for a PR 😄

[magicmatatjahu]

@mcturco I also noticed that we should change the photo in the og metadata. Currently the old logo is still there.

[mcturco]

@magicmatatjahu good call! Do you want to open up a separate issue for that?

[magicmatatjahu]

@mcturco #295 :)

[asyncapi-bot]

🎉 This issue has been resolved in version 0.11.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v0.11.1

Your semantic-release bot 📦🚀