How haltazar/portfolio works
Main System Components
a. Client-Side Layer
• Next.js App Router (app directory structure)
• Component Architecture
• Static Assets
b. Build/Development Layer
• Next.js Build System
• TypeScript Compilation
• TailwindCSS Processing
c. Deployment Layer
• Vercel Platform Integration
Component Organization
a. Core Layout Components
• Root Layout (app/layout.tsx)
• Page Component (app/page.tsx)
b. Feature Components (app/_components)
• Header
• Hero
• Skills
• Contact
• Footer
• Status
c. Reusable UI Components
• Cards (ProjectCard, WorkCard, ContactCard)
• UI Components (from components/ui)
Specific Implementation Details
a. Next.js App Router Architecture:
app/
• layout.tsx (Root Layout)
• page.tsx (Home Page)
• _components/ (Component Organization)
b. Component Hierarchy:
Layout
• Page
• Header
• Hero
• Skills
• Contact
• Footer
c. Build Pipeline:
Source Files → TypeScript → Next.js Build → Optimized Bundle
Integration Points
Connections between:
• UI components and their styling (TailwindCSS)
• Build configuration files (.eslintrc.json, next.config.mjs, etc.)
Notes for Implementation
• Clear separation between app router components and shared UI components
• Build and optimization pipeline
• Development tooling integration
• The Next.js app router architecture
• Component organization and hierarchy
• Build and deployment pipeline
• Static asset management
• Styling system integration