I worked on the migration database integrity constraints

[orajiakuchibuchi]

Before my contribution, I realized the system was working fine but there were no foreign key integrity constraints in the database design.
I worked on the migration schemas, adding the foreign key integrity constraints. I also rearranged the order of the migrations.
This provides a better database relationship and schema structure.
Test run on a new database.
After running the php artisan migrate command,
Go to http://localhost/phpmyadmin
Click the database > Database designer

Below are screenshots of the old and new database design view

[orajiakuchibuchi]

I worked on the master dashboard as well. adding the side menu, and dashboard card. new cards for the following: total number of schools, admins, teachers, and students. Added the side menu

[changeweb]

@orajiakuchibuchi Great work! I didn't add foreign key constraint because in some cases, we need to delete a row from a table but it could not be deleted just because of foreign key constrained was integrated.

If you can add some Tests which test of delete actions without being affected by foreign key, I would be confident enough to merge the PR.

[olakehinde]

@orajiakuchibuchi You should add the onDelete('cascade'); to the foreign ket declaration in all your migration files so that as @changeweb has indicated, when a model entity is deleted, all the child models/relationships associated with it can also be deleted.
For example:
$table->foreign('school_id')->references('id')->on('schools');
becomes
$table->foreign('school_id')->references('id')->on('schools')->onDelete('cascade');