How rudrajeetcodes/port works
This repository is a personal portfolio website with interactive landing and themed subpages, plus serverless endpoints that provide GitHub, WakaTime, and Spotify data. A visitor views the site; browser code renders portfolio interactions and requests selected data, while API handlers fetch external services and, for Spotify playback, use Redis caching. The sampled code confirms only some browser-to-API links, so unsampled UI wiring is not inferred. OAuth is represented as separate browser and server flows where the excerpts show their external requests.
Main entry points: api/spotify.js Playback endpoint · spotify.js Spotify browser client · index.html Portfolio page · script.js Page interactions
Components 19
Portfolio website
- Portfolio page
index.html - Page interactions
script.js - Fun page
Fun/fun.html - Fun navigation
Fun/fun.js - Personal page
Personal/personal.html - Personal navigation
Personal/personal.js
GitHub activity
- GitHub activity
api/github.js - Weekly GitHub stats
api/github-weekly.js - Contribution calendar
api/github-contributions.js - GitHub API
Spotify integration
- Spotify browser client
spotify.js - Playback endpoint
api/spotify.js - OAuth login endpoint
api/spotify-login.js - OAuth callback endpoint
api/spotify-callback.js - Spotify API
- Redis cache
Coding statistics
- WakaTime statistics
api/wakatime.js - WakaTime API
Other components
- Visitor
Connections 17
- Visitor → Portfolio page: opens
- Visitor → Fun page: opens
- Visitor → Personal page: opens
- Portfolio page → Page interactions: runs
- Fun page → Fun navigation: runs
- Personal page → Personal navigation: runs
- Page interactions → Contribution calendar: fetches
script.js - GitHub activity → GitHub API: queries
api/github.js - Weekly GitHub stats → GitHub API: queries
api/github-weekly.js - Contribution calendar → GitHub API: queries
api/github-contributions.js - Spotify browser client → Playback endpoint: fetches
spotify.js - Playback endpoint → Spotify API: fetches
api/spotify.js - Playback endpoint → Redis cache: reads and writes
api/spotify.js - Spotify browser client → Spotify API: requests authorization
spotify.js - OAuth login endpoint → Spotify API: redirects to authorize
api/spotify-login.js - OAuth callback endpoint → Spotify API: exchanges code
api/spotify-callback.js - WakaTime statistics → WakaTime API: fetches summaries
api/wakatime.js