Hello WebDevs, it’s been a while that I started this project and I’ve been on and off of the project for the last two weeks. I got off in a very bad momentum but I am slowly doing the project as planned. I alread started coding and I am creating the administration panel template for the project. The screens will be patterned to the template and the body will be the only one changing from time to time or when the user switch pages.
I wanted to have a screenshot of the work so far but it seems there is nothing much to show, but I will share on this blog soon. So far the pages that were created were the template and some forms or will be the entry points of the date needed on the web application.
Exciting times! Probably June will be the best month to launch the initial version. This is for educational purposes for those starting off with PHP. Then we will improve the system as we go along and start another system with different approach, probably with a framework or we start on the bootstrap.
If you are starting off in PHP, maybe you put your views or requests on the comment section.
So it started, the design phase is now on. I started already for the teacher panel and something with the administration panel. It is still a bit bare, I am still putting the contents that make sense. My design skills are still in the hibernation mode so, the detail is a bit off I am hoping to create the body out of it, the whole panel is still out of sync.
As it was defined previously, it will be as simple as a school project. But of course the synchronicity of the contents should be as tight as a drum. It should work as one and look as one. Like any other system the contents should be organized as the data could come from any direction and it is always subject for corrections.
The teacher’s access will have basic panels, the dashboard will have a filter according to the level he/she is handling. It will have so called ‘cards’, that will be grouped by level. The cards will have the number of students on that level and section if there are several. It will also contain the teacher’s schedule id and the status of the grades. The status should be released in every quarter. On that note, there should be no corrections done or it will be requested to admin that will have adjustments on the grades.
Watch out for my next post so I can write about the admin panel.
What to design first? Yes, you read it right, I will be starting to design the admin panel first so the workflow will be the backend first before the frontend, which includes the inquiry forms and login for the students. Why backend to frontend? The reason behind is that the backend will all have the information needed in the frontend. The static pages for the frontend will be less headache than the information or data flow we need in the backend.
We will going to have a login for the administrators (school principals, director) and for the department heads and teachers. If you would picture a school set up this will be a medium size private organization. Basically the teachers can input grades for that day then the initial average will be computed but still the whole grading sheet will be subject for revision so it will have an open status until the teacher will finalize it for that quarter. The administrators can arrange schedules and assign teachers for a grade level. They can also adjust percentages for the composition of the final grades and fees needed per grade level.
The Administrator panel should have the controls to adjust or approve any pending items needed for school management.
The set-up should be minimal but rich with process that will be needed for learning experience. Having this set-up this should cover the school management needs.
Let’s start designing then.