How abhinavrai2004/myportfolio works
Main Components
• Next.js Application: Represent the core of your project (the “app” directory) that includes page routing, layouts, and component rendering.
• Presentation/Component Layer: Illustrate the various individual UI components (organized under app/components and its subdirectories like homepage, navbar, footer, and helper components).
• API Layer: Indicate the minimal server-side functionality, seen in app/api (for example, app/api/google/route.js), which may be handling serverless requests or integration with external services.
• Static Assets and Public Files: Include the “public” folder housing images, lottie animations, pngs, and svg files.
• Utility Functions and Data Layer: Represent the “utils” folder containing helper functions (e.g., check-email, time-converter) and data files (contactsData, educations, projects-data, etc.) used to populate the UI content.
• Configuration and Styling: Include build and style configuration files such as next.config.js, tailwind.config.js, postcss.config.js, SCSS files, and others (e.g., .eslintrc.json) that play a vital role in how the project is built and maintained.
Mapping Relationships and Interactions
• That the API route (app/api/google) exists as a separate component that the front-end can call when certain actions need backend processing.
• Public folder to the presentation layer as the source of static media (images, lottie animations, svg files) that are used within the components.
• External integrations like EmailJS (for sending emails) and optionally reCAPTCHA for contact forms, showing that these external services interact with the client-side actions.
Architectural Patterns & Design Principles
• Separation of concerns: the project divides UI concerns (components and layouts), data (found in ‘utils’), API endpoints, and configuration (Next.js and styling configurations).
• Use of Next.js “App Router” where pages and layout files are co-located, which is a modern architectural approach.
• That styles are managed via SCSS (in app/css) alongside Tailwind CSS for utility classes, highlighting a hybrid approach for styling.
• That the project organizes the portfolio sections modularly, indicating a component-based architecture consistent with React and Next.js practices.
– The flow from UI components to API endpoints when actions (like submitting a contact form) occur.
– The retrieval and use of static data from the utils folder to render dynamic sections.
– The integration with external services (EmailJS, reCAPTCHA, etc.) as part of the data flow.