snapcraft.io
snapcraft.io copied to clipboard
/store: UX Search bar should always be available
I think that withing the store pages, the search bar should always be available. Currently if you want to search a new snap after you clicked on a snap page, you need to click back on the store link and begin searching.
Expected behaviour
Clicking into a snap, that the search bar for searching snaps to be still avalable
Steps to reproduce the problem
Click on the link to a snap page on the store, you don't have the search bar.
Specs
- URL: e.g. https://snapcraft.io/node
- Operating system: Ubuntu 20.04
- Browser: Chrome stable
I agree that this is a great idea!
@clagom here's a quick proposal https://zpl.io/aNedZ5k would you mind taking a look?
I'm happy about that. I tried to check the link, is it meant to be private or is it so by mistake? :relaxed:
@fcole90 sorry, should've posted the screenshots as well :)
I think it's a good improvement. Maybe snapcraft.io/store doesn't need to change, visually, from the current search bar/suru design, but it's a detail.
@spencerbygraves you may want to have a visual look at this
@clagom both Charm Hub and Jaas have the search bar in the header. I can see that space is tight but should we have something consistent with that? ubuntu.com also has the search there.
I thought about that @spencerbygraves, but that would be a bigger change with some ripple effects on the homepage and on the store landing page design. Feels this might be a good first step towards that, with more data from users to see if the change is effective at all.
Just a quick and rough idea, but how about having a little more extended header that includes the search bar? In this way it is available but not so much prominent and giving more importance to the main content :blush:
On the home page it could stay as it is, as there it would make more sense to have it being more prominent. Like google home page vs a search page :blush:
As we will be working on a potentially much bigger redesign of the chrome of Snapcraft, I will move this issue to icebox to consider then, as it could bring a number of breaking changes.