How bernardinolintang/bernardinolintangwebsite works
Project Type & Purpose
• This is a static single‐page application (SPA) built with React + TypeScript, styled with TailwindCSS, bundled by Vite, and deployed on Vercel.
• Purpose: showcase portfolio content (About, Projects, Tech Stack, Contact) as a fast, responsive, client‐side web experience.
Key Components
a. Development Environment
• Local machine / Developer
• Source code repo (GitHub)
• Node.js + npm (dependencies from npm registry)
• Vite dev server (runs on localhost during development)
b. Build & CI/CD Pipeline
• Vite build process (bundles src/ into static assets)
• Output: build/ directory (HTML, CSS, JS bundles, assets)
• Vercel integration (on push to main branch → triggers build & deploy)
c. Hosting & Delivery
• Vercel (CI/CD + CDN + Edge network)
• Public/static hosting (serves index.html, JS, CSS, images, PDFs)
• CDN caches assets globally
d. Client (Browser)
• HTTP request to CDN → fetches index.html
• Loads JS bundle, CSS, assets
• React runtime renders UI, handles routing, fetches any external images (e.g., Figma fallbacks)
e. UI Library & Internal Modules
• src/components/ui/* (atomic UI components)
• ThemeProvider, WireframeKit, portfolio‐specific components
• TailwindCSS utility classes (post‐processed at build)
Relationships & Data Flow
• Developer → pushes code → GitHub repo
• GitHub webhook → Vercel build start
• Vercel runs npm install → vite build → outputs build/
• Vercel deploy → distributes to CDN
• End‐user’s browser → requests site → CDN edge → serves static files
• Browser executes JS → React renders pages, user navigates SPA
• (Optional) Browser requests external images from fallback sources (Figma URLs)
Architectural Patterns & Principles
• Client‐side rendering: All UI rendered in browser
• Atomic design: Reusable UI components under src/components/ui/
• Single Responsibility: Each React component (accordion, alert, button, etc.) encapsulates one piece of UI logic
• Separation of concerns: Styling (Tailwind) kept in CSS, layout and logic in TSX
• CI/CD via Vercel for zero‐config deploys of static sites
Essential Elements
• Nodes: Developer → GitHub → Vercel Build & Deploy → Vercel CDN → Browser
• Subcomponents: Vite Bundler, TailwindCSS Processor, React Runtime, UI Libraries
• Assets: index.html, CSS, JS bundles, PDFs, images