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

    • Session Recording

      Project 2 Notes

      Overall, solid stuff last week. We are still going through your work/​code and will be sharing your evaluations soon, probably this weekend.

      Reading Discussion

      We’ll begin our third unit, Typography As Interface, with a discussion of our selected readings:

      • A Software Design Manifesto
        Mitchell Kapor, 1990

      • My website is a shifting house next to a river of knowledge. What could yours be?
        Laurel Schwulst, 2018

      • Unit Nº 3: Reading Responses

      Further reading

      Again we have several additional readings as fodder and reference for your projects:

      • Design Interface: How Man and Machine Communicate
        Gianni Barbacetto, 1987

      • Typeface As Programme
        Jürg Lehni, 2011

      • Interface Writing: Code for Humans
        Nicole Fenton, 2014

      Our Third Project

      Then we’ll go through your last project for the semester:

      Project Nº 3: Binding

      And finally… Images?!

      In a departure from previous years, we’ll discuss images on the web:

      Working with Images

      And a quick demo

      It’s going to be quick on time, but we want to “connect the dots” today, going through some of the particulars of sketching in code and putting multiple pages together into a website. Our agenda:

      1. Make a new repo binding on GitHub, set to Public ( same as before )

      2. Clone it down locally and create a landing page

        • Add an index.html with some basic HTML structure
        • Pull in our reset, locally/​self-contained
        • Also create a common.css there with some basic styles/​size variables
        • Commit/​push, then enable Pages and add the link to the repo’s About section
      3. Make a subpage and stylesheet for sketching

        • Create a folder direction-1/ with its own index.html and sibling style.css
        • Link the HTML to the project’s reset, the root/​common stylesheet, and also its own
        • With relative URL⁠s: ../ means “go up a level”⁠—so our direction points at the reset with href="../reset.css"
        • Do this in the cascade order, “large to small”: reset, common, then direction!
        • Copy in some plain, semantic DOM from your first project
        • Also add a link back to your landing page href="../", somewhere handy up top
      4. Duplicate this three times for your distinct typographic treatments

        • Copy the direction-1/ folder so you have direction-2/ and direction-3/ as well
        • Change something in each individual direction style.css, to easily tell them apart
        • Back on the landing/​root index.html, make a <ul> with links to the directions
        • Since they are children, href="direction-1/" will go down to that folder (and request its index.html)
        • You can keep some basic/​shared styles up in common.css (remember, D.R.Y.)
        • Each direction’s style.css can then be used to sketch their own typographic system

      This is how you will sketch in code!

      For Next Week

      • Select your additional texts for Project 3, Binding, adding them to the doc:

        Project Nº 3: Reading Selection

      • And you’ll get sketching⁠—this time, in code:

        Project Nº 3: Sketching in Code

        With some starter semantic DOM from your first text, develop your three typographic directions. Make these distinct! Not just riffs on the same thing. We want to see variety, to start.

      • When you’ve covered enough with these⁠—to establish and define three different feelings⁠—submit your URL⁠s:

        Submission Form

    • 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

    • Some More JavaScript

    • 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

    • Putting a (Link/​Meta) Bow on It

    • Week Nº 23

      Mar. 11

    • 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”

    • The end