School site build · 2022
Escuela de Sto. Rosario
A school website with admissions, programmes and two portals — a parent-facing enquiry funnel on a Firebase database, and an admin grid that reads every enquiry back.
- Role
- Front-end, routing and portal UI
- Stack
- ReactReact RouterMaterial UIReact-BootstrapAuth0Firebase Realtime DB
- Live
- react-school-web-app.vercel.app
- Source
- GitHub

01What the build involved
01
A site with two front doors
Parents get the public pages: home, about, the preschool gallery, programmes and admission. Staff get a teacher portal, students get their own. Routes switch through a TransitionGroup fade, and a ScrollToTop component resets the window on every navigation — small things, but without them a long admissions page left you halfway down the next screen with no explanation.
02
Real data, no server of its own
The contact form writes to an inquiry list and the admission form to an enrollee list, both in Firebase’s Realtime Database, called through its plain JSON endpoints rather than the SDK. The teacher portal fetches both lists, turns the objects into rows and shows them in Material UI data grids behind tabs, so the office sees enquiries and enrolments without anyone maintaining a backend.
03
Two kinds of sign-in, one lesson
The teacher portal goes through Auth0 with a redirect back to /teacher-portal. The student portal is a front-end demo: a form that flips a boolean and shows the student dashboard, with no server check behind it. It was fine for a prototype, but an admin screen that can read every family’s enquiry is exactly the wrong place for a demo login — that is the habit I took into later builds, where the session is checked again on every request.
02What it left behind
Outcome
A live school site at react-school-web-app.vercel.app: public admissions pages, an enquiry and admission funnel writing to Firebase, and a teacher portal reading both lists back in data grids — with no server to maintain and no account needed for a parent.
Another pass
The student portal’s front-end-only login is the thing I would remove before calling this finished: an admin view over every family’s enquiry needs a server-side check, so both portals would sit behind Auth0 with one role table. I would also move the Firebase reads behind a small API route, so the dashboard stops knowing the database’s shape.
03Inside the product
Click any screenshot to view it full size