SI28/Publication: Difference between revisions

From XPUB & Lens-Based wiki
m (Rephrase pieces intro)
No edit summary
 
(95 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This page documents the process we followed to create the final publication of [[SI28|Special Issue 28]], and it will be included in the publication itself. Woooooo
This page documents the process we followed to create the final publication of [[SI28|Special Issue 28]], and it will be included in the publication itself. Woooooo


== Protocol ==
== General decisions ==


* Include what ought not be printed in <syntaxhighlight inline lang='html'><div class=noprint></div></syntaxhighlight>
* The [[Projects SI 28]] page '''will not be printed''', and it will contain just brief intro and description of each project, with '''a link to the dedicated project page'''.
* The [[Projects SI 28]] page '''will not be printed''', and it will contain just brief intro and description of each project, with '''a link to the dedicated project page'''.
* If parts of other pages appear or are transcluded, '''avoid repetitions''': do not print them. ''E.g. if there is a writing machine in a radio show, only write a short explanation and then transclude the page of the wiring machine within the <code>noprint</code> div''.
* If parts of other pages appear or are transcluded, '''avoid repetitions''': do not print them. ''E.g. if there is a writing machine in a radio show, only write a short explanation and then transclude the page of the wiring machine within the <code>noprint</code> div''.
Line 12: Line 11:


== Workflow ==
== Workflow ==
As decided in the [https://pad.xpub.nl/p/Prototyping-02-12-2025 Prototyping class of the 2<sup>nd</sup> December 2025]:<br>
Dirty wiki scraping based on full consensus while allowing anarchy!
{{:SI28/Publication/Workflow graph}}
===1. Wiki page content===
* Finish the content of all wiki pages you contributed to
* <code>Edit source</code>: Include what ought not be printed in <syntaxhighlight inline lang=html><div class=noprint></div></syntaxhighlight>
* <code>Edit source</code>: make sure the page is structured like the following:
<syntaxhighlight lang="html"><h1>TITLE</h1>
summary / short intro text
<div class=box>
  CONTENT
</div>
</syntaxhighlight>


As decided in the [https://pad.xpub.nl/p/Prototyping-02-12-2025 Prototyping class of the 2<sup>nd</sup> December 2025]:
=== 2. CSS Stylesheet ===
The wiki has 2 important types of CSS stylesheet


[[File:Amazine.gv.png]]
* 1x [[Amazine.css]]: The '''''global''''' stylesheet that is applied to the entire publication
** Please do not edit this css!
* [[Main Page/pagetitle.css|pagetitle.css]]: A stylesheet that '''''only applies to the page with the same title''''', which overwrites the global css ''only inside of the .box class''
** This sheet is a template you can edit locally!
** Check the Content subheading down below for which pages you're responsible to create and upload the PDF + CSS to sergio
Put <code>?action=render</code> after the URL and download both.


[[Amazine_graph|<small>(messy graphviz source code can be found here)</small>]]
==== Edit Footer ====


=== Approach ===
In the <code>pagetitle.css</code> template, on <syntaxhighlight inline lang=css>@page:left</syntaxhighlight> and <syntaxhighlight inline lang=css>@page:right</syntaxhighlight> you’ll find a comment on the code. Make sure to edit them! Only edit the content inside the quote.


Dirty wiki scraping based on full consensus while allowing anarchy!
===== <syntaxhighlight inline lang=css>@page:left</syntaxhighlight> =====
 
# EDIT SECTION – Writing-Machines / Public-Event / Radio-Show
# ADD COMMENT(optional) – you can customize the color of the text
 
===== <syntaxhighlight inline lang=css>@page:right</syntaxhighlight> =====
 
# ADD RELATED PROJECT(optional)
# EDIT SECTION – Writing-Machines / Public-Event / Radio-Show
 
==== <syntaxhighlight inline lang=css>.box</syntaxhighlight> class ====
The wiki page content is contained inside a div with a “box” class. You are free to change the CSS '''''within this box class''''' however please use the page-unique stylesheet. This way, all the pages will have a unified border but we still have creative freedom over the CSS within this box.
 
You can treat the .box class like you would the body.


=== Stylesheets ===
Please also add <syntaxhighlight inline lang=css>.box</syntaxhighlight> in front of any other CSS you code, for example if you want to edit h3 within the box:


* The global, shared CSS we are all going to be using for ''all'' pages is [[Amazine.css]]. We decide together how it should be, following the [[#Protocol]].
<syntaxhighlight lang=css>
* Each of us can include '''their own stylesheet''', on top of <code>Amazine.css</code>
.box h3 {
  color: pink;
}
</syntaxhighlight>


=== <code>make-amazine.sh</code> ===
Feel free to ask a classmate for help!


=== Bash script for automation <code>make-amazine.sh</code> ===
# create a local folder called <q>amazine</q>: <code>mkdir amazine</code>
# create a local folder called <q>amazine</q>: <code>mkdir amazine</code>
# move inside this folder: <code>cd amazine</code>
# move inside this folder: <code>cd amazine</code>
# inside this folder, make a bash script with the name <q>make-amazine.sh</q>: <syntaxhighlight inline lang='bash'>nano make-amazine.sh</syntaxhighlight>
# inside this folder, make a bash script with the name <q>make-amazine.sh</q>: <syntaxhighlight inline lang='bash'>nano make-amazine.sh</syntaxhighlight>
# inside this script, change the wiki page links to the one you want to work with
# inside this script, change the wiki page links to the one you want to work with
# create and edit your own CSS file: <syntaxhighlight inline lang='bash'>nano mypage.css</syntaxhighlight>
# create and edit your own CSS file: <syntaxhighlight inline lang=bash>nano mypage.css</syntaxhighlight>
# then run the bash script: <syntaxhighlight inline lang='bash'>bash make-amazine.sh</syntaxhighlight>
# then run the bash script: <syntaxhighlight inline lang='bash'>bash make-amazine.sh</syntaxhighlight>
# check if this generated a pdf!
# check if this generated a PDF!


<syntaxhighlight lang='bash'>
<syntaxhighlight lang='bash'>
Line 53: Line 89:
</syntaxhighlight>
</syntaxhighlight>


== Pieces ==
=== 3. Upload to Sergio ===
 
See [[SSH proxy jump#Uploading files with FTP using the SSH proxy jump|here]] how to upload to Sergio.
 
Please adhere to the file names listed below in Content
 
* Upload your <code>PAGENAME.pdf</code> inside <code>/var/www/html/amazine/</code> in Sergio
* Upload your <code>PAGENAME.css</code> inside <code>/var/www/html/amazine/styles/</code> in Sergio
* Mark these steps as finished in the [[#Content]] list below, by using the emojis!
* Finished! :D
 
== Content ==
 
<div style='padding: 0 1rem;border: solid 3px #D00'>
<h3 style='text-align: center;'>Important</h3>
'''Wikipage titles + File names:''' Title listed here should be used for wiki page + PDF + CSS file names, but '''replace the <code>/</code> with a <code>_</code>'''<br>
'''Responsibility:''' Name in () is person responsible for the PDF and CSS.
</div>
 
'''Legend''':
🟡 = Content finished;
🔵 = Final proofread done;
🟣 = CSS finished;
🟢 = Uploaded on Sergio.
 
----
 
*[[SI28/Publication/Colophon|Colophon]] (Barbara) 🟡🟣🟢
*[[SI28/Publication/Introduction|Introduction]] (Lea) 🟡
*[[SI28/Index|Index]] (Youjung) 🟡🟣🟢
*Writing-Machines
**[[Writing Machine Directory/statemachines|Writing-Machines/State-Machines]] (KIKI) 🟡
**[[Writing Machine Directory/arnhem|Writing-Machines/Arnhem]] (Phillip) 🟡🟣🟢
**[[Writing Machine Directory/beatles|Writing-Machines/Beatles]] (Ema)  🟡🟣🟢
**[[Writing Machine Directory/deathcorewritingmachine|Writing-Machines/Death-Core-Writing-Machine]] (Ema)  🟡🟣🟢
**[[Writing Machine Directory/glyphica|Writing-Machines/Glyphica-Text-Machine]] (Lea) 🟡
**[[Writing Machine Directory/The Internet Archive Feelings Writing Machine|Writing-Machines/Internet-Archive-Feelings-Writing-Machine]] (Tommi) 🟡🔵🟣🟢
**[[Writing Machine Directory/mudcellpoem|Writing-Machines/Mud-Cell-Poem]] (Youjung) 🟡🟣🟢🔵
**[[Writing Machine Directory/poetrygenerator|Writing-Machines/Poetry-Generator]] (Youjung) 🟡🟣🟢
**[[Writing Machine Directory/walking|Writing-Machines/Psychogeographic-Walking-Machine]] (Lea) 🟡
**[[Writing Machine Directory/reading and interpreting a dotmatrixs scoring|Writing-Machines/Reading-and-Interpreting-a-Dotmatrixs-Scoring]] (Robin) 🟡
 
*Public-Event
**[[Projects SI 28/A story in a story in a story|Public-Event/A-story-in-a-story-in-a-story]] (Barbs) 🟡🔵
**[[Projects SI 28/Gesture Machine|Public-Event/Gesture-Machine]] (Valentin) 🟡🔵
**[[Projects SI 28/The Metathinking Metamachine|Public-Event/The-Metathinking-Metamachine]] (Tommi) 🟡🔵🟣🟢
**[[Projects SI 28/The-Calm-Machine|Public-Event/The-Calm-Machine]] (Sibyl) 🟡🔵
**[[Projects SI 28/Writing Machine Ensemble|Public-Event/Writing-Machine-Ensemble]] (Ema, Daan, Robin) 🟡🟣🟢
**[[Projects SI 28/Water Vessel Dwelling in Temporality|Public-Event/Water-Vessel-Dwelling-in-Temporality]] (Soda) 🟡🔵🟣
**[[User:Lucatorsera/Marginalia|Public-Event/Marginalia]] (Luca) 🟡
**[[Projects SI 28/Love Machine|Public-Event/The-Love-Machine]] (Phillip) 🟡🟣🟢
*Radio-Shows
**[[SI28-Radio-Worm/Week1|Radio-Show/Week1]] (Robin) 🟡
**[[SI28-Radio-Worm/Week2|Radio-Show/Week2]] (Daan) 🟡
**[[SI28-Radio-Worm/Week3|Radio-Show/Week3]] (Ema)🟡🟣🟢
**[[SI28-Radio-Worm/Week4|Radio-Show/Week4]] (Soda) 🟡🔵
**[[SI28-Radio-Worm/Week5|Radio-Show/Week5]] (Lea) 🟡
**[[SI28-Radio-Worm/Week6|Radio-Show/Week6]] (Daan) 🟡
**[[SI28-Radio-Worm/Week7|Radio-Show/Week7]] (Youjung) 🟡🟣🟢🔵
**[[SI28-Radio-Worm/Week8|Radio-Show/Week8]] (Tommi) 🟡🔵🟣🟢
*[[SI28-Glossary|Glossary]] (Valentin) 🟡🔵
 
Front + back cover design (Kiki)
 
== CSS Tips&Tricks ==
 
=== Page break ===
in wikipage HTML, put an empty <syntaxhighlight inline lang=html><div></syntaxhighlight> on the spot you want a page break:
 
<syntaxhighlight lang=html>
<div class=break></div>
</syntaxhighlight>
 
in CSS:
<syntaxhighlight lang=css>
.break {
  break-before: always;
}
</syntaxhighlight>


Pieces the publication is made of (initially copied from [[Dirty wiki scraping#Pieces]]).
=== High resolution images ===
To not have pixelated images, in your wikipage HTML, change image dimensions to something big like 940x940px. Then alter the <syntaxhighlight inline lang=css>img {}</syntaxhighlight> in CSS as you see fit.


* cover
'''Tip:''' If you want it to fill the page and not go over the border, use <syntaxhighlight inline lang=css>width: 100%;</syntaxhighlight>
* [[SI28/Publication/Colophon]]
* [[SI28/Introduction]]
* content
** [[SI28-Glossary|Glossary]]
** [[Writing_Machines_Notebook|<s>Writing Machines Notebook</s>]]
** ''Some'' blog pages:
*** <s>[[User:LEa/blog/2025-10-13]]</s>
*** <s>[[User:LEa/blog/2025-10-30]]</s>
*** <s>[[User:LEa/blog/2025-11-19]]</s>
*** [[User:Youjung/Workshop at Brussels]]
*** [[User:Youjung/Workshop Continues: from Brussels to CCU]]
** All [[:Category:Writing Machines|Writing Machines]]
** All pages belonging to [[:Category:SI28/Radio Shows]]
** ''<s>Event documentation</s> (include some images and docs in the projects pages)''
** All pages belonging to [[:Category:SI28/Projects]]


[[Category: SI28]]
[[Category: SI28]]
[[Category: SI28/Shred]]

Latest revision as of 13:04, 17 December 2025

This page documents the process we followed to create the final publication of Special Issue 28, and it will be included in the publication itself. Woooooo

General decisions

  • The Projects SI 28 page will not be printed, and it will contain just brief intro and description of each project, with a link to the dedicated project page.
  • If parts of other pages appear or are transcluded, avoid repetitions: do not print them. E.g. if there is a writing machine in a radio show, only write a short explanation and then transclude the page of the wiring machine within the noprint div.
  • Links:
    • Do not write the full URL in the text unless we want it to be printed
    • Keep colour change
  • Add here other decisions made

Workflow

As decided in the Prototyping class of the 2nd December 2025:
Dirty wiki scraping based on full consensus while allowing anarchy!

Amazine.gv.png


1. Wiki page content

  • Finish the content of all wiki pages you contributed to
  • Edit source: Include what ought not be printed in <div class=noprint></div>
  • Edit source: make sure the page is structured like the following:
<h1>TITLE</h1>
summary / short intro text
<div class=box>
  CONTENT
</div>

2. CSS Stylesheet

The wiki has 2 important types of CSS stylesheet

  • 1x Amazine.css: The global stylesheet that is applied to the entire publication
    • Please do not edit this css!
  • pagetitle.css: A stylesheet that only applies to the page with the same title, which overwrites the global css only inside of the .box class
    • This sheet is a template you can edit locally!
    • Check the Content subheading down below for which pages you're responsible to create and upload the PDF + CSS to sergio

Put ?action=render after the URL and download both.

Edit Footer

In the pagetitle.css template, on @page:left and @page:right you’ll find a comment on the code. Make sure to edit them! Only edit the content inside the quote.

@page:left
  1. EDIT SECTION – Writing-Machines / Public-Event / Radio-Show
  2. ADD COMMENT(optional) – you can customize the color of the text
@page:right
  1. ADD RELATED PROJECT(optional)
  2. EDIT SECTION – Writing-Machines / Public-Event / Radio-Show

.box class

The wiki page content is contained inside a div with a “box” class. You are free to change the CSS within this box class however please use the page-unique stylesheet. This way, all the pages will have a unified border but we still have creative freedom over the CSS within this box.

You can treat the .box class like you would the body.

Please also add .box in front of any other CSS you code, for example if you want to edit h3 within the box:

.box h3 {
  color: pink;
}

Feel free to ask a classmate for help!

Bash script for automation make-amazine.sh

  1. create a local folder called amazine: mkdir amazine
  2. move inside this folder: cd amazine
  3. inside this folder, make a bash script with the name make-amazine.sh: nano make-amazine.sh
  4. inside this script, change the wiki page links to the one you want to work with
  5. create and edit your own CSS file: nano mypage.css
  6. then run the bash script: bash make-amazine.sh
  7. check if this generated a PDF!
# --------- CSS
# download Amazine.css from the wiki to my local folder
curl 'https://pzwiki.wdka.nl/mediadesign/Amazine.css?action=raw' -o Amazine.css

# --------- HTML
# (OPTIONAL) download local copy of the wiki page as HTML file
# curl 'https://pzwiki.wdka.nl/mediadesign/Writing_Machines%E2%80%93Protocols%E2%80%93Feedback?action=render' -o  specialissuepage.html
# wget -E -k -p -l 1 'https://pzwiki.wdka.nl/mediadesign/Writing_Machines%E2%80%93Protocols%E2%80%93Feedback?action=render'

# --------- PDF
# generate a PDF with weasyprint, for each of your wiki pages
weasyprint -s Amazine.css -s mypage.css 'https://pzwiki.wdka.nl/mediadesign/mypage?action=render' mypage.pdf

3. Upload to Sergio

See here how to upload to Sergio.

Please adhere to the file names listed below in Content

  • Upload your PAGENAME.pdf inside /var/www/html/amazine/ in Sergio
  • Upload your PAGENAME.css inside /var/www/html/amazine/styles/ in Sergio
  • Mark these steps as finished in the #Content list below, by using the emojis!
  • Finished! :D

Content

Important

Wikipage titles + File names: Title listed here should be used for wiki page + PDF + CSS file names, but replace the / with a _
Responsibility: Name in () is person responsible for the PDF and CSS.

Legend: 🟡 = Content finished; 🔵 = Final proofread done; 🟣 = CSS finished; 🟢 = Uploaded on Sergio.


Front + back cover design (Kiki)

CSS Tips&Tricks

Page break

in wikipage HTML, put an empty <div> on the spot you want a page break:

<div class=break></div>

in CSS:

.break {
  break-before: always;
}

High resolution images

To not have pixelated images, in your wikipage HTML, change image dimensions to something big like 940x940px. Then alter the img {} in CSS as you see fit.

Tip: If you want it to fill the page and not go over the border, use width: 100%;