tl;dr Redesign an existing website. Rarely do we get to design something from scratch. It’s far more common to redesign an existing product. This project is an opportunity for you to redesign an existing website. We’ll do this by creating a new site for the Apple Harvest Festival.
Project Document Summary:
Coding Resources:
| Submissions | Deadline | Slip Day Deadline | Credit |
|---|---|---|---|
| Milestone 1 (p2m1) | Wed 3/6, 11:59pm | Thu 3/7, 11:59pm | 36 points (correctness) |
| Milestone 2 (p2m2) | Wed 3/13, 11:59pm | Thu 3/14, 11:59pm | 52 points (correctness) |
| Final Submission (p2fin) | Wed 3/20, 11:59pm | Thu 3/21, 11:59pm | 100 points(correctness) |
Plan to submit on time. We strongly encourage you not to use your slip days unless you have a legitimate need for a deadline extension.
You will re-design and code a responsive website for a cohesive audience for Ithaca’s Apple Harvest Festival.
Your project should be a static 3-5 page website (HTML and CSS only) designed for a specific audience. Each page in the site should contain substantial content in support of the audience’s goals. The majority of the content should likely be written text. But you’ll also need to include media, like images (avoid video and audio for now). The content need not be original.
Your website should be static and without interactivity (no JavaScript). Nothing about your site should be dynamic; the user may only passively consume content (they can’t tap or click things cause that page changes). This means no forms, including a contact form. It also means dropdown menus, hamburger menus, and image carousels aren’t an option for this project (please wait for Project 3).
We employ the user-centered design process in this class. You must design your site first, then code it. Please do not code your website and then “reverse engineer” the design documents. We want you to learn web design and development best practices.
Thoroughly document your design process in the design-plan/design-journey.md document. We want to see the alternatives you considered and why or why not you decided to use them. Please explain your thought process and design rationale. Design is about decisions, and we want to understand why you made the decisions you did in support of your site’s audience.
Generally, please use the methods and strategies we learn in class. In web programming, there are many ways to solve a coding problem. Please use the approaches presented in this class.
When working for a client, you’ll need to check their requirements frequently to ensure you’re meeting their expectations. You don’t want to spend weeks working on something only to discover at the last minute that what you’ve been working on doesn’t meet their requirements.
Refer to the Project Requirements frequently and consistently use them to evaluate your own work. Just like you would if you were working for a client.
Milestones and the final submission are graded for correctness. You will receive detailed instructions for each milestone and the final submission as to what components are required for the assignment.
Generally across all milestones plus the final submission, we will assess your project in three parts:
If you need help on this assignment, you have the following options:
Ask a peer in the course for help.
Working with your peers is one of the best ways to get help in this course. Helping a peer improves your learning and theirs!
Attend TA Office Hours.
Office hours are the best way to seek help in this course. You are encouraged to make regular use of office hours and work with your peers during office hours.
Current office hours are posted to the office hour schedule.
Start assignments early and seek help early; office hours right before deadlines are often be packed.
Because we want you to learn how to evaluate your own work, we ask that you not ask the TAs to check, endorse, or pre-grade your submission.
Post a public question on Ed Discussions (link in Canvas course).
Do you have a general question about the course material or an assignment? The course Q&A forum is the best place to receive clarification on course content.
If you need help with an assignment/project, please seek help with a peer or visit office hours. We want to help you, but it’s often difficult for us to effectively help you with your code in online forum.
TAs prioritize helping students in office hours first then answering questions on Ed. We try to respond to your questions within 48 hours (Monday-Friday, 9am-4pm).
Attend the instructors’ office hours.
The instructors’ office hours are always open. Please feel free to stop by for anything. We are always happy to help you with any problem no matter how big or small.
Instructor Office Hours:
Please do not email info1300@cornell.edu, the instructors, or the TAs for help with an assignment/project. Please use the above methods.
Create your Project2 repository (you only need to this once)
Visit https://landrace.infosci.cornell.edu/courses/info1300-2024sp/repos/project2 in your web browser and click on the Create repository link
This will create your repo in our course organization on github.
Access your Project1 repository in the course GitHub organization
Visit the following URL in your web browser: https://github.com/cornell-info1300-2024sp/NETID-project2
Replace NETID in the URL with your NetID.
Open the project repository as a codespace.
Your submissions should be your own work and adhere to the course citation policy. Please note that no credit is provided for submitting design and/or code that is taken from the course-provided examples. You also are required to use the methods and techniques covered in class; no credit is provided for using methods that are not covered in this class. Lastly, please note that all files must be in the location specified in this document for credit; our grading process cannot reliably locate your work in other locations; incorrectly placed files will not be graded.
Submit all materials to your GitHub repository’s main branch for this assignment. When you’re finished with each milestone or the final submission, stage, commit, and push your submission to GitHub. Then fill-out the submission form to complete your submission. Please do not email your submission to the instructor or to the course email. Our course infrastructure does not support email submissions.
Pro Tip: Back up your progress every time you work on your project: stage, commit, and push your changes to the GitHub server every time you work on your project (no need to complete the submission form). This acts as a backup for your work. Codespaces is configured to auto-save your files, but this does not change the contents of your Git repo.
If your computer fails, you may access your codespace again (with all your backed-up work) from any internet-connected computer such as the Engineering computer labs or a loaner library laptop, and continue working on the assignment. Please back up your work frequently. We don’t want you to lose any of your hard work.
The design process is the most important part of designing and coding a website. You will document your design process in the design journey: design-plan/design-journey.md.
Your design journey should be written in Markdown. Please refer to the official Markdown Reference Documentation.
Use Codespace’s Command Palette to preview your Markdown: Markdown: Open Preview
You will need to include photos/images in the design-journey, etc. Use only .jpg or .png images (.heic images are not permitted). All images must be oriented correctly for credit. If an image is sideways, use an image editor and rotate the image. Place all design related image files in the design-plan directory and link them in your Design Journey with relative URLs; please do not place design journey images in the site’s images directory nor use absolute paths in your URLs.
We will grade design-plan/design-journey.md using Codespace’s Markdown Preview. Make sure your design journey is complete by viewing it using Code’s Markdown Preview. Everything, including images, must be visible for us to grade it. If it’s not visible, then we can’t grade it. We also can’t give you partial credit either.
Each student in this course is expected to abide by the Cornell University Code of Academic Integrity.
Submit your own work.
Submitting work that isn’t your own may result in a 0 for the offending assignment.
You are encouraged to discuss and collaborate with your peers.
However, you may not share or copy code.
You are encouraged to seek out and use additional resources to help you complete your assignments.
Please feel free to use the instructor provided examples, Mozilla documentation, and other resources you find (e.g. example code, StackOverflow, ChatGPT, tutorials, etc.)
Please note that you still need to submit your own work. You may not copy someone else’s work, including work produced by generative AI, and submit it as your own.
We encourage you to use additional resources as a reference rather than for copying code.
Using a resource as a reference means you study the resource so that you understand it and can use the same ideas in your project/code independently.
While it’s tempting to copy code from elsewhere and modify it to suit your purposes, modifying code and writing code from scratch are two distinct skills. You’ll learn more if you study a resource’s code and try and implement the same ideas independently in your code!
Cite all resources you used in writing your code near where you used the resource.
Leave a comment in your code wherever you used a resource to help you write your code. In the comment specify the URL of resource you used.
Note: You are not required to cite instructor provided code or examples in your submission.
Please see the syllabus for additional details about copying code and academic integrity.