Anonymous
Not logged in
Talk
Contributions
Create account
Log in
Publication Station
Search
Editing
Courses/Hybrid publishing resources
From Publication Station
Namespaces
Page
Discussion
More
More
Page actions
Read
Edit
History
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
<slidy theme="a" /> == publicationstation.wdka.hro.nl/wiki == <span style="background:#FF248D">'''Hybrid Publishing'''</span> ==Focus== '''Transforming a source (manuscript) into multiple publishable outputs, within a hybrid publishing workflow''' ==Hybrid Publishing Workflow== # various outcomes from one workflow # constant connection between source-content and outcome # avoiding repeating tasks ==Hybrid Publishing Workflow== [[File:hybrid-workflow.png]] http://networkcultures.org/blog/publication/from-print-to-ebooks-a-hybrid-publishing-toolkit-for-the-arts/ [https://raw.githubusercontent.com/DigitalPublishingToolkit/Hybrid-Publishing-Toolkit-for-the-Arts/master/trailer-From_Print_to_Ebooks:_a_Hybrid_Publishing_Toolkit_for_the_Arts.gif EPUB trailer] == How?== How can we achieve a publishing workflow where we can go '''from the source''' (a word document, a wiki page, a webpage) to several outputs (an EPUB, a website, an animated gif, an inDesign project)? == Structure == By putting the '''content into an explicit structure''', which can withstand those transformations. So what is a title (heading) in a format, remains a title when translated to a different format. == How to achieve explicit structure? == An explicit structure is achieved by '''marking the text''' with structural information. '''marking the text = markup''' == Markup languages == [http://en.wikipedia.org/wiki/HTML HTML]: <source lang="html4strict"> <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> </source> [http://en.wikipedia.org/wiki/Wiki_markup Wiki markup]: <pre> = 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 </pre> [http://en.wikipedia.org/wiki/Markdown Markdown]: <pre> # 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 </pre> == Pandoc == [http://johnmacfarlane.net/pandoc '''pandoc''']: software for converting between markups with [[File:pandoc_diagram.png]] == ****************** == == mark a text in MS Word/Libre Office == create a '''.docx''' file and mark it up with a few of the following paragraph and characters styles: * headings * body text * block quotes: indented blocks of text * footnotes * hyperlinks * Preformatted text * Bold * Italics Save in '''.docx''' == convert == Convert your docx file into a an HTML file using Pandoc. :shell <pre>pandoc -f docx -t html5 -s input.docx -o output.html</pre> '''pandoc''' - program dedicate to the conversion between different markups. '''-f''' - option standing for “from”, is followed by the input format; '''-t''' - option standing for “to”, is followed by the output format; '''-s''' - option standing for “standalone”, produces output with an appropriate header and footer; '''-o''' - option for file output; '''input.docx''' - docx input filename - you need to replace it by its actual name == convert once more, now toward Markdown == <code>-t markdown</code> Option: toward Markdown <code>--atx-headeres</code> Option: use nice Markdown headers == Why Markdown ? == * simple * only '''one way''' to create a structure * compatible with HTML, but easier to read and write * allows the inclusion of HTML tags. * any plain text editor such as [http://www.sublimetext.com/ Sublime Text] or [https://wiki.gnome.org/Apps/Gedit Gedit] can edit Markdown files. * there are WYSIWYG Markdown editors such as [http://macdown.uranusjr.com/ MacDown]. == ******* == {{:Hybrid_publishing_resources}} ==software used== * '''Shell terminal''' - a text-based interface to your file system. there are plenty of terminal tutorial online, here are some: ** http://mac.appstorm.net/how-to/utilities-how-to/how-to-use-terminal-the-basics/ ** http://computers.tutsplus.com/tutorials/40-terminal-tips-and-tricks-you-never-thought-you-needed--mac-51192 ** http://pzwart3.wdka.hro.nl/wiki/Null/Terminal * [http://johnmacfarlane.net/pandoc/installing.html '''pandoc'''] - markup converter software * '''plain-text editor''': [http://www.sublimetext.com/ Sublime Text] or [https://wiki.gnome.org/Apps/Gedit Gedit] * '''Markdown''' syntax: http://daringfireball.net/projects/markdown/syntax provides a good overview not only of the syntax, but also the philosophy behind Markdown.
Summary:
Please note that all contributions to Publication Station are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
Publication Station:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation
Main navigation
Main page
Printmaking Studio
Print Studio
Dig. Publishing Studio
Namespaces
Grafiwiki
Random Page
Log in
Wiki tools
Wiki tools
Page tools
Page tools
User page tools
More
What links here
Related changes
Page information
Page logs