Web Programming | Spring 2019 | Collaborative Project

• Do not edit this file.
• Do not start this project until you have read these instructions carefully.

Instructions

In collaboration with your assigned project partner, create an interactive, single- or multi-user, browser-specific project using your computer’s webcam, microphone, and mouse as input, and the screen and speakers as output. In addition to HTML and CSS (via Sass), use Gulp as your task runner and P5.js as the primary interactive JavaScript tool. The topic of your project may be one or more of politics, art, consumerism, capitalism, animal rights, human rights, etc.

Pairs

• Malik Zeryab and Djourn Gordon-Taylor
• Paige McAllister and Chris Lam
• Catherine Lu and Fabio Silva
• Escarleth Fernandez and Salvador Muñoz-Castillo

Before You Begin

1. Log in to GitHub.
2. Fork this repo(sitory). See this video on how to carry out this step and step 3.
3. Clone your fork, using either the web site or the GitHub Desktop client.
4. Checkout your personalized branch, the one with your name and GitHub user handle.

Automated Workflow

You must use Gulp to develop this project, and you will need to implement two work flows: development and production. The development work flow must be invoked by typing gulp and should carry out common development tasks on HTML, Sass, and JavaScript, including browser refreshing.

The production work flow must be invoked by typing gulp build and should call up only production-level tasks, such as compressing files, including images.

For both work flows, running npm i must install the required Gulp modules.

• Use only version 4 or greater of Gulp.
• Include only tasks that your work flows use; no superfluous tasks.

See a Gulp Template for HTML, CSS, Sass, and JavaScript for ideas, and also look at the various Gulp tutorials we’ve covered in class.

Rules

• Running gulp must invoke the development work flow of this project.
• Running gulp build must invoke the production work flow of this project.
• Only submit files that are required by your project: Do not submit working files, such as .psd, .ai, .indd, or .sketch files.
• Use lowercase, combined with kebab case, to name folders and files (do-this or do-this.html); no spaces in folder or file names (not this); no camel case (notThis); no snake case (not_this).
• Observe a logical ordering of files in your scaffold, one in which audio, video, images, HTML files, Sass files, CSS files, and JavaScript files are neatly organized.
• Your HTML should validate against the w3c-validation Atom package.
• Your JavaScript should validate against the linter-eslint Atom package. (Install this file as .eslintrc.json in your home directory.)
• Your Sass should validate against the linter-sass-lint Atom package. (Install this file as .sass-lint.yml in your home directory.)

iArt Mix Exhibition

Although this project is due a week after the iARTMix show, which takes place on 1 May, consider getting it done a week early for inclusion in the show.

Due

10:00 AM on Tuesday, 7 May 2019.

Submission

You will need to issue a pull request back into the original repo, the one from which your fork was created. See the Issuing Pull Requests section of this site for help on how to submit your assignment.

Note: This assignment may only be submitted via GitHub. No other form of submission will be accepted.