Two systems I built at Triglobs, Allegra's music-course booking and the SISTER student information system, turned out to share one pattern: a single source of data and a portal per role.
Allegra Private Music Course and the Bumi Santri Ar-Rumi boarding school look like two different worlds. One schedules lessons at students' homes and in a studio. The other tracks students' attendance, memorization, savings, and fees. But the starting problem was similar: important information was scattered, and every party needed to see a different slice of the same data.
The pattern I used in both projects is one source of data with a portal per role. Allegra has portals for students or parents, teachers, admins, and super admins. SISTER has a guardian portal and a management panel. Data is recorded once; what differs is what each role sees first.
The clearest example is the guardian home screen. It leads with the last 30 days of attendance, memorization progress, outstanding fees, and savings balance, because that is what guardians most want to know. A light mode and larger text are there on purpose, so the screen is easy to read for every age group.
On technology, I chose Laravel, Filament, and Vue.js on cPanel. The decision came from the clients' real constraints, not from trends, for the same reason as in my earlier article on choosing Laravel over Next.js for a cPanel deployment.
The lesson I take away: before building features, ask who opens this system and what they want to see first. The answer shapes the architecture of the portals.