Editing Hybrid publishing resources (section)

= 4. make book.epub =

== 4.0 make book.md ==
'''You don't have to perform this step, the makefile does it for you.'''

It generates a single Markdown file <code>book.md</code> and save it it inside the <code>md/</code> folder.

<code>book.md</code> consists of the content from all the individual Markdow files inside the <code>md/</code> folder, in alphabetical order (00 to ZZ). 

If you want to '''change the order the publication, you can change the filenames in order to do so'''. 

'''Markdown filenames should NOT contain spaces or dots, except for the extension''' <code>.md</code>


== 4.1 make book.epub (EPUB) ==
Produce the epub file: <code>make book.epub</code>


== 4.1.1 Essential files for EPUB ==
To produce an EPUB a few files are needed, namely:
* cover image <code>epub/cover.jpg</code>
* metadata <code>epub/metadata.xml</code> 
* CSS stylesheet  <code>epub/styles.epub.css</code> 


These files will strongly influence the EPUB's outcome, and consequently should be edited for each publication.


== 4.1.2 Fonts (optional) for EPUB == 
<code>lib/</code> is folder for storing custom fonts, that will be used in the EPUB

If you choose to use fonts, make sure to '''change the makefile to include the use of fonts in the makefile epub rule''', such as in the rule bellow, where <code>--epub-embed-font=lib/UbuntuMono-B.ttf \</code> is added to allow for the use of the Ubuntu Mono font. Also include the font on the EPUB style-sheet with <code>@font-face</code> rule

== 4.1.3 EPUB check ==
The health of the created EPUB can be checked with http://validator.idpf.org/


== 4.1.5 make book.epub : An iterative process ==
This work is in many way as cyclical  process, where you work in circles: changing the source files (markdown files, the EPUB's stylesheet, the EPUB's metadata) and seeing the results of those changes in Calibre (or other ebook-viwerer)



-----