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

    • Week Nº 26

      Apr. 8

    • Week Nº 27

      Apr. 15

    • Project Nº 5: “Functions”

      Apr. 22

    • In this capstone project, students will identify a problem⁠—whether in their own life, or in the lives of others. They will then design and implement their answer to this problem using the tools, technologies, and techniques they’ve learned in this course.

      The problem should be something they can realistically and feasibly hope to solve⁠—or at least improve, with what they know, can learn, and in the time they have. This isn’t a hypothetical thing; this is an actual thing. Students will research and understand this problem, before conceptualizing and building a web-based solution.

      From its very beginnings, the web has been open to participation. If you didn’t like how was, you could spin up your own site. If there was something you wanted it to be and it wasn’t out there, you could bring it into the world. This is fundamental to the web, as a medium.

      And the web’s utility has been defined, in no small part, by individual people trying to meet a specific need. Many sites, even today⁠—after decades of growth and commercialization⁠—were started to solve a problem, whether for a specific individual or for a community.

      These sites, and the web, proliferated when others found them⁠—as the desire of one is often the desire of many. And online, you can “cast a large net.” People have found shared joy, confusion, interest, and ultimately usefulness in the web. (Among other things.) And this is at the core of its ubiquity.

      The goal of this project is to give students the time and space to explore a topic of their own interest, within the lens of the material we’ve covered in this course. The final deliverable will likely be a website⁠—though it doesn’t strictly have to be. We do, however, require that it make use of the fundamental web skills of HTML, CSS, and JavaScript we have learned here together.

      Students should focus on a strong conceptual base⁠—as the project will rest entirely on their own idea. And then we will use the rest of the semester (and of our course) to tackle the problem.

      Define Your Problem

      You’ll identify three (3!) distinct, possible problems you can consider:

      • The problems could be mundane, little annoyances; they could be some bigger, vital difficulties.

      • It could be something in your daily life, or out in the world, or in your community.

      • It is important that these problems are interesting and meaningful to you, whether they affect you directly or not.

        We’re not swapping! They are yours.

      • Don’t be afraid to push the conceptual boundaries of a “problem”⁠—but it can also be something straightforward.

      • Consider also problems that will allow you to research and conceptualize your solution thoroughly. Have “runway.”

      • Like any function, your project should take an input and have an output. It should transform the input, to answer the problem.

        Ask yourself: what are my inputs; what are my outputs?

      • And again, your projects should be achievable and address real concerns. Where can you “make a dent?” We have 7 weeks now; can you approach it in that time?

        Framed as small, medium, or large⁠—shoot for a medium!

      Do this in a (nicely-formatted) Google Doc. For each problem:

      • Write a paragraph (100–150 words each) describing its nature and how you hope to solve or improve it.

      • Each proposal should include some basic background context for the problem at hand, as well as a brief outline of how (conceptually, practically, etc.) you might address it with what you know and the near horizon of what you can learn.

      • Separately, unpack and identify what you think the challenges will be for this particular problem.

      • A goal here (always) is to challenge yourself⁠—tell us what you are hoping to learn from working on it!

      Submission Form
      When you are done, submit your link⁠—make sure that it is shared to all newschool.edu accounts!

      Due Mar. 11

      Balance challenging but achievable

      If you don’t give yourself both enough latitude and limits here, you will be struggling later. We do not have a week to burn on not-enough /​ too-much concepts!

      We will unpack the rest of the project and its milestones next week!

    • Week Nº 28

      Apr. 22

    • Week Nº 29

      Apr. 29

    • Week Nº 30

      May 6

    • “Everything Else”

  • Project “Index”

    May 15

  • The end