Merge branch 'master' into 3158Fix

.all-contributorsrc

@@ -555,6 +555,15 @@
       "contributions": [
         "doc"
       ]
+    },
+    {
+      "login": "raj17ce",
+      "name": "Raj Patel",
+      "avatar_url": "https://avatars.githubusercontent.com/u/116947399?v=4",
+      "profile": "https://github.com/raj17ce",
+      "contributions": [
+        "code"
+      ]
     }
   ],
   "contributorsPerLine": 7,

.github/workflows/if-nodejs-pr-testing.yml

@@ -60,6 +60,7 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: "${{ steps.nodeversion.outputs.version }}"
+
       - name: Install dependencies
         run: npm ci
       - if: steps.packagejson.outputs.exists == 'true'
@@ -72,3 +73,12 @@ jobs:
         name: Run release assets generation to make sure PR does not break it
         shell: bash
         run: npm run generate:assets --if-present
+
+      - if: steps.packagejson.outputs.exists == 'true'
+        name: Upload Coverage to Codecov
+        uses: codecov/codecov-action@e28ff129e5465c2c0dcc6f003fc735cb6ae0c673
+        with:
+          fail_ci_if_error: true
+          files: ./coverage/lcov.info
+          token: ${{ secrets.CODECOV_TOKEN }}
+          verbose: true

.github/workflows/netlify-edge-functions-test.yml

@@ -0,0 +1,21 @@
+name: Run tests for netlify edge-functions
+
+on:
+  pull_request:
+    types: [opened, reopened, synchronize, ready_for_review]
+
+jobs:
+  netlify-tests:
+    strategy:
+      matrix:
+        deno-version: [1.46.0]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Deno
+        uses: denoland/setup-deno@3a041055d2e2068f6e2c59904ee0ec2dfa9d9665
+        with:
+          deno-version: ${{ matrix.deno-version }}
+      - name: Test with Deno
+        run: deno test --allow-env --trace-ops netlify/**/*.test.ts
+

.gitignore

@@ -21,3 +21,4 @@ cypress/videos
 *storybook.log
 /storybook-static/
 coverage
+deno.lock

.storybook/AsyncAPIStorybookTheme.ts

@@ -0,0 +1,42 @@
+import { create } from '@storybook/theming/create';
+
+export default create({
+  // Brand Information
+  brandTitle: 'AsyncAPI Initiative',
+  brandUrl: 'https://www.asyncapi.com/',
+  brandImage: 'img/logos/asyncapi-horizontal-white-logo.svg',
+  brandTarget: '_blank',
+
+  // Typography
+  fontBase: '"Work Sans", sans-serif',
+  fontCode: 'monospace',
+
+
+  // Themes
+  base: 'dark',
+
+  /* -- FULL THEME IS NOT BEING USED DUE TO LACK OF STORYBOOK SUPPORT FOR CUSTOMIZING THE SETTINGS & ACTIONS BAR BG/TEXTCOLOR INDEPENDENTLY. --
+  colorPrimary: '#47BCEE',
+  colorSecondary: '#8851FB',
+
+  // UI
+  appBg: '#1b1130',
+  appContentBg: '#ffffff',
+  appPreviewBg: '#ffffff',
+  appBorderColor: '#dfe6ea',
+  appBorderRadius: 4,
+
+  // Text colors
+  textColor: '#ffffff',
+  textInverseColor: '#ffffff',
+  textMutedColor: '#5c6870',
+  inputTextColor: '#2e3438',
+
+  // Toolbar
+  barTextColor: '#9E9E9E',
+
+  // Toolbar default and active colors
+  booleanBg: '#dfe6ea',
+  booleanSelectedBg: '#8851FB'
+  */
+});

.storybook/manager.ts

@@ -0,0 +1,6 @@
+import { addons } from '@storybook/manager-api';
+import AsyncAPIStorybookTheme from './AsyncAPIStorybookTheme';
+
+addons.setConfig({
+  theme: AsyncAPIStorybookTheme,
+});

.storybook/preview.tsx

@@ -1,6 +1,7 @@
 import React from "react";
 import "../styles/globals.css";
 import type { Preview } from "@storybook/react";
+import { themes } from '@storybook/theming';
 import {
   Title,
   Subtitle,
@@ -20,6 +21,7 @@ const preview: Preview = {
       },
     },
     docs: {
+      theme: themes.light,
       toc: {
         title: 'Table of contents',
       },

CODEOWNERS

@@ -15,4 +15,4 @@ markdown/community/*.md @thulieblack @quetzalliwrites
 
 README.md @quetzalliwrites @derberg @akshatnema @magicmatatjahu @mayaleeeee @asyncapi-bot-eve
 #docTriagers: TRohit20 BhaswatiRoy VaishnaviNandakumar J0SAL
-#codeTriagers: sambhavgupta0705
+#codeTriagers: sambhavgupta0705 devilkiller-ag

CONTRIBUTING.md

@@ -1,13 +1,20 @@
-# Contributing to AsyncAPI
-We love your input! We want to make contributing to this project as easy and transparent as possible.
+# Welcome to AsyncAPI
 
-## Contribution recogniton
+Welcome to our open-source project! We're excited to have you join our community and contribute to making our project better. Please follow this guide to ensure a smooth contribution process and maintain the quality of our codebase and documentation. 
 
-We use [All Contributors](https://allcontributors.org/docs/en/specification) specification to handle recognitions. For more details read [this](https://github.com/asyncapi/community/blob/master/recognize-contributors.md) document.
+We encourage all contributors to familiarize themselves with these guidelines and actively participate in the project's growth. If you have any questions or need assistance, don't hesitate to contact the project maintainers or community members.
 
-## Summary of the contribution flow
+## Code of Conduct
+
+AsyncAPI has adopted a Code of Conduct (CoC) that we expect project participants to adhere to. Please [read the full CoC text](./CODE_OF_CONDUCT.md) to understand the expected behavior.
+
+## Our Development Process
+
+We use Github to host code, track issues, feature requests, and accept pull requests.
+
+## Contribution flow
 
-The following is a summary of the ideal contribution flow. Please, note that Pull Requests can also be rejected by the maintainers when appropriate.
+The following is a summary of the ideal contribution flow.
 
 ```
     ┌───────────────────────┐
@@ -36,44 +43,70 @@ The following is a summary of the ideal contribution flow. Please, note that Pul
     └───────────────────────┘
 ```
 
-## Code of Conduct
-AsyncAPI has adopted a Code of Conduct that we expect project participants to adhere to. Please [read the full text](./CODE_OF_CONDUCT.md) so that you can understand what sort of behaviour is expected.
+Issues and pull requests without activity from the creator within 14 days will be automatically closed by a triager or committer. However, closure does not mean rejection. If you wish to revisit a closed issue or pull a request, open a new one referencing the closed item.
 
-## Our Development Process
-We use Github to host code, to track issues and feature requests, as well as accept pull requests.
+Issues and pull requests without activity from the triager or committer within 14 days may occur for many reasons. The creator may use the `/ptal` comment in the pull request to call out maintainers.
 
-## Issues
-[Open an issue](https://github.com/asyncapi/asyncapi/issues/new) **only** if you want to report a bug or a feature. Don't open issues for questions or support, instead join our [Slack workspace](https://www.asyncapi.com/slack-invite) and ask there. Don't forget to follow our [Slack Etiquette](https://github.com/asyncapi/community/blob/master/slack-etiquette.md) while interacting with community members! It's more likely you'll get help, and much faster!
+### Issues
 
-## Bug Reports and Feature Requests
+[Open an issue](https://github.com/asyncapi/asyncapi/issues/new) **only** if you want to report a bug or a feature. Don't open issues for questions or support; join our [AsyncAPI Slack workspace](https://www.asyncapi.com/slack-invite) and post your queries on the relevant channels. Don't forget to follow our [Slack Etiquette](https://github.com/asyncapi/community/blob/master/slack-etiquette.md) while interacting with community members! It's more likely you'll get help, and much faster!
 
-Please use our issues templates that provide you with hints on what information we need from you to help you out.
+### Bug Reports and Feature Requests
 
-## Pull Requests
+Please use our issues templates, which provide hints on what information we need from you to help you out.
 
-**Please, make sure you open an issue before starting with a Pull Request, unless it's a typo or a really obvious error.** Pull requests are the best way to propose changes to the specification. Get familiar with our document that explains [Git workflow](https://github.com/asyncapi/community/blob/master/git-workflow.md) used in our repositories.
+### Pull Requests
 
-## Conventional commits
+**Please open an issue before starting a Pull Request unless it's a typo or a really obvious error.** Pull requests are the best way to propose changes to the specification. It may be rejected if no issue was created first to discuss the need for a pull request.
 
-Our repositories follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification. Releasing to GitHub and NPM is done with the support of [semantic-release](https://semantic-release.gitbook.io/semantic-release/).
+Get familiar with our document that explains the [Git workflow](https://github.com/asyncapi/community/blob/master/git-workflow.md) used in our repositories.
 
-Pull requests should have a title that follows the specification, otherwise, merging is blocked. If you are not familiar with the specification simply ask maintainers to modify. You can also use this cheatsheet if you want:
+## Conventional commits
+
+Our repositories follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification.
 
-- `fix: ` prefix in the title indicates that PR is a bug fix and PATCH release must be triggered.
-- `feat: ` prefix in the title indicates that PR is a feature and MINOR release must be triggered.
-- `docs: ` prefix in the title indicates that PR is only related to the documentation and there is no need to trigger release.
-- `chore: ` prefix in the title indicates that PR is only related to cleanup in the project and there is no need to trigger release.
-- `test: ` prefix in the title indicates that PR is only related to tests and there is no need to trigger release.
-- `refactor: ` prefix in the title indicates that PR is only related to refactoring and there is no need to trigger release.
+Pull requests should have a title that follows the specification; otherwise, merging is blocked. If you are unfamiliar with the specification, ask maintainers to modify it. You can also use this cheatsheet if you want:
 
-What about MAJOR release? just add `!` to the prefix, like `fix!: ` or `refactor!: `
+- `fix: ` prefix in the title indicates that the PR is a bug fix.
+- `feat: ` prefix in the title indicates that the PR is a feature.
+- `docs: ` prefix in the title indicates that the PR only relates to the documentation.
+- `chore: ` prefix in the title indicates that the PR is only related to cleanup in the project.
+- `test: ` prefix in the title indicates that the PR is only related to tests.
+- `refactor: ` prefix in the title indicates that the PR is only related to refactoring.
 
-Prefix that follows specification is not enough though. Remember that the title must be clear and descriptive with usage of [imperative mood](https://chris.beams.io/posts/git-commit/#imperative).
+A prefix that follows specification is not enough. Remember that the title must be clear and descriptive, using the [imperative mood](https://chris.beams.io/posts/git-commit/#imperative).
 
-Happy contributing :heart:
+Happy contributing! :heart:
 
 ## License
+
 When you submit changes, your submissions are understood to be under the same [Apache 2.0 License](https://github.com/asyncapi/asyncapi/blob/master/LICENSE) that covers the project. Feel free to [contact the maintainers](https://www.asyncapi.com/slack-invite) if that's a concern.
 
-## References
-This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md).
+## Contribution recognition
+
+We use the [All Contributors](https://allcontributors.org/docs/en/specification) specification to handle recognitions. Read the [`recognize contributors` document](https://github.com/asyncapi/community/blob/master/recognize-contributors.md).
+
+## Maintainers setup
+
+To streamline project management and facilitate onboarding, the maintainer's setup includes two roles: `triager` and `committer`.
+
+There are also two separate areas of responsibility: docs and code. A committer can be responsible for code only, and a triager can be responsible for docs only. A maintainer can hold all roles and participate in different areas.
+
+We recognize that because of the project's size and complexity, areas of responsibility can also become more granular. For example, a committer can be responsible for docs, but only community docs or a committer can be responsible only for project design. Project maintainers assess and approve these exceptions.
+
+### Triager
+
+Triagers are responsible for labeling, commenting, and managing issues and pull requests.
+
+- Triagers assess newly-opened issues and pull requests.
+Responsibilities include labeling issues and pull requests, commenting, closing, and reopening items as needed, as well as assisting users and novice contributors.
+- Triagers are crucial in enforcing the contributor guide and maintaining a clean backlog.
+If a triager plans to become a committer, they should consult existing committers to gradually gain more rights. It's crucial to earn the trust of existing committers so they feel confident in your ability to merge PRs. A triager should consistently demonstrate dedication by regularly fulfilling their duties and actively reviewing PRs, providing code/docs suggestions and recommendations. This shows the committers that the triager is knowledgeable about the docs/codebase and committed to maintaining its quality.
+
+### Committer
+
+Committers are responsible for technical oversight, pull request approval, and onboarding of new maintainers.
+
+- Committers approve pull requests and oversee the technical direction of the project.
+- They are responsible for reviewing and approving pull requests for merging.
+- Committers also play a role in onboarding new maintainers and triagers.

README.md

@@ -134,6 +134,24 @@ After cloning repository to your local, perform the following steps from the roo
 
 Now you're running AsyncAPI website in a development mode. Container is mapped with your local copy of the website. Whenever you make changes to the code, the website will refresh and changes visible in localhost:3000.
 
+## Use shared Markdown fragments
+
+To minimize the duplication of content and make it easier to maintain, there are shared fragments you can use when working with Markdown files. These fragments are stored in the `/assets/docs/fragments` directory.
+
+To include a fragment in a Markdown file:
+
+1. Import the fragment at the top of the file (but below the frontmatter) using the following syntax:
+
+    ```md
+    import DesiredFragmentName from '@/assets/docs/fragments/fragmentYouWantToImport.md';
+    ```
+
+1. Add the imported fragment to the desired location in the Markdown file using the following syntax:
+
+    ```md
+    <DesiredFragmentName />
+    ```
+
 ## Lint the code
 To lint the code, run the following command:
 ```
@@ -377,6 +395,9 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/Shiva953"><img src="https://avatars.githubusercontent.com/u/120790871?v=4?s=100" width="100px;" alt="Neutron"/><br /><sub><b>Neutron</b></sub></a><br /><a href="https://github.com/asyncapi/website/commits?author=Shiva953" title="Code">💻</a></td>
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/sagarkori143"><img src="https://avatars.githubusercontent.com/u/129517558?v=4?s=100" width="100px;" alt="Sagar Kori"/><br /><sub><b>Sagar Kori</b></sub></a><br /><a href="https://github.com/asyncapi/website/commits?author=sagarkori143" title="Documentation">📖</a></td>
     </tr>
+    <tr>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/raj17ce"><img src="https://avatars.githubusercontent.com/u/116947399?v=4?s=100" width="100px;" alt="Raj Patel"/><br /><sub><b>Raj Patel</b></sub></a><br /><a href="https://github.com/asyncapi/website/commits?author=raj17ce" title="Code">💻</a></td>
+    </tr>
   </tbody>
 </table>
 

assets/docs/fragments/bindings-overview.md

@@ -0,0 +1 @@
+Bindings in AsyncAPI provide a way to add protocol-specific information to the AsyncAPI documentation. They can be added to different document parts, such as servers, channels, or messages; they specify standard details specific to a particular protocol. The purpose of bindings is to enhance the API's understanding and usage by providing additional context and configuration options for different protocols.

assets/docs/fragments/contribution-notes.md

@@ -0,0 +1,14 @@
+Code isn't the only way to contribute to OSS; Dev Docs are a **huge** help that benefit the entire OSS ecosystem. At AsyncAPI, we value Doc contributions as much as every other type of contribution. ❤️
+
+To get started as a Docs contributor:
+
+1. Familiarize yourself with our [project's Contribution Guide](https://github.com/asyncapi/community/blob/master/CONTRIBUTING.md) and our [Code of Conduct](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md).
+2. Head over to our [AsyncAPI Docs Board](https://github.com/orgs/asyncapi/projects/12).
+3. Pick an issue you would like to contribute to and leave a comment introducing yourself. This is also the perfect place to leave any questions you may have on how to get started.
+4. If there is no work done in that Docs issue yet, feel free to open a PR and get started!
+
+### Docs contributor questions
+
+Do you have a documentation contributor question and you're wondering how to tag me into a GitHub discussion or PR? Never fear!
+
+Tag me in your AsyncAPI Doc PRs or [GitHub Discussions](https://github.com/asyncapi/community/discussions/categories/docs) via my GitHub handle, [`alequetzalli`](https://github.com/alequetzalli) 🐙.

assets/docs/fragments/how-to-contribute.md

@@ -1,23 +1,10 @@
-## How to contribute to AsyncAPI Docs
-
-Did you know that you can contribute Docs to AsyncAPI as well? Code isn't the only way to contribute to OSS; Dev Docs are a **huge** help that benefit the entire OSS ecosystem. At AsyncAPI, we value Doc contributions as much as every other type of contribution. ❤️
-
-To get started as a Docs contributor:
-
-1. Familiarize yourself with our [project's Contribution Guide](https://github.com/asyncapi/community/blob/master/CONTRIBUTING.md) and our [Code of Conduct](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md).
-
-2. Head over to our Docs GH Board [here](https://github.com/orgs/asyncapi/projects/12).
+import ContributionNotes from '@/assets/docs/fragments/contribution-notes.md';
+import TalkToMe from '@/assets/docs/fragments/talk-to-me.md';
 
-3. Pick an issue you would like to contribute to and leave a comment introducing yourself. This is also the perfect place to leave any questions you may have on how to get started.
-
-4. If there is no work done in that Docs issue yet, feel free to open a PR and get started!
-
-### Tag me in your AsyncAPI Doc PRs
-
-Do you have a documentation contributor question and you're wondering how to tag me into a GitHub discussion or PR? Never fear!
+## How to contribute to AsyncAPI Docs
 
-Tag me in your AsyncAPI Doc PRs or [GitHub Discussions](https://github.com/asyncapi/community/discussions/categories/docs) via my GitHub handle, [`/alequetzalli`](https://github.com/alequetzalli) 🐙.
+Did you know that you can contribute Docs to AsyncAPI as well?
+<ContributionNotes />
 
 ### Talk to me
-
-I want and need to listen 👂🏽 to all of your perspectives and ideas. Please don't be shy to express to me what you think needs to be documented first or what is missing. 📝 There's a lot of good work ahead, but **you** determine _our content roadmap_ because the OSS community needs should always come first.✨
+<TalkToMe />

assets/docs/fragments/talk-to-me.md

@@ -0,0 +1 @@
+I want and need to listen 👂🏽 to all of your perspectives and ideas. Please don't be shy to express to me what you think needs to be documented first or what is missing. 📝 There's a lot of good work ahead, but **you** determine _our content roadmap_ because the OSS community needs should always come first.✨