How virajmandlik/reportease-portal works
Project type and purpose
• This is a full-stack web application called “Reportease-Portal” composed of:
• A primary Admin/User Portal front-end (React + TypeScript + Vite + Tailwind)
• A static Landing Page site (React + TypeScript + CRA/Vite)
• A Node.js/Express back-end API server with modular PDF/HTML report generation.
• The back-end handles authentication, CRUD over academic data (courses, departments, events, clubs, etc.), Excel/PDF report creation, file uploads, and serves static reports.
File structure
• Top-level directories:
• Backend/ – Express API, controllers, routes, middleware, DB connection, PDF generation module, static report output.
• Frontend/ – Admin portal React app (App.tsx, components, assets, store, UI library).
• LandingPage/ – Marketing site React app (pages, components, assets).
• Backend follows an MVC-style organization: routes → controllers → utils/db layer. PDF generation is factored into a sub-module (pdfGenModule) with its own controllers, queries, views.
• Config and template files: .env-style DB config in dbConnection.js, Excel templates under Backend (e.g., course_template.xlsx), EJS templates in pdfGenModule/views.
README
• Minimal README indicates project name/version but no extra architecture docs. Rely on folder conventions and naming.
Detail
• pdfGenModule as a layered mini-service: Queries → Controllers → Views → Output.
• DB connection object (dbConnection.js) as the bridge to the Data Store.