getprojectsidea/create-school-management-system-with-php-mysql

This repository is a legacy PHP/MySQL school management system built as a server-rendered web app with a custom, framework-free structure. The core app lives under School Management System/, and the database schema is in Database/DemoSMS.sql.

The application is organized into three main runtime layers: view/ for HTML pages, model/ for action and data-access scripts, and controller/ for bootstrap/configuration. This is not a modern API-first split; instead, page scripts typically include shared layout files, read data directly, and post to small PHP handlers for CRUD operations.

The primary entry points are index.php at the project root and view/index.php, with controller/index.php and controller/config.php likely handling initialization and database connection setup. The architecture is centered on PHP page loads rather than a single front controller with a formal router.

Presentation is built from a large set of reusable partials in view/: headers, sidebars, navbar, footer, and role-specific chrome such as header_admin.php, header_teacher.php, header_student.php, and header_parents.php. This indicates the UI is segmented by user role, with different dashboards and menus for each audience.

The model/ directory contains many small purpose-specific endpoints, mostly named by action: add, update, delete, get, approve, confirm, and login. These scripts are the mutation boundary of the system and are the main bridge between forms in view/ and the MySQL database.

The domain modules are the standard school-management set: students, teachers, classes/classrooms, subjects, grades, attendance, exam marks, timetables, events, payments, salary, petty cash, messaging/friends, and leave requests. The volume of my_*, all_*, and show_* pages shows the app exposes both administrative lists and personal “my records” pages for different user roles.

A strong data-flow pattern appears throughout the repo: browser submits a form from a view/*.php page, the matching model/*.php script writes to or updates MySQL, then list/detail pages pull the refreshed data back for display. There are also many get_*.php scripts used for fetching entity records and populating forms or tables.

Analytics and dashboards are supported through charting and reporting assets. The repo vendors Chart.js under Chart.js-master/ and also includes chart-related pages plus AdminLTE dashboard scripts under dist/js/pages/, which suggests graphs are used on the dashboard and summary views.

The frontend stack is mostly static vendor assets: Bootstrap, AdminLTE, jQuery plugins, DataTables, CKEditor, Select2, Datepicker, Daterangepicker, FullCalendar, Morris, Flot, iCheck, and related UI helpers. These are bundled as local dependencies rather than fetched from a CDN, so the app is self-contained and deployable as a traditional PHP site.

File uploads are supported through the uploads/ directory, which is treated as a storage boundary for user-uploaded content. There are also log files like error_log in multiple places, implying the app is meant to run on a conventional PHP web server with filesystem access.

The database layer is MySQL-centric and likely owns all core business state: people records, enrollment, attendance, marks, schedules, finance, and communication data. DemoSMS.sql is the seed/schema artifact that defines the tables the PHP scripts expect.

Overall, this repo is a monolithic, server-rendered CRUD system with role-based screens, many specialized action scripts, and a database-first architecture. When diagramming it, the key boundaries are: browser/UI pages, PHP action handlers, MySQL persistence, static vendor assets, and uploaded files/logs.