User:Castrobot/research-20150914: Difference between revisions
mNo edit summary |
|||
| Line 1: | Line 1: | ||
http://gadgets.boingboing.net/gimages/ponyebook.jpg | http://gadgets.boingboing.net/gimages/ponyebook.jpg | ||
| Line 72: | Line 71: | ||
==challenging the roles: designer, developer, editor== | ==challenging the roles: designer, developer, editor== | ||
How to integrate the work of the developer, designer and editor into one workflow? | How to integrate the work of the developer, designer and editor into one workflow? | ||
[[File:Corrections_INC-1WEB.jpg]] | [[File:Corrections_INC-1WEB.jpg]] | ||
[[File:idealworkflow.png]] | [[File:idealworkflow.png]] | ||
How can repetition and redundancy be avoided? | |||
Blog posts: | Blog posts: | ||
Revision as of 08:58, 14 September 2015
EPUB positive points
an off-line website
- based on HTML, CSS, JS
- can be used to archive websites
- simple
- pleasant reading experience (when coupled with e-ink screens)
- readable and writable
Calibre Edit function
current possibilities
- generative books
- further explorations of the apparatus of the (scholarly) book
- book trailers
The book of the future
"The book of the future will not simply imitate the forms of a codex migrated onto new platforms … It will arise from an analysis of the functions of each element of design for the purpose of navigation, orientation, representation, reference and commentary and then rethink the ways the capacities of networked electronic environments can extent these functionalities and encode them in a innovative approach to design".
Johanna Drucker Graphesis: Visual Forms of Knowledge Production.
Frustrating EPUBs
EPUB retailers & publishers
System of lock-ins through ebooks are sold
Consumers don't own the ebooks they purchase
Difficulty in sharing the e-books
consumers reading habits surveilled
3 Examples of lock-ins and DRM
Amazon's deletion of Orwell's 1984
E-Book Backup by Jesse England
MIT-Press - locked into Adobe Editions
Verso Watermarking
Bibliotecha: off-line network for book swapping
EPUB Production
challenging the roles: designer, developer, editor
How to integrate the work of the developer, designer and editor into one workflow?
How can repetition and redundancy be avoided?
Blog posts: How to Handle Corrections in a Hybrid Workflow, Hybrid workflow how-to: Making automated workflows, part 1, Collaborative workflows, Making the VolkskrantBuilding.epub
Hybrid Publishing
- Two or more outputs
- One workflow, that branches out
- Connection between source and outputs
tools
- Structured text - Markdown
- Pandoc - document format converter
- Git - distributed versioning
- Makefile - recipe book
- Calibre - ebook viewer, manager, editor
Publishing Pipelines
Within WdKA Publication Station, not obsessed with EPUB.
Beyond Social
- online publication
- work-in-progress
- contributions from outside WdKA
- web and paper
Wikis
- no initial structure: only pages and users
- structure and editorial protocols can be defined by users
- text structures are explicit
- messy and difficult to penetrate: more a writing than a reading space
- API (Mediawiki) can request content from pages programmatically
Publishing Pipeline - CMS
Wiki -> Wiki API -(content)-> Pandoc(conversion) -> Output (static HTML, EPUB, ICML (inDesign Project), visualization, ...)
Beyond Social Outputs
- Website http://beyond-social.org/
- Paper Publication - using browser Web-to-print
- Beyond Social articles & authors map