Bold Admin is a production-ready School Management System for a single school's administrative and teaching staff. It gives the school one ordered, trustworthy place to hold its core records — students, teachers, grades, subjects and classes — and gives the administrator a dedicated panel to keep those records correct and complete. Teachers use the same records for their daily teaching work: reviewing who is in their classes, which subjects are taught, and how students are performing, and entering marks for their students. Teacher-entered marks are held as Pending Admin Approval and become visible to students and parents only after the administrator approves them. The system also includes an Attendance Management module for recording and reviewing daily student attendance, and a Fee Management module for recording each student's fee obligations and payments. A Parent Portal lets parents view their own child's attendance and approved grades and download a grade report card, subject to a fee-clearance business rule.
The product is delivered as a Python Flask backend, a ReactJS frontend, a PostgreSQL database, and Docker-based deployment. It is intended for three active human roles: the School Administrator, who owns record accuracy; the Teacher, who reads the records to plan and track teaching; and the Parent, who reads their own child's attendance and grades. Access to school records is protected: the administrator self-enrolls, and the administrator, teachers and parents verify their identity before reaching protected surfaces.
The audience is a school office, its teaching staff and the school's parents. The tone is clear and correct but warm and optimistic — a records tool people are happy to open every day.
Bold Admin is a web application with three runnable services: a shared backend process exposing the application APIs and domain modules, a database holding application-owned persistent data, and a frontend React application serving the user interface. The backend is the single shared process for all feature APIs; the frontend talks only to that backend, and the backend is the only service that talks to the database.
The current delivery covers:
Three active human roles use the system: the School Administrator (full record management, grade approval, plus the teacher list, fee list and admin panel), the Teacher (read access to students, grades, subjects, classes and attendance for daily teaching work, plus entering marks that stay pending until approved), and the Parent (read access to their own child's attendance and approved grades, plus a conditional grade report card download). Identity is application-owned: the administrator self-enrolls through Sign Up, and all three roles sign in through Login. The teacher list, the fee list, the admin panel and the Parent Portal are restricted to their respective roles; the student, grade, subject, class and attendance lists require a signed-in session.
Narrow exclusions: the system does not include timetable scheduling, a student portal, messaging, online payment gateway processing, or any capability beyond the nine named destinations and the identity surfaces required to reach them. Grade report cards are generated inside the application for the Parent Portal only; they are not a general report-card generation capability for the administrator or teacher.
Removed from scope
Added to scope
Bold Admin is delivered entirely as a first-party application. The Flask backend owns all school-record data, all attendance data, all fee data and all identity state; the ReactJS frontend renders every surface; PostgreSQL persists everything; Docker packages and runs the three services together. There is no provider-owned or external surface in the current delivery — every page a person sees is built and owned by this application. Fee records are maintained inside the application; no external payment provider is integrated. Grade report cards are composed by the backend from the application's own grade, student and fee records and delivered as a download from the Parent Portal.
Access is split into two boundaries. The anonymous boundary covers Landing, Login and Sign Up: these are reachable without a session and are where a person first meets the product and establishes identity. The protected boundary covers the seven record lists, the admin panel and the Parent Portal: these require a signed-in session, and the teacher list, fee list and admin panel additionally require the administrator role, while the Parent Portal requires the parent role and shows only the signed-in parent's own child. A protected destination never establishes access to itself; identity is always established at Login or Sign Up first.
The fee-clearance business rule is enforced by the backend, not only in the frontend: when a student has any school fee that has been pending for more than 60 days, the grade report card download for that student is blocked and the Parent Portal shows the reason inline. The rule gates the report card download only; it does not block the parent's view of attendance or grades.
Everything described in this document is current. No future-horizon capabilities are committed; the exclusions listed above are deliberate boundaries, not deferred work.
FR-1 — Production-ready School Management System (explicit) As a School Administrator I should have a production-ready School Management System so that my school's records are held in one dependable place.
FR-2 — Python Flask backend (explicit) As a School Administrator I should have the system's APIs served by a Python Flask backend so that all record operations run through one consistent service.
FR-3 — ReactJS frontend (explicit) As a School Administrator and Teacher I should use a ReactJS frontend so that every list and the admin panel are responsive and consistent.
FR-4 — PostgreSQL database (explicit) As a School Administrator I should have all school records persisted in PostgreSQL so that data survives restarts and is consistent across sessions.
FR-5 — Docker deployment (explicit) As a School Administrator I should have the system deployed with Docker so that backend, frontend and database run together reproducibly.
FR-6 — Student list (explicit) As a School Administrator I should see and manage the student list so that student records are correct and complete. As a Teacher I should see the student list so that I know who is in my classes.
FR-7 — Teacher list (explicit) As a School Administrator I should see and manage the teacher list so that teacher records are correct and complete.
FR-8 — Grade list (explicit) As a School Administrator I should see and manage the grade list so that student results are recorded accurately. As a Teacher I should see the grade list so that I can track student results.
FR-9 — Subject list (explicit) As a School Administrator I should see and manage the subject list so that the school's subjects are recorded accurately. As a Teacher I should see the subject list so that I know which subjects are taught.
FR-10 — Class list (explicit) As a School Administrator I should see and manage the class list so that class records are correct and complete. As a Teacher I should see the class list so that I know my classes and their students.
FR-11 — Admin panel (explicit) As a School Administrator I should have an admin panel so that I can manage all school records from one place.
FR-12 — Administrator self-service enrollment (required_inference) As a School Administrator I should be able to create my own account so that I can start using the system without an invitation.
FR-13 — Identity verification before protected records (required_inference) As a School Administrator or Teacher I should verify my identity before reaching protected records so that school data stays private.
FR-14 — Attendance Management module (explicit) As a School Administrator I should record and manage daily student attendance so that the school has an accurate attendance history. As a Teacher I should see the attendance list so that I know which students were present or absent.
FR-15 — Fee Management module (explicit) As a School Administrator I should record and manage student fee obligations and payments so that the school knows what each student owes and has paid.
FR-16 — Attendance and fee summary on the admin panel (explicit) As a School Administrator I should see attendance and fee summary counts on the admin panel so that I can spot gaps in attendance recording and outstanding fees from one place.
FR-17 — Parent Portal (explicit) As a Parent I should have a Parent Portal so that I can see my own child's attendance and grades without asking the school office.
FR-18 — Grade report card download for parents (explicit) As a Parent I should be able to download my child's grade report card from the Parent Portal so that I have a record of their results.
FR-19 — Fee-clearance business rule for grade report card downloads (explicit) As a School Administrator I should have grade report card downloads blocked when school fees are pending for more than 60 days so that outstanding fees are enforced consistently.
The School Administrator is the person accountable for the accuracy and completeness of the school's records. Their product context is the admin panel and the seven record lists, which together form their working surface. Their primary goal is to keep students, teachers, grades, subjects, classes, attendance and fees correct and current so that the rest of the school can rely on them.
Their distinct responsibilities are the full management lifecycle of every record type — creating, editing and removing students, teachers, grades, subjects, classes, attendance records and fee records — plus sole access to the teacher list, the fee list and the admin panel. They are the only role that self-enrolls through Sign Up, and the only role that can change record state. Their relevant inputs are record details (names, class assignments, subject associations, grade values, contact details, attendance dates and statuses, fee amounts, due dates and payments) and their own account credentials. They interact with teachers indirectly: the records they maintain are the records teachers read. Their observable success is an admin panel whose summary counts match reality, and record lists that render without errors and reflect every change immediately.
What makes this role different is ownership: the administrator is the only participant who writes, and the only participant who sees the teacher list, the fee list and the admin panel.
The Teacher is a member of the school's teaching staff who uses the records for daily teaching work. Their product context is the student list, class list, subject list, grade list and attendance list, which they read to know who is in their classes, which subjects are taught, how students are performing, and who was present or absent. Their primary goal is to have an accurate, current view of their students, their results and their attendance without needing to ask the office.
Their distinct responsibilities are reading and filtering: filtering the student list by class, searching classes and opening a class to see its students, searching subjects, filtering grades by student, subject or class, and filtering attendance by class, student or date. They do not create, edit or remove records, and they do not see the teacher list, the fee list, the admin panel or the Parent Portal. Their relevant inputs are their own account credentials and the filter selections they make. They interact with the School Administrator indirectly: the administrator's record changes are what the teacher reads. Their observable success is a read-only list that loads cleanly, filters correctly, and shows the current state of the school's records.
What makes this role different is read-only scope: the teacher consumes the records the administrator maintains, with no write controls and no access to administrator-only destinations.
The Parent is a guardian of a student at the school who wants to see their own child's attendance and results without contacting the office. Their product context is the Parent Portal, which shows the attendance records and grade records of the child linked to their account, plus a grade report card download. Their primary goal is a current, trustworthy view of their child's attendance and grades, and a report card they can keep.
Their distinct responsibilities are reading their own child's records and requesting the report card download: filtering attendance by date range, filtering grades by subject, and downloading the grade report card when the fee-clearance rule allows it. They never see another student's records, never create, edit or remove any record, and do not see the record lists, the teacher list, the fee list or the admin panel. Their relevant inputs are their own account credentials and the filter selections they make. They interact with the School Administrator indirectly: the administrator's attendance, grade and fee records determine what the parent sees and whether the report card download is available. Their observable success is a Parent Portal that loads cleanly, shows only their child's current attendance and grades, and either downloads the report card or states plainly why it is blocked.
What makes this role different is scoped read-only access plus one conditional action: the parent reads only their own child's records and can download a report card only when no school fee has been pending for more than 60 days.
The visual identity follows the Karim Rashid sensual pop minimalism direction: soft, bright, curved and optimistic, with no flat grey admin tables, no square corners, no blue or indigo buttons, no photographic stock imagery, and no hard shadows or hairline borders.
Mode: light only.
Colour tokens (exact hex by role):
#FFF4F1#FFFFFF#241A2B#FF4FA3#B6F03C#7A6E80Typography:
clamp() so they scale between the mobile and desktop sizes and stay entirely inside the viewport and their container at 375 px, 768 px and 1280 px.Shape language: capsule buttons, blob panels and curved section edges. Corners are fully round; no sharp boxes. Section edges curve with a 64 px radius between the blush ground and white panels.
Spacing rhythm: generous, soft spacing on a 4 px base with 16 / 24 / 32 / 48 / 64 px steps; capsule panels carry generous internal padding so text never touches a curved edge.
Imagery style: glossy 3D blob shapes and simple rounded icons for students, teachers, classes and grades. No photographs.
Accessibility: text and controls remain whole at every viewport; the pink-on-blush and lime-on-white combinations are used only where contrast supports readable text, with #241A2B text on light surfaces and white text on the pink hero.
The public entry is a full-width bubblegum pink hero block with a curved lower edge that fills the first screen. An oversized Comfortaa headline — "Every student record, in one soft place" — sits left at 44 px on mobile rising to 72 px on desktop, with the subline "Bold Admin holds the student, teacher, class, subject and grade lists for your school." beneath it in Quicksand. A large glossy 3D blob cluster sits to the right of the headline, its lime highlight morphing slowly. The lime capsule call to action "Open the panel" pins directly under the headline. Below the curved edge, the blush ground carries a short strip of rounded icon chips naming the record types, each in a white capsule with a pink left rail. The concept recomposes only accepted content and controls: the headline, subline, CTA, Sign Up and Login links, and the record-type summary.
Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d
Landing Hero Motion Brief
prefers-reduced-motion, the blob cluster renders static with its lime highlight fixed, hover bounces are removed, and the record-type chips wrap into rows so every item is fully readable.prefers-reduced-motion, a usable static arrangement is provided.docker-compose.yml).The provisioned service inventory is: backend (shared Flask process for application APIs and domain modules, including the attendance, fee and parent-portal modules), database (PostgreSQL for application-owned persistent data), and frontend (React application UI). The backend is the single shared process for all feature APIs; the attendance and fee modules, the Parent Portal reads and the grade report card download with its fee-clearance check are added as routes and domain modules inside that existing backend process, so no additional services are required for the current scope.

Bold Admin holds the student, teacher, class, subject and grade lists for your school.
Teacher marks stay pending until the administrator approves them, so families only see approved grades.
Seven record lists, all in reach

Bold Admin holds the student, teacher, class, subject and grade lists for your school.
Teacher marks stay pending until the administrator approves them, so families only see approved grades.
Seven record lists, all in reach
No comments yet. Be the first!