The Holistic Educator - front end application

Tracks connections teachers make with students (i.e. a teacher would be able to see who she/he/they has checked in with or not ‘today’).
Informs teachers of the supports needed to fulfill social-emotional needs (key word filters would suggest books or web resources).

This project is near and dear to me as a huge advocate for social-emotional learning in schools. This application is a tool that many teachers who are tracking their connections with students will find helpful to ensure that they are reaching every student.

How does it work?

A teacher signs in, selects the Student Roster tab.
A teacher can index all of her/his/their students to see relevant data about each of her/his/their students.
A teacher can then choose to update or delete an existing student and/or create a new student.

The first step in my planning process was to conduct market research. I asked other teachers about tools they wished to have in the classroom. Most teachers polled said they would like a way to keep track of the students with whom they have had check-ins.
Next, I broke down my application into several versions and focused on the first approachable version, which would require just one resource to which I’d apply CRUD actions - a student roster (including an option for a single note to be added to each student.)
Starting with the back-end API, I routed my user and student resources, wrote curl scripts, and tested their accuracy in the development server.
Upon success using CRUD actions on these resources in the back-end, I moved onto connecting my back-end to a front-end client server, using Handlebars to display the most relevant data for the user to apply CRUD actions through the front-end.

As a teacher, I want to sign in/up
As a teacher, I want to Create a new student in my roster.
As a teacher, I want to Read multiple student names.
As a teacher, I want to Read a single note for a student.
As a teacher, I want to Update a student I own in my roster.
As a teacher, I want to Delete a student I own in my roster.
As a teacher, I want to Create a check-in note for each student.
As a teacher, I want to Read a check-in note for each student.
As a teacher, I want to Read multiple check-in notes for each student.
As a teacher, I want to Update a check-in note for each student.
As a teacher, I want to Delete a check-in note for each student.
As a teacher, I want to see which students have had check-ins (notes added).
As a teacher, I want to see which students have not had check-ins (no notes added).

My problem-solving strategy was to console log everything I assumed I knew about my code to be sure my code represented what I thought it did. I also used breakpoints in Dev Tools to trace functions that were running up to a certain point in my code. In addition, I tried features in other branches before merging them into the master.
Still need to … have success and failure feedback messages not linger too long between user actions.
Would like to eventually …. sort student list alphabetically and add other tabs for other features.

A tab for “check-in status”, for example, would render options for a teacher to “view who I have checked-in with today” and “who I have not checked-in with today”.
Another tab for “suggested resources” would allow a teacher to select a student, which would render a list of suggested social-emotional learning resources.
A final tab for a “user profile” that displays user email and number of students associated with this user.