How meet41/aidsscet works
Project type and purpose
• This is a full-stack, content-management web application built as a single-page app (SPA) with React (Create React App), supplemented by two back-end layers:
a. A Node.js/Express server (in /server) for REST-style endpoints or SSR.
b. Firebase Cloud Functions (in /functions) to expose serverless APIs, hooks, and Firestore triggers.
• The app serves as an administrative portal (adding/editing sections such as About, Academics, Athletics, T&P, Library, Alumni, etc.) backed by Firebase services (Auth, Firestore, Storage).
File structure
• Top-level directories:
• public/ – static assets + PWA manifest, index.html
• src/ – React components, API client (api.js), auth module (src/auth), routing (PrivateRoute)
• server/ – custom Node.js/Express server code + package.json
• functions/ – Firebase Cloud Functions (HTTP functions, triggers) + ESLint config
• firebase.json / .firebaserc – Firebase Hosting & Functions deployment config
• Patterns & roles:
• React SPA (component-based UI, client routing)
• “src/api.js” likely routes client calls to either /api (Express) or /functions
• Auth flows in src/auth (Firebase Authentication)
• CRUD and file operations via Cloud Functions + Firestore + Firebase Storage
• Deployment scripts in root/package.json orchestrate build → hosting and function deployments.
README
• Bootstrapped with Create React App.
• Only standard CRA scripts described (start, test, build, eject).