How roshaneleshaddai/rdconclave works
Project type and purpose
• This is a full-stack web application built on Next.js (React + Node.js).
• It delivers a static/dynamic site for a conference or event platform (pages like “hackathon”, “schedule”, “speakers”, “registrations”), plus serverless API endpoints for user registration and retrieval.
• Uses file-system routing (“app/…”), Server Components and Client Components, SSR/SSG, and Tailwind CSS for styling.
File structure
• Top-level “app” directory holds the UI and API routes:
– app/page.jsx and other route folders (hackathon/, meet/, etc.) → React pages served by Next.js.
– app/components/ → reusable header, footer, startpage components.
– app/api/register/route.js and app/api/registrations/route.js → Next.js Route Handlers (serverless functions).
• “public” directory contains static assets (images, PDFs, templates).
• “.next” directory is the build output (SSR bundles, static HTML, client JS chunks).
• Config files: next.config.mjs, jsconfig.json, tailwind.config.js, postcss.config.* for routing, TypeScript support, CSS/styling pipeline.
README for additional insights
• Standard create-next-app with next/font optimization.
• No explicit database driver in the tree; API handlers likely interact with an external database or service (to be drawn as a component).