FRONTEND DEPLOY BACKEND DEPLOY

Requirements for the Project (Rubric)

Create a Node/Express application from scratch using the MongoDB database. It must contain the following elements:

Models & Controllers

• At least two Mongoose data models. One of these must be a User data model, as you need to implement logon.
• Implement user registration and logon. A full stack project, authentication must use JWT tokens.
• Model attributes should use several different data types (number, string, boolean, date, array etc.).
• Include validation of your attributes to prevent the creation of invalid records.
• For any models beside the User model, implement all the CRUD (create, read, update, delete) operations in your controllers and routes.
• Bonus: implement some non-CRUD operations (like searching, sorting, paging, etc.).
• Implement access control middleware so that at least the create/update/delete operations require authentication. You can have unauthenticated read operations if it makes sense in your application.
• Implement access control logic in your controllers, so that one user can’t access another user’s data. This logic must be present for every controller operation or your application is not secure.
• Include appropriate notifications to the user. For full stack applications, the messages should be returned as needed with the API. (For some APIs, the HTTP status code suffices.) Then the front end displays the message or messages to the user. For server side rendered applications, you need to store the message in the user session, perhaps using the connect-flash NPM package.
• Implement error handling middleware so that all exceptions and error conditions are handled and so that the user gets user friendly messages for each event.
• Use best practices in the organization of application code and in indentation. You may want to use eslint and prettier to make sure your code complies.

User Interface The user interface is the front end for full stack applications, or the EJS views for server side rendered applications. In either case, the UI should have these capabilities:

• Registration, logon, and logoff are supported.
• All CRUD operations for each of the data models besided the User model are supported.
• Links or buttons should be provided to help the users navigate the application.
• Style your application. Again, this is not the focus, so keep it simple until you have done everything else.
• Deployment FRONTEND DEPLOY
• Include security protections for your application. Include security packages like xss-clean and helmet, appropriately configured.
• Deploy the application to Render.com. DEPLOY BACKEND

Bonus Items (these are entirely optional)

• Do something extra:

• more complicated data model
• additional NPM packages
• callouts to other public APIs - cloudinary

• Implement some test cases using Mocha, Chai, and Puppeteer.
• For full stack applications, implement Swagger to document the API.