Proposal to Redesign the AsyncAPI Website

[Mayaleeeee]

I propose redesigning the AsyncAPI website to address numerous structural, usability, and user experience issues identified during the UX audit I conducted while working on the Design System. These issues are pervasive across almost every part of the website, necessitating a redesign. This proposal outlines the steps to enhance the user experience and interface.

Why We Need This Redesign

A better user experience on our website will:

1. Foster Growth: A seamless and enjoyable user experience will encourage more users to engage with our tools and community.
2. Demonstrate Commitment: Improving our website shows that we care about our users' experiences, leading to increased user satisfaction and loyalty.
3. Attract Designers: This project will generate more design-related issues, attracting designers and UX researchers to contribute to our project and fostering community involvement.

Goals

1. Enhance Usability: Simplify the website structure and improve navigation to make it more intuitive for users.
2. Improve User Experience: Address interface issues and create a visually appealing, user-friendly design.
3. Engage the Community: Encourage contributions from designers and developers by creating a collaborative environment.

Implementation Plan

Phase 1: Planning and Initial Redesign

• Proposal Discussion: Create a proposal to discuss the redesign and gather initial feedback from community stakeholders. - (what I'm currently doing)
• Create and Prioritize Issues: Based on the UX audit findings, create and prioritise issues for the redesign.
• Initial Design Work: Start with the homepage redesign and expand to other website sections.

Phase 2: User Research and Validation

• Usability Testing: Conduct usability tests on the redesigned sections to gather feedback and identify any remaining issues.
• A/B Testing: Implement A/B testing to compare the new design with the current version and measure user engagement and satisfaction improvements.

Phase 3: Development and Iteration

• Implement Design Changes: Begin development based on validated design improvements.
• Ongoing Testing and Feedback: Continuously gather feedback through additional usability and A/B testing to ensure ongoing improvements.

I am fully committed to driving this redesign effort. I have already started with the homepage redesign and am prepared to lead the redesign of the other website sections. You can review the UX Audit for more details.

All feedback and suggestions are welcome. Your input is invaluable in making the AsyncAPI website better for everyone. Please feel free to share your thoughts and ideas in the comments.

@asyncapi/tsc_members Your input is important to us. Please join the conversation and vote!

Thank you for your support and collaboration.

[Mayaleeeee]

/vote

[git-vote]

Vote created

@Mayaleeeee has called for a vote on Proposal to Redesign the AsyncAPI Website (#1231).

The members of the following teams have binding votes:

Team
@asyncapi/tsc_members

Non-binding votes are also appreciated as a sign of support!

How to vote

You can cast your vote by reacting to this comment. The following reactions are supported:

In favor	Against	Abstain
👍	👎	👀

Please note that voting for multiple options is not allowed and those votes won't be counted.

The vote will be open for 28days. It will pass if at least 51% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.

[asyncapi-bot-eve]

Hi @Mayaleeeee, since you are not a TSC Member, you cannot start or stop voting. Please read more about voting process

[Mayaleeeee]

That's incorrect, @asyncapi-bot-eve. I am a TSC member.

[jonaslagoni]

I dont see how this is a TSC decision 🤔

It's up to the codeowners of the website to decide whatever they want to happen with it 🤨

[Mayaleeeee]

I dont see how this is a TSC decision 🤔

It's up to the codeowners of the website to decide whatever they want to happen with it 🤨

Thank you for your feedback!

While code owners manage the website, a major redesign affects the community by improving usability and user experience, which benefits all users. Involving the TSC ensures we have broad support and input from key stakeholders. We highly value the code owners' expertise and want to ensure this initiative aligns with our collective goals.

Thank you!

[akshatnema]

These issues are pervasive across almost every part of the website, necessitating a redesign.

@Mayaleeeee Can you please list out these issues on the website? Currently, we are already migrating to new Figma design (created by you), as per the New UI Design Kit for website project. So, how are you planning these changes and why aren't they accounted in the present design?

cc: @AceTheCreator

[akshatnema]

For better visibility, tagging codeowners of the website - @anshgoyalevil @sambhavgupta0705

[Mayaleeeee]

These issues are pervasive across almost every part of the website, necessitating a redesign.

@Mayaleeeee Can you please list out these issues on the website? Currently, we are already migrating to new Figma design (created by you), as per the New UI Design Kit for website project. So, how are you planning these changes and why aren't they accounted in the present design?

cc: @AceTheCreator

Thanks for raising this question.

The UX audit helped shape the design system/UI Kit I created. It identified key issues, which I addressed by developing components for the system. However, these were noted not in the Figma design system but in another file called - UX Audit.

Additionally, redesigning the homepage (the one in the Figma DS) wasn't initially on the agenda. I did it to test how the design system was coming along. It wasn't part of the task list, but it was necessary.

The proposal I've made aims to implement these changes into the website redesign. Once accepted, I'll follow the plan highlighted in this proposal for the redesign, focusing on the specific sections and issues that need attention.

I hope this clears things up. Thank you!

[Mayaleeeee]

Hey everyone! Let's keep this conversation going over on the website repo.

Thanks a bunch!

asyncapi/website#3018

[Shurtu-gal]

That's incorrect, @asyncapi-bot-eve. I am a TSC member.

@Mayaleeeee I believe the GitHub username is case sensitive. Could you raise a PR changing the following.

https://github.com/asyncapi/community/blob/master/MAINTAINERS.yaml#L2

[git-vote]

Vote status

So far 0.00% of the users with binding vote are in favor (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
0	0	3	43

Binding votes (3)

User	Vote	Timestamp
akshatnema	Abstain	2024-06-03 9:25:59.0 +00:00:00
fmvilas	Abstain	2024-06-05 7:01:35.0 +00:00:00
jonaslagoni	Abstain	2024-06-03 8:56:48.0 +00:00:00
@whitlockjc	Pending
@char0n	Pending
@emilianozublena	Pending
@GreenRover	Pending
@Amzani	Pending
@theschles	Pending
@smoya	Pending
@ivangsa	Pending
@dan-r	Pending
@kennethaasan	Pending
@dalelane	Pending
@lbroudoux	Pending
@GeraldLoeffler	Pending
@Pakisan	Pending
@Tenischev	Pending
@anandsunderraman	Pending
@VisualBean	Pending
@M3lkior	Pending
@derberg	Pending
@BOLT04	Pending
@alequetzalli	Pending
@magicmatatjahu	Pending
@ron-debajyoti	Pending
@rcoppen	Pending
@CameronRushton	Pending
@KhudaDad414	Pending
@AceTheCreator	Pending
@Florence-Njeri	Pending
@Souvikns	Pending
@devilkiller-ag	Pending
@princerajpoot20	Pending
@KieranM1999	Pending
@imabp	Pending
@Samridhi-98	Pending
@aayushmau5	Pending
@mcturco	Pending
@NektariosFifes	Pending
@thulieblack	Pending
@sambhavgupta0705	Pending
@lewis-relph	Pending
@anshgoyalevil	Pending
@Shurtu-gal	Pending
@Mayaleeeee	Pending

[derberg]

please remember to follow docs https://github.com/asyncapi/community/blob/master/voting.md

when voting is canceled, it should be canceled

[derberg]

/cancel-vote

[git-vote]

Vote cancelled

@derberg has cancelled the vote in progress in this issue.