How adrianhajdin/yc_directory works
Main System Components
a) Client Layer:
• Next.js Frontend (App Router)
• UI Components (ShadCN)
• Client-side Authentication
• Error Boundaries (Sentry integration)
b) Server Layer:
• Next.js API Routes
• Server Actions
• Authentication Service (NextAuth)
• GitHub OAuth Integration
c) Data Layer:
• Sanity CMS
• Content Management Studio
• Real-time Updates
• Content API
Component Relationships
[Client Layer]
• ↑↓
[Server Layer]
• ↑↓
[Data Layer]
Detailed Component Breakdown
Frontend (App Router):
• Root Layout (/app/layout.tsx)
• Authentication Pages
• Startup Pages
• User Profile Pages
• Studio Integration
API Routes:
• Authentication Endpoints
• Sentry Integration
• Server Actions
Database Schema (Sanity):
• Startup Schema
• Author Schema
• Playlist Schema
Key Flows to Highlight
Authentication Flow:
User → GitHub OAuth → NextAuth → Session Management → Protected Routes
Content Management Flow:
Sanity Studio → Content API → Server Actions → Client Components
Technical Stack Indicators
• Next.js 15
• React 19
• TypeScript
• Tailwind CSS
• Sanity
• ShadCN
• GitHub OAuth
Important Implementation Details
Features:
• Live Content API integration
• Authentication system
• View tracking system
• Search functionality
• Editor picks feature
Keep the abstraction level high enough to understand the system architecture but detailed enough to show the unique features of this startup directory platform, particularly the integration between Next.js and Sanity, and the authentication flow with GitHub.
Remember to emphasize the modern Next.js 15 architecture with the App Router pattern and server components, as these are crucial aspects of the system's design.