The visible feature was only the surface
Students and guardians need familiar routes to notices, routines, results, and admission information. A school-site prototype can explore that navigation and content organization before introducing a live content service.
The system also had to respect concrete constraints. Public pages use repository-local sample content rather than a connected school database. Admin login uses client-side in-memory state and does not establish server-side authentication or authorization. The teacher admin route is a placeholder, and forms should not be assumed to persist submissions. No integration with the separate school-management backend was verified.
My role covered frontend information architecture and react interface development, with responsibility for next.js routes, reusable school-content components, responsive navigation, and a demonstration admin area.
I turned the constraints into boundaries
A responsive Next.js school website prototype for notices, admissions, routines, results, downloads, staff, and galleries, using local sample content and a demonstration admin interface.
Bundled content makes the public information structure inspectable without depending on a live database or content-management service.
The portfolio describes the in-memory login and placeholder management routes as interface exploration rather than completed school administration.
Reusable cards and navigation support several types of school information without requiring a separate layout implementation for every page.
The key decision: Prototype navigation with local content.
The implementation had to prove the model
I delivered the work across the full path: Composed school information into dedicated Next.js pages and reusable React components. Added responsive navigation, document views, gallery presentation, and an admin interface demonstration. Kept public demonstration content in repository-local data and static assets.
The result is concrete: The source provides a multi-page school information prototype with clear public-resource navigation. The work demonstrates frontend composition; it does not establish persisted administration or a connected full-stack school system. Bundled content allows the public interface to be explored without configuring a school database.
The senior engineering lesson was that solving the visible workflow is only half the job. The architecture must also make constraints, failure modes, evidence, and ownership explicit enough for the next change to remain safe.