[Help Design Lemmy] Search Improvements
-
In a recent discussion it was mentioned that the search function in Lemmy is awkward to use and could be improved. As a result I already made two small changes:
- Change community selector to use
!community@example.comformat (#3218) - Search field in community sidebar (#3217)
Are there any other UI or UX changes you can think of to improve searching in Lemmy? Im mainly looking for frontend changes, such as reorganizing the input positions, changing default values etc.
As far as I remember, the loading indicator disappears when the local search is finished and the search appears to be done, even when the remote search is continuing. This makes finding a new remote community pretty awkward.
- Change community selector to use
-
In a recent discussion it was mentioned that the search function in Lemmy is awkward to use and could be improved. As a result I already made two small changes:
- Change community selector to use
!community@example.comformat (#3218) - Search field in community sidebar (#3217)
Are there any other UI or UX changes you can think of to improve searching in Lemmy? Im mainly looking for frontend changes, such as reorganizing the input positions, changing default values etc.
I'm not a UI or UX expert, but I wonder if it would make the search page nicer if instead of the search target (form select) would be tabs instead of a dropdown since it is distinct selection from the other filters in the search?
using bootstrap tabs (I didn't put any effort into styling just added bootstrap tabs and removed the form select butto dropdown):
Edit: now that I think about it, the tab might be kinda confusing unless also the other dropdowns are slightly altered to give more context in the current form selection tab, e.g. (text changes):
But yeah I just wanted to throw out ideas, I'm not sure about them myself. The search inside a community is nice addition!
- Change community selector to use
-
As far as I remember, the loading indicator disappears when the local search is finished and the search appears to be done, even when the remote search is continuing. This makes finding a new remote community pretty awkward.
Right, this is because it currently uses two separate api calls for search and resolve object. It will be fixed in 1.0 with https://github.com/LemmyNet/lemmy/pull/5752.
-
I'm not a UI or UX expert, but I wonder if it would make the search page nicer if instead of the search target (form select) would be tabs instead of a dropdown since it is distinct selection from the other filters in the search?
using bootstrap tabs (I didn't put any effort into styling just added bootstrap tabs and removed the form select butto dropdown):
Edit: now that I think about it, the tab might be kinda confusing unless also the other dropdowns are slightly altered to give more context in the current form selection tab, e.g. (text changes):
But yeah I just wanted to throw out ideas, I'm not sure about them myself. The search inside a community is nice addition!
The tabs could make sense, but then they should be between the search bar and results, because each tab has the same buttons. You can make a pull request with what you have so far and then we can discuss it in detail.
-
The tabs could make sense, but then they should be between the search bar and results, because each tab has the same buttons. You can make a pull request with what you have so far and then we can discuss it in detail.
Ah good point!
I'll hopefully manage to set up lemmy-ui locally at home after work and make that pull request - I edited that in with webdev tools since didn't want to lose that thought before I get home (sorry if this just pollutes the discussion).
-
In a recent discussion it was mentioned that the search function in Lemmy is awkward to use and could be improved. As a result I already made two small changes:
- Change community selector to use
!community@example.comformat (#3218) - Search field in community sidebar (#3217)
Are there any other UI or UX changes you can think of to improve searching in Lemmy? Im mainly looking for frontend changes, such as reorganizing the input positions, changing default values etc.
One of my most favourite things was watching the wizards over in r/BotDefense killing shitbots enmass via the open API weddit had until spez got even more greedy.
I know it's not directly tied to what you're asking via the UI, but I am interested in how you could help some of those excellent bot hunters of day gone yonder.
- Change community selector to use
-
When you do a search and it returns a mix of communities, posts, comments, users... They all sorta jumble together in weird ways. Maybe the content type of the search should not default to "All" maybe it should default to "Posts" or even just blank (forcing the user to choose).
Also the mixed results all jumble together, communities and users are tiny lines of text compared to posts and comments, maybe they need to have borders or more spacing. And maybe add more info next to communities and users.
Makes sense. My idea is to use a fixed order for the different types of results, eg always put communities first, then users etc. What do you think? For communities it would make sense to display the short description as well, and for users both post and comment count?
-
Makes sense. My idea is to use a fixed order for the different types of results, eg always put communities first, then users etc. What do you think? For communities it would make sense to display the short description as well, and for users both post and comment count?
Yea I don't think it makes any sense to try to sort these items against each other. Maybe section headers would be nice too, a title for the
Communities:section, etc? -
Ah good point!
I'll hopefully manage to set up lemmy-ui locally at home after work and make that pull request - I edited that in with webdev tools since didn't want to lose that thought before I get home (sorry if this just pollutes the discussion).
No worries. Make sure to follow the documentation on join-lemmy.org for development, and use the
release/v0.19branch for both lemmy and lemmy-ui as the main branch is currently broken due to 1.0 changes. -
Yea I don't think it makes any sense to try to sort these items against each other. Maybe section headers would be nice too, a title for the
Communities:section, etc?I thought about that too, have to figure out how it can be implemented (im not very good at frontend stuff).
-
One of my most favourite things was watching the wizards over in r/BotDefense killing shitbots enmass via the open API weddit had until spez got even more greedy.
I know it's not directly tied to what you're asking via the UI, but I am interested in how you could help some of those excellent bot hunters of day gone yonder.
Lemmy has an open API, and instance admins have even more data available by accessing the database directly. One of the lemmy.world admins is also working on a feature for vote analytics, though at Lemmy's current size it seems very low priority.
-
In a recent discussion it was mentioned that the search function in Lemmy is awkward to use and could be improved. As a result I already made two small changes:
- Change community selector to use
!community@example.comformat (#3218) - Search field in community sidebar (#3217)
Are there any other UI or UX changes you can think of to improve searching in Lemmy? Im mainly looking for frontend changes, such as reorganizing the input positions, changing default values etc.
For post searches, could there be a [] Search Title Only? I have been reading a post and had my client crash and was unable to find the post again, despite recalling some or all if the title.
I also do a foreign word of the day and when I want to check if I am duplicating a post I have to skim through all of the posts that include that word.
- Change community selector to use
-
For post searches, could there be a [] Search Title Only? I have been reading a post and had my client crash and was unable to find the post again, despite recalling some or all if the title.
I also do a foreign word of the day and when I want to check if I am duplicating a post I have to skim through all of the posts that include that word.
Good point, this is one of those features which is already implemented in the backend but not added to lemmy-ui yet. Made a pull request for it.
