An Attempt at Exhausting Oneself

An eight-week course to explore the versatility of HTML and CSS, critically analyze the unique characteristics of the web medium, and establish yourself as a thoughtful designer who considers ethics and sustainability.

Please arrive on time (13:30) for each course and get in touch as soon as you can to notify me of your absence or lateness

Course Overview

What speaks to us, seemingly, is always the big event, the untoward, the extra-ordinary: the front-page splash, the banner headlines. Railway trains only begin to exist when they are derailed, and the more passengers that are killed, the more the trains exist. Aeroplanes achieve existence only when they are hijacked. The one and only destiny of motor-cars is to drive into plane trees. […] What’s really going on, what we’re experiencing, the rest, all the rest, where is it? How should we take account of, question, describe what happens every day and recurs every day: the banal, the quotidian, the obvious, the common, the ordinary, the infra-ordinary, the background noise, the habitual?

Georges Perec, Approaches to What? from L’Infra-ordinaire, translated and published in English in Species of Spaces and Other Pieces, 1975.

Social media has made visible something that was never new but is now undeniable: the need to curate ourselves in digital spaces that work both as reflection and alternative to so-called “real” life (IRL). Foucault and Butler understood this long before Instagram—the performative nature of identity itself. Yet what digital platforms have done is make this performance explicit, almost mandatory, while promising that technology will help us know ourselves better. We track our sleep, our heart rate, our running routes. We broadcast these metrics as markers of authenticity. Strava, Spotify, Apple Health: these platforms blur the line between self-knowledge and public performance, affirming a peculiar modern fantasy—that there exists a perfected, knowable, quantifiable version of ourselves worth sharing.

Algorithmically curated feeds like TikTok’s — and even ones like Spotify’s and Tinder’s — can connect us with people and ideas that expand our worlds and minds while also making us feel more seen and less alone. But they can also make us feel really alienated, misunderstood, and commodified when they use our own data to show a warped version of ourselves.

Michelle Santiago Cortés, “Because Your Algorithm Says So” on The Cut, published on February 8, 2022.

But something essential slips through this apparatus. Big Data companies monitor every trace of our behavior—online and offline—to construct increasingly precise portraits that serve their interests, not ours. Artificial intelligence refines these portraits further. Yet for all their precision, they cannot capture what remains fundamentally human about us: the fluidity, the indecisiveness, the contradictions, the moments when we do not cohere into any stable identity at all.

It may seem that social media, by making social interaction asynchronous, shifting a portion of it online to an indefinite “virtual” space, and subjecting it all to constant monitoring, measurement, and assessment would not be a recipe for producing a sense of personal continuity. The way our self-expression gets ranked in likes and shares in social media would seem to subordinate identity to competition over metricized attention, dividing peers into winners and losers. And the creation of identity in the form of a data archive would seem to fashion not a grounded self but an always incomplete and inadequate double — a “self partially forced from the body.” You are always in danger of being confronted with your incohesiveness, with evidence of a past self now rejected or a misinterpreted, misprocessed version of one’s archive being distributed as the real you.

Rob Horning, “Sick of Myself” on Real Life Magazine, published on May 17, 2017.

Drawing on Georges Perec’s systematic explorations of the infra-ordinary—“that which is generally not taken note of, that which is not noticed, that which has no importance”—and on Bernadette Mayer’s experiments with memory and journaling practices, this assignment invites you to ask: what if a website could operate as a counter-space to social media? Not a platform for extraordinary moments, but an archive of the mundane.

transparency has become an exercise in addressing biases (I am writing in English and using digital mediums) and in trying to improve as a person and be accountable to myself, others and through time. It’s also about letting go, as in accepting that identity is dynamic and fluid, that all portrayals are biased, that we don’t have that much control of other people’s interpretations about us, and that their portrayals are as valid as ours.

Aarón Montoya-Moraga, “Self-portrait in Open Source (Unfinished)” in Adjacent 4: Bodies and Borders, published in October 2018.

Rather than performing perfection, you are invited to explore how constraint-based, programmatic, and systematic processes can unveil neglected aspects of existence. These methods—the very rigor and limitation that might seem opposed to spontaneity—can reveal what algorithmic systems miss: the texture of daily life, the unspectacular, the overlooked.

Taking the words of Redell Olsen about literature, you are asked to create a website that acts “as an enclosure or provisional park for an already existing wilderness that cannot definitively be contained.” A website that would become a small-scale alternative to the logic of social media platforms—a space organized not around engagement metrics or the extraordinariness of content, but around language, text, and the careful documentation of what it means to move through the world.

Language is laggy, boundless, bounded, overlapping, constrained, situated, uttered anywhere, everywhere, embedded, becoming. Extending ourselves onto a website might not only be an interior, individual practice of preservation, but part of a broader non-linear history that welcomes many visibilities, each with countless lines and opacities.

Chia Amisola, Domain Naming, published in February 2024.

Assignment Brief

Each of you will create a website that is an inventory of your daily life: the elements usually unnoticed and unpublicized. Your goal is to collect a substantial amount of these over time. You have the freedom to choose the content, themes, and formats, and can structure your data in any way you prefer. Your website should be no more than 10MB (10,000KB) in total size and should be created using only HTML and CSS. JavaScript is not allowed.

Step 1, Week 1
Define your System

Before you begin collecting data, you must define the system through which you will observe and document your daily life. What constitutes the “infra-ordinary” for you? What aspects of your life do you wish to inventory? Consider developing a constraint-based method inspired by Perec or Mayer. This might be a temporal constraint—documenting something every hour, every Tuesday, every time you eat—or a spatial constraint where you record everything you notice in a specific location, or a categorical constraint that focuses on particular types of moments: all the things you throw away, all the questions you ask yourself, all the moments of boredom. You might also develop a procedural constraint, recording only through lists, measurements, or overheard conversations.

Step 2, Weeks 2–3
Collect and Accumulate

Begin your systematic documentation. The goal is accumulation rather than curation—gathering a substantial body of material that reflects the texture of daily life over time. Aim to collect for at least two weeks, though longer periods mean richer material. As you collect, think about the unique characteristics of web-based documentation. How does the digital format shape what you can document? What forms can your documentation take—text, image, list, table, timestamp, measurement, description? How do the 10MB size constraints affect your collecting practices? What gets left out, and what does that absence reveal?

Step 3, Week 3
Develop your Taxonomy

With your collected material in hand, develop the organizational structure for your website. How will you categorize, index, and present this inventory? Your taxonomy is not neutral—it reveals your values, priorities, and understanding of the material. Think about whether you will organize chronologically or thematically, hierarchically or flatly. Consider how visitors will move through your material and what connections or patterns you want to reveal—or obscure. Your organizational system might be linear, letting visitors progress in a predetermined order, or rhizomatic, offering multiple entry points through the same content. The structure you choose will shape what can be seen and understood.

Step 4, Week 4
Archive your Collection

Before moving into design, you must send me an HTML page presenting your archive of collected material. The page must include a <p> describing what you collected and how, followed by a <table> in which each row represents one entry. Every entry must follow the same structure across the whole table—consistent columns, consistent granularity. This step confirms your collection is substantial and organized before any design work begins.

Step 5, Weeks 4-5
Design without Designing

Create the visual and interactive language of your website without using graphic design software. The spirit of this assignment is amateurish in the best sense—it seeks to break free from the polished aesthetics of professional web design and social media platforms. Your design decisions should emerge from the materiality of HTML and CSS themselves, the constraints of the 10MB file size, the nature of your content and taxonomy, and the methods available to you without JavaScript. Consider typography as a primary design element—font choices, sizes, spacing, and line length all shape how your content is read. Think about color and contrast, layout and composition, rhythm and pacing as information unfolds across the page. How do these elements relate to the content itself?

Step 6, Weeks 6-7
Build and Refine

Develop your website using HTML and CSS. Remember that the entire website must be 10MB at most. Pay attention to clean, well-structured HTML and efficient CSS without unnecessary redundancy. Optimize file sizes for images or other assets, and test functionality across different screen sizes. Think about how visitors enter and navigate your website and how the interface guides—or doesn’t guide—reading and exploration. The relationship between interface and content matters. Consider moments of surprise, friction, or revelation. Pay close attention to microtypography and detail: line length, leading, and spacing; hierarchy and emphasis; link styling and hover states; margins, padding, and negative space. Even an amateur website is a graphic artifact, and your interface shapes how the content is read.

Step 7, Week 8
Final Presentation

Show your website to the class during a 12-minute presentation. Address what you chose to document and why, how your constraint or system shaped what you observed, and what you discovered through systematic observation. Discuss how the technical and size constraints affected your design decisions and what your website reveals—or conceals—about the infra-ordinary of your life. Be prepared to discuss how your approach differs from social media documentation and the gap between what you intended to create and what emerged through the process.

Learning Goals

  1. Build a contemporary and critical understanding of the web and technology through theories that challenge mainstream assumptions.
  2. Deepen your technical and conceptual knowledge of web and design through a disruptive, critical, and experimental practice.
  3. Explore web tools and their constraints, and get familiar with the structures and paradigms specific to this medium.
  4. Overcome constraints by pushing the limits of what is possible, without fear of failure.
  5. Work openly and generously with your fellow students, and treat design as a collaborative practice.
  6. Propose design solutions that are inventive and grounded in ethical, social, and sustainable thinking.

Readings

You will be expected to read three texts during the block. During small group and individual talks, we will discuss and reflect on these texts in relation to your concepts, process and experiments in development.

  1. Chia Amisola, Domain Naming, published in February 2024, Link
  2. Laurel Schwulst, “My website is a shifting house next to a river of knowledge. What could yours be?”, originally published on The Creative Independent on May 21, 2018, Link
  3. Ruben Pater, Chapter “The Designer as Amateur” in Caps Lock: How Capitalism Took Hold of Graphic Design, and how to Escape it, published by Valiz in 2021, Link

Schedule

Block 4 (3A)

06.04.2026

No class
☀︎  Easter Monday  ☀︎

07.04.2026

13:30

Lecture
Introduction to the assignment

15:00

Individual talks
How do you feel about coding, particularly for the web? Are you interested in or fascinated by digital culture? Present a project from the last 12 months that represents the best your practice. (all students, 5 minutes per student)

For week 2
Write a proposal of ~200–300 words outlining what you will document and why. Describe the constraint or system you’ll use to collect data, the structure and taxonomy of your website, and your relationship to the material. How does the constraint reveal something free-form documentation would miss? How might systematic observation surface what usually stays hidden?

13.04.2026

13:30

Lecture
How to create a clean coding environment?

14:00

Group talks
Clearly present your idea and emphasize the key points of your webzine, using the text you have written as a foundation (groups of 5 students, 6 minutes per student)

14.04.2026

13:30

Lecture
Why shouldn’t I use “position: absolute”?

14:00

Lecture
On feedback

14:30

Peer feedbacks
Present your idea to your peers and share ways of improving it through collective talks

For week 3
Build a raw archive of your collected material, organized according to your chosen system. It might take the form of text files, spreadsheets, folders of images, or handwritten notes to be digitized. You are not yet designing — you are observing and recording. What emerges when you commit to this over time? Does the constraint become generative or restrictive? Does sustained observation change your relationship to the mundane?

20.04.2026

13:30

Lecture
What is image compression?

14:00

Group talks
Present your archive of collected material and your sitemap and discuss how the system you built influenced it. (groups of 5 students, 6 minutes per student)

21.04.2026

13:30

Lecture
What is the “handmade web”?

14:00

Peer feedbacks
Present your idea to your peers and share ways of improving it through collective talks

For week 4
Send me an HTML page presenting your archive. It must include a <p> describing what you collected and how, followed by a <table> where each row is one entry with a consistent structure. Also create a sitemap or structural diagram showing how your content will be organized: your main organizational principles, the navigation, the relationship between sections, and how your taxonomy reflects or resists typical web conventions. What does your organizational system reveal about how you understand your own life? Does it impose order on chaos, or preserve the messiness?

27.04.2026

No class
☀︎  Spring break  ☀︎

28.04.2026

No class
☀︎  Spring break  ☀︎

04.05.2026

13:30

Lecture
What is a “brutalist” website?

14:00

Group talks
Present your archive of collected material and your sitemap and discuss how the system you built influenced it. (groups of 5 students, 6 minutes per student)

05.05.2026

No class
☀︎  Liberation Day  ☀︎

For week 5
Prepare a 10-minute presentation on your research and experiments. Bring visual materials and/or coded prototypes and discuss your next steps.

11.05.2026

13:30

Midway presentations
3 students

14:30

Midway presentations
3 students

15:30

Midway presentations
3 students

16:30

Midway presentations
3 students

12.05.2026

13:30

Midway presentations
3 students

14:30

Midway presentations
3 students

15:30

Midway presentations
3 students

For week 6
Make visual sketches, mockups, or prototypes showing your design approach. These might be hand-drawn, built directly in HTML/CSS, or made through other non-traditional means. Can a website feel intimate, personal, and unpolished in ways that resist the homogenizing force of platform design?

18.05.2026

13:30

Lecture
How to typeset for the web?

14:00

Anonymous peer feedbacks
Display the visuals you prepared to a group of students without providing any additional explanations, and provide feedback on the other students’ work

19.05.2026

13:30

Lecture
How to create simple interactions with CSS only?

14:00

Group talks
Present your visuals and explain how you responded to the feedback from other students. Also discuss any challenges you’re expecting during the coding of your website. (groups of 5 students, 6 minutes per student)

For week 7
Develop your website using HTML and CSS. Pay close attention to microtypography and detail: line length, leading, and spacing; hierarchy and emphasis; link styling and hover states; margins, padding, and negative space. The website should be fully functional, with all technical constraints met. Does your interface fade into the background or assert itself? Does it replicate familiar web patterns or resist them?

25.05.2026

No class
☀︎  Pentecost  ☀︎

26.05.2026

13:30

Lecture
How to publish a static HTML website?

13:45

Lecture
How can I improve my presentations?

14:00

Individual talks
Present what is one problem you don’t manage to solve and why (all students, 6 minutes per student)

For week 8
Publish your website and send me the link along with a folder of your full site (no larger than 10MB / 10,000KB). Prepare a 12-minute final presentation focused on your process, research, and experiments. Fill in the self-assessment form based on the criteria listed below.

01.06.2026

13:30

Final presentations
3 students

14:30

Final presentations
3 students

15:30

Final presentations
3 students

16:30

Final presentations
3 students

02.06.2026

13:30

Final presentations
3 students

14:30

Final presentations
3 students

15:30

Final presentations
3 students

16:45

Results and discussion

Assessments

Assessment in the Coding programme takes three forms, and the way they’re weighted might be surprising. In order of importance: Assessment as Learning, Assessment for Learning, and Assessment of Learning.

Assessment as Learning comes first — and matters most. The goal is for students to develop a critical eye toward their own work and each other’s. This means regular self-evaluation and peer feedback, not as a formality, but as a genuine part of how the course runs.

Assessment for Learning happens mainly through individual talks and the Midway presentation. These are opportunities to get direct feedback and clarify what still needs to happen before the end of the block.

Assessment of Learning is what most people think of when they hear “assessment” — the final evaluation. It measures each student’s response to the assignment against the learning objectives set at the start. It’s about the work, not the person.

The final assessment follows a self-assessment form submission and an 18-minute individual presentation: 12 minutes to present, 6 minutes of discussion. The evaluation is based strictly on what’s presented in that session — no comparisons between students, no personality judgments. Each student is assessed on their own terms, against clear criteria.

Those criteria are listed below.

Creative
Ability

Find creative, original responses to the editorial and technical constraints of the assignment.
Produce web design work that is both coherent and unexpected.

Capacity for
Critical Reflection

Use research to continuously question your own work and its relevance to the brief.
Develop a considered and ethical position, backed by concrete references.

Capacity for
Growth and Innovation

Push through technical difficulties rather than work around them.
Treat constraints as an invitation to rethink the problem, not just solve it.

Organizational
Ability

Build a research process that weaves together editorial, graphic, and technical thinking.
Work consistently and methodically throughout the block.

Communicative
Ability

Articulate your work with precision — say what it does and why it matters.
Present your research in a way that’s clear and easy to follow.

External
Awareness

Ground your practice in current issues, particularly around technology and the web.
Bring the same rigor to graphic and typographic decisions that you bring to everything else.

Capacity for
Collaboration

Draw on the class as a resource — share, question, and build on what others are doing.
Contribute generously to the group, not just your own work.

Student Works

Block 2 (3B)

Ana
Rašević

Conversations with an Algorithm
Visit website

Anna
Srikitkul

Speech of a Train
Visit website

Disha
Swamininathan

Map of Words
Visit website

Ema
Liukenskyté

vinted???
Visit website

Florens
Deichmann

Finding Joy
Visit website

Hugo
Jonker

Excerpts Of A Few Months
Visit website

Jakob
Blessing

A Shadow Wanders The Walls Of These Halls
Visit website

Janine
Heckmann

Ritualized Moments of Awareness
Coming soon

Julie
Laures

On Dishes, Love And Maintenance
Visit website

Kaeden
Lewis

Trash Tracker
Visit website

Kaya
Chobanova

Unsolicited Advice
Visit website

Keren
Ehrli Schmid

Word Check
Visit website

Misha
Bojinova

Flaws of Flows
Visit website

Patricia
Scurtu

Impostor Syndrome
Coming soon

Petra
Ahola

Noting the Ordinary
Visit website

Puck
Pruim

Woolgathering
Visit website

Sasha
Dima

Documenting until Death
Visit website

Stan
van der Made

Print Diary
Visit website

Teun
Hanselman

Buried City/Blue Gate
Visit website

Theodora
Fischer

Proof I lived
Visit website