How eyalsberro/portfolio works
Main Components Identification
a) Client-Side Layer
• Next.js App Router (app directory structure)
• Static Assets (public directory)
• Component Architecture
b) Page Structure
• Main sections (Photography, Web Development, About Me, Contact)
• Shared Components (Header, Footer, HeroSection)
┌─────────────────────────────────────────┐
• Next.js Application │
• ┘
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
• (page) │ │ Components │ │ Public │
• Route Group│ │ Layer │ │ Assets │
• ┘ └─────────────┘ └─────────────┘
Component Relationships
• Data flow between pages and components
• Asset loading paths
• Component inheritance
Specific Implementation Details
a) App Router Structure
• Nested routing structure under app/(page)
• Photography section's complex nested structure
• Shared layouts and components
b) Static Asset Management
• Relationship between public/pictures and their corresponding routes
• Demonstrate how images are served to different sections
c) Component Architecture
• How shared components (Header.jsx, Footer.jsx, HeroSection.jsx) are used across pages
• Relationship between components and their CSS modules
Additional Notes
• Clear separation between route groups and shared components
• Modular nature of the photography sections
• Demonstrate the relationship between .js files containing data (projects.js, pictureBTS.js, etc.) and their corresponding pages
• Optimization features provided by Next.js