How luanrebuli/luan-portfolio works
Project type and purpose
• This is a single-page application (SPA) portfolio website built in React/TypeScript.
• Its sole purpose is to present Luan Rebuli’s profile, skills, projects and a contact form.
• It is deployed as static assets on Vercel and integrates a third-party EmailJS service for form submissions.
Key parts of the file structure
• Top-level config: vite.config.js, package.json, .eslintrc.cjs
• public/index.html + locales (en.json, pt.json)
• src/
• assets – images & media
• components – reusable UI pieces (IntroductionPage, Profile, Projects, Skills, ThemeButton, LanguageSelection)
• containers – larger composition units (OfflinePC, OnlinePC)
• routes – React router entrypoints
• styles – global and styled-component definitions
• i18nify.js – internationalization setup
• main.jsx – React DOM bootstrap / Vite entry
Insights from README
• Built on ReactJS + Vite + TypeScript, styled with TailwindCSS & Shadcn UI
• Hosted on Vercel, contact form powered by EmailJS
• Performance, responsiveness, theme switching, i18n
a. Client Browser
• Loads index.html from Vercel CDN
• Executes bundled React application (main.jsx → App → routes → components/containers)
b. Hosting & CDN
• Vercel deployment of static assets (JS, CSS, images, locales)
• Edge caching for fast global delivery
c. React Application
• Route manager (src/routes/index.jsx)
• UI components grouped under “components” and “containers”
• Global styles & theme toggle
• Internationalization service (i18nify.js + JSON locale files)
d. Third-party services
• EmailJS API endpoint for contact form submissions
• External links to GitHub/project deployments
Architectural patterns and design principles
• Component-based UI (atomic/reusable components)
• SPA routing (client-side)
• Separation of concerns:
• UI components vs. containers vs. routing
• Static assets vs. build config vs. localization
• Third-party integration kept modular (EmailJS)