How shreya8660/portfolio works
Project type & purpose (from README + tree)
This is a static portfolio website (no backend code present) hosted on Vercel. The purpose is to serve a personal portfolio page with styling, client-side interactivity, and downloadable/viewable documents (CV, certificates), plus images.
Key evidence:
• Portfolio/index.html → single-page/static entrypoint
• Portfolio/styles.css → styling
• Portfolio/script.js → client-side behavior only
• Portfolio/assets/*.pdf, Portfolio/certificates/*.pdf, Portfolio/pic/* → static media
• README links a Vercel deployment → typical static hosting + CDN delivery
Core runtime artifacts
• HTML document: Portfolio/index.html
• CSS: Portfolio/styles.css
• JavaScript: Portfolio/script.js
Static assets
• CV PDF: Portfolio/assets/Shreya_V_CV.pdf
• Certificates PDFs: Portfolio/certificates/*
• Images: Portfolio/pic/* (directory exists; contents not listed)
Supporting/metadata
• README.md (documentation)
• .vscode/ (editor config; not runtime)
Because it’s static:
• Client → Hosting (Vercel) → Static assets is the main runtime flow.
• Any “logic” is in-browser (JS manipulating DOM, handling clicks, navigation, downloads).
• No DB, no server API is visible from the repo; avoid inventing one. If the site links to external services (e.g., LinkedIn, GitHub, email), show them as optional external nodes.
User / Browser (Client Runtime)
• Loads HTML/CSS/JS
• Executes script.js
• Renders DOM
• Fetches images/PDFs
Vercel Hosting (Static Site)
• Serves index.html, styles.css, script.js
• Serves static assets under /assets, /certificates, /pic
Vercel Edge Network / CDN
• This is key for accuracy on Vercel: requests are served from edge caches globally.
Source Repository (GitHub or similar)
• Not shown in tree, but typically Vercel deploys from Git.
External Links (Optional)
Runtime request flow (critical):
• Browser → CDN/Vercel: GET / (serves index.html)
• Browser → CDN/Vercel: GET /styles.css
• Browser → CDN/Vercel: GET /script.js
• Browser → CDN/Vercel: GET /pic/... (images)
• Browser → CDN/Vercel: GET /assets/Shreya_V_CV.pdf
• Browser → CDN/Vercel: GET /certificates/...pdf
Client-side behavior flow (inside browser):
• script.js → DOM (manipulate elements, handle navigation/scrolling/buttons)
• User interaction → script.js handlers → (may trigger) navigation/download requests for PDFs/images
• Engineer pushes to Git repo → Vercel deploy pipeline → CDN updated → users get new content
Architectural patterns used
For this project, call out:
• Static site architecture (no server-side app)
• Client-side enhancement (JS enhances UX; not required for serving content)
• CDN-based delivery (Vercel edge caching for performance)
Avoid patterns that aren’t evidenced (microservices, REST APIs, DB, queues).
Relevant tech labels
• “HTML/CSS/Vanilla JS”
• “Vercel Static Hosting + CDN”
• “PDF/Image static assets”
Clear labels for each component
Use exact names tied to repo:
• index.html (entrypoint)
• styles.css (styling)
• script.js (client-side logic)
• /assets/*.pdf (CV)
• /certificates/*.pdf (certificates)
• /pic/* (images)
• “Vercel Hosting / CDN”
“Separate into as many components as possible” (without inventing)
To be very detailed for this repo, break out these nodes explicitly:
• index.html (root document)
• styles.css
• script.js
• CV PDF (assets/Shreya_V_CV.pdf)
• Certificates PDFs (certificates/Udemy.pdf, certificates/Yuvamytr.pdf)
• Image directory (pic/)
• Hosting platform (Vercel)
• Edge CDN (Vercel)
• Browser cache (client-side)
• Optional external links (only if present in HTML)
That level of granularity is appropriate here because the system is small; accuracy comes from showing the real runtime relationships (browser requests static files; JS drives UI; PDFs/images are fetched as separate resources).
Quick checklist before finalizing
• Confirm paths and references by scanning index.html for:
• <link href="styles.css">
• <script src="script.js">
• <img src="pic/...">
•
• Any external CDNs (Google Fonts, Font Awesome). If present, add “External CDN” nodes.
This is the main “hidden architecture” static sites often have.