Status visualisation component
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
Summary
A community request came through about using the existing stepper component as a means of tracking/visualising the status of something e.g. - status of data ingest.
While we would want to keep this as a separate component to the stepper, it does seem like a worthwhile suggestion.
📝 Acceptance Criteria
- Assess priority of this
- Research and create designs
Guidance
This was a quick mock up of an example of the above:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing stepper component and the supplied status-visualisation mock-up. Assess the priority of keeping this as a separate component, then research and create designs for tracking the status of work such as data ingest. Done means the priority assessment and designs are available for review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100