If you’re seeing this, the site behind it is likely broken!

Hi, there. I use these course sites as little sandboxes to experiment with and learn various “brand new” CSS properties—and your browser does not support (at least) one of them. Apologies. It “should” always work in current/updating Safari and Chrome!

  • Typography & Interaction

    ’25–26

  • The Syllabus

  • Our Class

  • Unit Nº 1: “Type and the Web”

    Wks. 1–6

    • Week Nº 1

      Aug. 29

    • Everything Is a “Web Page”

    • Week Nº 2

      Sep. 5

    • It’s All About Type

    • Week Nº 3

      Sep. 12

    • An Intro to HTML

    • Week Nº 4

      Sep. 19

    • An Intro to CSS

    • Week Nº 5

      Sep. 26

    • The Box Model

    • Project Nº 1: “Manuscript”

      Oct. 3

    • Week Nº 6

      Oct. 3

  • Unit Nº 2: “There Is No Perfect Layout”

    Wks. 7–10

    • Week Nº 7

      Oct. 10

    • Responsive Design

    • DevTools /​ Web Inspector

    • Week Nº 8

      Oct. 17

    • Finally, Flexbox

    • And (CSS) Grid

    • Week Nº 9

      Oct. 24

    • Some Additional, Advanced CSS

    • Project Nº 2: “Spread”

      Oct. 31

    • Week Nº 10

      Oct. 31

  • Unit Nº 3: “Typography as Interface”

    Wks. 11–15

    • Week Nº 11

      Nov. 7

    • Working with Images

    • Week Nº 12

      Nov. 14

    • Week Nº 13

      Nov. 21

    • Thanksgiving Week

    • Project Nº 3: “Binding”

      Dec. 5

    • Week Nº 14

      Dec. 5

    • Week Nº 15

      Dec. 12

  • Winter Break

  • Unit Nº 4: “Interface as Interface”

    Wks. 16–21

    • Week Nº 16

      Jan. 21

    • Week Nº 17

      Jan. 28

    • An Intro to JavaScript

    • Week Nº 18

      Feb. 4

    • Week Nº 19

      Feb. 11

    • Week Nº 20

      Feb. 18

    • Project Nº 4: “Links”

      Feb. 25

    • Week Nº 21

      Feb. 25

  • Unit Nº 5: “If All You Have Is a Hammer, Everything Looks like a Nail”

    Wks. 22–30

    • Week Nº 22

      Mar. 4

    • Puttin’ a (Link/​Meta) Bow on It

    • Week Nº 23

      Mar. 11

    • Spring Break

    • Week Nº 24

      Mar. 25

    • Week Nº 25

      Apr. 1

    • Session Recordings

      Overall Notes

      (Some of) Eric’s Feedback

      Michael’s Feedback

      Quick Questions

      • How many people are doing extensions? These are somewhat hard for us to quickly diagnose, compared to web pages.

      • Are the per-group feedback video recordings helpful?

      • How are folks feeling about/​navigating our expanded LLM policy?

      Some Overall Notes

      • We didn’t see a lot of work in some roadmaps, and many folks hadn’t made real progress towards their goals outside of these.

        We’re trying to help even out the arc of this work⁠—but ultimately you have to put in the time! We’re expecting to see progress each week (and are checking for this).

        Also, Index project progress⁠—many hardly or didn’t even touch it at all!

      • This is not, primarily, a content project⁠—if you are burning your time here, we want you to refocus on the function! Give yourself just enough here to model your data, then come back to populating/​fleshing this out further, later.

      • Likewise, for assets (separate of content)⁠—you might think of an illustration or icon as an asset. This also not primarily an asset project, but leave some time (towards the end) for these.

      • Revisit your roadmaps, if you haven’t⁠—again, to both keep yourself on track/​focused and also to show us your progress.

      • You should be (well) into code! If you aren’t in code⁠—or haven’t answered the biggest “is this feasible” question yet⁠—you are behind.

      • Don’t check any API keys/​tokens into your repos! They shouldn’t be public . If you have an API that needs these, talk to us.

      • As you get into the technical aspects of your MVP, ruthlessly trim your scope! Narrow your focus! Pick the one thing and make it robust and thorough, “putting a pin” in your other ideas.

        All things equal, a thoroughly working project is worth more than any particular taste/​design. We only have a few more weeks⁠—and by next class, you should be showing us a working MVP on your phone!

      Project Check-Ins, Continued

      Our same groups again, today:

      Group Nº 1

      • Ali
      • Zarah
      • Sooim
      • Evgenii
      • Sophia
      • Mia
      • Riya
      • Lucy
      • Kinza
      • Trenton

      Group Nº 2

      • Michael
      • Soko
      • Chareese
      • Amanda
      • Katie
      • Melody
      • Maika
      • Kimaya
      • Noor
      • Cason

      Structure for today

      • We’d like you to see both of us today⁠—switching groups from last week and then circling back around.

      • But it’ll still be pretty quick! Ballpark a few minutes each, and be ready to get what you need from us.

      • Give us a brief run-down of your project, any “swings,” and your overall progress from last week.

      • Have your in-progress, core functionality prototype up on your phone!

      • We’ll also look at your updated roadmaps, to frame our discussion of progress/​efforts⁠—are we “current,” here?

      • Same as before: we want to make sure you are “unblocked” on your project⁠—do you know what you are doing overall, and what you are doing for next week?

      For Next Week

      • We’re moving on to our next project milestone, the fabled MVP. By next week, the last “beam” of your project should be in place:

        Project Nº 5: Minimum Viable Product

      • Send us your links and an update, as is custom:

        Submission Form

    • Week Nº 26

      Apr. 8

    • Week Nº 27

      Apr. 15

    • Project Nº 5: “Functions”

      Apr. 22

    • Week Nº 28

      Apr. 22

    • Week Nº 29

      Apr. 29

    • Week Nº 30

      May 6

    • “Everything Else”

  • Project “Index”

    May 15

  • The end