Week 20, February 19

More Quick Notes #

• DevTools!

  The console again! What’s it telling us? (Or what is it not telling us?) Remember that any JS after an error won’t run!

  Not trying to call anyone out! For every person asking in the Slack—which we love—we know there are more silently suffering.

• Paths!

  Some folks are getting tripped up by their paths—in HTML href="something" / src="else" attributes or CSS url("entirely") properties. A quick refresher:

  • /folder means “from the root” (the domain)—which is different from our Live Server plugin to GitHub! (This is rarely what you want.)

  • folder/ means “in a subfolder of my folder”—keeping in mind that this is relative to the HTML file or CSS file itself!

  • ../folder means “up a level, then down”—if your stylesheets are organized in an assets directory, you might need to up first!

  You can edit/check these quickly in the Inspector!

• Simulating Pseudo-Classes (States)!

  With an element selected in the DevTools, click the :hov button above the styles cascade to emulate :active, :hover, or other states.

  We’ll do a 30-second demo!

• Attribution!

  As folks round out their code, we want to reiterate our policy on attribution. We need to see all three parts in your comments:

  • Why you incorporated a resource
  • What (or where ) the resource is
  • How you understand it to work

  It’s not an attribution without all three!

Notes on Format #

You’ll be presenting your projects next week! Let’s talk through it:

Project 4 Notes on Format

Project Check-Ins #

The rest of the day will be for looking at your projects! We’ll use the same groups as before:

• You’ll each see both instructors, today
• Same 4 minutes or so with each person
• Have your live work up in Dev Mode for mobile
• Give us a quick background, then show us your progress
• Let’s focus on conceptual and design feedback (save specific technical questions for Slack)
• Use the time with your peers! One person at your table can answer your technical question (and will learn from it themselves)

For Next Week #

• You will be finishing your Links projects:

  Project 4 Refinement and Review

  As you hone your work, read back through the previous phases carefully and make sure that you aren’t missing anything. We are expecting to see continued evolution of your work based on your concept and our ongoing feedback!

• Make sure you “turn in” your URLs, as usual:

  Submission Form

• And prepare to present your work next week! We’ll split into two groups, and using the entire class for this purpose. Keep in mind our structure:

  Project 4 Notes on Format