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.com format (#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.

  • Die4Ever@retrolemmy.com
    link
    fedilink
    English
    arrow-up
    7
    ·
    2 days ago

    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.

    • Nutomic@lemmy.mlOPM
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      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?

      https://github.com/LemmyNet/lemmy-ui/pull/3219

      • Die4Ever@retrolemmy.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        2 days ago

        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?

        • Nutomic@lemmy.mlOPM
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          I thought about that too, have to figure out how it can be implemented (im not very good at frontend stuff).