lemonade512 / bluebonnetspointsapp Goto Github PK

In case the quota ever runs out, there should be a nice page with a user-friendly notification. For more information see the appengine docs.

The current flow for new users is to sign in with a google account and create a profile. The officers would like to first approve all new users before those users have been fully created.

It seems awkward to have the table inside the form even though it isn't really a part of the form. Perhaps we should move the table outside the form, but we will need to make sure it still looks good.

In case someone messes up, I would like the ability to bring back point records, events, or other objects that have been deleted by the users. I think the best way to do this is to add a deleted property to all objects that could then be manually changed if something goes wrong.

I think it would be easier for officers to change member information from the members page rather than going to each individual profile page.

Currently, there are no automated tests for the frontend code. I would like a framework to make sure code changes don't mess up the user experience.

Two events with different case ("Monday Fun Run" or "mOndaY fun rUn") are treated differently. I would like to remove this case sensitivity as I think it could be confusing to users to have two events with the same name treated differently.

Currently, members can be "active" or "inactive". New members start out as "babies" and have different point requirements. Therefore, we need to add a third option to member status that reflects this. Most likely this will involve changing the active boolean field in the UserData model.

A fixed-table layout would allow having a consistent width for each column in the point reductions table.

I have yet to look at the website on firefox or safari. I would like to make sure the everything is the same on these browsers as on Chrome.

Users want to know what events contribute to their points. One option is to add a pop-up bubble that comes up when users hover over their points in the progress bars on their dashboards.

This looks like a nice flask extension for handling HTML forms. It might be good to transition to using this but I haven't looked into it enough to know what all it can be used for.

When a user inputs anything from a date to a name, the input should be verified for correctness. At some point we need to go through all the forms to make sure all user input is verified and properly handled.

My CSS skills are lacking, so a lot of my CSS needs to be rewritten to be maintainable.

At one point in time I was told members could earn points by logging study hours. If this is still the case they may want a form that members can fill out with their hours and what they studied. These forms could then be approved by officers.