amupitan / notecard-maker Goto Github PK

• Signin page
• Login page
• Store signins/logins in database
• Hash passwords
• Store users' notecards in database

• Add validations for sign up
• Add validations for updating info
• Add validations for uploading notes
• Add validations for login
• Add validations for adding note-cards, creation of note-cards ( #7 ) has be completed first

The documentation in the middle of the page makes it cluttered. By moving it to a new page, it will make it look loads better.

When a user signs in, allow the user to visit their "users" page. This should contain all their previous notecards they have uploaded.

*have an option to delete notecards/decks of notecards.

When the user signs in/logs in, display their name on the upper corner instead of the sign-in and log-in buttons.

• Allow multiple note uploads
• Include form entry for optional meta data
• Display warning that if title is not filled in neither form nor note then a random title is given
• Allow typed notes

Store username if user selects remember me before logging in

As described in #9

This would be a low priority one.

Give option for user to manually type what they want on the front side and what they want on the back side.

However, there are other websites that already do this, so this should not be a priority.

Change all function styles and other data structure styles if any to use ES6 features

When we switch to production, cookie.secure show be set to true and HTTPS should be used

The views/documentation.ejs file retrieves a <%=info%> which comes from routes/documentation.js.

routes/documentation.js reads through data/description.json and generates a string of xml elements. I think this would be neat to say we did for portfolio 3, but now I'm having this little problem.

We could do a workaround, that would consist of creating a partial file (a file that holds snippits of files; purpose is to reduce repeat code and to make the main files smaller) of it and including it.. but that's not that new.

Move information from homepage and other pages to JSON files

Have a page that displays all the notecards the parser created with all of them currently selected. Give the use an option to unclick notecards that they don't want to study at the moment(or if our parser picked up something the user wasn't anticipating)

Create a section that has examples using the correct syntax.

I would think people would rather see examples than read the documentation.

Instead of restricting the user to just uploading a text file, we should have an text box that allows users to copy and paste their notes in. Just in case they have notes in other formats.