Website Homepage Redesign

[Mayaleeeee]

Description:

The current homepage design has several usability and visual issues. The layout appears cluttered, which impacts the overall user experience and makes navigation less intuitive. Our goal is to create a cleaner, more engaging, and user-friendly homepage that highlights key content and calls to action more effectively.

Your task is to ensure the homepage's overall design and usability are responsive across all device types.

Deliverables (the outcomes that prove this work is complete)

• A fully responsive homepage tested across multiple devices (desktop, tablet, mobile), ensuring layout and content adjust properly.
• Enhanced navigation and visual elements that provide a more engaging user experience.
• A redesigned layout that reduces clutter and organizes content to avoid overwhelming users.

[lucky29-git]

@Mayaleeeee can i work on this?

[Mayaleeeee]

Heads Up!

Hey everyone! 😊

Please hold off on tackling this issue for now. It's planned for a Q4 bounty, and I might add more details before giving it the green light.

I’ll let you know when everything’s good to go! Thanks so much for your patience and understanding.

cc @lucky29-git

[lucky29-git]

Sure, @Mayaleeeee! I've already started my research on this 😀, now am just waiting for your signal. Let me know if there's anything else you need.

[Mayaleeeee]

Sure, @Mayaleeeee! I've already started my research on this 😀, now am just waiting for your signal. Let me know if there's anything else you need.

Hey @lucky29-git

I plan to work on this issue myself for the Q4 bounty program. I really appreciate your interest and enthusiasm! If you're looking for something else to dive into, here's another bounty issue
that you might be interested in.

Thanks for understanding!

[sambhavgupta0705]

Are these designs approved by all code maintainers??
I don't think we have discussed these changes yet

[Mayaleeeee]

Are these designs approved by all code maintainers?? I don't think we have discussed these changes yet

@sambhavgupta0705 Thanks for asking.
The redesign is part of a larger #3018 effort that’s still under discussion and hasn’t been fully approved. I’ll cover this in detail during our meeting on Thursday. Please join us there for more context and to share your thoughts.

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q4, bounty/advanced, bounty/design, bounty/upgraded
First assignment to regular contributors: 2024-09-20 00:00:00 UTC+12:00
End Of Life after: 2024-10-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[Mayaleeeee]

Thanks @aeworxet

I plan to work on this issue myself for the Q4 bounty program.

[aeworxet]

@Mayaleeeee is an AsyncAPI Maintainer specified in https://raw.githubusercontent.com/asyncapi/community/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list.

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Medium	2024-09-17	2024-10-07	2024-11-17	2024-10-20	2024-11-03	2024-11-17

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[Mayaleeeee]

Hey @aeworxet,

After watching the videos created by @derberg on Slack regarding the landing page, I see that the scope of this issue has expanded. It now includes creating additional content, understanding more detailed requirements, and doing some research.

Considering the extra work involved, I want to upgrade this to an advanced issue to reflect the expanded scope.

I’ll add any further details to the issue if needed, but I wanted to give you a heads-up!

Here’s the link to the Slack discussions for reference: link.

[aeworxet]

Upon request of the AsyncAPI Maintainer, who is also the Bounty Program Participant (@Mayaleeeee), the Complexity Level of this Bounty Issue was reclassified to Advanced (upgraded) and its Timeline changed.

Bounty Issue was Reclassified and its Timeline changed

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Advanced	2024-09-17	2024-10-07	2024-12-01	2024-10-27	2024-11-17	2024-12-01

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[aeworxet]

Looping in @fmvilas, @derberg, and @akshatnema in advance, as I will need their opinions anyway.

I would suggest using a 'mobile-first' approach when solving this Bounty Issue, since the 'mobile-first' approach is prevalent in modern web design.

[Mayaleeeee]

Hola, everyone,

Here is a quick update on the project. I’ve started working on the design, and you can find the progress so far in the Figma file linked below:

[Figma Link]

That said, I’ll need to continue working on it after our online conference, as I’ll get more information for the homepage design from Lukasz’s presentation. I’ll keep refining things as I gather the details.

[Mayaleeeee]

Hola, everyone,

Here is a quick update on the project. I have started working on the design using the insights gathered from the clips and the presentation made by @derberg. You can find the WIP design in the Figma file linked below:

Figma Link

[Mayaleeeee]

Hola, everyone,

Here is a quick update on the project. I have completed the deliverables for this issue and updated the other versions of the website. Before moving forward, I am waiting for a review from one of the code maintainers, @derberg.

I also explain each section of the new design during our design meeting. You can find the recording here.

You can find the screenshot of the designs below or here in the Figma file. cc @ @aeworxet

[Mayaleeeee]

Hi @aeworxet

I want an extension for the project until the second week of December.

Thank you

[aeworxet]

Upon request of the AsyncAPI Maintainer, who is responsible for the resolution of the Bounty Issue from the AsyncAPI's side and is also the Bounty Program Participant (@Mayaleeeee, githubID 105395613), all remaining target dates of the Bounty Issue's Timeline are extended by two calendar weeks.

Bounty Issue's Timeline Extended

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Advanced	2024-09-17	2024-10-07	2024-12-15	2024-10-27	2024-11-17	2024-12-15

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[aeworxet]

AsyncAPI Maintainer (@akshatnema, githubID 76521428) delayed response in Slack for two periods of three consecutive working days, so all remaining target dates of the Bounty Issue's Timeline are extended by two calendar weeks.

Bounty Issue's Timeline Extended

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Advanced	2024-09-17	2024-10-07	2024-12-29	2024-10-27	2024-11-17	2024-12-29

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[aeworxet]

Discussion on latest changes is currently ongoing in Slack.

[aeworxet]

@Mayaleeeee, the AsyncAPI Maintainer who is responsible for the resolution of this Bounty Issue from the AsyncAPI's side, is still not available, without a clear time limit on the absence, so this Bounty Issue's Timeline is frozen for an indefinite amount of time.