Feedback

[case-eee]

@tmikeschu thanks for taking this on! i have a few pieces of feedback/questions:

• I love this idea. I think it's a great mix of all the concepts we discussed: logic, AJAX, DOM manipulation, testing, etc.
• Are we expecting them to setup the test files themselves? Is that something we need them to know how to do?
• I'm a little confused on each expectation. Perhaps a screencast/screenshot of what this should look like would be helpful in clarifying expectations
• We may want to be more specific with where we'd like them to write their JS (if we don't want to cause them more overhead). I'm not convinced this is a good idea, but I'm just trying to put myself in their shoes and thinking what setups they've seen thus far.
• I'm more specifically unclear on objectives 3 and 4. What does 3 look like in practice? When they tab, the info should appear then disappear again? How do we visit "WordWatch based on the Word Watch API database" in 4?

[tmikeschu]

• Tests

  • I didn't get around to this yet, but I plan on having the test files set up, with example syntax.

• Expectations

  • Great idea! I already have some screenshots made that I will add.

• JS location

  • Maybe we make it clear to write all JS in index.js?

• 3 and 4

  • 3 gets at screen-reader-able content, I'll make that more clear. The info would never appear, just readable by a screen reader.
  • 4 is unclear and should read: "Word Watch, I should see the top used word and its count, based on the Word Watch API database"

I think it would be helpful to have a video demo of a completed project, similar to Nate's video for the current assessment.