Brand Refresh: Iconography

[mcturco]

This issue will be specifically geared towards defining a set of icons for use across AsyncAPI.

[mcturco]

To kick off this issue, just wanted to leave some thoughts that I had about how to organize iconography sets. I am envisioning that there will be two "buckets" of icons:

1. Marketing
2. Tooling

This also directly resonates with my recent thought of creating two separate design systems: 1 for Marketing (website, docs), and 1 for Tooling (products, UI). This is because the application of styles will be a little bit different depending on medium. For example, on the website we might have icons to represent things like Documentation or Use Cases but on Tooling products, we most likely will not have a use for icons like that.

Within those two buckets, we can definitely have sub-categories to make it easier to choose from. Before we can define the specific icons that we will need however, I think it would be great to perform an audit of the icons that we are currently using in those two buckets. Then, we can kinda get an idea of what icons we can streamline and improve upon and then make our own kit.

Would love some help on this issue if there are any visual/product designers out there looking to make a contribution! 💪

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[Savio629]

@mcturco Are you still planning on working on this issue?
I would like to help you out tho I'm still new to designing stuff.