🐞[Bug]: Fixed scroll arrow buttons on FAQ page causing poor UX and visual clutter

[rahulrr-coder]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

On the FAQ page (https://www.recodehive.com), there are two fixed arrow buttons positioned on the right side of the page - a blue upward arrow and a green downward arrow. These buttons are meant for scrolling to the top and bottom of the page.

Issues identified:

1. Redundant functionality: Having both scroll-to-top and scroll-to-bottom buttons is unnecessary. Users can naturally scroll down, but a scroll-to-top button is more useful.
2. Poor visual design: The buttons are statically fixed in their position, creating visual clutter and disrupting the clean UI of the FAQ page.
3. User experience: The buttons appear buggy and don't provide a good user experience. They remain visible at all times, which is distracting.
4. Obstructs content: The fixed positioning can potentially obstruct or overlap with page content, especially on smaller screens.

Current behavior:

• Both arrow buttons are permanently visible and fixed on the right side
• They remain in the same position regardless of scroll position
• The styling doesn't match well with the overall page aesthetics

Expected behavior

Recommended solutions:

1. Remove the scroll-to-bottom button entirely - This is rarely needed as users naturally scroll down.

2. Improve scroll-to-top button behavior:

   • Show the scroll-to-top button only when the user has scrolled down a certain distance (e.g., after 300-400px)
   • Hide it when at the top of the page
   • Use smoother animations for appearance/disappearance
   • Improve the styling to better match the website's design system

3. Better positioning: Consider repositioning to the bottom-right corner with appropriate spacing to avoid content obstruction.

4. Accessibility: Ensure proper ARIA labels and keyboard navigation support.

Add ScreenShots

What browsers are you seeing the problem on?

Firefox

Record

• I have read the Contributing Guidelines
• Are you a GSSOC'25 contributor
• I want to work on this issue

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[github-actions]

👤 Issue assigned to @rahulrr-coder.

[github-actions]

✅ This issue has been closed. Thank you for your contribution!