gdes 2342: Web Design Course description: [t]he control which designers know in the print medium, and often desire in the web medium, is simply a function of the limitation of the printed page. We should embrace the fact that the web doesn't have the same constraints, and design for this flexibility. But first, we must accept the ebb and flow of things John Allsopp The Dao of Web Design In over two decades of its existence, the web has evolved into a ubiquitous and egalitarian platform that empowered graphic designers to expand their expertise into the digital realm. The ability to create and edit web sites through coding have made the computer a meta-tool, a tool to create other tools, and with the emergence of high-level languages such as html, css, and Javascript, coding has never been more accessible to the graphic designer. In this class, we will take advantage of these resources and become fluent in the language of the web and explore how our previous practices in print design translate into this dynamic and interactive medium. This is an introductory level coding/design class that will acquaint you and your peers to the tools and craft of web design. All assignments and projects will focus on your ability to visually articulate content through html/css/ jquery. In addition, we will touch upon the basic concepts and practices of user-centered design to maximize your web site s utility and usability for our audiences. Course Objectives: have proficient knowledge of html/css/jquery. learn the basic concepts of user-centered design. inspire authenticity for all aspects in the design process (research, ideation, prototyping, etc.) use critique as constructive conversation to help further refine formal solutions. apply knowledge and skills from prerequisite classes to explore their applications. emphasize making and critical visual thinking. Course prerequisites: dha/gdes 1311, 1312, and 1315, or design minor; experience using Adobe Illustrator, Photoshop, and InDesign. May take concurrent to semester doing portfolio review. Criteria for evaluation: A: strong design process / thorough research / frequent participation in critiques and class discussions / focused / ability to generate mulitple solutions / mastery of form and usability / excellent (digital) craftsmanship / effectively articulate and sketch ideas B: can improve on the items from the A student / needs to generate more solutions / seldom participation / needs refinement in craftsmanship / final outcome of projects is good but needs to improve on process. Instructor: Eugene Park ebpark@umn.edu Office hours: Tuesdays 2pm 4pm* McNeal Hall 246e Studio: M & W 11:45am 1:55pm McNeal Hall 316 Jan 21 May 09, 2014 C: completes work only to satisfy minimum requirements / very few instances of participation / unwilling to break initial mold / doesn t make significant improvements to projects / frequently late D: little or no participation / chronic tardiness / incomplete work / lack of refinement / express little to no interest / doesn t follow instructions *also available for appointments page 1 of 6
Student Learning Outcomes: 1. Can identify, define, and solve problems The main problems to be identified, defined, and solved when creating a web site are as follows. Visual Communicate the identity and goals of an organization Communicate the key tasks a user can accomplish Apply design elements and principles (e.g., color, imagery, space, typography, writing, navigation, and unity of the whole) Apply the principles of user interface design Technical Use related software, including programs from Adobe Creative Suite 6, Sublime Text 2, and TextWrangler. Plan and construct custom functions with Javascript to implement various technical features (e.g. complex animations, automated processes, feedback loops). Technical also for web Mark text for html and style texts and objects with css, and dynamically animate with jquery and Javascript. Design the site for a standards-compliant browser on Mac, Windows, and Linux operating systems. Construct informational architecture and wireframes to plan how the user will access the contents of a website. Apply card-testing to evaluate and edit the feasibility and accessibility of a website before coding. Apply a few key principles of accessibility Evaluating Learning Outcomes The aforementioned learning outcomes will be assessed through the creation of the following. Web site components Web site goals, user research, site map, sketches, wireframes, style guides, prototypes, an incremental build of the html, css, and jquery of final site, construction of custom functions in Javascript, and presentation of final product. All visual elements must adhere to the principles of user interface design by presenting themselves clearly to the user and be responsive upon user input. The intent of the website must also be clear to the intended users and free of any visual distractions and technical imperfections. Usability tests Identify key tasks, user research, write related scenarios, conduct the user tests, organize the data, assess the outcomes, and revise the product based on user input. The purpose of usability tests is to ensure that all components of the app and web site flow efficiently through the user experience. As such, all user tests must be able to provide constructive input to the student's design process and such improvements must be evident in each product iteration. 5. Can communicate effectively Create products that communicate the identity and goals of the sponsoring organizations, as well as meet the needs of users. Participate in written and spoken critiques, as well as present the final web site to the class. page 2 of 6
Class schedule: Jan 22 introductions / algorithm poster brief 27 exchange posters / html & css lecture 29 algorithm poster final critique / pick poem Feb 03 web poetry hand sketches 05 hand sketches edit / secure web hosting 10 web poetry project critique 12 web poetry project critique 17 web poetry project final critique 19 jquery intro. / narrative project brief 24 narrative storyboard due 26 type specimens / hand sketches due Mar 03 hand sketches critique 05 hand sketches critique 10 narrative pages critique / open project brief 12 narrative pages final critique / topics review 17 spring break : no class 19 spring break : no class 24 narrative pages critique / final topics due 26 narrative pages final critique 31 open project info. architecture / audiences Apr 02 card sorting exercise 07 site map and wireframes due 09 type specimens / hand sketches due 14 digital sketches due 16 digital sketches edit 21 begin coding final project 23 code / refine 28 code / refine 30 half of web site due May 05 code / refine 07 open project final critique 16 all projects due by 11:00 pm Grading breakdown: 20% critique participation 10% coding exercises 10% algorithm poster project 10% web poetry project 25% narrative project 25% open project Grading late work: The student is required to complete all course assignments on time: that is, each assignment is to be finished by 11:45 am on the day it is due, unless specified otherwise. Work completed after this time but by 11:45 am of the next class period will be marked down a full letter grade. If you have a scheduling problem regarding an assignment due date, please speak to the instructor before the due date about alternative means of meeting the course obligation. Extra credit: No extra credit will be given. Recommended texts: There are no required textbooks for this class. All reading assignments will be provided by the instructor at the appropriate times. Students who wish to engage in further reading outside of class can consult the following books: Jon Duckett, HTML & CSS: Design and Build Websites (Indianapolis, IN: Wiley, 2011). Brian Miller, Above the Fold: Understanding the Principles of Successful Web Site Design (Louisville, KY.: How Books, 2011). schedule is subject to change page 3 of 6
Format for the course: This is a 3-credit course, and divides our contact time in two weekly sessions. Class is centered primarily on discussions and critique of work done outside of class, anchored by lectures and in-class exercises. Final class meeting: Our final class meeting will take place 11:45 am, May 07, 2014. There will be no final examination, but students must be present and bring all finalized projects for critique. Any student who fails to attend the final meeting will forfeit all critique participation credit. Classroom decorum: Classroom is a time when we meet and be productive towards satisfying the class objectives. You are expected to be respectful of the time of your peers and be attentive and in all classroom activities and discussions. This means no phone use or texting during class times except in cases of emergency. Headphones for music are not allowed during lectures, class discussions, and critiques. Required equipment/software: Students are required to have a basic photo editing and vector editing software such as Adobe Photoshop and Illustrator. In addition, a basic text editor for coding will also be necessary. Apple s TextEdit will work under the right configurations, but other popular editors such as Sublime Text 2 and Textwrangler are free to download. You must also have an up-to-date web browser that supports Java and can inspect html/css/javascript elements. Please bringing your own laptops to class. The projects in this class demands careful file management, and constant transfer between computers might risk file corruption. You must have a webhost to present your web apps. The university provides hosting space to all enrolled students, but its services are very limited. So it is highly encouraged that you purchase your own host and domain name. Also make sure that you have a ftp software such as Fetch, Filezilla, or Cyberduck. Note on Dreamweaver: Use of Dreamweaver is not allowed in this class. Many web classes across the country do not permit the use of this software for many good reasons. Dreamweaver, like many other third party software, adds many unnecessary features such as templates that promote bad design. But most importantly, Dreamweaver undermines the age-long practice that coding, just like Typography, is a form of craft that demands attention to detail and careful planning. There are many free text editors that are useful tools to meet these ends. Note on critique: Critique is a time during class where we give useful input to improve the work of our peers. Whether any of us like the work from our classmates is irrelevant. So try to tailor your comments and suggestions to be as objective as possible. Key questions might include: What is the work doing? How is the work doing what it is doing? What do we think the designer s intention might have been? What associations or references does the work call to mind? Each student is highly encouraged to practice being as specific as possible and avoid vague and subjective statements such as: I like I don't like is good could be better, etc. Release of work: Students understand that enrollment in this course grants consent for their work to be selected for inclusion or college or departmental publications (online and print). Your instructor may select to use your work to represent his/her skills via teaching portfolio (online and print). page 4 of 6
Attendance policy: Attendance is essential in a studio course. The design process involves input and feedback among class members. You are expected to be on time for each class and work in class on class projects for the entire period. Repeated tardiness and/or consistently leaving class early will be considered an attendance problem and can result in a lower course grade. Three tardiness will count as one unexcused absence. Three unexcused absences will result in two letter grades deducted from final grade. Five or more unexcused absences will result in course failure. Excused absences are defined in the policy found here and include the following circumstances: illness, participation in intercollegiate athletic events (not intramural), subpoenas, jury duty, military service, bereavement, and religious observances. Any circumstance that you believe falls under the excused absence category must be verified by presenting the instructor with documentation (e.g., a note from your doctor) that gives the date(s) for which you should be excused (the details of the circumstance do not need to be explained). Students are responsible for information covered during any missed class session and are to acquire this information from a fellow classmate. The instructor will be available to answer follow-up questions during scheduled office hours or during class time, when appropriate. No appointment is needed for office hours. Incompletes An incomplete will not be given for this course unless there is a medical emergency or other extraordinary circumstance that can be verified and deemed reasonable by the instructor. If such an emergency occurs, please notify the instructor as soon as possible. To receive an incomplete, both the student and the instructor must sign a formal contract outlining what needs to be done in order to remove the incomplete. The incomplete must be completed satisfactorily by the end of the following semester or the University automatically turns the incomplete into a failing grade. Personal electronic devices in the classroom Designated class hours are intended for gdes 5342 studio work, discussion, and critique. Your ideas and designs will thrive in an atmosphere of open exchange so have fun, share your ideas and opinions respectfully. In the computer lab, opportunities, responsibilities, and distractions of the digital world are at your fingertips. You must resist. In other words, no Internet exploration or device use that is not directly related to this class, no work from other classes. m&w 6:15 8:25 p.m. http://policy.umn.edu/policies/education/ Education/CLASSROOMPED.html Use of class notes and materials: Students may not distribute, via the Internet or other means, instructor-provided lecture notes or other instructor-provided materials, except to other members of the same class or with the express consent of the instructor. http://policy.umn.edu/policies/education/ Education/CLASSNOTESSTUDENTS.html Scholastic dishonesty and student conduct code: Any student found to have committed or to have attempted to commit misconduct as defined in this policy is subject to appropriate disciplinary action. http://www1.umn.edu/regents/policies/academic /Student_Conduct_Code.pdf Sexual harassment University policy prohibits sexual harassment as defined in the University Policy Statement of December 11, 1998; copies of this statement are available at http://www1.umn.edu/regents/policies/humanre sources/sexharassment.html. page 5 of 6
Climate of inclusivity You are expected to be attentive during class, ask questions if you do not understand something, and offer your opinion. You are also expected to listen respectfully to other students and to me when speaking. The University of Minnesota is committed to providing a safe climate for all students, faculty, and staff. All persons shall have equal access to its programs and facilities without regard to race, color, creed, religion, national origin, sex, age, marital status, disability, public assistance status, veteran status, or sexual orientation. Racism, sexism, homophobia, classism, ageism, and other forms of bigotry are inappropriate forms of expression in this class. Reports of harassment are taken seriously, and there are individuals and offices available for help. Academic freedom and responsibility Academic freedom is the freedom, without institutional discipline or restraint, to discuss all relevant matters in the classroom, to explore all avenues of scholarship, research, and creative expression, and to speak or write on matters of public concern as well as on matters related to professional duties and the functioning of the University. Academic responsibility implies the faithful performance of professional duties and obligations, the recognition of the demands of the scholarly enterprise, and the candor to make it clear that when one is speaking on matters of public interest, one is not speaking for the institution. http://www1.umn.edu/regents/policies/ academic/academic_freedom.pdf. Availability of disability and mental health services The University of Minnesota is committed to providing all students equal access to learning opportunities. Disability Services (DS) is the campus office that works with students who have disabilities to provide and/or arrange reasonable accommodations. Students who have, or think they may have, a disability (e.g. mental health, attentional, learning, vision, hearing, physical or systemic), are invited to contact DS to arrange a confidential discussion at 612-626- 1333 (V/TTY) or ds@umn.edu. Students registered with DS, who have a letter requesting accommodations, are encouraged to contact the instructor early in the semester to discuss accommodations outlined in their letter. Disability Services 180 McNamara, Mpls 612 626 1333 ds.umn.edu As a student you may experience a range of issues that can cause barriers to learning, such as strained relationships, increased anxiety, alcohol/drug problems, feeling down, difficulty concentrating and/or lack of motivation. These mental health concerns or stressful events may lead to diminished academic performance or reduce your ability to participate in daily activities. University of Minnesota services are available to assist you with addressing these and other concerns you may be experiencing. You can learn more about the broad range of confidential mental health services available on campus via www.mentalhealth.umn. edu or contact Counseling/Consulting Services. Counseling/Consulting Services 199 Coffey Hall, St. Paul 612 624 3323 uccs.umn.edu Academic services If you would like additional help, please contact one of the offices listed below. Center for Writing 10 Nicholson Hall, Mpls 612 626 7579 writing.umn.edu Student Academic Success Service 340 Appleby Hall, Mpls 199 Coffey Hall, St. Paul 612 624 3323 sass.umn.edu page 6 of 6