Madarij
Education platform
Product development
A school platform bringing academic records, teams, and families into workspaces shaped around their roles.
The English homepage of the local Madarij website preview.
01 / The idea
A whole school, finally connected.
Madarij connects school teams and families around academics, communication, administration, and transport. The bilingual website introduces the product, while a separate school application provides role-scoped workspaces and persistent school records.
School information passes between people with very different responsibilities. A teacher, an administrator, and a parent need access to different parts of the same student journey. Madarij needed both a clear explanation of that product and an application that respects those boundaries.
My contribution
Product design and development across the public website and school application, with attention to clear information, school roles, and modular software architecture.
Built with
- Astro
- GSAP
- Rust
- Leptos
- Axum
- PostgreSQL
02 / The process
How I built it.
Give the website and application distinct jobs
I built the bilingual French and English website in Astro, using illustrated feature chapters and audience pages to explain the platform. GSAP adds restrained motion where it helps the presentation. The school application is separate, so the public explanation and the day-to-day workspace can evolve around their own needs.
Build around school roles and records
The application uses Rust and Leptos, an Axum API, and PostgreSQL. School-scoped workspaces connect classes, student records, attendance, homework, and assessments. Teachers work with their assigned classes; family views are linked to the appropriate children. The interface includes loading, empty, validation, and session-expiry states.
Keep permissions close to the data
Request-level authorization and PostgreSQL row-level security enforce school boundaries. Version checks help detect conflicting edits, and audited changes record administrative actions. Integration tests exercise cross-school access and class permissions with the restricted database role used by the application, rather than relying only on hidden interface controls.
03 / The result
What it brings together.
The project brings a public product story and persistent school workflows into one coherent direction. Academics, family access, accounting, and transport form the product scope; local demonstrations use fictional records. Production rollout and commercial operations remain separate release work.
- A bilingual French and English product website
- Dedicated journeys for school teams and families
- School workspaces with scoped roles and records