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

    • Session Recordings

      Eric’s Feedback

      (Some of) Michael’s Feedback

      Project 4 Recap

      Everyone should have received their evaluations on Slack earlier this afternoon. This should also function as a proxy for your mid-term standing in the class⁠—today is the halfway mark, if can believe it! You can, as always, respond to us there with any questions or concerns.

      We’d like to remind folks here of our overall grade calculation for the Spring. Your remaining Index and Functions projects are, combined, worth twice as much⁠—and your readings, milestones, and engagement can likewise bolster your scores. So take that into account moving forward!

      A couple things we wanted to bring up here, as a group:

      • Unconsidered feedback

        There was an overall, noticeable lack of engagement with our prior feedback⁠—both from previous project evaluations (more technical), but also from in-class and Slack notes (more design and behavior).

        We were pretty disappointed by this⁠—our process here is much of the point of this course, and meaningfully incorporating and responding to feedback is central to our design discipline. We expect more here.

      • “AI,” again

        From our syllabus:

        We think you first need to write code yourself to understand the medium. Copying/​adapting from Chat⁠GPT/​Copilot is no different from anywhere else and is ultimately a disservice to your education. These are always to be treated like any other tools at our disposal⁠—as aides to your understanding, not shortcuts around learning. We think you know the difference.

        After looking through your project repos, we think we were wrong about the last sentence⁠—it appears to us that many of you do not know the difference.

        We will be revisiting our acceptable LLM use for Project 5⁠—likely landing somewhere between “zero-tolerance” and “heavily restricted.” We’ll share this with you next class, when we return after Spring Break.

        In the meantime, these tools should be nowhere near your planning/​roadmapping milestones. The entire point of these steps are to exercise your abilities!

      More on Project 5

      Before we break out into groups to discuss your proposals, let’s talk through the rest of the project:

      Project Nº 5: Functions

      Problem Feedback

      We’ll split into two groups to go through your proposals:

      Group Nº 1

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

      Group 1 FigJam Page

      Group Nº 2

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

      Group 2 FigJam Page

      Here’s how we’d like to structure this, today:

      • We’ll be using the FigJam pages above! Sign in and such as we get settled today, so we are ready to go.

      • Then add three (or more) sticky notes to your section, one note for each of your problems/​proposals.

      • You can copy/​paste from your Google Doc, but only write titles/​short descriptions⁠—just enough to differentiate them!

      • We’ll be using these for dot voting⁠—a way to gather overall popularity and help in your decision-making.

      • We both want to hear everyone’s proposals, which means we’ll have only a few minutes with you each.

      • Very briefly introduce us to each of your three problems, in a minute or two⁠—stay “high level!”

      • We will both have three “votes,” which we will assign/​distribute to your problems based on feasibility and “overall vibes” and such.

      • After we place our votes, the rest of the group will place theirs⁠—use the stamp tool with your avatar for your dots.

      • You can likewise distribute these as you see fit⁠—all on one project, spread across, however you feel.

      • At the end, everyone should have… 33 dots/​votes in their section!

      This will help give you an idea of what is resonating with us and your classmates⁠—the goal here being to help you narrow down to one of your problems.

      You are not required to follow this vote

      Which problem you pursue is still up to you⁠—but if your heart is set on a problem that didn’t find much traction, you likely need to refine /​ develop the idea further.

      For Next Week Class

      • If you’re feeling any big, directional swings after today and want our feedback after revising/​narrowing⁠—we need to know in the next couple days! There is really no time to burn, here.

      • You’ll be refining your concept, roughing out your features, prioritization, and planning for the next six weeks:

        Project Nº 5: Project Roadmap

      • As we note over there, your roadmap should also include what you are working on for when we next meet⁠—beyond just the roadmap itself. You will need to make other progress, starting into your actual features/​tasks. Identify the MVP and work back from there!

      • We will also be checking in on your Index project milestone/​progress, which we discussed last week:

        Project Index: Adding Context and Form

      • Make sure we have a link to your roadmap, a quick update on your progress, and your Index URL:

        Submission Form

    • Spring Break

    • Week Nº 24

      Mar. 25

    • Week Nº 25

      Apr. 1

    • 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