Wano University
Campus platform with its own mini-language
A campus platform for booking rooms, parking and meals, with live sensor dashboards and a system-specific language. Built by a team of five with React, Express and PostgreSQL.
- Year
- 2026
- Kind
- Web
- Role
- Team of five: led the web app, project setup, code review
- Stack
- Figma Prototyping
- React Client
- Express.js API
- Prisma ORM
- PostgreSQL Database
- PLY Parser
- FastAPI API
The brief
Wano University is a campus management platform. Students and teachers book rooms, labs and equipment, find a free parking spot, bike or scooter, and buy cafeteria meals. Staff validate tickets and access to rooms. Admins manage users, permissions and the campus sensors, with dashboards and alerts for temperature, energy use and air quality.
It was one project for three second-year modules at once: Software Engineering, Web Technologies Lab and Compilers, which asked for a small command language for the platform, the LSS. We were a team of five.
I led the web app. I set up the project, taught the team React, Express and Prisma, and reviewed every pull request they opened. Along the way I worked on nearly every layer, from the database and the API to the interface and the LSS.
How it's built
It started in Figma. Before any code, we did the user research (two personas, a student and an admin) and a clickable prototype of the app's screens, and the student side and the staff side ended up as two different interfaces. The app was built from those screens.
The frontend is a React single-page app built with Vite, with React Router, Tailwind and shadcn components. It talks to an Express API, which reads and writes a PostgreSQL database through Prisma. Passwords are hashed with bcrypt. Logging in returns a JSON Web Token, and a middleware checks it and the user's role (student, teacher, staff or admin) on every protected route. I'd always used sessions before, so JWT was new to me.
The campus maps are Leaflet drawn over a floor plan image, and admins click a spot on the plan to register a room, sensor or parking space there. Leaflet was probably the trickiest thing to learn. The dashboards use Chart.js and refresh on their own with SWR, which refetches on a timer and when you come back to the tab. There's no real hardware, so the sensor readings are random numbers.
The LSS lives in a terminal popup you can open from any page once you're logged in. A command like rent lab: 4, 09:00, 11:00, 15/06/2026 goes to a small Python service (FastAPI), where a PLY lexer and parser read it and call the same Express API with your token, so the terminal can't do anything your role can't. It has variables and takes keywords in English or Portuguese.
The frontend is on Vercel, the backend on Render and the database on Neon. Render's free plan puts the server to sleep when nobody's using it, so the live demo takes a minute or two to wake up. That's also why we never hosted the language service: it only runs locally.
- 01Figma Prototyping
The user research and the clickable prototype the app was built from.
- 02React Client
The app: pages for each role, the maps, the dashboards and the terminal popup.
- 03Express.js API
The API: login, roles, reservations, payments and tickets.
- 04Prisma ORM
Turns database rows into JavaScript objects (and back).
- 05PostgreSQL Database
Where everything is stored.
- 06PLY Parser
Lexer and parser for the LSS, the platform's command language.
- 07FastAPI API
The small Python service that runs LSS commands against the Express API.
Beyond the brief
The requirements didn't ask for payments, but I wanted to try them, so the app got a cafeteria. You see the menu and buy meal tickets with Stripe in test mode, which fakes payments with test card numbers. Each ticket is a QR code that staff scan with their phone to validate it, and reservations work the same way at the door of a room.
The app is also a PWA, so it installs on a phone like a normal app, and it has Portuguese and English and custom colour themes. Payments, the QR codes and the PWA were my ideas; the interactive maps came out of the Figma prototypes.
Looking back
Most of what I used here I learned for this project: JWT, QR codes, payments, and wiring a Python service to an Express API. Time management was difficult, as Wano was built in the same month as Forsaken Elegy, with exams on top.
If I did it again, I'd give every part of the work a deadline from the first week, so less of it piles up at the end. There are no plans to continue it.