How manukotari/manoj-portfolio works
Project Type and Purpose
• This is a single-page, front-end portfolio application built with ReactJS and plain CSS.
• It uses Swiper for sliding components and EmailJS for the contact form.
• Hosted as a static site (Firebase Hosting), serving assets and the React bundle.
File Structure Analysis
• Top-level:
• public/ – contains index.html and static assets
• src/ – React source code
• .firebaserc, firebase.json – Firebase hosting configuration
• package.json / package-lock.json – dependencies and scripts
• src/ hierarchy:
• App.js, index.js – application entry points
• components/ – logically grouped UI components (header, footer, home, services, skills, about, projects, qualification, testimonials, contact, scrollup)
• assets/ – static resources (PDF resume, images)
• No backend code – it’s purely client-side with reliance on an external EmailJS API.
Insights from README
• Features: responsive layout, fixed navigation, modals, tab panels, slider + pagination, scroll-to-top, contact form.
• Deployment: implied use of Firebase CLI (via firebase.json).
Main Components
a. Client Browser
b. Static Hosting (Firebase Hosting)
c. React Application
• Core modules:
· Routing & Navigation (Header, ScrollUp)
· Page Sections (Home, Services, Skills, About, Projects, Qualification, Testimonials, Contact)
· UI Utilities (Swiper slider, Modals, Tab Panels)
• Asset Loader (loads images, PDF, CSS)
d. External Services
• EmailJS API (for sending contact-form emails)
e. Developer / CI (local dev environment, npm build scripts, Firebase CLI)
Relationships and Interactions
• Browser requests index.html and JS/CSS bundles from Firebase Hosting.
• React app initializes in the browser, mounts App component.
• User interacts with UI components (clicks nav, scrolls, opens modals, slides content).
• On contact form submission, React uses @emailjs/browser to send an HTTP request to EmailJS.
• Developer triggers npm build → Firebase CLI deploy → updates content on Firebase Hosting.
Architectural Patterns and Design Principles
• Component-based architecture: each UI section is a separate React component.
• Unidirectional data flow: React props/state manage component interactions.
• Static hosting pattern: decoupled front end served via CDN (Firebase Hosting).
• API integration: form handling via external EmailJS service.
– Header/Nav, Home, Services, Skills, About, Projects, Qualification, Testimonials, Contact, ScrollUp
5. Assets (images, PDF) as sub-components of the app loaded at runtime.