[Website]: Document new typography components

[mcturco]

Reason/Context

In a recent push of changes on the @asyncapi/website, I added a few components to help ensure that the typography across the website remains consistent. I think it would be a great start to our design system if we documented these components into this repo.

The components are in this directory on the website -> https://github.com/asyncapi/website/tree/master/components/typography

The documentation needs to match the current state of these components on the website, and in the future we can work on iterating on the design when needed. The goal of this is to be a place where contributors can go to know which components to use in their contributions and how the props work.

Let's also make sure that the components are stored within a folder for the sub-system, Website

Any questions, let me know!

[yashsehgal]

Hey @mcturco I would love to document the components.

[mcturco]

Awesome, @yashsehgal! Go for it!

[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 ❤️