How arjuncodess/analyzr works
Main Components
a. Client-Side Components:
• Website with Tracking Script (public/tracking-script.js)
• Analyzr Dashboard (Next.js Frontend)
b. Server-Side Components:
• Next.js API Routes
• Supabase Database
• Discord Integration Service
[Client Layer]
[API Layer]
[Service Layer]
[Data Layer]
Detailed Component Breakdown
a. Client Layer:
• Next.js frontend with key pages:
• Dashboard (/app/dashboard)
• Authentication (/app/(auth))
• Site Analytics (/app/site/[website])
• Settings (/app/settings)
b. API Layer:
• Two main API routes:
• /api/track (for analytics tracking)
• /api/events (for custom events)
c. Service Layer:
• Analytics Service (actions/fetchAnalytics.ts)
• User Management (hooks/useUser.ts)
• Page Speed Metrics (actions/pageSpeedMetrics.ts)
• Discord Client (lib/discord-client.ts)
d. Data Layer:
• Supabase Database (config/supabase.ts)
• Data models for:
• User data
• Analytics events
• Custom events
• Website configurations
Flow Representations
• Data flow from client websites through the tracking script
• API request/response paths
• Discord notification flow
• Database interactions
Component Interactions
• How tracking script data flows to the database
• How the dashboard retrieves and displays analytics
• How custom events trigger Discord notifications
• How performance metrics are collected and processed
Additional Elements
Include:
• Version/environment indicators
• Security boundaries
• Error handling paths
• Caching mechanisms
Technical Stack Indicators
• Next.js 13+ (App Router)
• Supabase
• Discord API
• Edge Functions
• shadcn/ui components