Skip to content

Search UI/UX Review #193

Closed
Closed
@srenault-meeds

Description

@srenault-meeds

Rationale

Meeds provide a feature to let users searching for content shared in worspaces, by users.
This one needs to be reviewed as its UX/UI does not help users to find contents:

  • input field is not enough viewable for users. Indeed, customers regularly reports its bad UX
  • cards UI are all different
  • it is difficult to access the content: for some, we can click to it to open the content; for others, only the bottom is clickable
  • some contents are listed but we cannot understand why this has been listed from what has been searched (description is missing for example)

Image

Regarding matching computing / pertinence, additional filters, it will be reviewed in other related MIPs.

1. Functional Requirements

Top User Stories

UI Changes

Given I access the search
Then a drawer opens as currently with review of the global display to match with UI of notifications or appcenter for example:

  • main page is displayed with side margins
  • search input is reviewed for better usability
  • autofocus is done to the search field to start searching

Image

Given I start searching for contents
Then results appear as currently depending their pertinence score
But a new UI is provided:

List

  • News:
    • Name
    • Context Infos: Space - Author (Last) - Publication Date (or edited)
    • Text where the searched content can be read
      • If no, then summary or first characters
  • Notes:
    • Name
    • Context Infos: Space - Author (Last) - Publication Date (or edited)
    • Text where the searched content can be read
      • If no, then summary or first characters
  • Posts/Comments:
    • Searched word
    • Context Infos: Space - Author - Publication Date (or edited)
    • Text where the searched content can be read
      • If no content (only image or video), then display name of image or video in the title & inform users the content is a video or an image
  • Tasks:
    • Name
    • Context Infos: Task Project - Assignee if so - Due date if so - Priority
    • Text where the searched content can be read
      • If no, then display "No description"
  • Actions
    • Name
    • Context Infos: Program - Points - Recurrence if so
    • Text where the searched content can be read
      • If no, then display "No description"

Cards:

  • People: Mobile view of people card
  • Spaces: Mobile view of spaces card

Precision: no more search to perks is provided.

Image

Behaviour when hovering results

Depending the content listed, when hovering it, actions can be suggested

  • news: Bookmark
  • notes: Bookmark
  • tasks: --
  • posts/comment: Comment, Kudos, Bookmark
  • actions: Contribute, Bookmark

Example:
Image

Behaviour when clicking to results

When the content can be opened in a drawer if possible, as for example:

  • action
  • task

Behaviour when using keyboard

When using the search
Then it must be possible to use keyboard actions:

  • Enter to launch the search
  • ESC to remove text
    • If no text, then it closes the search drawer
  • tab to access result (with focus and hover display)
    • then other tab to access options (bookmark, etc.)
    • then enter to activate the option

Filters

No change is requested for filters UX/UI

Impacts

--

Gamification

--

Notifications

--

Analytics

--

Unified Search

  • UX/UI will be reviewed accordingly
  • Tasks need to be indexed in ES to search for it (currently searched using the DB)

2. Technical Requirements

Expected Volume & Performance

  • No change on Search app loading only when needed to not impact global pages performances
  • No change in stored data
  • Search application shouldn't require custom CSS and the already existing custom CSS has to be dropped in order to optimize the page size

Security

  • No change in security model

Extensibility

  • No change on Search extensibility, except the fact that we will be able to group results for People and Spaces, which will need an improvement inside Search application and without major change on extensibility mechanism of Search

Configurability

N/A

Upgradability

N/A

Existing Features

N/A

Feature Flags

N/A

Other Non Functional Requirements

N/A

3. Software Architecture

Security

N/A

Access

The Search application has to be changed in order to allow:

  • listing items as it's now
  • listing group of items

The Search extensions has to change in order to :

  • Choose either search result items will be listed in a group (if grouping is enabled, then the extension has to define the label and icon of grouping). When grouping is enabled, the Search application will apply a dedicated template to list items
  • Change the look and feel of each search result

Services & processing

N/A

Data and persistence

N/A

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Completed

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions