How cavargasl/portfolio works
Main Components Identification
The system should be represented in three main layers:
• Domain (Core Business Logic)
• Application (Use Cases)
• Infrastructure (External Interfaces)
Component Relationships
• Inward dependencies (Infrastructure → Application → Domain)
• Repository interfaces in the domain layer
• Implementation of repositories in the infrastructure layer
• Service consumption by UI components
Specific Implementation Details
Create sections showing:
a) Domain Entities:
Jobs
Projects
Skills
TechnicalTests
b) Repository Interfaces:
JobRepository
ProjectRepository
TechnicalTestRepository
c) Infrastructure Implementations:
LocalJobsRepository
LocalProjectsRepository
LocalMarkdownTechnicalTestRepository
Additional Elements
Include:
• Language handling (es/en)
• Data flow directions
• External dependencies
• Testing boundaries
Architectural Patterns
Highlight:
• Dependency Injection patterns
• Repository pattern implementation
• Service layer pattern
• Clean Architecture boundaries
Technical Stack Integration
Integration points for:
• Next.js/Astro frameworks
• React components
• Markdown processing
• Infrastructure utilities
Testing Boundaries
Indicate:
• Unit test coverage
• Integration test boundaries
• Mock implementations
• Test utilities
• Clear separation of concerns
• Dependency flow (always inward)
• Interface abstractions
• Clean Architecture principles
• Domain-driven design concepts
Remember to maintain a balance between detail and clarity, focusing on the hexagonal architecture while showing how the portfolio's specific features fit into this pattern.