Final Project - pippinbarr/dart450-2018 GitHub Wiki

Final Project: Web Intervention

Pitch presentation due: Tuesday, 6 March 2018, in class
Final presentation due: Tuesday, 17 April 2018, in class
Final project due: Sunday, 29 April 2018, on this page
Grade: This assignment is worth 50% of your final grade. 5% for the initial pitch and prototype and 45% for the final project itself (see the Rubric for specific grading guidelines)

Contents

Brief
Requirements
Rubric
Submitting
The Projects

Brief

Project

Create a web intervention.

Drawing on the ideas we've reviewed in class (as well as your own research), develop and implement a concept for a webpage that can be considered a "web intervention", specifically an intervention into conventional understandings of the web. This page should thus be readable as an interactive critique of/engagement with some aspect of conventional web design, aesthetics, functionality, cultural usage, etc. In order words, the page should both surprise us and lead us to think about the web we know.

This project may be completed individually or in teams of two.

Hypothetical starting points:

  • Surveillance - you could create some kind of meditation on how our devices are increasingly "aware" of details of our lives, from using cookies to track usage patterns, to knowing the number of times we click the mouse button, or even whether our face is visible in our webcam.
  • Social media - one could imagine a webpage that extends on the idea of "social media" by extending it to a near-future vision of webpages/sites that serve as our friends in the absence of real world interactions with other humans.
  • Environmentalism - it would be possible to create a page to visualise and understand the environmental impact of the internet, calculating actual energy usage of clicking links, say, or of leaving a screen illuminated, or of moving data back and forth over the network.
  • Play - you could make a webpage that reconceptualises traditional functionality- and clarity-oriented web design and interactions with a playful toy/game-like approach to experiencing the web. Perhaps a news page that reimagines presenting information in a playful way.

Pitch presentation

In class on Tuesday, 6 March 2018

Create and deliver a roughly 5-minute presentation of your web intervention concept, the technologies you envisage using (libraries, approaches to the underlying code), and an early prototype/example/sketch of how the page might work (actually implemented or mocked up with a plan for code).

This presentation will be worth 5% of your total grade for the course.

Final Presentation

In class on Tuesday, 17 April 2018

Create and deliver a roughly 5-minute presentation of your final project. This should most importantly include a demo of the project itself but also discussion of your user experience goals, development process, and perceived outcomes (e.g. a test run of your Artist's Statement).

The presentation isn't explicitly worth a grade, but is a chance to show the rest of us your work, get some feedback, and help Pippin understand what you're doing!

Artist's Statement

The final project must include a README.md in its directory that provides a roughly 500 word artist's statement that briefly explains the underlying concept you chose, what user experience you intended to create, and your implementation of these ideas in HTML/CSS/JavaScript.

Requirements

Form

  • The site can be a single page or as many pages as you wish

Aesthetics

  • Focus on using interactivity as opposed to content
  • The work should be interesting visually, but does not have to be highly polished with perfect CSS styling etc

Technology

  • Project must include the use of HTML, CSS, and JavaScript
  • Project must exhibit good programming style (commenting, naming, structuring), but does not have to explicitly include any specific elements of coding - just whatever gets the job done

Rubric

Technical (70%)

  • Commenting (clear explanatory language, comments at start of each file explaining it, comments explaining functions and specific lines of code that are potentially unclear, attribution of copied code where appropriate)
  • Style (sensible/helpful naming of variables and functions, well-structured and indented code, use of functions to separate and reuse functionality, sensible file structure)
  • Functional (the code runs with no errors in the console and no bugs in the interaction)
  • Iterative (evidence of multiple Git commits with well-written summaries showing cumulative progress)
  • Complexity (ambitious use of code both discussed in class and found and researched separately)

Conceptual (30%)

  • Concept (clearly defined, interesting, and fits with the project brief)
  • Realisation (effectively designed and implemented in code)
  • Experience (well expressed through the user experience)

Grades

For each category above, a grade will be assigned from the following:

A = Excellent
B = Good
C = Acceptable
D = Poor
F = Didn’t do it

Submitting

Due date and time

TBD.

(Your submission will be considered final as of the final submission time and Pippin will download all the projects in their current state at that point.)

How to submit your project

  1. On this page in the "Projects" section below, following the format indicated, add
  • Your name
  • A link to your assignment folder in your dart450 repository on github.com (navigate to the folder on github.com and copy the URL from the location bar in your browser)
  • A link to your assignment website on GitHub Pages or another hosting service if you prefer
  1. Check to make sure your links work

The Projects

Jane Donne

Marc-Olivier Lamothe

Jonathan Béliveau

Claudia Goyette

Jeanne Garneau-Lévesque

Émilie Brunet

Kevin Lam

Kathleen Capiral

Sevan Belleau

Emma Spellacy

Gavin Park

Victor Le

Laura Hernandez