How adityamullaguri/portfolio works
This repository is a portfolio website with an administrative CMS. Visitors browse portfolio content and can submit a contact message; an administrator logs in, edits content or uploads media, and reviews messages. The Express server routes these requests to SQLite-backed public and protected APIs, while the browser scripts provide the public experience and dashboard. Backup/restore and optional GitHub persistence support content durability. The README is empty, and some source excerpts are partial, so links from the public frontend to particular API endpoints are not asserted without direct evidence.
Main entry points: server.js Express Server · admin.js Admin API · db.js Portfolio Database · backup.js Backup and Restore
Components 18
Public Portfolio
- Portfolio Page
index.html - Portfolio Interactions
script.js
Admin CMS
- Dashboard SPA
admin/admin.js - Admin Pages
admin/dashboard.html
Application Backend
- Authentication
server/routes/auth.js - Admin API
server/routes/admin.js - Public API
server/routes/public.js - JWT Guard
server/middleware/auth.js - Media Uploads
server/middleware/upload.js - Express Server
server/server.js
Persistence
- Portfolio Database
server/db.js - Backup and Restore
server/backup.js - Initial Content Seed
server/seed.js - State Snapshot
data/portfolio-state.json - Uploaded Media
data/uploads
Other components
- Visitor
- Administrator
- GitHub
Connections 27
- Visitor → Portfolio Page: visits
- Express Server → Portfolio Page: serves
server/server.js - Express Server → Admin Pages: serves
server/server.js - Administrator → Admin Pages: opens
- Admin Pages → Dashboard SPA: loads
admin/admin.js - Dashboard SPA → Authentication: authenticates
- Dashboard SPA → Admin API: calls
admin/admin.js - Portfolio Page → Portfolio Interactions: loads
- Portfolio Interactions → Public API: fetches content
- Portfolio Interactions → Public API: submits contact
- Express Server → Authentication: mounts
server/server.js - Express Server → Public API: mounts
server/server.js - Express Server → Admin API: mounts
server/server.js - Authentication → Portfolio Database: reads and writes
server/routes/auth.js - Authentication → JWT Guard: guards session
server/routes/auth.js - Admin API → JWT Guard: guards routes
server/routes/admin.js - Admin API → Portfolio Database: reads and writes
server/routes/admin.js - Admin API → Media Uploads: handles media
server/routes/admin.js - Media Uploads → Uploaded Media: writes files
server/middleware/upload.js - Express Server → Uploaded Media: serves files
server/server.js - Public API → Portfolio Database: reads and writes
server/routes/public.js - Express Server → Initial Content Seed: runs seed
server/server.js - Initial Content Seed → Portfolio Database: initializes content
server/seed.js - Initial Content Seed → Backup and Restore: restores state
server/seed.js - Backup and Restore → Portfolio Database: exports and imports
- Backup and Restore → State Snapshot: persists snapshot
- Backup and Restore → GitHub: publishes content
server/backup.js