A Jekyll template for creating books in multiple formats:
- print PDFs for high-end book publishing
- screen PDFs for reading on screen
- a website of books
- epubs for ebook distribution
- Cordova-ready files for for Android, Windows and iOS apps
- MS Word outputs for old-school editing.
Read the guide for much more. The guide is the template in action as a website. You can also download PDF and epub versions of the sample book that the template generates by default.
While you do not need to be a developer, you do need some technical confidence to make books this way. You should be able to use this if:
- you know how to open the command line (aka Terminal or Command Prompt) and enter commands
- you can read this README and feel like you know what's going on.
It's also highly recommended that you have just enough familiarity with Git version control that you can sync your work with GitHub using GitHub Desktop (or similar).
If you happen to be a front-end developer with experience using static-site generators and Node, you'll feel right at home.
The guidance below will get you started. You will also need to consult the docs for more detail as you create books this way. Those are in the _docs
folder here, or you can read the current template docs online, keeping in mind that your project might not include the latest updates to the template.
The fastest way to get working is by using Gitpod. If you open this project with Gitpod, Gitpod will automatically create a virtual machine for you to work on in your browser – no need to install anything on your own computer. To do that:
- Go to this repo's page on GitHub. (This can be the original page or the page for the fork or branch you want to work in.)
- In the browser address bar, insert this before the URL:
https://gitpod.io/#
. Then hit enter. - Follow the prompts to create a Gitpod workspace, using your GitHub account. If you're prompted to choose an editor, we recommend the VS Code (browser) option.
- After a few minutes, your Gitpod workspace will appear: a code editor and a Terminal for you to enter the commands described below.
The first time you work on this project on your machine, run this at the command line, in the same folder as this README file:
npm run setup
Note that if you're using Gitpod, you don't need this step: it's done for you automatically.
Now the Electric Book template is ready to use.
Start by entering this at the command line, in the same folder as this README file:
npm run electric-book
That lists available electric-book
commands and options. You can also use eb
instead of electric-book
:
npm run eb
That's shorter, so we'll use that in the commands below.
The default output
command serves your project as website:
npm run eb -- output
Note that the output
command comes after the free-standing --
, including spaces on either side, after electric-book
or eb
. (This is required by npm when parsing the command.)
That is the shortest command, and implies the default --format
option, web
.
So the full command for the default web output is actually:
npm run eb -- output --format web
Note that each option, like --format
, also has a short alias. For --format
, that's -f
. (Note that one-letter aliases use a single -
.) So the command above is the same as:
npm run eb -- output -f web
Unless you really want the web output, you must specify the output format you want. For example, this command will generate a print-PDF version of the book that's in the book
folder, instead of serving a website:
npm run eb -- output --format print-pdf --book book
Note that the book
folder is the default, so you don't have to specify it. Here's the same command using short aliases. It outputs the default book
:
npm run eb -- output -f print-pdf
If you're outputting a book other than the default book
, you must specify the book folder you want with the --book
(aka -b
) option. For example, this will generate a screen PDF of the book that's in the samples
folder:
npm run eb -- output -f screen-pdf -b samples
Note that when you specify a book with --book
(or -b
), any other books in your project will not be generated or processed at all. A useful effect of this is that if you're working on the web version of a specific book and want your website to rebuild faster after each change you make, specify the book you're working on in your output command. For example, if I run this in the default template:
npm run eb -- output -b samples
then the website output will only include the book in the samples
folder, and not the book in the book
folder (or any other book folders).
The Electric Book template includes a shorter French version of the samples
book. If you want to output, say, a screen PDF of that French version of the book in samples
, you add the --language
option, like this:
npm run eb -- output --format screen-pdf --book samples --language fr
or, using short aliases:
npm run eb -- output -f screen-pdf -b samples -l fr
As mentioned above, the command npm run eb
will list all available commands and options.
For example, if you want your website to rebuild faster by only rebuilding the files you're working on, add the --incremental
option (aka -i
). This particular option doesn't even need a value after the option:
npm run eb -- output --incremental
If you want to enable maths rendering, add the --mathjax
option:
npm run eb -- output --format screen-pdf --book samples --mathjax true
Note that if maths is already enabled in a project's Jekyll config(s), the output script will detect that, and it isn't necessary to pass --mathjax true
as well. (This is unlike older versions of the Electric Book output scripts, which did not check Jekyll configs.)
To get a Word export of a book, use the export
command instead of output
, e.g.:
npm run eb -- export --book samples --format screen-pdf
The check
command checks that your project and its books include the folders and files required. It checks this for any books for which there are folders in _data/works
. To run it, enter this at the command line:
npm run eb -- check
If you want to use the Electric Book template on your local computer, you need to have several things installed:
- Jekyll (which also requires Ruby and Bundler)
- Node.js
- Gulp
- GraphicsMagick (for creating multiformat images)
Optionally, you can also install:
- PrinceXML, required for PDF output. Prince is the only proprietary dependency.
- Pandoc for Word export
- rsvg-convert for good SVGs in Word export (this is already installed on most Mac and Linux machines)
- Cordova, Android Studio, and (on OSX) XCode for building ebook apps.
And of course you should:
- work in a good editor like VS Code, Sublime, Brackets or Atom
- use Git (e.g. with GitHub Desktop) for version control and collaboration.
We use this template for our projects at Electric Book Works. If your organisation wants to use this template and needs help, we can provide paid consulting and support.