Exercise Friday

Independent Projects Overview


Project prompts will be available on Epicenter at 8:00 am Friday for full-time students and 8:00 am on Thursday for part-time students. Before you begin your project, make sure to take a moment to review the Independent Projects and Code Reviews lesson.

Authentication and Authorization Project Objectives


  • Does the project include working authentication?
  • Does the project include working authorization, including separate roles for users and admins?
  • Does the project include required CRUD functionality?
  • Were all objectives from the last course section met (see below)?
  • Project is in a polished, portfolio-quality state.
  • The prompt’s required functionality and baseline project requirements are in place by the deadline.

What is a polished, portfolio-quality state?

When a project is both polished and in a portfolio-quality state, this means:

  • You've reviewed your project and your README prior to submitting it to make sure there are no errors or missing information and you are consistent in your indentation, spacing, and code structure.
  • You are following the best practices and coding conventions we teach.

What are the baseline project requirements?

All independent coding projects at Epicodus have these baseline requirements:

  • A complete and informative README
  • The project's commit history demonstrates that the project’s required work schedule and hours have been met:
    • 8 hours completed on Friday is required for full-time students
    • 4 hours completed over the weekend is required for part-time students
  • Completion of the project based on the prompt and objectives. The prompt contains details on the project's theme and features that are not always detailed in the objective. Carefully read through the prompt towards the end of your work session to make sure that you are not missing anything.

Last Course Section's Objectives

  • Do routes follow proper convention, including a root route?
  • Does the project have the required validations and callbacks?
  • Does the project have the three scopes specified in the prompt? Are the scopes properly utilized in views?
  • Does the project include thorough unit and integration test coverage? Tests will need to be updated with authentication. Additionally admin & user access should be tested against each other. For example, testing that an admin can make a product and testing that a user can't make a product.
  • Is the database properly seeded with the Faker gem?
  • Are success and error flash messages used correctly?

Submission


Submit your code for review to the Authentication and Authorization code review on Epicenter.

Visit the Independent projects and code reviews page for details on how to submit your code, how feedback works and course completion requirements.

Lesson 27 of 27
Last updated July 14, 2022