avo-hq/avo

Dashboards improvements (Dashboards 2.0)?

Open

#2,146 opened on Dec 18, 2023

View on GitHub
 (0 comments) (4 reactions) (0 assignees)Ruby (1,778 stars) (308 forks)user submission
Back endDSL-relatedFront endHelp wantedTask

Description

How to make the dashboards better:

### Tasks
- [ ] multiple ranges on cards
- [ ] https://github.com/avo-hq/avo/issues/2301
- [ ] click on cards
- [ ] automatic card caching
- [ ] progress card
- [ ] datepicker ranges

Contributor guide

Tech stack
rubyjavascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Ruby on Rails basicsAvo dashboard familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the existing dashboard implementation in the Avo codebase, particularly the Avo::Dashboards module. Review the linked issue #2301 for context on multiple ranges. Engage with maintainers to clarify acceptance criteria for each task, such as 'click on cards' and 'automatic card caching'. Consider starting with a single task, like datepicker ranges, which may be more self contained.