inconsistent visibility of AsyncAPI Studio (Beta) in Documentation Tools section

[Jatin24062005]

Description
AsyncAPI Studio is a really well-built and promising project for visually designing AsyncAPI documents and event-driven architectures. It is clearly highlighted in the header → Tools dropdown as “Studio (Beta)”, which is great.

However, when navigating to the Docs → Tools section, AsyncAPI Studio is not listed or documented at all, while other tools like Generator, CLI, Modelina, Parsers, etc., are present.

This creates confusion for users because:

• Studio appears to be an official tool (visible in the main navigation)
• But it has no dedicated entry or documentation under the Tools section
• New users may miss Studio entirely when browsing documentation

---

📍 Where the issue appears

• Header → Tools dropdown: Shows Studio (Beta) ✅
• Docs → Tools → Overview: Studio is missing ❌

---

✅ Expected behavior

• AsyncAPI Studio should be listed in the Docs → Tools section

• Ideally include:

  • A short overview of AsyncAPI Studio
  • Its purpose (visual editor for AsyncAPI files)
  • Status clearly marked as Beta
  • Link to Studio usage or getting-started guide

---

💡 Why this matters

AsyncAPI Studio is one of the most user-friendly ways to work with AsyncAPI, especially for:

• Beginners
• Architects
• Visual learners

Having structured documentation alongside other tools would significantly improve discoverability and adoption.

---

📸 Screenshots

1. Studio in the header Tools dropdown
2. Studio missing from Docs → Tools section)

[github-actions]

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.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[sammy200-ui]

@Jatin24062005 this might be a intentional design choice, cause studio is a app and has tutorial build in it . But still a valid issue that can addressed for once

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

[princerajpoot20]

@Jatin24062005 @sammy200-ui
Regarding your missing docs issue, it is not a website issue. The website only renders what it gets from the respective repository. So basically, there are no docs present in the Studio repo. Reference: https://github.com/asyncapi/studio/tree/master/docs

Once you add the docs there, they will automatically be propagated to the website.

Hence, transferring this issue to the Studio repo as it is not in the scope of the website repo.

[github-actions]

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.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.