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

    • Students will collaboratively assemble, connect, and present a collection using Are.na as a CMS (Content Management System)⁠—and will then design and build an interface to explore and understand it, using its API (Application Programming Interface).

      The goal of this project is to apply all the skills you’ve learned thus far in a media-based project⁠—connecting varied content, tools, and form together. You will collect and then organize items on a theme, before giving it shape and structure in the form of a website.

      The site should contain all the contents of the collection, as well as an explanation of the organizing principle⁠—highlighting the connections between its items. The design of the website should reflect this theme in its interface⁠—and allow for interaction within it. We will introduce and use JavaScript to facilitate this, understanding how it meshes with HTML and CSS to dynamically render and manipulate pages. The final website will, of course, be responsive.

      Assemble a Collection

      Assemble a collection around a theme of your choosing. This topic should start from your own interest, but be aimed at broader use and collaboration from others.

      Gather and link your items in an Are.na channel, taking care to edit the metadata it applies for each. (We should not see default, junky filenames and such as titles.) In the channel description, explain the idea behind your blocks and why they constitute a collection. As you curate this grouping, consider what brings them together⁠—what are their links to each other?

      You should have at least 30 items, to start. They should include all the Are.na content types for a varied mix of audio, images, links, documents, text, video. We expect at least one of each type of media (not just images and links), but the best collections are more evenly distributed across all of the types.

      Everything in your grouping should be collected⁠—that is, things you did not create yourself⁠—and there should be a clearly identifiable, cohesive theme. We’d also like some content to come in “fresh” from the web (creating new blocks), not just linking of existing blocks already on the site.

      The collection is the foundation for the other steps! Be deliberate in your curation and metadata.

      Here are some channels for reference and inspiration:

      • Typography and Interaction, Too
        Our example channel showing different media types!
      • Eggs in Art and Design
        Laurel Schwulst
      • How to Think About Thinking
        Glenn Mendonsa
      • Ocean
        Bryce Wilner
      • What Is a Digital Garden?
        Sarah Holloway

      Be sure the channel is set to Closed (not Private ) so we can see it! When you are done, submit a link to your channel.

      Submission Form
      Send us a link to your channel!

      Due Jan. 28

      We’ll unpack the rest of the milestones next week!

    • 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

  • The end