How amardeeplakshkar/svcdalauda works
Project type and purpose
• This is a full-stack web application—SVC Dalauda College Management Portal—built using Next.js 16 (App Router), React 19, and TypeScript.
• Purpose: provide a unified interface for faculty management, content (blogs/announcements/notices) publishing, dynamic form building, user authentication, and file storage.
File structure
• Top-level directories:
• app/ – Next.js App Router (client pages under app/(routes) and app/(auth), plus API routes under app/api).
• components/ – React UI broken into admin-specific, core (public site), UI primitives (Radix wrappers), and context providers.
• hooks/, lib/, shared/ – data-fetching hooks, utility libraries (supabase client, Drizzle ORM setup), and shared schemas/routes.
• public/ – static assets.
• config files – next.config.ts, tailwind.config.js, drizzle.config.ts, pnpm-workspace.yaml.
• Architectural patterns: layered separation (UI components → pages → API routes → service/utils → data layer).
• Key technologies surfaced by file names: Drizzle ORM (db.ts, schema.ts), Supabase (supabase.ts, storage policies), Clerk auth routes, React Hook Form + Zod (validation), Tailwind CSS, Radix UI.
README for additional insights
• Client Layer (Next.js pages + React components)
• API Layer (Next.js serverless routes under /api)
• Service Layer (Supabase client, file storage, business logic in lib/)
• Data Layer (PostgreSQL via Drizzle ORM + Supabase Storage)
• It specifies core features (Faculty CRUD, Content CRUD, Form Builder, Authentication via Clerk, Real-time data with React Query).