Open-Source Contribution Log for Students

Recruiters increasingly look past marksheets at public proof of work: merged pull requests, reported issues and sustained open-source activity. But most students contribute sporadically — a docs fix here, a Hacktoberfest PR there — and lose track of what they did, where, and whether it was merged. When placement season arrives they cannot quantify their own open-source journey, and GitHub profiles alone do not tell the story a resume needs: merge rate, skills exercised, consistency over time. This project gives students a purpose-built log. Every contribution is recorded with repository, title, type, status and date; the dashboard aggregates totals, merged counts and streaks; a six-month activity heatmap shows consistency at a glance; and analytics views break the log down by month, contribution type and repository so weak spots in the portfolio become visible.

1. The student opens the app and lands on the dashboard: stat cards, the filterable contribution table, the activity heatmap and a profile card.
2. New contributions are added through the log form — repository, title, type, status, date and optional notes — with validation on required fields.
3. Every save updates a single in-memory data store; all views re-render from it, so counters, the heatmap and charts stay consistent.
4. The status filter chips narrow the table to merged, open or closed entries; the search box matches titles and repository names.
5. The analytics view aggregates the store into monthly bars, a type-distribution donut and top-repository rankings.
6. The printable report view formats the log as a one-page summary the student can attach to applications.

Tech stack:

• HTML5, CSS3, vanilla JavaScript (single-file app, no framework)
• SVG charts (heatmap, bars, donut — no external chart library)
• Hash-based client-side routing (dashboard / analytics / log views)
• Runs from any static host or directly as a local file

• [Contribution log with rich metadata] Every entry captures repository, title, type (pull request, issue, code review, documentation), status (open, merged, closed, draft) and date — the fields a placement interview actually asks about.
• [Dashboard with live statistics] Total contributions, merged-PR count, repository count and day streak recompute instantly whenever an entry is added or edited.
• [Six-month activity heatmap] A GitHub-style contribution grid with intensity bands that makes consistency — or gaps — visible at a glance.
• [Analytics views] Monthly contribution bars, a contribution-type donut chart and per-repository breakdowns, plus an automatic "revise next"-style callout for the weakest area.
• [Status filters and search] Filter the log by status and full-text search across titles and repository names to find any contribution in seconds.
• [Fast log form] A validated add-contribution form with type/status dropdowns and a notes field for recording what was learned — notes that feed directly into viva answers.
• [Printable contribution report] The log formats into a clean summary suitable for resumes and placement interviews.

• Complete working web app (single-file HTML/CSS/JS) with all three views
• Full source code with comments explaining the data model and chart logic
• Project report PDF (background, methodology, architecture, screens, testing notes)
• PPT presentation for final review
• Viva Q&A preparation document (open-source workflows, heatmap computation, aggregation logic)

• The demo build keeps data in memory for the session — contributions do not persist across reloads until the localStorage/backend extension is implemented.
• No automatic GitHub API import yet; entries are logged manually (listed as future scope).
• The heatmap intensity bands are illustrative of the student's own log, not synced with github.com activity.
• Charts are rendered for typical student-scale data (tens of entries); very large logs may need pagination.
• The printable report is a clean summary, not a formatted resume template.