A light theme
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 77/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, javascript, nodejs
Research direction
Start in web/template.html at the :root color tokens and follow the storm drawing code that uses SKY and the colors in draw(). Read how the page, map, tables, and canvas colors are currently set, then run npm run data and npm run build and open site/leaderboard.html. Done when the light theme follows prefers-color-scheme, a toggle overrides and remembers the choice in localStorage, and both themes keep the tornado, map, tables, and red and blue markers readable.
Written by the indexing model from the issue text.
Description
The page is dark only.
What to build
- A light theme that follows
prefers-color-scheme: light, plus a toggle that overrides it (remembered inlocalStorage). - The CSS colours are already tokens on
:root(--sky,--panel,--line,--ink,--muted,--gold). The canvas tornado has its own colours in the script (SKYand the colours indraw()), which will need to read the theme too. - Keep the red (public commits) and blue (everything else) readable on a light background.
Where
- web/template.html: the
:rootblock at the top, and the storm's drawing code.
Done when
- Both themes look intentional, text has good contrast, and the tornado, map, and tables all switch.
Getting started: npm run data, then npm run build, then open site/leaderboard.html. No dependencies; see CONTRIBUTING.md.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from wbp318/github-leaderboard
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
wbp318/github-leaderboard#10 ·
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 54/100
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 68/100
All issues in wbp318/github-leaderboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
good first issue tests
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
eliasstravik/herdr-projects#1032 ·
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
growilabs/growi#12246 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
TMHSDigital/Free-Game-Dev-Assets#301 ·
Maintainers usually reply within 1 day