-
-
Notifications
You must be signed in to change notification settings - Fork 667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add extensions list in the website #1237
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
No objections from my side, we do it already with:
so, stuff from |
@derberg are we going up with this issue? |
yeah, but there first need to be done some work in |
Can I try my hands on it? |
be my guest, this is a PR than needs to be picked up asyncapi/extensions-catalog#112 and there are already a lot of comments that should be good to guide you on what is missing. of course I'm all yours if ya need help |
@derberg Is this issue still open? Can I work on this if it is? |
at the moment it is blocked by other issues |
hey maintainers, just wanted to know if this issue is now up for execution |
Hey @akkshitgupta currently I am working on it under AsyncAPI Mentorship Program |
closing this as the PR has been raised and merged |
Reason/Context
As part of the "MVP integration of extensions catalog with AsyncAPI tools" mentorship program (detailed at asyncapi/extensions-catalog#78), We would like to render these extensions in the website.
We want to add a new section, possibly under the "specification" section on the website, as shown in the provided image.
Additionally, we will create a pipeline to automatically update extensions website according to changes in the extension-catalog, which can be found at https://github.com/asyncapi/extensions-catalog". In other words, pushing extensions definitions from the extentions catalog to this repo and render these as a list whenever some change is introduced.
The text was updated successfully, but these errors were encountered: