Architect & Developer
Opti-campus University
The campus, from admissions through to deliberations.
01
The need
A campus isn't told on a single page. It is crossed: an application, a file, classes, then deliberation. If the path breaks in the middle, no one finds their way.
The rectorate has to follow. Students have to know where they stand. The two can't live in tools that ignore each other.
02
What the product carries
The whole path, from admissions through to deliberations. Not a brochure of the campus. The place where a file moves forward, where a decision lands, and where each person finds their seat.
At this scale, clarity matters more than the number of screens. A role should see what concerns it, without walking through everyone else's system.
03
How I set it down
The same demand as the school, at another measure. React in front, Django behind. The architecture has to hold when cohorts, roles, and deliberations multiply.
I drew the system so it would still read in six months, not so it would impress on demo day. The rectorate and the students had to find their way without a manual.
04
Where it stands
The project is in production. The rectorate and the students find their way. The campus has a path, from the first file through to deliberation.
We needed a campus that would hold, from admissions through to deliberations. Pierre set it up. The rectorate and the students find their way.