How vipulmadavi/my-portfolio works
Project Type and Purpose
• This is a static, single‐page portfolio website built with vanilla HTML, CSS, and JavaScript, packaged with Vite and deployed on GitHub Pages.
• It showcases a public GUI mode (graphical portfolio) and a hidden CLI mode (“terminal” view) behind a URL flag or command.
File Structure
• Top-level:
• index.html – entry point
• package.json / vite.config.js / tsconfig.json – build and TS config
• public/ – assets for GitHub Pages
• src/:
• main.ts / main.js – mode manager (decides GUI vs terminal)
• loader.js – dynamic module loader
• gui.css / style.css – theme and global styles
• gui/ – component‐based UI (hero, skills, projects, contact, qualifications, ticker)
• effects/ – custom Canvas API background (network graph)
• terminal/ – hidden CLI interface (filesystem simulation, terminal-app.js, CSS)
• No backend or database: purely client‐side.
README for Additional Insights
• Highlights dual‐mode interface, Canvas API for dynamic network background, responsive design, and GitHub Pages for hosting.
• No microservices or server components—static hosting only.
a. Client Browser
• Loads index.html, CSS, JS bundles.
• Renders either GUI-mode components or Terminal-mode components.
b. Build System (Vite)
• Dev server for local testing.
• Bundles and outputs static assets to public/ for deployment.
c. Static Hosting (GitHub Pages / CDN)
• Serves index.html and built assets over HTTPS.
d. External Services
• Canvas API for in-browser graphics.
• External links: LinkedIn, GitHub, Email, Resume PDF.
Relationships and Data Flow
• Developer runs “npm run dev” → Vite dev server → Browser (hot-reload).
• “npm run build” → Vite bundles src/ → Outputs to public/ → Git pushes to GitHub Pages.
• User browser GETs index.html → Static server responds → Browser fetches CSS/JS → main.js → decides GUI vs Terminal → dynamically loads gui-app.js or terminal-app.js → renders components/effects.
• Components invoke Canvas API for network effect or handle user interactions (e.g., typing commands in the terminal).
• Contact/component links trigger outbound requests to external URLs.
Architectural Patterns and Principles
• Component-based front-end (each section is a self-contained JS module + CSS).
• Single-Page Application (SPA) behavior via dynamic module loading.
• Static site deployment—no server logic.
• Separation of concerns: GUI vs Terminal code kept in separate folders.