Ayyubi Public School - Website & School Management System

Ayyubi Public School in Kushinagar, Uttar Pradesh runs classes 1 to 12 for more than 500 students with a faculty of 30. Everything that touched a parent - enquiries, admission forms, notices, fee questions - arrived by phone or in person, and lived on paper in the office.

They needed two things at once: a public website that made the school look like the institution it is, and an admin system behind it that the office staff could actually run without training.

What was built

The public site

• Home, About and Principal's Message - the school's story, its three pillars of Ilm, Tarbiyat and Akhlaq, and the academic partnership with Career Point, Kota
• Classes - what is taught from class 1 through 12, including Quranic studies alongside the standard curriculum
• Teachers - a faculty directory the office updates itself, no developer needed
• Facilities - computer and science labs, library, masjid and transport
• Admission - an online application form that replaces the queue at the office counter, with the session clearly marked so parents know it is current
• Notices - a noticeboard the school publishes to directly, so announcements reach parents the same day
• Gallery - photographs from school events, uploaded and ordered from the admin side
• Contact - address, phone and enquiry form, with every enquiry landing in the admin inbox rather than a personal WhatsApp

The admin portal

This is the half nobody sees and the half that decides whether a school website survives its first year. Office staff sign in and manage the whole site themselves:

• Admission enquiries - every application in one list, marked read or handled, searchable when a parent calls back
• Notices - publish, edit, and take down, with dates handled automatically
• Faculty records - add a teacher, upload a photograph, set the display order
• Gallery management - bulk upload, with images resized and re-encoded on the way in so a phone photograph does not slow the page down
• Class and section records - the structure the rest of the site reads from
• Role-based access - the principal, the office and the content editor each see only what they need

How it is built

• ASP.NET Core backend, exposing a clean REST API rather than server-rendered pages, so the site and any future app share one source of truth
• Entity Framework Core with SQL Server for admissions, staff, notices and gallery records
• Next.js front end - server-rendered for search engines, with pages cached and revalidated on a timer so the site stays fast without a redeploy every time a notice goes up
• JWT authentication with role-based authorisation on the admin portal
• Image pipeline that resizes and converts uploads to WebP automatically, because the people uploading are teachers with phone cameras, not designers
• Mobile-first throughout - almost every parent visiting this site is on a phone, often on a slow connection

The part that mattered most

A school website is easy to build and easy to abandon. The ones that die are the ones where every change needs the developer. So the brief was inverted: the admin portal was designed first, around what the office staff already do each day, and the public site was built to render whatever they put into it.

The result is a site the school runs on its own - notices go up the day they are written, admission enquiries arrive in one place instead of three phones, and the gallery grows after every event without anyone sending me a file.