-
-
Notifications
You must be signed in to change notification settings - Fork 776
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
[FEATURE] Roadmap Page Needs UI Redesign for Better Usability #3668
Comments
@Mayaleeeee Have a look at this. Do we need to redesign the roadmap page? And if so, how should we proceed? |
@akshatnema @derberg I have been having this on my mind for a while, and I have also tried tweaking the design and content. I would love to proceed with this. Let me know your thoughts! |
Yeah, we do. A redesign of the page will make it look appealing and user-friendly. Who is working on it? You or @Shriya-Chauhan |
I think @Shriya-Chauhan is interested in continuing with it. However, I can help with reviewing the design and code part. @Shriya-Chauhan You can continue working on this and share a draft of design with us. |
Alright! |
@devilkiller-ag @Mayaleeeee, isn't this issue part of the redesign of the website idea? |
Oh, I totally forgot about that! Thanks for reminding me. @Shriya-Chauhan |
Why do we need this improvement?
Description:
The current UI of the roadmap page is not visually appealing, and the text feels too cluttered, making it difficult to read and navigate. A cleaner and more structured design is needed to improve usability.
How will this change help?
A well-structured and visually appealing page will make it easier for the community to understand AsyncAPI’s direction and contribute effectively. Open to discussing design suggestions and potential improvements!
Screenshots
How could it be implemented/designed?
Suggested Improvements:
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: