[📑 Docs]: Add Django and FastAPI to asyncapi-tool supported technologies list

[huynguyengl99]

What Dev Docs changes are you proposing?

I’m preparing to submit a package defined via .asyncapi-tool, and it currently supports two well-known technologies: Django and FastAPI.

To ensure proper tagging and better visibility in the AsyncAPI ecosystem, I would like to update the file tags-color.ts to include Django and FastAPI as supported technologies.

These frameworks are widely used, and adding them will help the community categorize and discover packages more effectively.

I’m happy to follow the contribution process, and I’m also willing to work on this issue if needed.

Code of Conduct

• I agree to follow this project's Code of Conduct

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[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.

[princerajpoot20]

@huynguyengl99 Can you please share your tool where you have been using these technologies

[huynguyengl99]

Here’s my package repository: https://github.com/huynguyengl99/chanx

I recently updated the .asyncapi-tool file and plan to add the technologies once this PR is accepted:
https://github.com/huynguyengl99/chanx/blob/main/.asyncapi-tool

In short, the package helps build WebSocket apps, automatically generates AsyncAPI docs from code, and also provides a CLI to generate WebSocket clients from AsyncAPI definitions. It supports both Django and FastAPI, so I hope this PR can be accepted.

[princerajpoot20]

@huynguyengl99 Your .asyncapi-tool file is not following the required convention.

Please refer to this document on how to add the .asyncapi-tool file: https://www.asyncapi.com/docs/community/040-guides/add-new-asyncapi-tool-to-website .

If you still face any issues, I will be happy to help you. Thanks!

[huynguyengl99]

@princerajpoot20 Thanks for the clarification.
I may be missing something, but I followed the template from:
https://www.asyncapi.com/docs/community/040-guides/add-new-asyncapi-tool-to-website#yaml-format-file-structure

I copied the structure and updated the fields according to my package.
The only fields I removed were:

• links.websiteUrl — since I only have a GitHub repository, and I noticed some other tools omit this as it’s not required.
• filters.technology — because this PR to add Django and FastAPI as supported technologies is still pending. I plan to include them once it’s accepted.

I’m not fully sure which part of my .asyncapi-tool file is not following the required convention. Could you help point out what I should adjust? After the PR is approved, I will add Django and FastAPI under filters.technology as expected.

Thanks for the guidance!

[princerajpoot20]

@huynguyengl99 Oh, got it — you haven't added the technology part. Please add it to your repository first; only then does it make sense to add it to our website.

We need a reason/justification for why we are adding it on our end. Hence, I'm requesting you to please complete the .asyncapi-tool file on your side first, then update the issue here by giving a reference/reason to your file. We will then add it accordingly.

Hope it makes sense to you.

[huynguyengl99]

Okay, I’ll go ahead and add Django and FastAPI as the technologies for my tool first. Hopefully it will pass the CI/workflow checks and allow the tool to appear in the AsyncAPI tools list. If there are any updates regarding the acceptance or rejection of Django and FastAPI as AsyncAPI tool technologies, please let me know so I can update or remove them if needed.

[princerajpoot20]

As I mentioned before, you can simply go ahead and make changes in your repo. Nothing is going to break on our end. It will simply not show up on our website until we add your technology to our data.

[princerajpoot20]

@huynguyengl99 PR to show your tool has been created by the bot. Here is the PR: #4692. Your tool will be visible once it is merged.
We currently have a flaky CI pipeline, and a fix is in progress. It will be merged soon.

Thanks!

[huynguyengl99]

Thank you @princerajpoot20 , looks like my tool appeared in the https://www.asyncapi.com/tools, so should I close this PR and the issue?