nest.land
nest.land copied to clipboard
nestdotland
Better UX please
Is your feature request related to a problem? If so, please describe. When a user clicks a module, she is redirected. When using the back button to return to the main page, she is always taken to the top of the main page. This is very frustrating.
Describe the solution you'd like Right clicking on a module should show a context menu that would allow an 'Open in new tab' option. This would allow the user to go back to the main page tab and continue browsing from where she left off.
Hi @nhrones! Thanks for the feedback.
If I'm understanding correctly, you'd like to see:
- A "scroll" rememberer that can save your last scroll position when navigating back and forth from the modules gallery
- An anchor element on the gallery cards so you can right click and see "open in a new tab"
Let me know if I got this correct. These would both be great hacktoberfest issues!
Yes! You are correct. There are not that many elements in your database now, but eventually there could be tens of thousands. I love the tech-base this service is built on, but the UX is just too frustrating to use. I'd also like to see some basic filtering and search features. I'm a retired programmer with lots of free time. Let me know how I can help.
On Fri, Oct 16, 2020 at 9:07 AM Tate Berenbaum [email protected] wrote:
Hi @nhrones https://github.com/nhrones! Thanks for the feedback.
If I'm understanding correctly, you'd like to see:
- A "scroll" rememberer that can save your last scroll position when navigating back and forth from the modules gallery
- An anchor element on the gallery cards so you can right click and see "open in a new tab"
Let me know if I got this correct. These would both be great hacktoberfest issues!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nestdotland/nest.land/issues/295#issuecomment-710034071, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZAPQ2XTNSTJJFXIXN5TNTSLBASXANCNFSM4SSRU5TQ .
I might be wrong, but according to this StackOverflow answer, we should just be able to wrap the content inside of the <router-link> component in an <a> tag. I can try this out and make a PR.
