Non-Linear Project

Use HTML5, CSS3, Dreamweaver, image creation software (Photoshop, Illustrator, etc.), and whatever other software necessary to create a non-linear experience using text, images, animation, audio, and interactive feedback. The ways in which the project is interactive should be related to the experience you are trying to create. Your work should not merely look a certain way, it should also react to user input according to the logic of your intended experience. The user should be able to navigate through your project in a non-linear fashion. There should be several parts (pages, or page-states) to the project, with links that invite the user to advance to the next parts. There should be more than one path through the project. The project should not be a single animation (like one huge video file). It should be in several parts with links that invite the user to advance to the next parts.

The "plot" can be very literal or very surreal and abstract. You may have photographic characters, animated characters, or no characters. You must use words in some way (spoken words, written text, dialogue bubbles, photomontage with words in them). You must also use audio and animation in some way. But note: the entire site does not have to be animated, nor does the entire site have to contain audio.

Avoid creating something that relies heavily on someone else's illustrations (South Park, Adventure Time, etc.). You may use found content on the web, but you must recontextualize it into your original experience. Your site may even link to other areas of the web (social media or otherwise) for supplentation or augmentation, but the majority of the experience needs to happen on pages you've created.

Create a directory in your "sites" folder called "nonlinear" and upload your project to that directory. Your start page should be labeled "index.html" Your project should appear at http://nm.unca.edu/~youruserid/nonlinear/

The project should NOT require an online artist statement explaining its purpose and concept; these should be evident from the project itself. If there are any special technical instructions necessary for the user to navigate the project, these should be included at the beginning.

The project should be at least 15 pages (or segments/states). It can be longer, but not shorter.

Additional Responsive Design Details >>>



General Requirements:
1. must be comfortably surfable via cable modem (no pages/files over 20Mb)
2. must use audio
3. must use animation (something should be moving at some point)
4. must use words
5. must be non-linear (more than just one path)
6. must be in segments
7. must work cross-browser and cross-platform.
8. must contain at least 15 pages (or segments).
Responsive Requirements:
1. must be at least 5 responsive pages.
2. must contain at least three separate responsive states per "page" (a. 1 state at or above 1200 pixels wide, b. 1 state at or below 480 pixels wide).
3. column layout, image size, font size, and font typeface vary at each state


Grading criteria:
1. meets above requiremets
2. compelling experience (scope, profundity/humor/engagement/twist, originality, clarity, usability/navigability)
3. genre awareness/appropriateness (suitability of the experience for non-linear and web environment, how well does execution/implementation enhance the experience?)
4. sensory aesthetics (interactivity, code/software mastery, color, design, movement, sound)


Suggestions:
1. Content: Make a statement about something in which you are interested personally. Have fun.
2. Consider Meadows' non-linear plot types -- nodal, modulated, open
3. Surf the examples, read Pause & Effect
4. Use flowchart/site map software for prototyping.