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

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

  • Project “Index”

    May 15

  • Students will create a landing page for their Typography & Interaction projects from this year.

    The goal of this project is to cover, contextualize, contain, and consolidate your work from this course in one place⁠—an Index⁠—for what you’ve created here in design and code. This responsive page should contain links to each of your projects, some form of introduction and context around them, and also information about yourself as their creator. It will then function as a “business card” for you as a designer who can code, demonstrating your presence and prowess in this medium.

    Connecting your work

    To start, we’ll create a username.github.io repo. This is a special name that GitHub will make directly available at https://username.github.io/, as a parent/​index to your existing project repos/​subfolders.

    For this initial milestone, we want a aesthetic and functional MVP (Minimum Viable Product)⁠—meaning it is not at all done, but it works⁠—and can be “launched.” In our context, this means it has semantic HTML with at least your name, links to each of your three projects, and is responsively styled in CSS. Here we want to see some basic color, typography, and spacing/​hierarchy considerations⁠—make it look nice!

    Submission Form
    Your basic, styled “MVP” repo/​URL, to start.

    Due Jan. 28

    Adding context and form

    Following our fourth project, we’ll be adding it to our Index.

    In this milestone, we’d then like to see additional context provided⁠—for you, and for the project links. This could be in images, a short description/​write-up, or some combination or other approach. Put yourself in the mind of a visitor unfamiliar with you and with our course! And situate them.

    Design-wise, this additional content will likely necessitate more layout considerations. Here we’d like a particular focus on the viewport⁠—this is a contained experience, and we want it to feel considered and deliberate in the browser context.

    Submission Form
    Mid-way through, with more information and layout.

    Due Mar. 4

    Wrapping it up

    Likewise after our fifth project, we’ll add it to our Index, completing the page content.

    This last milestone should then focus on making the page fully finished⁠—refining our styles, editing our content, adding metadata, a favicon, etc. Here too is where we’d like to tastefully incorporate some JavaScript/​interactivity, if we haven’t before⁠—again showing a considered and deliberate use of the medium.

    Submission Form
    Your last course work, at the end of the semester.

    Due May 15

    Our expectations

    Work on this page will extend across the Spring semester, and it is due after everything else. It won’t be your primary focus⁠—that will be your fourth and fifth projects⁠—but we expect progress over the arc of the course.

    Importantly, we want this to be a reflection of your own personal design aesthetic. It needs to be functional, but above all, should imbue your taste in its design. We want it to be something you are proud of!

    We won’t be formally presenting this work, as with our other projects, but are happy to provide feedback during/​after its completion.

    Some basic requirements

    • It only needs to be a single page.

    • In the end, it should clearly introduce you, your projects, and link to all five of them.

    • Include a brief README.md for the repo, too⁠—with links to the repos for your projects.

    • The page should also contain some basic contact information, at least an email⁠—but the more connections to your online presence, the better: your portfolio, social networks, GitHub profile, etc.

    • Of course, this will be a live, public URL.

    • It should be fluidly responsive, as we do, working on any device.

    • We’d like to see some JS incorporated, for an interactive flourish.

    Everything else is up to you. Make it yours!

  • The end