How aviralacharya/portfolio works
Project type and purpose
• This is a simple, static portfolio website. The README and file tree show a collection of static assets (HTML, CSS, JavaScript, plus configuration files).
• Purpose: serve a personal or professional portfolio, possibly as a Progressive Web App (site.webmanifest indicates PWA support).
File structure
• Top‑level files only—no subdirectories. That means everything is served from a flat structure.
• Key files:
• index.html – entry point for the browser.
• styles.css – global stylesheet.
• script.js – client‑side behavior or interactivity.
• robots.txt and sitemap.xml – SEO and crawler directives.
• CNAME – custom domain configuration (e.g., on GitHub Pages).
• No backend code, no build scripts, no server‑side logic.
README for additional insights
• README only says “portfolio,” so there are no extra instructions on build steps or runtime dependencies.
• We infer deployment targets (e.g., GitHub Pages or any static‑file hosting).
Elements
• From Browser → DNS lookup.
• From Browser → Hosting (HTTP requests).
• From Hosting → Browser (HTTP responses with static files).
• Blue for “Network” elements (DNS, Hosting).
• Green for “Client” elements (Browser, local cache).
• Yellow for “Static resources” (HTML, CSS, JS, manifest).