How iamakchavan/akchavan works
Project type and purpose
• This is a single-page, full-client “Personal Portfolio Website Template” built with React, TypeScript, Vite, and Tailwind CSS.
• Its sole job is to present personal information, skills, and projects via a responsive UI; there is no custom backend or database in the repository.
File structure
• Top-level directories/files of interest:
• public/ – Static assets (images, favicon, preview.png).
• src/ – Application source.
– components/ – Reusable UI building blocks (VoiceAgent.tsx, Radix-based UI primitives in ui/).
– screens/ – Page-level components (Cogito, ElementLight, Live).
– lib/ – Utilities and helper functions.
– index.tsx – React entry point & client‐side router setup.
• index.html – Root HTML template.
• vite.config.ts – Vite dev/build config.
• tailwind.config.js & tailwind.css – Tailwind CSS setup.
• tsconfig*.json – TypeScript configuration.
• vercel.json – Deployment settings for Vercel.
a. Main components to represent:
• Browser (Client)
• React Application
– Entry Point (index.tsx + index.html)
– Router Layer (React Router DOM)
– Screens (Cogito, ElementLight, Live)
– Shared Components (VoiceAgent, UI primitives, badges, buttons, cards, separators)
– Utilities (lib/utils.ts)
• Build/System Tools
– Vite Dev Server & Bundle Pipeline
– TypeScript Compiler (TS → JS)
– PostCSS/Tailwind Processing
• Hosting & CDN
– Vercel (serves the static build)
• Static Assets
b. Relationships & data flow
1. Developer runs npm run dev → Vite Dev Server loads index.html, processes TSX/CSS, serves hot-reload.
2. Browser requests root → Vercel/CDN serves pre-built static HTML/CSS/JS.
3. React App bootstraps in the browser → index.tsx initializes Router.
4. User navigates → Router loads appropriate Screen component → reuses components from /components.
5. Components request utilities (lib/utils.ts) or import static assets.
6. Styles are applied via compiled Tailwind CSS classes & Radix UI primitives.
c. Architectural patterns & design principles
• Component-driven: UI split into small, reusable, focused components.
• Module-based routing: Each screen in its own folder for lazy loading.
• Utility-first styling: Tailwind classes, with helper libs (C V A, clsx).
• Unidirectional data flow: Props down, events/callbacks up.
• Static site: No client-side state management beyond React local state/hooks.