Submitting Your Work
Project deliverables must be submitted using GIT by the end of the due date given; if your assignment is received after midnight (i.e., the next day), it is considered late.
- If you need a one day extension, complete this form, at least 24 hours before the due date or incur a late penalty
- You will not "submit" projects as in other CompSci classes, instead you will be graded only on what is pushed on the
masterbranch of your project's repository in the course's Gitlab group - You are responsible for ensuring that all files are correctly
pushed to the repository on time so we recommend you push code to your repository very regularly (at least daily) to avoid excuses such as "my computer crashed" - All code files must include your name
All submissions must represent your own work and must include credit for any print or electronic resources used, as well as anyone you consulted with.
Craftsmanship
While your code is not expected to be "elegant" or sophisticated as you learn all of these new languages, it is expected to be follow common coding conventions, written readably, with good names, and indented appropriately to reflect the structure of the elements you are defining. Furthermore, to reduce the chance of bugs and help ensure your web site displays the way you expect in a browser, it must use common, standard, features and pass validation using the W3C validators online:
HTML Style Guide Validator CSS Style Guide Validator JavaScript Style Guide Validator JSON Style Guide Validator Accessibility Style Guide Validator
Make sure to give credit where credit is due: all code "borrowed" from the Internet must be formatted consistently with your other code and attributed in comments right before it is used.
Projects
Programming projects are to be done individually, unless otherwise noted.
Files to Submit
You should submit only
- code files (html, css, js, or vue)
- data files (json, xml, or csv)
- text files (md or txt)
- image files (gif, jpg, or png)
- sound files (mp3, au, or wav)
Make sure to give credit where credit is due: all asset files (images, sounds, etc.) must
- be royalty free and not "stolen" off of the web
For example, use fotolia.com, istockphoto.com, everystockphoto.com, or pay attention to the Creative Commons licenses on web sites. If you choose to use your own images or a friend's make sure to include a credit and a Creative Commons license so other's know how they can use your images. - attributed to their original author (even if it is you)
For example, use thefiguretag or afootertag at the bottom of the page - include ALT text attribute to describe its contents
For example, in case it does not load or is being viewed by a visually impaired user
Each programming project must be in a separate folder that includes a README file (either plain text or Markdown) that includes:
- your name and Net ID
- the date you started the assignment, the date you completed the assignment, and an estimate of the number of hours you worked on it
- list of the students with whom you discussed the assignment
In accordance with the Collaboration Policy, you are expected to keep track of anyone with whom you have had a significant conversation about a program (including the Teaching Team) - any books, papers, or online resources that you consulted
- any assets (code, images, or sounds) used including links to the original work
- any bugs or concerns still remaining
- any features you believe to be extra credit (so we do not miss them in the grading)
You will lose points on your assignment if it does not include a proper README file. Here is a template to get you started.
We would appreciate it if you also included your impressions of the assignment to help improve it in the future.
