βοΈ 1.2.5.1 JavaScript and Web Browsers Independent Project
Independent Projects Overviewβ
Project prompts will be available on Fidgetech Code Central once you let your instructor know that you have reached the end of a section. Before you begin your project, make sure to take a moment to review the Independent Projects and Code Reviews lesson. This lesson details:
- 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 Fidgetech Code Central.
- Select your current course.
- On your course page, select this section's code review.
- 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 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.
JavaScript & Web Browsers Project Objectivesβ
This section's independent project will be reviewed for the following objectives:
- Form gathers input from the user.
- Branching is used to determine the result.
- Web API object properties or methods (not including
window
methods for alerting, prompting, or confirming) are used to display the result to the user. - Event handler properties or event listeners are used to handle events.
- When the user submits the form again (for a second or third time) previous results are hidden, cleared, or replaced.
- Variable names are descriptive of what they represent and use lower camel case (e.g.
myVariableExample
). - Web page is styled using custom CSS.
- Project is in a polished, portfolio-quality state.
- The promptβs required functionality and baseline project requirements are met.
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.
- 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
- It is not required to include a link to your site hosted on gh-pages, but you are welcome and encouraged to do so!
- The project's commit history shows at least 8 hours of work.
- 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 JavaScript and Web Browsers code review on Fidgetech Code Central:
- Navigate to the code review detail page on Fidgetech Code Central:
- Select Introduction to Programming from the list of courses,
- Select the code review title corresponding to the section,
- Once on the code review detail page, scroll down to the Submission section and follow these steps:
- Input the GitHub repository URL containing your project into the GitHub repo URL input.
- Add a submission note for your teacher to review
- Hit the Submit Project button β you will be taken to a confirmation page.
Visit the Independent Projects and Code Reviews lesson for details on deadlines, how to submit your code, how feedback works, and course completion requirements.