How eduardoooxd/portfolio works
Main Components
• Frontend Application: Representing the Next.js app that handles server-side rendering and static generation. This includes the components under /src/app, which define pages, layouts, sitemap, robots file, etc.
• Global State & Domain Logic: Highlight the /src/context (for global state management) and /src/domain (defining contact form models, experience, screen-size, and theme definitions).
• Utility Libraries: Indicate /src/lib which provides hooks, MDX parsing, helper functions, and common types. This supports the orchestration of data flow and component interactions.
• Email Handling: Point out /src/email where Resend-powered email templates or functionalities reside.
• External Dependencies/Services: Include external services like Resend for email and PostHog (as hinted by the provider in /src/providers/posthog.tsx) for analytics, along with public assets in /public and the integration of third-party libraries like Framer Motion.
Relationships and Data Flow
• Utility & Domain Contributions: Show that both UI components and server actions rely on utility functions (/src/lib) and domain models (/src/domain) to perform validations, data formatting, and business logic operations.
Architectural Patterns and Design Principles
• Modular Architecture: Emphasize the separation of concerns (UI, business logic, global state, and utility functions).
• Server-side Rendering and Static Site Generation: Point out that Next.js app structure supports these features, optimizing for SEO and performance.
• Component Reusability: Note that the portfolio is built with reusable React components, which improves maintainability and scalability.
• Responsive Design & Animations: Indicate that visual presentation is enhanced with media queries and Framer Motion animations.
Relevant Technologies and Frameworks
• Next.js 14, React, Framer Motion, and Resend are core to the functionality.
• Integration with PostHog (analytics) and the use of TypeScript (notice the .ts/.tsx files).