You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current placement and elements of the contact us section on our website need to be redesigned for better usability and visual coherence. The issues include improper button styling, poor visibility of the input box, and the need to integrate the feedback form into a more accessible area of the website, away from the footer.
Current Issues:
Button Styling: The buttons within the contact us section lack proper styling, which affects their consistency with the overall website design.
Input Box Visibility: The input box for user contact details is not prominently visible or clearly distinguishable from surrounding elements.
Feedback Form Integration: The feedback form is currently located in the footer, which makes it less accessible and disrupts user interaction flow.
Expected behavior
Desired Corrections:
Button Design: Ensure that buttons in the contact us section are styled consistently with the website's design language, including hover and active states for improved user feedback.
Input Box Visibility: Enhance the visibility and usability of the input box, making it more prominent and user-friendly.
Optimal Feedback Form Placement: Integrate the feedback form into a more prominent and accessible area of the website, such as the sidebar or a dedicated contact page, to improve user engagement and usability.
The redesigned contact us section should be visually appealing, easy to use, and seamlessly integrated into the website's navigation and user experience. Users should find it straightforward to locate and utilize the contact options provided.
Add ScreenShots
On which device are you experiencing this bug?
No response
Record
I have read the Contributing Guidelines
I'm a GSSOC'24 contributor
I'm a VSOC'24 contributor
I have starred the repository
The text was updated successfully, but these errors were encountered:
@AsmitaMishra24 I have assigned u , just want to request u that can u provide the SS of the new contact us section after your contribution , so that it will be helpful
@AsmitaMishra24 I have assigned u , just want to request u that can u provide the SS of the new contact us section after your contribution , so that it will be helpful
@apu52, Sure, also I will move the feedback section to the footer. Is that okay, or should I keep the feedback as it is?
@AsmitaMishra24 I have assigned u , just want to request u that can u provide the SS of the new contact us section after your contribution , so that it will be helpful
@apu52, Sure, also I will move the feedback section to the footer. Is that okay, or should I keep the feedback as it is?
no keep it as it is .or maybe u can implement this button in more advanced UI
@AsmitaMishra24 I have assigned u , just want to request u that can u provide the SS of the new contact us section after your contribution , so that it will be helpful
@apu52, Sure, also I will move the feedback section to the footer. Is that okay, or should I keep the feedback as it is?
no keep it as it is .or maybe u can implement this button in more advanced UI
Is there an existing issue for this?
Describe the bug
The current placement and elements of the contact us section on our website need to be redesigned for better usability and visual coherence. The issues include improper button styling, poor visibility of the input box, and the need to integrate the feedback form into a more accessible area of the website, away from the footer.
Current Issues:
Expected behavior
Desired Corrections:
The redesigned contact us section should be visually appealing, easy to use, and seamlessly integrated into the website's navigation and user experience. Users should find it straightforward to locate and utilize the contact options provided.
Add ScreenShots
On which device are you experiencing this bug?
No response
Record
The text was updated successfully, but these errors were encountered: