How neslang-05/zenith works
Project type and purpose
• This is a full-stack, role-based web application built with Next.js (App Router) that serves three user groups—administrators, faculty, and students—for managing and viewing academic results.
• The README confirms it’s a “Result Management System” called Zenith, using Firebase Auth, Firestore, and serverless functions for CSV import, PDF generation, and email notifications.
File structure
• Top-level “app” directory: Next.js v13 App Router with nested folders for “admin,” “faculty,” “student,” plus shared pages like “login,” “signup,” “privacy,” etc.
• “components” & “components/ui”: Custom React components and a UI library (buttons, tables, dialogs, etc.).
• “hooks”: Custom React hooks (use-mobile, use-toast).
• “lib”: Core business logic and integration helpers—Firebase config (firebase.ts), auth utilities, emailActions, CSV parsing, PDF generator, generic utils.
• Configuration files: next.config.mjs, tailwind.config.js, tsconfig.json, PostCSS config.
• Public assets: Static avatars under “public.”
README for additional insights
• Tech stack: Next.js + Tailwind CSS on the frontend; Firebase Auth, Firestore, and Firebase Functions on the backend.
• Database design: Firestore collections for Users, Results, Classes, Analytics.