How oowais/yet-another-portfolio works
Client Layer (Browser) → Nuxt Application Layer → Server Layer
Detailed Component Breakdown
A. Client-Side Components:
• Home (index.vue)
• Education (education.vue)
• Work (work.vue)
• Navigation Components
• Sidenav
• VerticalNav
• Feature Components
• ThemeSwitch
• SkillsCard
• Project Components
• Project Card
• Work Components
• Work Card
B. Application Core:
• Configuration Layer
• app.config.ts
• nuxt.config.ts
• tailwind.config.ts
• Asset Management
• CSS (Tailwind)
• Static Assets
C. Server Layer:
• Server Configuration
• API Routes (if any)
Key Relationships to Highlight
• How pages utilize shared components
• Theme switching mechanism
• Demonstrate the relationship between Tailwind CSS and components
• How the server handles requests
Technical Stack Indicators
Badges or labels for:
• Nuxt 3
• Vue.js
• Tailwind CSS
• TypeScript
Specific Implementation Details
• Component hierarchy
• Routing flow
• Asset pipeline
• Build process
• The component-based architecture
• The clear separation between pages and reusable components
• The configuration system
• The static asset handling
Remember to:
• Notes about key architectural decisions
For this specific Nuxt 3 application, focus on:
• The single-page application (SPA) nature
• The component reusability pattern
• The theming system implementation
• The static site generation capabilities
• How components are organized and reused
• How the routing system works
• How the theming system is implemented
• How the build process transforms the application
A small section showing the development and production deployment flows, as mentioned in the README.