How kvj-harsha/prcouncil works
Project Type and Purpose
• This is a full-stack, content-driven web application built with Next.js (React) on the frontend and Firebase services (Authentication, Firestore/Realtime Database, Hosting) on the backend.
• Purpose: public-facing site for IIIT Raichur’s PR Council events, feedback, photo galleries, and admin interfaces.
File Structure
• Top-level “app” directory uses Next.js App Router; subdivided into:
– app/page.tsx (public home page)
– app/events, app/feedback, app/members, etc. (public routes)
– app/admin/ (protected admin console pages for events, feedback, deletion)
– app/components/ (shared UI pieces and PrivateRoute guard)
• lib/firebase.js holds Firebase config and SDK initialization.
• Config files: next.config.ts, tailwind.config.ts, postcss.config.mjs, tsconfig.json.
• Deployment likely on Vercel (via Next.js) and Firebase hosting services.
README for Insights
• Confirms tech stack: Next.js + Tailwind CSS; Firebase for auth, database, hosting.
• Features: event galleries, deletion requests, feedback forms, team members page.
Main Components & Their Relationships (to include)
a. Client Browser (Mobile/Desktop)
b. CDN / Vercel Hosting (Next.js Static + Server-side Rendering)
c. Next.js Frontend
• Public Pages (home, events, feedback, members)
• Admin Pages (add-event, deletion, events list, feedback list)
• Shared UI Components (Navbar, Footer, Hero, PrivateRoute)
d. Firebase Services
• Authentication (Sign-in/Sign-up, PrivateRoute guard)
• Firestore / Realtime Database (events data, feedback entries, deletion requests, team members)
• Storage (public/photos galleries)
• Hosting (optional if used in addition to Vercel or for static assets)
e. External Integrations
• Social Media Links (YouTube, LinkedIn, Twitter, Facebook, Email)
Architectural Patterns & Principles
• Component-Based Design: reusable React components under app/components.
• App Router (Next.js): file-based routing for public vs. admin areas.
• Protected Routes: PrivateRoute ensures only authenticated admins can access admin subpages.
• Server-Side Rendering (SSR) / Static-Site Generation (SSG): ensure SEO and performance.
• Utility-First CSS (Tailwind) for styling.