How danielpopoola/statify works
Project type and purpose
• This is a full-stack web application (Django + static JS components) that displays a Spotify user’s music summary (tracks, artists, etc.) via OAuth.
• The backend (Python/Django) handles authentication, data fetching, persistence, and template rendering. The frontend is a collection of React-style components shipped as static JS/CSS.
File structure
• Top-level:
– manage.py, Pipfile/Pipfile.lock/requirements.txt → Python/Django environment
– package.json, .babelrc → Node/Babel build for client-side JS
– vercel.json → deployment config (likely for static hosting or serverless functions)
• spotify_dashboard/ → Django project settings, URLs, ASGI/WSGI entry points
• spotify_oauth/ → Django app: models, migrations, views, URL routes, templates, static assets
• staticfiles/ → collected static assets (CSS/JS) ready for serving in production
• README.md describes the goal: show a Spotify user's music summary.
README for architecture clues
• Very high level – no explicit architectural notes.
• The project name “Statify” implies a dashboard; features correspond to playlists, top artists/tracks, theming.