User:Kim/Projects That May or May Not Be Made
Protocol
- What is it?
- Why make it?
- Workflow
- Timetable
- Rapid prototypes (scratches)
- Write one sentence instruction for a work.
- Make it.
- Previous practice
- Relation to a wider context (personal reader?)
- Choice made
General
- formats
- Workshop (series)
- Tool (?)
- Browser Extension
- Website
- Collection/ Archive
- Reading, Performance
- Newsletter
- Book
- interests
- paratext (footnotes, comments, links, page numbers, postscripts, index)
- server (side)
- manuals, handbooks, encyclopedia
- use, user, hacking, piracy
1
1. What
A collection of (fabulated, imaginary, fictional) interfaces. Not focussing on, but including websites.
2. Why
To counter tendencies of over simplification of interfaces and make space for agency and exploration. To Question 'use'.
3. Workflow
- collect One sentence Interfaces
- small rapid prototype like realisation
- versioning over perfection
4. Timetable
Over a fixed Period (4 Weeks) realize one Interface a day.
5. Rapid Prototypes
One Sentence Interface
- An Interface that gets worn down with use.
- An unconfident (uncertain) interface that needs a lot of reassurance, frequently changes its opinion and is generally viewless.
- An Interface that has no boundaries - You loose yourself in it
- no - exit interface
- An Interface that tells you something about itself.
- An ineffective Interface.
- Text as interface.
- An Interface that situates its user.
- A very active Interface that is made of verbs only.
- An Interface that sabotages itself.
- An urgent Interface.
- a recycled interface like an old, used canvas.
7. Context
User:Kim/reading/N. Katherine Hayles: Writing Machines
User:Kim/reading/Johanna Drucker: Performative Materiality
DATA browser 06 EXECUTING PRACTICES, 2018 User:Kim/reading/Executing Micro-Temporality
2
1. What
The same content in different back ends.
2. Why
To study how th organisation of information impacts its front end presentation and possibilities for interaction/ use. And meanwhile explore what (low tech) options exist besides proprietary platforms or template builders.
3. Workflow
- come up with a content
- put it into aspired back end format
- open question of styling + presentation
5. Rapid Prototypes
A back end that is
- a single txt file
- Table / CSV
- pdfs
- a wiki
- a library (of physical books)
- another website
- a nested List
- a notes app
- a chat
- an etherpad
I made this website entirely based on are.na channels: https://network-matters.xyz/ or this one based on a wiki page: https://hub.xpub.nl/cerealbox/~kim/assessment-frontend/