How gitpugal/forms works
Project type and purpose
• This is a full-stack web application built with Next.js (app directory uses Next 13’s App Router), React/TypeScript, Prisma, Firebase, NextAuth, and various third-party integrations (Stripe, Google Sheets, Notion, SMTP mail).
• Its domain: a form-builder and form-management platform supporting user auth, workspace/org management, embedded forms, campaign workflows, and integrations.
File structure
• Top-level “app” directory holds both UI pages (React server/client components) and API routes (app/api/**).
• Key sub-directories under app:
• (auth), (dashboard), (campaign), (embed), (onboard), (site) – these group related page routes and layouts.
• app/api/** – Next.js Route Handlers implementing RESTful endpoints for auth, forms, workspaces, invitations, payments, integrations, webhooks, etc.
• “components” directory houses reusable React UI components (including Editor.js form-builder tools).
• “lib” contains core configuration/utilities: Prisma client, Firebase config, queue utilities, auth options.
• “services” wraps calls to Firebase, workspace/form/org logic.
• Prisma schema at schema.prisma drives the relational data model.
• Config files: next.config.mjs, tailwind.config.ts, postcss.config.mjs, tsconfig.json.