How mikatrow/piqzi works
This is a Next.js personal portfolio: a browser request renders profile, skills, listening activity, projects, and social links. Activity retrieves the current Spotify track, falling back to recently played. The README gives only brief identity details; some section implementations were not sampled, so their internal data wiring is not asserted.
Main entry points: page.tsx Home page · spotify.ts Spotify client · layout.tsx Root layout · Profile.tsx Profile section
Components 17
Page composition
- Home page
src/app/page.tsx - Root layout
src/app/layout.tsx
Portfolio sections
- Profile section
src/app/components/Profile.tsx - Profile data
src/data/profile.ts - Tools section
src/app/components/Tools.tsx - Activity section
src/app/components/Activity.tsx - Projects section
src/app/components/Projects.tsx - Project data
src/data/projects.ts - Social links
src/app/components/Socials.tsx - Social data
src/data/socials.ts
Spotify activity
- Spotify client
src/app/lib/spotify.ts - Token refresh
src/app/lib/spotify.ts - Recent-track lookup
src/app/lib/spotify.ts
Other components
- Visitor
- Spotify accounts API
- Spotify player API
- Spotify recent API
Connections 17
- Visitor → Root layout: requests page
- Root layout → Home page: renders children
- Home page → Profile section: renders
- Home page → Tools section: renders
- Home page → Activity section: renders
- Home page → Projects section: renders
- Home page → Social links: renders
- Profile section → Profile data: reads
- Root layout → Profile data: reads metadata
- Projects section → Project data: reads
- Activity section → Spotify client: calls nowPlaying
- Spotify client → Token refresh: requests token
- Token refresh → Spotify accounts API: refreshes token
- Spotify client → Spotify player API: checks playback
- Spotify client → Recent-track lookup: falls back
- Recent-track lookup → Token refresh: requests token
- Recent-track lookup → Spotify recent API: fetches recent track