How gi0210lee/next14-notion-clone works
Main System Components
a) Frontend Layer:
• Marketing Pages (/(marketing))
• Authentication Pages (/(auth))
• Main Application (/(main))
• Public Preview (/(public))
• UI Components (/components)
b) Backend Layer:
• API Routes (/api)
• Convex Backend Integration (/convex)
• EdgeStore Integration (for file storage)
c) State & Data Management:
• Hooks (/hooks)
• Providers (/components/providers)
┌─ Client Layer ─────────────────────┐
• ┌─────────┐ ┌─────┐ ┌───────────┐ │
• Marketing│ │Auth │ │Main App │ │
• ┘ └─────┘ └───────────┘ │
• ┘
┌─ Application Layer ────────────────┐
• ┌─────────┐ ┌──────┐ ┌─────────┐ │
• Next.js │ │React │ │TailwindCSS│
• ┘ └──────┘ └─────────┘ │
• ┘
┌─ Backend Services ────────────────┐
• ┌────────┐ ┌─────────┐ │
• Convex DB│ │EdgeStore│ │
• ┘ └─────────┘ │
• ┘
Key Relationships to Highlight
• Client components → Next.js Router
• API Routes → Backend Services
• Authentication flow between components
• Data flow between documents and storage
Component Details
• Purpose
• Key dependencies
• Data flow direction
• Security boundaries
Technical Stack Callouts
Technologies:
• Next.js 13+ (App Router)
• Convex for backend
• EdgeStore for file storage
• TailwindCSS for styling
• TypeScript for type safety
Architectural Patterns
Patterns:
• Server Components vs Client Components
• Route Groups structure
• Provider pattern for global state
• Hook-based state management