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

Improve Project page UX by Adding a return to projects button. #2805

Open
2 tasks done
kartikey2001 opened this issue Oct 24, 2024 · 3 comments
Open
2 tasks done

Improve Project page UX by Adding a return to projects button. #2805

kartikey2001 opened this issue Oct 24, 2024 · 3 comments

Comments

@kartikey2001
Copy link
Contributor

kartikey2001 commented Oct 24, 2024

Have you checked that your feature request isn't already filed?

  • I read through FAQ and searched through the past issues, none of which addressed my feature request.
  • Yes, I have checked that this feature request isn't already filed.

Description & Motivation

I would like to suggest an improvement to the Project page to enhance the user experience. Currently, the page lacks a return button which will bring the user back to the project section page, and I believe adding the following changes will significantly improve usability.

Current Behavior:
If we currently open a project card there is no way to return back to the project page.

Pitch

[Change 1]: I would like to add a button which will take us back to the project page.

Why this is needed: It will make the page more efficient.

How it helps: It will make it easier for the users to toggle between the different pages.

image

This is a sample of the return button .

After the proposed changes are made:
Users will be able to easily able to toggle between different projects.
The overall user experience will be improved by this one button.

Alternatives

No response

Additional context

If you have any specific design or suggestions for this feature, I would appreciate your feedback.

I am eager to contribute to improving the user experience by working on this feature. May I proceed with the development and submit a pull request for your review?

@george-gca
Copy link
Collaborator

I am not convinced. You can either click on the projects tab on the header and it will take you there, or click the back button of your browser. Why would we need another button for this?

@kartikey2001
Copy link
Contributor Author

While navigating the site, I noticed a usability challenge when moving from the project card section back to the main project page. It felt unintuitive, as most users today prefer simpler navigation without relying on the browser's back button, which can disrupt focus. Repeatedly using the main navigation bar to return feels inconvenient and affects the flow of the experience. Adding a dedicated "Back" button or link would enhance the UI, keeping users’ attention on the content and making navigation more seamless.

If you’d like, you could gather feedback from users or team members with a poll to see if this navigation feature would be beneficial for them in future updates.

@george-gca
Copy link
Collaborator

It felt unintuitive, as most users today prefer simpler navigation without relying on the browser's back button, which can disrupt focus.

This seems too much strong of an affirmative. Can you back this up? I mean, is there a recent study showing that most users today don't use the browser's back button?

I know that the back button might behave unintuitively when the site is heavy on ajax, meaning that the browser can't really detect the previous state and then go back correctly, but this is not the case with this template.

I don't feel the urge to create a back button in this page (or in the blog posts, which would be a similar case to this). But I am not against creating a poll to gather more information about this need. Can you create this one? I believe you will better describe the situation and its needs in it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants