How rafaeluzzi/uzziportfolio works
Project type and purpose
• From the file tree and “uzziportfolio” README, this is a single-page portfolio website built with React/TypeScript (Vite + Tailwind), deployed on Netlify, with one serverless function (Spotify Now Playing).
• Purpose: showcase a developer’s work, play short sound effects, show live Spotify data, and provide a contact wizard.
File structure
• Top-level files:
– index.html, src/main.tsx: entry for React app
– vite.config.ts, tsconfig.json: build & TS config
– tailwind.config.js, postcss.config.js: styling pipeline
– netlify.toml + netlify/functions/spotify.ts: deployment + serverless API
• src/components: dozens of UI sections (Hero, About, Experience, Projects, Contact, etc.)
• src/lib/sfx: sound-effect assets
• static assets & config: .bolt, backups folders, components.json
• package.json + lock: dependencies (React, Vite, Tailwind, etc.)
README for additional insights
• README is minimal but the file tree and Netlify function imply an architecture: a React SPA calling a serverless endpoint that proxies Spotify API.
a. Main components
– Client Browser (User’s device)
– React SPA (hosted on a CDN via Netlify)
– Static Asset Store (images, sfx, CSS, JS bundles)
– Netlify Build & Deployment Pipeline (Vite build + tailwind)
– Netlify Functions (spotify.ts)
– External Spotify API
b. Relationships & interactions
– Browser requests JS/CSS bundles & static assets from Netlify/CDN
– React app initializes, renders components, plays SFX from asset store
– “NowPlaying” component calls the Netlify Function endpoint
– Function fetches data from the Spotify API, returns JSON to SPA
c. Architectural patterns & principles
– SPA architecture: client-side routing & rendering
– Serverless backend for third-party API integration (no dedicated server)
– CI/CD: automated builds via Netlify (Vite → production assets)
– Modular component design (React + TypeScript, TSX files per section)
d. Key technologies
– React + ReactDOM, Vite (dev server + bundler)
– TypeScript, TailwindCSS, PostCSS
– Netlify (hosting + functions), Spotify Web API
– Static assets (wav/mp3) served from src/lib/sfx
• React SPA
– main.tsx, App.tsx, src/components/...
– Routing, state management (if any), UI logic
• Build & Deploy
– vite.config.ts → bundle → dist/
– netlify.toml triggers deploy
• Serverless Function
– spotify.ts: authenticates & proxies Spotify Web API
• External Services
– Spotify Web API (token endpoint, now-playing endpoint)