How azuredevops7/pwj-netflix-clone works
This is a small browser-based movie and TV discovery app with registration, login, session gating, catalog browsing, and trailer playback. The principal flow is: a signed-in browser loads catalog sections, requests movie data, renders selectable titles, and opens matching YouTube trailers. Authentication submits credentials to the application API and stores a returned token; session.js checks that token and redirects as needed. The README contains no useful architecture detail, so relationships below are limited to calls visible in the sampled JavaScript; HTML wiring and unsampled behavior are not inferred.
Main entry points: script.js Catalog loader · login.js Auth client · register.js Registration client · session.js Session gate
Components 13
Authentication
- Login form
login.html - Registration form
register.html - Auth client
login.js - Registration client
register.js - Session gate
session.js - Token storage
- Application API
Catalog browsing
- Catalog loader
script.js - Movie renderer
script.js
Media integrations
- TMDB API
- Trailer lookup
script.js - YouTube
Other components
- Visitor
Connections 11
- Auth client → Application API: posts credentials
login.js - Auth client → Token storage: stores token
login.js - Registration client → Application API: posts registration
register.js - Registration client → Login form: redirects after signup
register.js - Session gate → Token storage: checks token
session.js - Catalog loader → Application API: requests wishlist
script.js - Catalog loader → TMDB API: fetches catalog data
script.js - Catalog loader → Movie renderer: renders results
script.js - Movie renderer → Trailer lookup: handles selection
script.js - Trailer lookup → TMDB API: fetches trailers
script.js - Trailer lookup → YouTube: embeds trailer
script.js