How rutaganda-salim/fizzy works
Main System Components
A. Client-Side (Frontend) Layer:
• Next.js 14 Application
• 3D Rendering Engine (Three.js)
• Animation System (Framer Motion)
• Component Library
• State Management
B. Content Management Layer:
• Prismic.io Headless CMS
• Content Types
• Preview System
C. API Layer:
• Next.js API Routes
• Revalidation System
• Preview Controls
[Client Layer] ←→ [API Layer] ←→ [CMS Layer]
Detailed Component Breakdown
Client Layer (Left Column):
• Pages (src/app directory)
• Components (src/components)
• 3D Elements (FloatingCan, SodaCan, ViewCanvas)
• Slice Components
• Hooks (useStore, useMediaQuery)
API Layer (Middle Column):
• Include:
• Preview API Routes
• Revalidation Endpoints
• Content Type Definitions
CMS Layer (Right Column):
• Show:
• Prismic.io Connection
• Content Models
• Preview Service
Important Details
• File structure organization (src/components, src/slices, etc.)
• API routes for preview and revalidation
• Content type definitions and their relationship to components
• 3D asset management (public directory)
• Integration points between Next.js and Prismic
Additional Notes
• Preview system workflow
• How static and dynamic content is handled
• Build-time vs. runtime processes
• Points of client-side interactivity
Remember to emphasize the unique aspects of this project:
• The 3D rendering pipeline
• Animation system integration
• Content management workflow
• Preview and revalidation mechanisms