Exercise Friday

Independent Projects Overview


Project prompts will be published on Epicenter at 8:00 am Friday for full-time students and 8:00 am on Thursday for part-time students. Before the prompt is published, only the objectives will be visible (the same that are listed below).

Before you begin your project, make sure to take a moment to review the Independent Projects and Code Reviews lesson. This lesson details:

  • Independent project deadlines
  • How to submit your code
  • How feedback works
  • Course completion requirements

Accessing the Project Prompt


To access your independent project prompt, follow these steps:

  • Login to Epicenter. You should automatically be taken to the Courses page, but if not, select Courses from the navigation bar at the top of the page.
  • Select your current course from the Your courses section.
  • On your course page, select this section's code review from the Code reviews section.
  • This will bring you to a code review detail page with:
    • The prompt theme and requirements
    • A list of objectives
    • A list of optional further exploration objectives
    • A location to submit your project
    • A survey to fill out about how the section and project went
    • A location to leave a submission note for your teacher to read
  • Once you've completed your project, submit the GitHub repository containing your project in the Submission section of the code review detail page. See below for detailed instructions and a review of deadlines.

Git, HTML, and CSS Project Objectives


Your instructor will review your code for the following objectives:

  • The following HTML tags are all used: p, h, ul, ol, li, em, strong, a, img, div, and span.
  • Project includes a custom-made stylesheet that uses typography styles, the box model (including margin, border, and padding), and floats.
  • Code is clean, well-refactored, and easy-to-read. This includes correct indendation, spacing, and including only necessary comments and debugging tools.
  • Commits are made regularly with clear messages that finish the phrase "It will…"
  • The project repo contains a README that includes:
    • application name
    • names of contributors
    • description of application
    • link to site on GitHub Pages
    • a "technologies used" section
    • application setup instructions
    • link to site on GitHub Pages
    • a "known bugs" section
    • copyright, date, and license information
  • Site is successfully deployed to GitHub pages.
  • 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. Make sure that your:
    • Code is clean, well-refactored, and easy-to-read. This includes correct indentation, spacing, and including only necessary comments and debugging tools.
    • Variable names are descriptive and use lower camel case (e.g. myVariableExample).
    • Commits are made regularly with clear messages that finish the phrase "It will…".

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.

Submission


Once you've completed your project, submit your code for review to the Git, HTML and CSS code review on Epicenter:

  • Navigate to the code review detail page on Epicenter:
    • Go to the Courses tab,
    • Select Intro under the Your courses section,
    • Select the code review title corresponding to the section under the Code reviews section,
  • Once on the code review detail pade, scroll down to the Submission section and follow these steps:
    • Input the GitHub repository url containing your project into the Submission link input.
    • Do not submit the link to your live GitHub Pages site, ie: your-username.github.io/your-portfolio. Instead, submit the link to the GitHub repository containing your code, ie: github.com/your-username/your-portfolio.git.
    • Add a submission note for your teacher to review
    • Complete the survey
    • Confirm that you "have read and understand the guidelines for Independent Projects" by checking the checkbox.
    • Hit the submit button - you will be taken to a confirmation page.
    • On the submission confirmation page, select whether or not you want to request a meeting with your teacher

Deadlines

The deadlines for the initial submission are:

  • Friday at 5:00 pm for full-time students.
  • Sunday at 8:00 am for part-time students.

Keep in mind that resubmission deadlines are different! Visit the Independent Projects and Code Reviews lesson for details on deadlines, how to submit your code, how feedback works, and course completion requirements.

Lesson 64 of 64
Last updated October 14, 2021