How vader4k/pitch works
Project type and purpose
• This is a full-stack Next.js application (folder app) bootstrapped via create-next-app.
• It provides a user interface for listing and creating “startups,” user profile pages, and authentication flows.
• It integrates with NextAuth for authentication, Sanity as a headless CMS for content, and Sentry for error tracing/monitoring.
File structure
• Top-level “app” directory holds Next.js routes in the new App Router style:
• app/layout.tsx, app/page.tsx (global layout + homepage)
• app/(root)/startup/* and app/(root)/user/* dynamic routes for Startups and User pages
• app/api/auth/[...nextauth]/route.ts for NextAuth API route
• app/studio/[[...tool]]/page.tsx for embedding the Sanity Studio in-app
• components/ holds reusable React components and a components/ui/ subfolder with atomic UI building blocks.
• lib/ contains shared utilities, validation, and action handlers.
• hooks/ holds custom React hooks (e.g., use-toast).
• sanity/ directory holds the Sanity schema, client configuration, queries, and type generation.
• Configuration files:
• next.config.ts, tsconfig.json, tailwind.config.ts, postcss.config.mjs
• Sentry configs: sentry.client.config.ts, sentry.server.config.ts, etc.
README for additional insights
• Confirms Next.js App Router use, font optimization, development setup, and suggests deployment on Vercel.
Detailed capture of essential elements
• Shared lib/ and hooks/ modules as utilities accessible from both server and client code.
• Tailwind CSS pipeline (PostCSS → CSS) as part of the build process.
• Where the Sentry SDK is initialized (in instrumentation.ts) and which sentry config file applies to client vs. server.