How jorgeslfreitas/portfolio works
Project Type and Purpose
• This is a static portfolio website built with plain HTML, CSS, and JavaScript.
• It has no backend or database—its sole purpose is to serve personal/professional information to visitors.
High-Level Architecture Components
a. Client (Browser)
• User’s web browser (Chrome, Firefox, etc.) that renders HTML, CSS, JS.
b. Static Web Host / CDN
• A server or CDN (e.g., GitHub Pages, Netlify, Vercel) that delivers files over HTTPS.
c. Static Assets
• index.html: entry point.
• CSS modules under assets/css/:
• global.css (reset, base styles)
• header.css, skills.css, projects.css, forms, accordions, etc.
• JavaScript modules under assets/js/:
• acordeon.js (handles interactive accordion sections)
• Fonts under assets/fonts/:
• neue-machina-regular.otf.
• favicon & manifest under assets/favicon/.
Relationships and Data Flow
1. Browser issues an HTTPS GET for index.html.
2. index.html references CSS, JS, images, fonts.
3. Browser fetches those assets in parallel.
4. CSS modules style the DOM; JS modules enhance interactivity (accordion behavior).
5. Browser renders the complete UI to the user.
Architectural Patterns & Design Principles
• Separation of Concerns: HTML for structure; CSS split into feature-specific modules; JS for behavior.
• Static-First: Entire site is pre-built; no runtime server logic.
• Modular Asset Organization: Assets grouped by type and feature for maintainability.