How michaeldahl7/dashboard works
Main Components
a. Client-Side (Frontend):
• React Application Layer
• UI Components (shadcn/ui)
• State Management (Tanstack Query)
• Routing (Tanstack Router)
• Form Handling (Tanstack Form)
b. Server-Side:
• API Layer (Tanstack Start)
• Authentication Service (Better Auth)
• Database Layer (PostgreSQL with DrizzleORM)
c. External Services:
• Social Auth Providers (Google, Discord)
Architecture Representation
[Client Layer]
• ↑↓
[API Layer]
• ↑↓
[Service Layer]
• ↑↓
[Data Layer]
Component Details
Frontend (Client Layer):
• Modular structure reflecting the /apps/web/app directory
• Areas:
• Components (/components)
• Routes (/routes)
• Services (/services)
• Hooks (/hooks)
Service Layer:
• Packages structure:
• Auth Package (/packages/auth)
• DB Package (/packages/db)
• UI Package (/packages/ui)
Data Layer:
• Database schemas from /packages/db/src:
• Auth Schema
• House Schema
• Item Schema
• Location Schema
Key Flows to Highlight
a. Authentication Flow:
User → Social Auth → Auth Service → Database
b. Data Flow:
Client → API Routes → Services → Database
Important Details
• Monorepo structure (apps/ and packages/)
• Multi-house support architecture
• Authentication boundaries
• API route organization
• Database schema relationships
Specific Implementation Notes
• Separation between public and authenticated routes (_public.tsx vs _authed.tsx)
• House-based multi-tenancy
• Demonstrate the inventory tracking system's components
• Theme switching mechanism
This architecture should emphasize the modern full-stack nature of the application while showing how it leverages the monorepo structure to maintain clean separation of concerns between UI components, business logic, and data access layers.