How rehanalik/zcrum works
Project type and purpose
• This is a full-stack Next.js (v13+) web application that provides a project management interface (organizations, projects, issues, sprints).
• It uses the Next.js App Router (app/ directory), React components (components/), server actions (actions/), authentication pages (app/(auth)/), onboarding & main workflows (app/(main)/), and Prisma ORM (prisma/) to persist data.
File structure
• Top-level:
• app/ – Next.js App Router: directory-based routes, layouts, server & client components
• actions/ – server “action” modules for CRUD operations (issues, projects, sprints, organizations)
• components/ – reusable React components (UI primitives in components/ui/)
• lib/ – low-level utilities and Prisma client instantiation (lib/prisma.js, lib/utils.js)
• prisma/ – schema and migrations for database
• data/ – static JSON reference data (companies.json, status.json)
• hooks/ – client hooks (use-fetch wrapper)
• middleware.ts – Next.js middleware (e.g., for authentication guard)
• public/ – static assets
• The file structure suggests an MVC-style boundary:
• View: app/ pages & components/ React UI
• Controller → actions/ modules, Next.js route handlers, middleware.ts
• Model: Prisma schema + database
Key insights from README
• Bootstrapped via create-next-app.
• Uses next/font, optimized for Vercel deployment.
• No detailed architecture in README, so infer common full-stack Next.js pattern.