forrtproject / forrtproject/flora-explorer
Streamline study discovery and apply remaining editorial recommendations
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 5h 6m
- Merged PRs (30d)
- 1
Description
The September walkthrough found that outcome charts and citation guidance separate Browse search controls from the first results, especially in reproduction mode on phones.
Suggested acceptance criteria:
- Put result count and first results directly after filters, with a compact or collapsible summary chart; provide explicit outcome/year filters and clear-search/reset controls.
- Show an explicit empty-state message over the chart when no assessed outcomes match, instead of an empty 0–1 axis.
- Consider full-title cards on desktop or a clear table/card switch.
- Standardise computational/numerical reproduction terminology and sentence case. Consider Coverage & outcomes and Journal citation metrics as clearer section names, with definitions retained.
- Label RR complement as Not identified as an RR, preserving uncertainty.
- Clear Link copied after a short interval or a subsequent filter change.
- Replace the diagonal WIP ribbon with a compact status badge that remains visible on mobile; keep essential experimental caveats beside affected results.
- Shorten repeated introduction/citation prose and explain when to choose the explorer versus Replication Atlas.
Retain the plum palette, serif headings, evidence access and CSV alternatives. Validate the redesign with first-time students and evidence-seeking researchers, plus keyboard/screen-reader and real mobile testing. The current patch addresses the narrow selector, chart-grid overflow, link contrast, tooltip relationships/dismissal and tab scroll; these broader design decisions remain.
Contributor guide
Research direction
Start by reviewing the current patch areas named in the issue: the selector, chart-grid overflow, link contrast, tooltip relationships and dismissal, and tab scrolling. Map the remaining acceptance criteria across the explorer and Replication Atlas, then validate the completed redesign with first-time students, evidence-seeking researchers, keyboard and screen-reader users, and real mobile testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, data-visualization, design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100