smartcontractkit / smartcontractkit/chainlink

[FEAT] Alert UX

Open
#4,589 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
8.2k
Forks
2k
Avg merge
1d 23h
Merged PRs (30d)
202

Description

Description

  1. Change the alerts position so that when the alert pops up, it is visible even when the content area has been scrolled down.
  2. Add fade in/out transition

Motivation

  1. The alert isn't always visible when the user has scrolled down to create a job (this isn't really an issue when adding a bridge). They then have to scroll up to receive any feedback resulting in a poor user experience. Additionally, if the user is adding multiple jobs, they might have to scroll down again to see the create job button.
  2. When adding multiple jobs to a node, there is no clear feedback that a new job has been added unless the user is actively watching the alert that is still there and sees the content updated with new values.

Justification

  1. I would suggest making the alert position relative to the top menu bar and still above the main content area (note: the CSS position value wont be relative) so that it looks like its a floating alert.
  • Consider giving the alert margins rather than being full width so that it is in line with the margins in the content area.
  • Consider starting a style guide so there is interface consistency among all chainlink apps.
  1. Fade in/out might not be the best solution, maybe a slide in from left and slide out right is better, or some other variation. Having some feedback for when adding multiple jobs in a row is important.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the alert implementation and the styles controlling its position relative to the top menu and content area. Reproduce the create-job flow after scrolling, then verify that alerts remain visible and provide clear transition feedback when multiple jobs are added; the final transition style is left open by the issue.

Written by the indexing model from the issue text.

Assessment

Domain
design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.