How codedu-collective/kind-hands works
Project Type and Purpose
• Kind Hands is a full-stack, server-rendered web application built on Next.js 16 with TypeScript and Tailwind CSS.
• It’s a charity platform that connects donors and volunteers to causes, events, and team information, backed by a PostgreSQL database via Prisma ORM.
File Structure Analysis
• Top-level directories:
• app/ – Next.js App Router pages (server & client components).
• components/ – Reusable UI components organized by feature (landing, causes, event, layout, etc.).
• lib/ – Database client wrapper (Prisma).
• prisma/ – Database schema, migrations, seeds.
• utils/ – Data-fetching helpers (cause/event retrieval).
• Config files: next.config.ts, tsconfig.json, eslint.config.mjs, postcss.config.mjs.
• Build scripts and dependencies defined in package.json/pnpm-lock.yaml.
README Insights
• Confirms tech stack: Next.js App Router, React 19, TypeScript, Tailwind CSS.
• Lists setup of environment variables (DATABASE_URL, POSTGRES_URL, PRISMA_DATABASE_URL).
• No separate API folder: server components call Prisma client directly for data.
Main Components
a. Frontend Layer (Client Browser)
• React components (components/*)
• Tailwind CSS for styling
• Static assets from public/ via Next.js static file server
b. Next.js Server (Node.js)
• App Router (app/) for routing & rendering
• Server Components fetch data using utils/* → lib/prisma.ts
• Client Components for interactivity (ThemeToggle, subscribe forms, etc.)
c. Data Access Layer
• Prisma Client (lib/prisma.ts)
• TypeScript types (implicit in utils & Prisma schema)
d. Database Layer
• PostgreSQL instance (PRISMA_DATABASE_URL)
• Prisma schema and migrations (prisma/schema.prisma, prisma/migrations/)
e. Build & Deployment
• PNPM build pipeline (pnpm dev, build, start)
• Vercel (or other Node host) for serverless deployment
• Tailwind CSS/PostCSS during build
Relationships and Interactions
• Browser → HTTP Request → Next.js Server Router
• Router invokes Server Component (app/page.tsx or dynamic route)
• Server Component calls utils/get/* → Prisma Client → PostgreSQL
• Data returns to Server Component → HTML/JSON → Browser
• Client Components hydrate on the browser for interactivity
• Static assets served directly from public/ via CDN or Next.js
Architectural Patterns & Principles
• File-based routing with Next.js App Router (server-first, with selective client components).
• Layered architecture:
• Presentation (React UI)
• Business Logic (utils/get, server components)
• Data Access (Prisma)
• Persistence (PostgreSQL)
• Convention-over-configuration: Next.js, Prisma migrations.