Counties for your state, like Louisiana's parishes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, javascript, node.js
- Domain
- data-engineering, data-visualization
Research direction
Start with src/parishes.mjs and how scripts/build.mjs aggregates parish data, then inspect the matching template and scripts/collect.mjs select() logic. Run npm run data and npm run build, and open site/leaderboard.html to check the result. Done means one state's county data appears with towns, cities, universities, people, contributions, and the busiest person, with collection volume considered against the API budget in docs/data.md.
Written by the indexing model from the issue text.
Description
Louisiana goes down to the parish: every parish's people, contributions, and busiest person. The same would be great for any state.
What to build
- For one state you know: a list of its counties and the towns, cities, and universities in each, following src/parishes.mjs.
- Aggregation in scripts/build.mjs (see how
parishesis built) and a view in the template like "Louisiana, by parish". - Ideally, generalise the parish code so adding a state is just adding a data file.
Note: county detail only means much where many people are looked up. Louisiana looks up everyone active; other states look up 80. A state with counties may want the same (see select() in scripts/collect.mjs), within the daily run's API budget (docs/data.md).
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
-
accessibility help wanted
Difficulty 3/5 1-2 days Newbie friendliness 78/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