-
-
Notifications
You must be signed in to change notification settings - Fork 638
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
Enhancement Request: Improving the What the experts are saying Section on the AsyncAPI Website #1696
Comments
Is it "What the experts are saying section"? @Mayaleeeee |
I can work on it! |
Yeah, thanks for the correction. |
Signed-off-by: SumantxD <[email protected]>
@Mayaleeeee How does this design look? PR #1698 |
@Mayaleeeee i have tried solving this issue here is the PR #1697 |
Please follow the discussion workflow I was already working on this issue!! |
@Lucif3r-in but you were not assigned |
@Lucif3r-in and @SumantxD, this issue is still under review. In terms of assigning issues, it'll be given to the first person who showed interest first!! Kindly wait until then! |
@Mayaleeeee, I totally agree it makes sense to make some improvements. wdyt @derberg @AceTheCreator? |
Thanks @thulieblack |
Please check the updated PR #1704 |
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 ❤️ |
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 ❤️ |
is this still valid? @Mayaleeeee |
yeah, you can check it here |
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 ❤️ |
Still valid! |
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 ❤️ |
This will be done on the homepage redesign project #3192 |
Reason/Context
Why do we need this improvement?
The current testimonial section on the AsyncAPI website needs improvement for several reasons. Firstly, the testimonial section appears jampacked and clustered together, making it challenging for users to quickly and easily access individual testimonials. The crowded layout hampers readability and can overwhelm users with excessive content presented at once. We can create a more user-friendly and engaging experience for website visitors by addressing this issue and improving the testimonial section.
How will this change help?
Implementing the suggested improvements to the testimonial section will have several positive impacts by enhancing the readability and usability of the testimonials by providing a clear separation between each testimonial. Users will be able to focus on and absorb the content of each testimonial without being overwhelmed by a cluttered layout. Additionally, incorporating adequate white space and a visually appealing design will improve the overall aesthetics of the testimonial section, making it more visually appealing and engaging for users.
What is the motivation?
As a Product Designer, my motivation is crafting seamless and enjoyable experiences for website visitors, ensuring easy access and engagement with desired content. By advocating for improvements to the testimonial section, I aim to enhance user-friendliness, visual appeal, and overall satisfaction with the AsyncAPI website.
Description
I recommend a redesigned testimonial section that offers a more organized and visually appealing presentation. This can be achieved by carefully implementing clear separation between testimonials, allowing users to focus on one testimonial at a time. Additionally, establishing a clear visual hierarchy within the section can be accomplished using larger or stylized fonts for testimonial quotes and design elements like quotation marks or speech bubbles to emphasize the testimonial content. By incorporating adequate white space, readability will improve, and the testimonials will have room to shine.
To implement the improvement, a single testimonial display with pagination can be utilized, allowing users to view one testimonial at a time and easily navigate through them, providing a focused and user-friendly browsing experience. This design approach ensures that each testimonial receives proper attention while maintaining an organized and visually pleasing layout.
Let me provide you with an example to illustrate what I mean. Imagine a testimonial section where testimonials automatically rotate, showcasing one testimonial at a time. Unlike this example, our design will include a pagination feature, allowing users to navigate through the testimonies at their own pace manually. However, our envisioned design will incorporate a pagination feature, allowing users to navigate the testimonies at their own pace manually. In this implementation, the prominently highlighted testimonial will briefly appear and fade away after a few seconds, making way for the following testimonial. Users can seamlessly utilize the pagination controls to explore the testimonials according to their preferences.
@AceTheCreator @thulieblack @derberg @akshatnema
The text was updated successfully, but these errors were encountered: