How ismaelherreradev/tasky works
Main Components
A. Frontend Layer:
• Next.js 14 Application Structure
• Landing Pages (src/app/(landing))
• Platform Pages (src/app/(plataform))
• Authentication Pages (src/app/(clerk))
• UI Components (src/components)
B. Authentication Layer:
• Clerk Authentication Service
• Role-based Access Control
• Organization Management
C. Backend Layer:
• tRPC API Routes (src/server/api)
• Router Handlers for:
• Boards
• Cards
• Lists
• Activity Logs
D. Database Layer:
• Turso (LibSQL)
• Drizzle ORM
• Schema Management
┌─ Client Layer ─────────────────────┐
• Next.js 14 Frontend │
• Public Routes │
• Protected Routes │
• UI Components │
• Authentication Layer ─────────────┤
• Clerk Authentication │
• User Management │
• Organization Management │
• Role-based Access │
• API Layer ────────────────────────┤
• tRPC API │
• Board Router │
• Card Router │
• List Router │
• Logs Router │
• Data Layer ────────────────────────┤
• Turso Database │
• Drizzle ORM │
• Schema Management │
Key Relationships to Highlight
• Client-to-API: Show tRPC connection between frontend and API layer
• Authentication Flow: Demonstrate how Clerk integrates with protected routes
• Data Flow: Illustrate how requests flow from UI through API to database
• Activity Logging: Show how system events are captured and stored
Technical Stack Callouts
A technical stack sidebar showing:
• Next.js 14
• Clerk
• tRPC
• Drizzle
• Turso
• TailwindCSS
• shadcn/ui
Additional Elements
• Version information
• Deployment targets (Vercel, Netlify, Docker)
• Scaling considerations
• How the application's components interact
• Where different types of logic reside
• How data flows through the system
• Security boundaries and authentication flows
• Integration points with external services