The Student Management System is a website that lets one teacher keep student records in a single, calm place. The teacher records students and manages their student data in one place — viewing the roster, adding a student, and editing or deleting an individual student record.
The product is deliberately scoped to a single teacher. There is no multi-teacher administration, no class scheduling, no grading, and no parent or student portal. The audience is exactly one person: the teacher who owns and maintains the student records.
Because student records are durable and private, the teacher establishes an application-owned identity through self-service enrollment on first use and verifies that identity on return before reaching student records. The public entry explains the product and leads the teacher into that access flow.
The system is delivered as a React web frontend backed by a shared FastAPI backend and a MariaDB database. The frontend presents four destinations: a public Landing page, a Login page for self-service enrollment and returning verification, a Students page listing the roster and adding records, and a Student Details page for editing or deleting one record. Students and Student Details require a verified teacher session; Landing and Login are reachable without one.
The only active human actor is the Teacher. The backend and database are supporting system actors that persist and serve student records; they are not personas and have no independent product goals.
Current accepted behavior is limited to: explaining the product publicly, establishing and verifying the single teacher's identity, listing students, adding a student, and editing or deleting a student record.
Removed from scope
The product is a first-party website owned and operated by the application. All four destinations are custom application pages; no provider surface or external destination carries accepted product behavior.
Access is split into two boundaries. Landing and Login are anonymous entry surfaces: the teacher can read the product explanation and complete self-service enrollment or returning verification without an existing session. Students and Student Details are protected surfaces: they require a verified teacher session because they expose durable, private student records. The Login page is the only place identity is established or verified; a protected page never establishes access to itself.
Identity is application-owned and single-account in effect: the system serves one teacher, so enrollment creates the teacher's account and returning verification confirms it. This is identity continuity for private records, not a differentiated permission system — there are no roles, no shared-state visibility rules, and no administrative tiers.
Everything described in this document is current. No future-horizon capabilities are accepted.
FR-1 — Public product explanation (explicit) As a Teacher, I should see a public Landing page that explains the student management system built for one teacher, so that I understand what the tool does before signing in.
FR-2 — Self-service enrollment (required_inference) As a Teacher, I should create my own account on first use, so that my student records are privately owned and resumable.
FR-3 — Returning identity verification (required_inference) As a Teacher, I should sign in with my email and password, so that I can reach my student records again.
FR-4 — Protected student records (required_inference) As a Teacher, I should be required to verify my identity before viewing or changing student records, so that private student data is not exposed.
FR-5 — View the student roster (required_inference) As a Teacher, I should see my students listed in one place, so that I can review my roster at a glance.
FR-6 — Add a student record (required_inference) As a Teacher, I should add a student record, so that new students are captured in the roster.
FR-7 — Edit a student record (required_inference) As a Teacher, I should edit one student's record, so that their details stay accurate.
FR-8 — Delete a student record (required_inference) As a Teacher, I should delete a student record, so that records I no longer need are removed.
FR-9 — Single-teacher scope (explicit) As a Teacher, I should be the only user of the system, so that the tool stays focused on my own records.
Product context. The Teacher is the sole user of the Student Management System. They run their own classroom records and need one calm, private place to keep student information current. The tool is used for daily admin work, not for institutional reporting.
Primary goal. Keep an accurate, up-to-date roster of students and manage each student's record without friction.
Distinct accepted responsibilities.
Relevant inputs and decisions. The Teacher enters account credentials on first use and on return; enters student fields when adding a record; decides which fields to change when editing; and confirms before deleting.
Interactions with other participants. There are no other human participants. The Teacher interacts only with the application, which persists and serves their records.
Observable success. The Teacher signs in, sees their roster, and can add, edit, or delete a student with the change reflected immediately — all within a warm, uncluttered interface.
The visual language follows the humane-technology direction of Yves Béhar: calm, warm, and safe for daily admin work.
Palette (light mode)
#F7F2EA (carries most of the page)#FFFDF8#2B2E2C#3E5C50 (main action colour)#C4694B (marks one focus item per screen)#8A8578Typography
clamp(40px, 7vw, 88px).Shape language. Soft rounded blocks with 24px radii; capsule buttons; gentle card edges; no sharp corners.
Layout. Single column with wide margins. One hero block, then a calm row of three feature panels. The student list uses soft rows with clear labels.
Imagery. Soft-lit still life of a desk, a notebook, and a plant; warm natural light on plain grounds; no stock people.
Accessibility of text and controls. Headlines, wordmarks, labels, numbers, card text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit; no element covers any part of them. Imagery and decoration may crop or bleed per the direction but never cover readable text or controls.
Avoid. Bootstrap blue buttons on white; gradient blob heroes; sharp 0px corners; grids of identical hover-lift cards; the generic indigo/blue-on-white SaaS template.
The public entry is a split hero on the oat ground. On the left, an oversized two-line headline in Work Sans at clamp(40px, 7vw, 88px) spans nine columns on desktop: "Every student, in one calm place." Beneath it sits a terracotta capsule CTA, "Open the roster", with a 2px inner light edge. On the right, a soft-edged photo panel shows a warm still life of a desk, a notebook, and a plant. Below the hero, a calm row of three feature panels describes the roster, adding a student, and editing or deleting a record. The subline reads "A student management system built for one teacher." The composition recomposes only accepted content and controls; it introduces no new behavior.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: layered_2d
Landing Hero Motion Brief
prefers-reduced-motion, all sections render in their final positions with no fade; the layout remains fully usable and readable.prefers-reduced-motion is set.
Student Management System
A student management system built for one teacher.
Record your students and manage their student data in one place — viewing the roster, adding a student, and editing or deleting a record when it changes.
Every student sits in a calm list, each name in clear type with a label for their class.
Roster
Enter a name and class, add the contact or note you keep, and the record joins the roster right away.
New student
Open any student to update their details, or delete the record with a confirmation step first.
Edit · Delete
No comments yet. Be the first!