Information Foraging Assignment: Nursery School

From CSE256A Wiki
Jump to navigation Jump to search

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:

  1. Asd
  2. Asdf
  3. Asdf
  4. asf

Prerequisite Readings

Before starting this project, you should read the following:

Running the Site Locally

  1. Open a terminal window or the terminal in your code editor.
  2. Navigate to your repository folder. This should be something like: cse256a-s20-<YOURWUSTLKEY>.
  3. Type in:
python -m http.server 8000.

This starts a local webserver from that directory.

  1. Navigate to: ​ http://localhost:8000/information-foraging/files/index.html

Project Set-up

Introductory Studio

The goal of this studio is to introduce you to the basic set of skills that you will need in order to begin modifying the nursery school site. While you won't emerge at the end of this knowing everything there is to know about html, css, and javascript, this should give you enough to be able to modify the starting code we've given you.

General model

For those who have never done any web programming before, we'll end up touching three kinds of files:

  • Html contains static information and it's organization (*.html)
  • Css allows you to set the visual properties and control how different website elements look (*.css)
  • Javascript enables your site to have interactivity and respond to what users do (*.js)

Running the Nursery School Site

  1. Open a terminal window or the terminal in your code editor.
  2. Navigate to your repository folder. This should be something like: cse256a-s20-<YOURWUSTLKEY>.
  3. Start a local webserver by typing in (from your repository directory):
python -m http.server 8000.
  1. Navigate to: ​ http://localhost:8000/information-foraging/files/index.html

Finding Content in HTML

Today's web browsers provide developer tools that can be handy in finding things you want to modify in the nursery school site. For purposes of this studio, we'll assume you are using Chrome. We're going to start by changing the "come visit" call to action in the center of index.html.

[[File:ComeVisitStart.jpg|thumb|Come Visit call to action in the center of index.html]]

First, we'll open the developer tools. From the three dots menu all the way on the top right, choose "More tools" and then "Developer tools."

Opening the developer tools in Chrome.

Now, you should see a panel open on the right hand side.

The developer tools appear in a panel on the right hand side of the Chrome browser.

Relevant skills

  1. Opening the developer tools
  2. Right click to inspect
  3. Locating an inspected element in the code
  4. How to get to the style info in case the css is a thing
  5. Creating an alternative style for something
  6. And looking up the elements (I did this with a in index.css to get the inline version)
  7. Troubleshooting: page changes not showing up - may need to clear the browser cache.
  8. Search and replace to do things like edit the header for each page. VSCode - replace in files
  9. make a sticky header https://www.w3schools.com/howto/tryit.asp?filename=tryhow_js_sticky_header

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.