How mikeheul/next-activity-tracker works
Project Type: Full-stack web application built with Next.js, using MongoDB for data storage and Prisma as the ORM.
Main Components
a. Frontend Layer:
• Next.js Pages/Components (app directory structure)
• Activity Chart Component
• Activity Tracker Client Component
b. API Layer:
• Next.js API Routes (/api/activity)
• Activity Data Fetching Logic
c. Database Layer:
• MongoDB Database
• Prisma ORM
• Activity Collection Schema
Component Relationships
[Frontend Layer] → [API Layer] → [Database Layer]
Detailed Component Breakdown
Frontend Layer (Top):
┌─────────────────────────────────┐
• Frontend Components │
• Activity Page │
• ActivityChart │
• ActivityTrackerClient │
• ┘
API Layer (Middle):
┌─────────────────────────────────┐
• API Routes │
• /api/activity │
• fetchActivities.ts │
• ┘
Database Layer (Bottom):
┌─────────────────────────────────┐
• Database │
• MongoDB │
• Prisma Schema │
• Activity Collection │
• ┘
Important Details
a. Data Model:
Activity {
• _id: ObjectId
• userId: String
• date: DateTime
• activityCount: Number
}
b. Key Technologies:
• Next.js (App Router)
• MongoDB
• Prisma ORM
• TypeScript
• Tailwind CSS