How owenhochwald/aftrbrnr works
Project Type and Purpose
• Aftrbrnr is a full-stack web application built with Next.js (App Router), React, and TypeScript.
• It provides a professional time-tracking platform: user authentication, project/client management, activity tracking, and dashboards.
High-Level Architecture Overview
Components:
• Browser (Client)
• Next.js Application Server
– UI Layer (React Components + App Router)
– API Layer (app/api/* routes, NextAuth endpoints)
– Middleware (authorization, session handling)
– Business Logic (lib/ folder: auth, authorization, session, utils)
• Database Layer (PostgreSQL via Prisma ORM)
• External Services (Google OAuth)
Relationships and Data Flow
1. User opens the browser → requests a page or API call.
2. Next.js App Router serves pages (SSR/SSG) or routes to client-side React components.
3. Client-side code calls internal API endpoints under /api (e.g., auth, track/actions).
4. API handlers invoke business logic in lib/, then use Prisma to query/update PostgreSQL.
5. NextAuth middleware intercepts auth-protected routes; delegates to OAuth provider (Google) and manages sessions.
6. Responses flow back to API → UI → browser.
Architectural Patterns & Design Principles
• Layered architecture: UI → API → Business Logic → Data Layer.
• Next.js App Router conventions: folder-based routing, server vs. client components.
• Reusable component library under components/ui for consistent styling.
• Prisma migrations manage database schema.
• Middleware enforces auth and role-based access control.
Relevant Technologies & Frameworks
• Next.js App Router (React + Server Components)
• NextAuth.js for authentication/authorization
• Prisma ORM + PostgreSQL for data persistence
• Tailwind CSS for styling
• TypeScript for static typing