How piyush-eon/jira-clone works
Project Type and Purpose
• This is a full-stack, Jira-style issue tracking web application built on Next.js (App Router), React, Tailwind CSS, Prisma (with Neon as Postgres), Clerk for auth, and Shadcn UI components. Users can sign up/in, create organizations, projects, sprints, and issues.
Main Architectural Components
a. Client Browser
• Renders React pages and components under the app/ directory
• Uses Tailwind + Shadcn UI for styling and interactive UI elements
b. Next.js Frontend Layer
• App Router pages (app/(auth), app/(main))
• Client and Server components (e.g., page.jsx, layout.jsx)
• Static assets (public/), global CSS, and data JSON for FAQs, status, companies
c. Authentication Service
• Clerk handles user sign-in/sign-up flows
• Redirects defined in environment variables (NEXT_PUBLIC_CLERK_*)
d. API / Business Logic Layer
• Route handlers in actions/ (issues.js, projects.js, organizations.js, sprints.js)
• Custom server-side utilities (lib/checkUser.js, lib/utils.js)
• Middleware for auth/session checks (middleware.js)
e. Data Access Layer
• Prisma ORM (prisma/schema.prisma, migrations)
• Neon (Postgres) database accessed via lib/prisma.js
f. Third-Party and Configuration
• Shadcn UI components in components/ui/
• eslint, Tailwind, Next.js configs
Component Interactions and Data Flows
• User → Browser → Next.js React Components (UI)
• UI triggers fetches or form submissions → Next.js server actions in actions/
• Actions validate auth via Clerk & lib/checkUser.js, execute CRUD via Prisma → Neon DB
• Responses propagate back up to UI; state updates rerender pages
• Static JSON data read directly by frontend for FAQs, statuses
Architectural Patterns and Principles
• Folder-based routing (Next.js App Router) dividing auth vs main flows
• Separation of concerns: UI vs API actions vs data layer
• Single source of truth for data via Prisma ORM models
• Use of middleware for cross-cutting concerns (auth checks)
• Server components handle data loading; client components handle interactivity