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 "Go to Top" button currently has inconsistent designs across different pages, with the version on the About page offering the best UI and functionality. This issue proposes using the About page's "Go to Top" button design as a standard and implementing it site-wide to enhance uniformity and user experience. Additionally, the chatbot is not visible on every page, limiting access to support options. This update will include adding the chatbot icon consistently across all pages, ensuring seamless user support navigation.
Steps to Reproduce
NA
Expected Behavior
No response
Screenshots/Logs
Additional Information
I agree to follow this project's Code of Conduct
I'm a GSSOC'24 contributor
I want to work on this issue
I can provide more details if needed
The text was updated successfully, but these errors were encountered:
👋 Thanks for opening this issue! We appreciate your contribution. Please make sure you’ve provided all the necessary details and screenshots, and don't forget to follow our Guidelines and Code of Conduct. Happy coding! 🚀
Priyanshi0112
changed the title
BUG:
BUG: Standardize 'Go to Top' Button Across Pages and Ensure Chatbot Visibility on All Pages
Nov 4, 2024
Preliminary Check
Bug Summary
The "Go to Top" button currently has inconsistent designs across different pages, with the version on the About page offering the best UI and functionality. This issue proposes using the About page's "Go to Top" button design as a standard and implementing it site-wide to enhance uniformity and user experience. Additionally, the chatbot is not visible on every page, limiting access to support options. This update will include adding the chatbot icon consistently across all pages, ensuring seamless user support navigation.
Steps to Reproduce
NA
Expected Behavior
No response
Screenshots/Logs
Additional Information
The text was updated successfully, but these errors were encountered: