How paultibe/roammates works
High-Level Architecture Components
a) Frontend Layer (Next.js Application):
• Sub-components:
• Pages/Routes (showing the main flow: dashboard → who → where → when → voting → review)
• Components (shared UI elements)
• Client-side Authentication (Auth0 integration)
b) API Layer (Next.js API Routes):
• API endpoints:
• Auth endpoints (/api/auth/[auth0])
• Profile creation (/api/create-profile)
c) Backend Layer (Deno):
• This at the bottom
• Connection to data storage (data.json)
Component Relationships
a) Client-Side Flow:
• Component reuse relationships
• Authentication flow
b) Data Flow:
• API calls between frontend and backend
• Data persistence flow to storage
• Authentication flow with Auth0
Key Technical Elements to Highlight
Create dedicated sections or callouts for:
a) Authentication & Authorization:
• Auth0 integration
• Protected routes
• User sessions
b) State Management:
• Firebase integration (shown in /lib/firebase)
• User model handling
c) External Services:
• Google Places API (indicated by GooglePlacesInput component)
• Voiceflow integration (indicated by voiceflow-test route)
Specific Implementation Details
Technical annotations for:
• Next.js 13+ App Router architecture
• TypeScript implementation
• Tailwind CSS styling
• Firebase integration
• Deno backend
Additional Elements
Create sections showing:
• Development tools and configuration
• Build and deployment pipeline
• Environment configurations
Integration points with external services
• The application's core trip planning functionality
• The social aspects (mate selection, voting)
• The authentication and authorization flow
• Data persistence strategy
• External service integrations