Courses/Hybrid publishing

From Publication Station
Revision as of 14:05, 4 March 2016 by Andre (talk | contribs)

<slidy theme="a" />

practicals


Plan

  • Hybrid publishing.
  • Motivations, concepts, tools, strategies, formats that have been present in hybrid publishing efforts of WdKA. 
  • Role and possibilities for publishing in an art school. 
  • Presentation publications developed to date and in-progress. 
  • Inauguration the device lab.


Why publishing?

  • hybrid publishing as an extension of efforts from Publication station - establishing dialog between analog & digital 
  • continuation of Digital Publishing Toolkit project & From Print to Ebooks – a Hybrid Publishing Toolkit for the Arts
  • publishing as a way to expose the research undertaken within WdKA
  • publishing as a learning tool


How hybrid?

Hybrid publishing

Ludovico quote on hybrid publishing


hybrid publishing works

Books Scapes, Julien Levesque, 2012

http://p-dpa.net/wp-content/uploads/2015/03/Screen-Shot-2014-02-15-at-17.17.18-600x150.png


E-Book Backup, Julien Levesque, 2012

http://p-dpa.net/wp-content/uploads/2015/03/9_ebookbackup4-300x225.jpg


Epicpedia Annemieke van der Hoek, 2008

Epicpedia.png


Multichannel publishing workflows

  • ePub
  • PDF
  • self-contained single-file HTML e-books
  • Comic book Archive

Multipleouptus.svg

Tools for hybrid publishing

open source, simple tools that work in combination, forming publishing pipelines


Hands-on exploration of strategies and tools

Markups

"In electronic processing of texts, this hierarchical ordering [...] as well as additional reading aids such bold or italic text, is made possible by using specific formatting codes. This process is called markup and the codes are called markup element"[1]

plain text files

Are only constituted by text. No images, no visual markings.

Are edited using plain text editors and NOT word processors.

Can displayed using the terminal cat myfile.txt will print the content of myfile.txt

Markings are done using (special characters)


Different Markup languages

Each markup uses a different marking syntax

HTML:

<h1>Revenge of the Text</h1>
 <p>There is a room in the <strong>Musée d’Orsay</strong> that I call the <em>room of possibilities</em>.</p>
 <p>That room contains:</p>
 <ul>
  <li>a snow flake</li>
  <li>the end of a cloud</li>
  <li>a bit of nothing</li>
 </ul>

Wiki markup:

= Revenge of the Text =
There is a room in the '''Musée d’Orsay''' that I call the ''room of possibilities''.

That room contains:
* a snow flake
* the end of a cloud
* a bit of nothing

Markdown:

# Revenge of the Text
There is a room in the **Musée d’Orsay** that I call the *room of possibilities*.

That room contains:
* a snow flake
* the end of a cloud
* a bit of nothing


Do

Create one plain-text file

Using either in HTML or Wiki syntax.

You can:

Save it dedicated folder.


turn this file into into other formats

Pandoc - a markup converter 

If you need to convert files from one markup format into another, pandoc is your swiss-army knife

Pandoc diagram.png


Pandoc - converting to HTLM

Pandoc - converting to ePub

converting to single-file self-contained e-book

  • HTML - web    (options: --standalone, --css, title, etc - so they get a sense of the options)  
  • HTLM - self-contained mulimedia e-books based on single HTML files 
  • EPUB (options: --epub-stylesheet, --epub-cover, --epub-chapter-level)



Epub An editable format

Calibre's edit book function to 

  • open an epub
  • navigate structure 
  • change content, style, metadata


converting to PDF

A complicated case.

Different approaches tried:


references