- Announcement: Click, Click extended: due on Friday 02/16
- Quickly talk about Navigation
- Individual meetings with me
- Work on your homework
- Click, Click: Finalize your design
- Click, Click: Begin programming your site. Have questions ready for your lab instructor on Wednsday. Have about 25-50% of the site online by Friday’s class.
- Read pages Conversation 1: art.yale.edu (pages 3 through 17) in this PDF and create a discussion question
- Seowon and Emily share weekly interest
- Discuss how to troubleshoot programming problems remotely:
- Push your most recent code to GitHub before reaching out for help.
- Send me an email with a link directly to the file on GitHub where you are having trouble. e.g. https://github.com/dylanfisher/ci18/commit/855f0a3cb824897f882dbe45d7aae7afc472f956
- I will then be able to make comments directly on your code on GitHub.
- Review Personal Journey exercises
- The remaining class will be spent working on your Click, Click projects
- Create an archive of each student’s Personal Journey, including your own.
- Create a new directory named
personal-journey-archivesomewhere in your GitHub repo and store all files related to the archive in this directory.
- The archive should consist of a home page that has a link to each student’s project.
- Consider how you represent each student’s project. Is it with a screenshot, or a text description, or something more abstract? Do you want to try to convey the meaning of the student’s project by how you represent it in your archive, or is it just a simple index? Be creative with how you structure your archive!
- What metadata do you want to include for each students project?
- Do the links in your archive link directly to the student’s project, or do you want to create an intermediate page where you display the project within your own website.
- If you have trouble locating someone’s assignment, i.e. they didn’t do it, please indicate this in some way within your archive. This could take the form of a missing image, a note that says it’s missing, etc. The archive should consist of 15 items even if some of projects are missing.
- Finally, add a link to the archive on your GitHub repo’s home page.
- Create a new directory named
- Emil and Jahyun start next class with weekly interest
- Vinny presents on art.yale.edu and go over discussion questions
- Workshop: Hovering
- Workshop files
- Get into groups of 3. Present your work to each other. Answer and record these questions from your classmates:
- What is the first thing you want to do when you land on the website?
- Is the user flow intuitive? Why or why not?
- Is something broken? If so, what is it? Does anyone in your group know how to fix it?
- If something is broken and no one knows how to fix it, what might you search for to find the answer?
- What do you think the designer’s intention is behind the design choices? Is it communicated clearly? How can it be improved upon?
- In terms of formal art/design concepts (typography, layout, scale, color, texture, rhythm) what is working? What could be improved upon?
- Is the site easy to navigate? Based on our presentation about navigation on Tuesday, is there enough information for the user?
- Any last comments about the experience?