How walterjiron/portafolio works
Project type and purpose
• Type: Single-page front-end application (React) built with Vite
• Purpose: A personal portfolio/site (renders header, skills, projects, contact sections, and serves a CV PDF)
File structure
• Top-level files:
– index.html: application shell
– package.json, vite.config.js, eslint.config.js: build/DevOps config
– .env.example: environment variables template
– public/: static assets (e.g. CV PDF)
• src/: all source code
– main.jsx: React entry point, mounts <App/> into index.html
– App.jsx: root component, orchestrates page sections
– components/: UI modules under subdirectories for Header, Contact, Projects, Skills
• Each component folder has a .jsx entry, a CSS module, and (where needed) an img folder with JS index of image imports
– index.css & App.module.css: global and scoped styles
• No backend or API layers—purely a front-end SPA
README
• Confirms usage of Vite + React HMR
• Mentions ESLint, plugins, and possible TS expansion (not in scope)
a. Main components
– Browser (end user)
– Vite Dev Server / Build Pipeline
– index.html shell
– React root: <App/>
• Header
• Skills
• Projects
• Contact
– Public static assets: CV PDF, images (served from public/ and imported via img modules)
– ESLint (static analysis during dev/build)
b. Relationships & interactions
– Browser requests index.html → Vite Dev Server (during dev) or CDN/static host (in prod)
– index.html loads the JS bundle (main.jsx → App → sub-components)
– <App/> passes props down to Header, Skills, Projects, Contact
– Components import CSS modules for styling (CSS Modules integrated by Vite)
– Projects & Skills components import image JS modules which reference static files in public or src/assets
– Clicking “Download CV” component triggers direct GET from public/Walter_Jiron_CV.pdf
c. Architectural patterns/design principles
– Component-based UI (React) with one-way data flow (App as parent)
– CSS Modules for scoped styles
– Vite’s plugin system for fast refresh (React or React-SWC)
– Separation of concerns: UI, styling, static asset management, build config
d. Key technologies/frameworks/libraries
– React (UI library)
– Vite (bundler/dev server) with @vitejs/plugin-react or plugin-react-swc
– Babel or SWC (JSX transpilation & Fast Refresh)
– ESLint (lint rules)
– CSS Modules (scoped styles)
Elements
– Labels: “Browser,” “Vite Dev Server,” “index.html,” “main.jsx/App.jsx,” each component folder
• From Browser → Dev Server (dev) or CDN (prod) for index.html
• From index.html → JS bundle → React root → child components ← CSS modules/static assets
• From component UI → static asset GET for CV PDF
• Rectangles for physical layers (Dev Server, CDN, Browser)