How isatishyadav/reels-finder works
Project Type and Purpose
• This is a single-page, client-side web application (“Reels Finder”) whose sole purpose is to let end users search Instagram Reels by title, description, or hashtag.
• It has no server-side code under version control—it’s deployed as static files (HTML, JS, CSS) and relies on external services (Instagram’s public endpoints or a proxy) to fetch data.
Top-Level File-Structure Analysis
• CNAME, index.html, beta.html: two entry points for production and beta.
• dist/css/style.css & dist/js: build output for production assets.
• js/main.js: developer-written client logic.
• No “backend” folder implies all runtime logic lives in the browser.
Key Components to Model
a. User’s Web Browser (Client)
• Renders index.html / beta.html
• Loads CSS (dist/css/style.css) and JavaScript (dist/js or js/main.js)
b. Static Hosting / CDN
• Serves all static assets (HTML, CSS, JS)
• e.g., GitHub Pages, Netlify, S3 + CloudFront
c. Front-end Application Layer
• Business logic in main.js: builds requests, parses JSON, updates DOM
d. External Reels Data Service
• Could be Instagram’s public search endpoints or a custom proxy/API
• Returns JSON payloads of reels metadata
e. Optional Analytics or Error-Logging Service
Relationships and Data Flow
• Browser → Static Host/CDN: GET index.html, CSS, JS
• Browser(main.js) → External Reels API: HTTP(S) GET/POST carrying search parameters
• External API → Browser: JSON with reel results
• Browser → (Optional) Analytics Service: usage/error events
Architectural Patterns & Principles
• Client-side single-page application (SPA)
• Clear separation between static asset serving and data retrieval
• “API gateway” is external (no self-hosted backend)
• Progressive enhancement: simple HTML + CSS with JS adding interactivity
Technologies and Frameworks
• HTML5, CSS3 (dist/css/style.css)
• Vanilla JavaScript (js/main.js)
• Hosting: any static hosting/CDN solution
• External: Instagram’s public endpoints or a serverless proxy