Grad Publication 2026

XPUB Graduation 2026

pad link (and to do from may 22nd): https://pad.xpub.nl/p/gradpub-meeting-220526

Pricing of the publication

   

Backend/software : literally impossible to calculate as it is part of Kim Kleinert's graduation project.

Git Café (technical support): 3h

Graphic Design: 10h

Writing: about 1h per student, so 15h in total (not including the introduction written by course director Michael)

Editing: 6h

Printing: 30h

Binding: 4h

Total:

Material Cost:

Paper: 400€

Printing: 9€/book. Since that's 150 books, that's1350€. We technically didn't pay for that as it is part of the Master Budget though

-> 1750€ in material cost ONLY, which means each copy costs 11.70€ to print.

Adding labour:

a minimum of 68h of labour. If paid minimum wage (which it shouldn't, we are all professional graphic designers and we should be payed a freelance rate), that's 1020€. 1020/150 is 6.80€ per copy

Guidelines for editing the glossary

Git repository link

Link to the word list

repository structure

├── README.md
├── assets
│   ├── images
│   └── media
├── students
│   └── student-template.md
└── words
    └── word-template.md

• each word in the glossary has its own markdown file inside of words/
• additionally, each student has their own markdown file inside of students/
• images can be uploaded in assets/images/
• other media (video and audio) can be uploaded in assets/media/

general

amount of contributions: contribute minimum 5 words (contributions can be short!) there is no upper limit
length of contributions: max 1500 characters
images: please upload high resolution images that can be used for printing, we wil take care of web compression
referencing: please use harvard style ~ more details soon
footnotes: no

steps for editing the glossary

1. open the words/ directory
2. make a file for the word you want to contribute to (copy the word-template.md file and rename it, no spaces or special characters in title)
3. if the file for this word already exists, skip 2.
4. to edit the files we write markdown language (cheat sheet and basic syntax overview) with a few tricks:
   1. to ensure that edits have a class with their contributor name, contents are wrapped in []and followed by {.username} (see word template)
   2. on the top of the markdown file we have a yaml metadata block. please here add the files glossary word in full length (spaces etc allowed) and your contributor / user name to the list

steps for editing student pages

1. open the students/ directory
2. create a file for yourself (copy the student-template.md file and rename it, no spaces or special characters in title)
3. fill in the yaml metadata information in the top of the document
4. add your project description text underneath (no title, formatting etc needed)

tips for editing

• don't over explain yourself, leave things out, be synthetic and fragmentary
• think of the word in its multiple uses (fields, meanings etc)
• do you maybe have a personal relation to this word? (where you first learned or used it, or how you understand it?)
• did you encounter a definition for this in your research? and do you agree with / use the word this way?
• make it fun! and have fun! dont overthink or overly formalize your entries
• when contributing, think of not only your final project but your research and process (you can also add things that you did not include in your project in the end)
• visual content makes things more interesting! think: screenshots, drawings, diagrams, memes, process pictures …
• < add your tip here >

Guidelines for words

Guidelines to come up/ add words to the XPUB glossary

This is not a strict protocol, because personal process may vary to add to the list.

Please don't take more than 20min to add your words in, it's supposed to be a fun process!

1. Add between 1 and 5 words to the list
2. Try to only add 1 word that is very conceptual/general (i.e: care, labour, feminism etc)
3. Add words that are very specific to your project!
4. Don't add synonyms of a word already present in the list (and don't double the words either)
5. Words don't belong to anyone. Just because you propose it doesn mean it's 'your' word... but anyone should / can add to the content under this word in the publication.
6. Words can be made of 2 words (i.e: reproductive labour). If an umberella term is already in there (here "Labour"), no need to add your word, you can contribute withe the more specific term in the content later

Tips:

• can you think of a concept?

• think of a term that already relates to 5 different projects
• a term that is very specific to you? one that comes up repeteadly in your research?
• a term or concept that you learned during your research?
• a word you're intrigued about because someone in the class said it but it's not in the list?
• a word that defines the class as a group?

Note: We WILL edit, especially in the content later on, mainly for content clarity, spelling mistakes, or repetitions.

WORD LIST

https://pad.xpub.nl/p/gradpub-words

from pad may 14.

• tools
  • publishing tools (or "tools for publication making")
  • tool-making
  • counter-tools
• language
  • metadata (added to git)
  • title (added to git)
  • Meaning-Making
• craft (added to git)
  • webcraft
  • witchcraft
• materiality
  • embodiment [or the other way around, open to interpretation]
• diy radio making (added to git)
• Technology
• Alternative
• Imaginaries
• games
  • toy
• development
• web standards
• knitting (added to git)
• capitalism
  • technocapitalism
• time
• efficiency
• information delivery
• unlearning
  • technology (duplicate?) !attention: if there are word duplicates, make sure to not name the .md files the same way!
  • language (duplicate?) !attention: if there are word duplicates, make sure to not name the .md files the same way!
• maintenance
  • repair
  • production means (tbd)
  • infrastructure (tbd)
• Magic
• Perception
• references
• resistance (added to git)
  • agency
  • practices for resistance
  • human-centered
  • feminism
  • Luddite
  • community
• invitation (added to git)
• license (added to git)
• dead media (added to git)
• collaboration
  • workshops
  • articulation work
• practice/praxis
• memes
• server
  • self hosting
• fandom
• intention
• border
• veil
• bureaucracy
  • migration

Timetable

WHAT needs to be done WHEN

WEEK	WHAT	DEADLINE
(1) 20-26.4	decide on methods make detailed plan for the upcoming weeks	thursday 23.4
(2) 27.3-3.5 (break)	maybe first protocols for writing	-
(3) 4.-10.5	?	-
(4) 11.-17.5	?	-
(5) 18.-24.5	Git cafe (20.5.) and deadline for content 22.5.	-
(6) 25.-31.5	finalize the content	-
(7) 1.-7.6	Testprinting and then actual printing	5.6
(8) 6.-14.6	binding	12.6
(9) 15.21.6	cutting	19.6

TO-DO

Physical Publication

• deciding on paper
• buying paper
• anything we need to do regarding printing? (maybe ask michael or helen if they have unlimited printing or someone tops up money on their card so we can print more than 10 pages :))

Website

• ??

Archive

pad links:

• GRAD PAD general https://pad.xpub.nl/p/GradPub2026
• (Martina & Feline) https://pad.xpub.nl/p/XPUB2-prototyping-trim2-WEEK-5
• (kim & chrissy, absent: Tessa & Imre) https://pad.xpub.nl/p/030226prototyping
• (sliding questions) https://pad.xpub.nl/p/gradpub26-sliding-scale
• (discussion of sliding questions) https://pad.xpub.nl/p/XPUB2-prototyping-trim2-WEEK-10
• (eleni) https://pad.xpub.nl/p/XPUB2_Meeting_070426

other:

freds page calculator:

print run/edition: (at least) 100 copies

• copies for the XPUB archive: (at least) 5
• ...

thesis inclusion:

1. one publication: projects
2. one publication: projects + full theses
3. one publication: projects + theses excerpts
4. one + 1/2 publications: projects, theses printed individually (assemble your own reader by choosing the ones you're interested in)
5. two publications: projects, theses

formats:

may be subject to the publication group and not entire class

• website
• print
• web to print
• how does this relate to: https://project.xpub.nl/ ?
• what is the role of the exhibition itself and material we 'need' for it? (exhibition website, flyer etc) how (if at all) do grad pub and exhibition material relate to another?

Proposed Prototypes

1. portal hopping (content)

User:Eleni/Collective Publication Prototype

Method: 'Portal Hopping' exchanging methodologies by entering each others (research) universe

implementation:

• every student has a mini booklet
• in there a protocol, performed by other students + documented
• snippets of the thesis and documentation of the project

Thesis: not fully included or in separate publication

2. the glossary we never made (content)

https://hub.xpub.nl/cerealbox/~kim/gradpub-prototype/

Method: agreeing on common terms, project (excerpts) that relate to this term are presented next to it and become its explanation (could possibly be extended into theses as well)

implementation:

• coming up with overlapping terms
• selecting snippets of our project (documentation, process ...) and assign them to the terms
• breaking up linearity / separation: projects are not presented individually but only through terms

Thesis: variable

3. Chrissy (form)

organizing content parallel, interacting with each other, breaking up with fixed sequentiality of book

sticker sheet with a sticker of each project

Interviews + Projects

commenting section could be interacting with the main text

things can run in parallel

4. Feline & Martina (form)

2 books in 1: process book + theses book

(layout and how content is organized / selected still open)

5. GitPub (form + process)

• assuming we make a html to print publication (markdown files as input format)
• keeping track of changes, files etc we compile them in a git repository
  • students could upload and update their own project files (or protocols or glossary terms etc)
• using git produces metadata such as author names, dates, commit messages
• including the metadata in the grad publication it becomes a record or our process of making

• 

  GitPub prototype

(demo)

unsorted ideas

(relevance check?) / are they off the table

• screenshots of work in progress
• year book