How hrushi2711/portfolio works
1. Project type and runtime boundary
This is a static, browser-only portfolio site. There is no backend, build step, or framework runtime in the repo. The app runs entirely in the browser using HTML, CSS, and vanilla JavaScript.
2. Primary content source: data.json
data.json is the single source of truth for most portfolio content: personal bio, experience, education, skills, project details, links, and likely resume metadata. The README makes clear the UI is meant to be driven from this file rather than hard-coded in HTML.
3. Rendering engine: app.js
app.js is the central orchestration layer. It likely:
- fetches data.json
- transforms JSON into DOM sections
- injects timelines, skill bars, and profile/contact blocks
- wires up UI interactions such as theme switching and collapsible sections
4. Presentation shell: index.html
index.html is the static entry point and probably contains the root containers that app.js populates. It also anchors the CSS and JS assets, making it the minimal structural shell for the dynamically rendered portfolio.
5. Visual system: style.css
style.css defines the entire look-and-feel: glassmorphism panels, dark/light theme styling, grid-based layout, responsive breakpoints, transitions, and micro-animations. The README emphasizes CSS Grid alignment and theme-driven styling as key architectural features.
6. Theme and persistence boundary
The site includes a dark/light mode engine that persists user preference via localStorage. This is an important client-side state boundary: the visual theme is stored in the browser, not in the JSON data or HTML.
7. Interactive content components
The UI appears to include a few dynamic components beyond simple text rendering:
- progress bars for skill levels
- expandable/collapsible timeline or education items
- animated emphasis nodes and other micro-interactions
These are all likely driven from the JSON content and DOM manipulation in app.js.
8. Asset handling
The repository includes a PDF resume file, Hrushikesh_Tiwari_Resume_03_2026_SD.pdf, which is likely linked from the page for direct download. This makes the resume part of the static asset layer rather than an external service dependency.
9. Hosting and deployment signal
The presence of CNAME indicates the site is intended for custom-domain static hosting, most likely on a platform like GitHub Pages. That means deployment is primarily an asset upload / static publish flow.
10. Data flow summary
The architecture is straightforward: browser loads index.html → app.js fetches data.json → JavaScript renders content into the DOM → style.css applies the full visual system → localStorage preserves theme choice. The PDF resume and any social links act as outbound static assets/external endpoints.
11. Important diagram boundaries
For an architecture diagram, the main boundaries are:
- Static file layer: HTML/CSS/JS/JSON/PDF/CNAME
- Client runtime: browser DOM, fetch, localStorage
- External links: resume download and social profiles
- No server-side API boundary: everything is resolved client-side from local files and hosted static assets
Main entry points: app.js app.js · data.json data.json · index.html index.html · style.css style.css
Components 16
Static files
Browser-delivered source and assets that make up the portfolio site.
- index.html · Static page shell that loads the app and anchors the layout.
index.html - style.css · Global visual system for layout, themes, and responsive styling.
style.css - app.js · Main orchestration layer that fetches data and renders the portfolio UI.
app.js - data.json · Single source of truth for portfolio content and metadata.
data.json - Resume PDF · Downloadable résumé document served as a static file.
Hrushikesh_Tiwari_Resume_03_2026_SD.pdf - CNAME · Custom-domain configuration for static hosting.
CNAME
Browser runtime
Client-side DOM, fetch, and persistence behavior executed in the browser.
- Browser · Client environment that loads the page, executes JavaScript, and renders the UI.
- DOM · Document structure populated by the portfolio renderer.
- Fetch · Browser API used to load JSON content from the static site.
- localStorage · Browser persistence for the selected visual theme.
- Renderer · Transforms portfolio data into sections, cards, and interactive widgets.
- Theme mode · Dark/light appearance state maintained in the client.
- Content blocks · Rendered bio, experience, education, skills, and project sections.
- Interactive widgets · Skill bars, collapsible items, and other micro-interactions.
External targets
Outbound destinations and hosting boundaries referenced by the site.
- Outbound links · External profile links and download targets surfaced by the portfolio.
- Static host · Custom-domain static hosting target for the published site.
Connections 18
- Browser → index.html: loads · The browser opens the static entry page.
- index.html → style.css: includes · The HTML shell links the global stylesheet.
- index.html → app.js: includes · The HTML shell loads the client-side script.
- app.js → Fetch: uses · The app requests structured content from the JSON file.
- Fetch → data.json: reads · Portfolio content is loaded from the static data source.
- app.js → Renderer: drives · The orchestration layer turns data into visible sections.
- Renderer → DOM: updates · Rendered portfolio markup is injected into the document.
- style.css → DOM: styles · CSS controls layout, theme styling, and responsive presentation.
- app.js → localStorage: persists · Theme choice is saved in browser storage.
- localStorage → Theme mode: restores · Saved preference initializes the active theme.
- app.js → Theme mode: toggles · User interaction switches the visual mode.
- Renderer → Content blocks: builds · The renderer creates the main portfolio sections.
- Renderer → Interactive widgets: builds · The renderer also creates interactive skill and timeline UI.
- data.json → Content blocks: defines · Portfolio content is driven by the JSON model.
- data.json → Interactive widgets: feeds · Skill levels and item states populate interactive widgets.
- data.json → Outbound links: references · Profile links and download targets are included in the data model.
- Outbound links → Resume PDF: downloads · The résumé PDF is exposed as a static downloadable asset.
- CNAME → Static host: targets · Custom-domain configuration points the site at static hosting.