How turnerlopezjuanpablo/myportfolio-turnerlopez works
Project Type and Purpose
• This is a static, client-side Single Page Application (SPA) built with React (using Vite as the bundler) serving as a personal portfolio website.
• No custom backend or API—content is either baked into the build (CV PDF, images) or loaded via React Context/hooks.
File Structure Analysis
Top-level (inside MyPortfolio/):
• index.html – the SPA entry point
• package.json & package-lock.json – npm dependencies and scripts
• vite.config.js – build configuration
• public/ – static assets copied straight to the build output
• src/ – all source code
• main.jsx & App.jsx – app bootstrap and root component
• Components/ – feature modules (AboutMe, Projects, Contact, etc.)
• Components/Context/LanguageContext.jsx – React Context for i18n
• customHooks/useLanguageHook.jsx – custom hook wrapping the Context
• styles/ – CSS/SCSS files scoped per component
Extracting Insights from README
• A React-JS portfolio deployed via Netlify (badge shows CI/CD)
• No mention of external APIs, so all data is either local or fetched via static JSON if added later.
a. Main Components to represent:
1) Developer Environment
– Local codebase (src/, public/)
– Vite Dev Server (hot-reload)
2) Build & CI/CD
– Vite build process (transpile JSX, bundle assets, minify)
– Netlify continuous deployment (Git ↔ Netlify integration)
3) Hosting & Delivery
– Netlify CDN (static hosting of HTML/CSS/JS)
4) Runtime in the Browser
– index.html loads bundle.js & styles
– React root (main.jsx → App.jsx)
– Component tree (TopNav, Presentation, AboutMe, Projects, Contact, etc.)
– LanguageContext providing i18n state via useLanguageHook
– Assets (images, PDF CV) served as static files
– Developer → Git repository → Netlify
– Netlify build triggers Vite → output to CDN
– End user browser → CDN → index.html + bundles
– index.html → React runtime → component hierarchy
– Components consume Context → render localized text
– Components import CSS/SCSS → style DOM
c. Architectural Patterns & Design Principles
– SPA architecture with clear separation between build pipeline, hosting, and runtime
– Component-based UI (React) implementing separation of concerns
– Context API for cross-cutting concerns (language state)
– Custom hooks for encapsulating reusable logic
d. Key Technologies & Frameworks
– React.js (v18+)
– Vite (for fast dev server & bundling)
– Netlify (CI/CD & CDN hosting)
– ECMAScript Modules, JSX
– CSS / SCSS modules & global styles
– Context API & custom React hooks