exampleSyllabus.md

What Is Code U?

In Code U at Hilliard City Schools, students prepare for careers in the high-demand fields of information technology, programming, and software development. Any student in Hilliard City Schools can enroll in this career-technical satellite program offered at both Bradley and Davidson High Schools. Students have opportunities to earn industry credentials that can prove valuable after high school in this job sector. IT, coding, software, and programming careers are among the most sought after in today’s workforce. The skills developed in this program also provide a head start for students interested in pursuing further education in college. Source Code U on Pinterest

What Is GitHub?

Git Repository Clone Commit Push Pull Here is link to the full GitHub glossary of terms

Learn more about GitHub Education here

Workflow

If you're using GitHub Desktop, these general instructions will help:

• https://guides.github.com/activities/forking/
• https://help.github.com/desktop/guides/contributing/

Enabling Edit->Automatically Sync after Committing is recommended. Here are the steps:

1. Fork (create your own branch of) the repository for the exercise/project.
2. Clone (download) the repository to your computer.
3. Edit the files to complete your solution.
4. Open the index.html file in a browser to see the results, and repeat.
5. Make sure all of your code is committed.
6. Push (sync) up to GitHub.
7. Create a pull request (merging the code) on the original repository.
8. You can continue to push fixes and improvements – just add a comment in the pull request to let me know it's been updated.

Feedback will be given in the pull request, so please respond with your thoughts and questions! You are welcome to open the pull request early as a work-in-progress if you are stuck and want to ask a question.

Testing

1. one
2. two
3. three
4. four

Requirements

These apply to real life, as well.

• All HTML files should pass W3C Markup Validation.
• All written JS should pass JSHint.
• Must apply "good programming style" learned in class
  • Functions should be "short" (see Sandi Metz's rules for developers).
  • Optimize for readability.
    • "Programs must be written for people to read, and only incidentally for machines to execute." -Harold Abelson
  • Avoid using anonymous callbacks within other functions, especially if the callback is more than one or two lines.
  • For projects, use Object-Oriented Programming.
• Any borrowed code must be properly annotated, otherwise it is plagiarism.