How pramodpots/bulb works
Project type and purpose
• From the README (“Personal Portfolio(Resume) maker”) and the file tree (Express entrypoint index.js, Jade views, Mongoose-like schema files, config/auth.js/passport.js), we see this is a full-stack Node.js/Express application.
• Purpose: allow users to log in via Google OAuth, fill out a form with project details/photos, and instantly generate a personal portfolio site.
File structure
Top-level:
• .env, .gitignore, Procfile – configuration and Heroku deployment
• index.js – Express server bootstrap
• package.json – dependencies (Express, Passport, Mongoose, Jade, etc.)
• config/ – auth and passport setup
• bulbschema.js & userschema.js – MongoDB models (Mongoose schemas)
• public/ – client-side assets (JS, CSS, JSON)
• views/ – Jade templates for SSR
Patterns:
• MVC-style separation:
– Models: userschema.js, bulbschema.js
– Views: .jade under views/
– Controllers/Routes: in index.js (mounting auth routes, form routes, static serve)
• External Service: Google OAuth via Passport
• Deployment: Heroku (Procfile)
Key insights from README
• OAuth login via Google
• Single-form entry → portfolio “builds” itself
• Hosted on Heroku, MongoDB likely used (no SQL files visible)
Putting it all together
• Break Express into sub-components:
• Auth module (config/passport.js)
• Routes/controllers (index.js)
• Views (views/*.jade)
• Static assets (public/)
• Form POST to server → DB write
• Portfolio GET → DB read → Jade render → HTML