How rsanch40/myportfoliowebsite works
Main Components
• Browser/User Interface – “Client:” Represents the end users visiting the website.
• Public Assets – The public folder holds static files like index.html, the manifest, and other assets (e.g., the resume PDF), which are served directly to the user’s browser.
• React Application – Represent the core of the app within the “src” folder with its main entry point in index.js and the root component App.js.
• UI Components – Illustrate the modular components under the src/components directory (e.g., Header, Navbar, Contact, Projects, and ProjectCard) as individual building blocks.
• Hooks/Utilities – Include a note for the custom hook (useInView) from src/hooks, which handles specific interactions or state logic related to viewport observations.
• External Services – Represent external systems such as:
• GitHub: Display project cards link to GitHub repositories.
• Firebase: Indicate the firebase.json configuration used for deployment/hosting.
Relationships and Interactions
• The user accesses the portfolio via a browser, which loads the initial static assets (from the public directory, particularly index.html).
• The index.html file loads the bundled JavaScript (built from the src directory) that initializes the React application.
• The React application (from App.js) integrates and orchestrates various UI components representing different sections (header, navigation, projects area, contact).
• UI components communicate with one another; for example, the Navbar might influence what the Header displays while project cards, when clicked, open an external link (to GitHub).
• The custom hook (useInView) manages viewport-related logic for animations or lazy loading within components.
• Firebase acts as both the deployment environment and host configuration, ensuring the website is served correctly.
Architectural Patterns and Design Principles
• Component-Based Design – The system follows a modular approach, with clearly separated UI components.
• Separation of Concerns – Styling (CSS files), logic (JS files), and hooks are neatly distributed in their directories.
• Single-Page Application (SPA) Architecture – The routing and dynamic content rendering are managed within the client side.
• External Integration – The project clearly defines boundaries between local presentation logic and external resources like GitHub repositories.
Relevant Technologies
• JavaScript/React (React components are central)
• HTML and CSS – For layout and styling (found in public/index.html and src/*css files)
• Firebase – Indicated by firebase.json for hosting and potentially other services.
• GitHub – The project cards link out to repositories.