How yaseenbashat/savebox works
Project type and purpose
• This is a lightweight full-stack Node.js web application that aggregates and displays user profiles (and playlists) from multiple social platforms (GitHub, LinkedIn, Reddit, Twitter, YouTube).
• It uses Express as the HTTP server, EJS as the view-templating engine, and individual OAuth setup modules to authenticate with each external API.
File structure
Top-level files
• package.json / package-lock.json – project metadata and dependencies
• main.js – Express server entry point
• authSetupGitHub.js, authSetupLinkedIn.js, authSetupReddit.js, authSetupTwitter.js, authSetupYouTube.js – per-service OAuth configuration and token management
• readme.txt – (currently empty) intended for high-level docs
Directory “views” (EJS templates)
• index.ejs – homepage / service selection
• githubProfile.ejs, linkedinProfile.ejs, redditProfile.ejs, twitterProfile.ejs, youtubeProfile.ejs – templates rendering fetched data
• playlists.ejs – specialized YouTube playlists view
Extracted architectural insights (README is blank, so rely on conventions)
• Monolithic backend serving both API-calls and view rendering
• MVC-style separation: main.js + authSetup*.js = Controller/Service layer, views folder = View layer
• No persistent database—data flows directly from external APIs to the user’s browser via server-side rendering
Detailed element checklist
• Browser / Client node
• Express Server boundary containing:
– Route Handler (main.js)
– OAuth Modules (authSetup*.js)
– EJS Renderer + view templates folder
• External Social API clouds for GitHub, LinkedIn, Reddit, Twitter, YouTube