How rahulp-fx/portfolio works
Project type and purpose
• This is a purely static, single‑page personal portfolio website.
• It consists of plain HTML/CSS files (index.html, pages/about.html, pages/contact.html, and corresponding styles) plus an assets folder for images or other media.
• It is deployed to Vercel (a static‑hosting/CDN platform), as indicated by the “Deployed App Link” in the README.
File structure
• Top‑level:
• README.md – project info and deployment link
• index.html – homepage
• style.css – global styles
• pages/ – secondary pages (about.html, contact.html) and their CSS
• There are no server or backend directories—this confirms a static‑site architecture.
README for additional insights
• The only content is the Vercel deployment URL, which implies a simple CI/CD pipeline on every push to the Git repo.
• No frameworks or build tools are mentioned, so we assume plain HTML/CSS with no compilation step.
a. Main components to include
• Developer local environment (code editor, Git).
• Git repository (e.g., GitHub).
• Vercel CI/CD pipeline.
• Vercel hosting + global CDN.
• End‑user browser.
• Static assets (HTML, CSS, images).
b. Relationships and interactions
1. Developer pushes commits → Git repository
2. Git hook triggers Vercel build → Vercel fetches code
3. Vercel builds (trivially copies) static files → deploys to CDN
4. User browser requests URL → CDN edge node serves the static HTML/CSS/assets
5. Browser renders pages and fetches assets
c. Architectural patterns and design principles
• Static‑site architecture (no backend): high performance, low maintenance.
• CI/CD on push to main branch ensures automated deployment.
• CDN distributed delivery for minimal latency.
d. Relevant technologies, frameworks, or libraries
• HTML5, CSS3
• Vercel hosting & built‑in CDN
• Git/GitHub (or other Git host)