The season in numbers
Use with: build-website. Resume line when done: Built {project_name}, a hand-collected stats site for {team} — live at {url}
Brief
Every score from your team's season, hand-entered into one data file, published as a results page with one chart. The chart answers the question your team argues about: goals per game, the win streak, home versus away. The site is small; the value is that the numbers are complete and correct.
Personalize
- The team. Yours: the one you play on, manage, or watch from the bench. You need access to every result, which means a team you were around for.
- The argument. Pick the one stat your teammates dispute and make the chart settle it. If nobody argues about anything, chart the thing the coach keeps repeating.
- The source. Where each score comes from: your own scorebook, the league page, the group chat. Name it on the site.
Milestones
- Collect every result into one file (CSV or JSON): date, opponent, score, home or away. Mark any game you could not confirm.
- Cross-check the file against a second source (a teammate's memory counts, but write down who).
- Results page live: full season as a table, newest first.
- The one chart, with axes starting at zero and labeled units.
- A short written note under the chart: what the numbers show and what they cannot show.
Done means
- Live URL with the full season table and the chart
- Every result traceable to a named source; unconfirmed games marked
- Chart axes honest: zero baseline, labeled, no cropped scales
- The note is written by you and claims only what the data supports
- At least 6 commits across at least 4 distinct days, authored by you
- SESSIONS.md has an entry per session, written by you