Technical overview

To set up the workflow, you still have to have some technical expertise. Once it’s set up, non-technical editorial team members with a couple of hours training (taught or self-taught) can add and edit books in it.

The technical team members who run the workflow need to be familiar with:

How it works

Very broadly, this is how the Electric Book template works.


A project folder (which you should track in Git as a repository) can contain one or more related books. Its folders and files follow the standard Jekyll structure. We store each book’s content in its own subfolder. In the template, the first book folder is simply called book.

Here is an explanation of all the folders and files in the template.

Files and folders to ignore

You should keep the following files and folders, but you can largely ignore them.