SI28/Publication: Difference between revisions

From XPUB & Lens-Based wiki
(Add publication workflow)
Line 10: Line 10:
** Keep colour change
** Keep colour change
* ''Add here other decisions made''
* ''Add here other decisions made''
== Workflow ==
As decided in the [https://pad.xpub.nl/p/Prototyping-02-12-2025 Prototyping class of the 2<sup>nd</sup> December 2025]:
=== 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 <code>Amazine.css</code>
=== <code>make-amazine.sh</code> ===
# create a local folder called <q>amazine</q>: <code>mkdir amazine</code>
# make a bash script with the name <q>make-amazine.sh</q>: <syntaxhighlight inline lang='bash'>nano make-amazine.sh</syntaxhighlight>
# 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>
<syntaxhighlight lang='bash'>
# --------- 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/Writing_Machines%E2%80%93Protocols%E2%80%93Feedback?action=render specialissuepage.pdf
</syntaxhighlight>


== Pieces ==
== Pieces ==

Revision as of 15:39, 2 December 2025

Working page for the publication of Special Issue 28.

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:

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

make-amazine.sh

  1. create a local folder called amazine: mkdir amazine
  2. make a bash script with the name make-amazine.sh: nano make-amazine.sh
  3. change the wiki page links to the one you want to work with
  4. create and edit your own CSS file: nano mypage.css
# --------- 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/Writing_Machines%E2%80%93Protocols%E2%80%93Feedback?action=render specialissuepage.pdf

Pieces

Pieces of the making the publication (initially copied from Dirty wiki scraping#Pieces).