Skip to content
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

[Feature] Implement a "Back to Top" Button for Improved Navigation #474

Open
1 task done
akathedeveloper opened this issue Aug 15, 2024 · 1 comment
Open
1 task done
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@akathedeveloper
Copy link

Problem

While navigating a long webpage, I found it inconvenient to scroll all the way back to the top after reaching the bottom. This manual scrolling can be time-consuming and disrupts the flow of browsing.

Description

To address this issue, I suggest adding a "Back to Top" button that appears once the user scrolls down the page. This button would allow users to quickly return to the top with a single click, improving the overall user experience.

Alternatives

Currently, the only alternative is manually scrolling back up, which can be tedious on long pages. The "Back to Top" button would provide a more efficient and user-friendly solution.

Additional context

This feature would be particularly useful for pages with a lot of content or where users frequently need to return to the top. A smooth scrolling effect when clicking the button would enhance the user experience.

Implementation

  • I would be interested in implementing this feature.
@akathedeveloper akathedeveloper added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Aug 15, 2024
@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 💻 aspect: code Concerns the software code in the repository labels Aug 22, 2024
@TimidRobot
Copy link
Member

🚧 status: blocked Blocked & therefore, not ready for work pending decision on how this will/won't be done in creativecommons/vocabulary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

2 participants