jettburns14 / contest-judging-tool Goto Github PK

Describe the feature you'd like

Sass is a CSS preprocessor that is very powerful and would make our stylesheets a lot more straightforward and structurally organized.
https://sass-lang.com/

Is your feature request related to a problem? Please describe.

Sometimes it's hard finding where to add a new style rule and if the rule already exists or if I might overwrite something. Our CSS has always been kinda messy, SASS would clean it all up and keep it clean.

Describe your idea

Instead of changing "tabs" on /admin, make each one its own view.

How would your idea improve the project or user experience?

• Prevents having to load a lot of data at once with /api/admin/stats, and could cut up that endpoint into a few new ones.
• Would split up bigger admin files like public/js/admin.js into separate smaller ones.
• Would generally be a better way of doing things, allowing each part of /admin to scale independently.

A few modules on the Admin Dashboard page and Entries page don't show the right data. Adjust a few queries to get correct data.

A few simple middleware functions would work fine, using the "express-validator" Node package.

When in Admin -> Contests, the thumbnails can be too big. Add a min-width or height so this is fixed.

Describe the feature you'd like

Right now a JSON "Not found" message object is sent back for nonexistent pages. A creative and fun 404 page would be nice to have.

Is your feature request related to a problem? Please describe.

A cryptic JSON message is sent back, instead of a page.

Additional context

Describe the feature you'd like

Build a custom calendar into our tool, so we don't have to use an external one. It would probably incorporate tasks and display them on their respective due dates. Allow events to be created. Possibly have email alerts for events or reminders. It would have its own dedicated view.

The design would be simple, nice colors used for distinguishing events, and fit nicely on the screen.

If we had to, an iframe with our Google calendar embedded could work, but where's the fun in that?

Is your feature request related to a problem? Please describe.

I don't use Google products, so can't access our calendar and keep updated with our schedule.

It's silly to do these things by hand, so automate it. Make sure it never fails though!

Describe the feature you'd like
Standard users could view the evaluations they submitted for all past contests, and edit evaluations for the active contest only. This allows users to see how they scored a previously judged entry, which would be useful to know while judging similar entries.

Admins could view, edit, and delete all evaluations submitted by all users.

Is your feature request related to a problem? Please describe.
If a user accidentally submits an evaluation before they are done with it, there is no way for them to re-evaluate the entry unless the evaluation is manually deleted from the database.

Describe the feature you'd like

The analytics could cover things like page views per day, week, month; how many logged in versus logged out users viewed pages; how many unique visitors do we get; etc....

This would probably be useful at a later time if/when more people know about the tool.

Because these stats could become quite extensive, creating another Heroku DB could be necessary.

https://github.com/JettBurns14/Contest-judging-tool/pull/11/files?file-filters%5B%5D=.ejs&file-filters%5B%5D=.js#diff-b4242b7beeb9a5e790a6735567c016d0R278

Describe the bug
Editing an existing announcement or creating a new announcement does not hide the tasks modal on the home page.

To Reproduce
Steps to reproduce the behavior:

1. Go to the home page.
2. Click "New Announcement"

Expected behavior
When the form for editing an announcement appears, all other sections on the page should be hidden.

Screenshots

Desktop (if applicable, please complete the following information):

• OS: MacOS
• Browser Chrome

Describe the feature you'd like

Would be nice to have. Click on a column header, like "ID", "title", "author", etc, to rearrange the table according to that selected header. Code would need to be resilient and work for many cases.

The edit message button now opens the edit form, but clicking "Save" throws an error: "There was a problem editing this message".

Creating new messages does the same thing.

Describe the feature you'd like

Is the "date" field on the new announcement form necessary? If the field stands for a message creation date, couldn't that field just be filled automatically during the database INSERT?

Is your feature request related to a problem? Please describe.

Having this field slows me down during development, when I have to input a valid date, when it may not be a necessary feature.

Additional context

I closed #11 due to complicated Git conflicts, so I'm applying Evan's changes to a new branch and merging that in instead.

Describe the feature you'd like
Currently, we have to enter all dates manually. It would be nice to have a date picker widget to easily view a calendar and select a date for all date fields.

KA is removing their public API, including the "/api/v1/user" endpoint, which I use to get a user's KA data during the login/signup process. Obviously my process will break once KA removes the endpoint, so I need to look into an alternative way of getting user data, perhaps with their internal API.

I'm using KA OAuth for the auth process because it's the best way to know a user is who they say they are on KA, because they must be logged into their KA account. Any alternative method, if it comes to that, will require this level of certainty.

• https://github.com/Khan/khan-api/wiki/Khan-Academy-API
• https://github.com/Khan/khan-api/wiki/Khan-Academy-API-Authentication

Sometimes an entry was hidden or deleted after we added its ID to the database, and therefore can't display in the judging page iframe, halting further judging until it's removed from the DB.

Add a skip button to /judging that lets the judge move on to a new entry.

Have all our tool's pages public, which don't send the server any requests unless users have a special web token. This way the entire tool is public, without danger of user interference.