SI28/Publication: Difference between revisions

From XPUB & Lens-Based wiki
Line 12: Line 12:


== 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>
As decided in the [https://pad.xpub.nl/p/Prototyping-02-12-2025 Prototyping class of the 2<sup>nd</sup> December 2025]:
Dirty wiki scraping based on full consensus while allowing anarchy!
 
{{:SI28/Publication/Workflow graph}}
{{:SI28/Publication/Workflow graph}}


=== Approach ===
===1. Wiki page content===
 
* Finish the content of all wiki pages you contributed to
Dirty wiki scraping based on full consensus while allowing anarchy!
* <code>Edit source</code> and make sure the page is structured like the following:
CODE BLOCK


=== Stylesheets ===
=== Stylesheets ===
* 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]].
* 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]].
* Each of us can include '''their own stylesheet''', on top of <code>Amazine.css</code>
* Each of us can include '''their own stylesheet''', on top of <code>Amazine.css</code>


=== <code>make-amazine.sh</code> ===
==== 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>

Revision as of 15:24, 3 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

Protocol

  • Include what ought not be printed in <div class=noprint></div>
  • 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 and make sure the page is structured like the following:

CODE BLOCK

Stylesheets

  • 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.
  • Each of us can include their own stylesheet, on top of Amazine.css

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

Content

Important

Wikipage titles + File names: Title listed here should be used for wiki page + PDF + CSS.
Responsibility: Name in () is person responsible for the PDF and CSS.

Legend

🟡 = Content finished 🟣 = CSS finished 🟢 = Uploaded on Sergio


Front + back cover design (Kiki)