He likes holding two incompatible ideas in one frame and making both of them convincing, and given more time he always pushes the strange part further — which is how the work worth looking at tends to get made.
Every school runs more clubs than any student can name and keeps no reliable list of them — what exists is a flyer, a rumor, or a teacher who happens to mention it. The team hit this at their own schools, then hit the harder version: a directory students maintain themselves goes stale within a semester. The people who actually know what is running are the district's activities directors, and they had no reason to touch anything built only for students.
Club Connected gives all three their own view of the same directory — student, club leader, activities director — so the people keeping it current are the people who need it accurate.
“We built this as students who couldn't find our own school's clubs — but the real fix has to work for the district too, since it's their activities directors who decide whether every student actually gets access.”
Club Connected, at the showcase
How it was built
Database Management
A real relational schema behind the directory — schools, clubs, memberships, attendance — kept consistent as students join, leave, and check in to meetings.
Project Planning
Three distinct roles, each with its own pages, permissions, and landing screen: student member, club leader, and district activities director.
Front-End Development
The calendar, the match queue, and the leader workspace are all their own code, written by hand with no framework doing the work for them.
ViteBuild Tool
SupabaseBackend & Database
n8nAutomation Platform
Also in the buildFiltered activity discovery · Keyword-based club-fit matching · Role-scoped district access
