Difference between revisions of "Information Foraging Assignment: Nursery School"
(Created page with "=Task Description= Washington University hosts and on-site nursery school for children ages 2.5-5 years old. In this project, we are going to work to improve nursery school si...") |
|||
| Line 38: | Line 38: | ||
# Creating an alternative style for something | # Creating an alternative style for something | ||
# And looking up the elements (I did this with a in index.css to get the inline version) | # And looking up the elements (I did this with a in index.css to get the inline version) | ||
| + | # Troubleshooting: page changes not showing up - may need to clear the browser cache. | ||
Your new version should perform 20% better than the old version, as measured by incorrect | Your new version should perform 20% better than the old version, as measured by incorrect | ||
Revision as of 17:46, 30 December 2019
Contents
Task Description
Washington University hosts and on-site nursery school for children ages 2.5-5 years old. In this project, we are going to work to improve nursery school site visitors’ ability to find relevant information using Information Foraging Theory. Information Foraging Theory describes how users search for information using different cues.
Specifically, we will study the following scenarios:
- Asd
- Asdf
- Asdf
- asf
Prerequisite Readings
Before starting this project, you should read the following:
Running the Site Locally
- Open a terminal window or the terminal in your code editor.
- Navigate to your repository folder. This should be something like: cse256a-s20-<YOURWUSTLKEY>.
- Type in:
python -m http.server 8000.
This starts a local webserver from that directory.
- Navigate to: http://localhost:8000/information-foraging/files/index.html
Project Set-up
Introductory Studio
General model
- Html contains static information organization
- Css tells you how to display it on the screen
- Javascript controls any interactive components
Relevant skills
- Opening the developer tools
- Right click to inspect
- Locating an inspected element in the code
- How to get to the style info in case the css is a thing
- Creating an alternative style for something
- And looking up the elements (I did this with a in index.css to get the inline version)
- Troubleshooting: page changes not showing up - may need to clear the browser cache.
Your new version should perform 20% better than the old version, as measured by incorrect clicks to get to an answer. We’ll use the baseline data that you have in your repository as the comparison. A user will be considered fully correct when they navigate to the data using the specified correct path and write an answer that makes sense for the question. Just being on the right page isn’t enough. Your new version should address each of the 10 tasks. The tasks are all posted on Piazza.
Submission
When you submit, you’ll submit your site and the (unique) “correct path” for each of the tasks. We will randomly choose three of the tasks to test. For future iterations, we’ll keep two tasks the same and then choose a different third task. This is intended to keep disincentivize degenerate designs while also giving you an opportunity to iterate.