How moksha-hub/atlassian-issue-tracker-clone works
Project type and purpose
• This is a full-stack web application—an “Atlassian Issue-Tracker Clone”—built on Next.js 14 (App Router), React, TypeScript, TailwindCSS and Shadcn UI on the frontend, Hono-powered serverless routes on the backend, and Appwrite as a BaaS for authentication, database, and file storage.
File structure
• src/app
– (auth), (dashboard), and (standalone) folders represent nested layouts and page groupings in the Next.js App Router.
– src/app/api/[[...route]]/route.ts and src/app/oauth/route.ts define serverless API endpoints (using Hono).
• src/components + src/features
– UI components (Shadcn/Tailwind) and feature folders (auth, workspaces, projects, tasks, members) each contain client hooks, server route handlers, schemas, and utility modules—indicating a feature-driven, domain-centric design.
• src/lib
– Bootstraps the Appwrite SDK, OAuth integration, RPC utilities, session middleware, and generic utilities.
• Configuration files
– next.config.mjs, tailwind.config.ts, postcss.config.mjs, tsconfig.json + .env.local for Appwrite endpoints and credentials.
README for additional insights
• Confirms technology stack (Next.js, React, TypeScript, Tailwind, Appwrite, Hono, Shadcn UI).
• Features: workspace & team management, project/task CRUD, multiple task views (table, Kanban, calendar), responsive UI.
a. Main components
– Client (Browser) running the Next.js React SPA/SSR app
– Next.js Server
• App Router rendering layouts/pages
• Serverless API layer (Hono) handling domain routes under src/app/api and src/features/*/server/route.ts
• Session middleware (lib/session-middleware.ts)
– Appwrite Backend
• Auth service (users, tokens)
• Database service (collections: workspaces, members, projects, tasks)
• Storage service (images bucket)
– External OAuth Provider (if OAuth flow is configured)
b. Relationships & data flow
1. Browser → Next.js SSR/SSG pages (HTML/CSS/JS)
2. Browser → Next.js API endpoints (fetch via feature hooks use-* API)
3. Next.js API → Appwrite SDK (reads/writes to collections)
4. Next.js Session Middleware ↔ Appwrite Auth (validate sessions/tokens)
5. (Optional) Browser ↔ External OAuth → Next.js OAuth route → Appwrite Auth
c. Architectural patterns & design principles
– Feature-based folder structure (domain-driven design)
– Next.js App Router with nested layouts for cross-cutting concerns (auth guard, dashboard wrapper, standalone pages)
– BaaS backend (Appwrite) for rapid development, decoupling persistence & auth from application logic
– Serverless functions (Hono) as the API layer, promoting microservice-like separation per feature
d. Key technologies/frameworks
– Next.js 14 (App Router)
– React + Shadcn UI + Tailwind CSS (UI layer)
– Hono (lightweight serverless router)
– Appwrite SDK (database, auth, storage)
– Zod schemas for validation in features
– hello-pangea/dnd, react-big-calendar, date-fns, etc., for rich task interactions