The gitbook-cli comes with a few commands that we can use to create a book. The former will watch our working directory and build the project whenever there is any changes while the latter will host it on a simple development server with hot-loading capabilities. This is where nodemon and live-server comes in. C:\Users\USERNAME\GitBook recreated again, there is. you will see all books available in GitBook Editor now, which are from J:\GitBook. launch GuiBook Editor, change library path from menu->Change Library Path, you need to choice Library full path like: J:\GitBook\Library. Since gitbook converts your markdown book into html files, it would be nice if we had a way to do a live reload of our html files directly. move whole GitBook folder from C:\Users\USERNAME\GitBook to J:\GitBook. Next, we would have to get the gitbook-cli from npm to work with gitbooks. Try npm -version after installing it to make sure it works.
#GITBOOK EDITOR OFLINE INSTALL#
The first thing I did was to install NodeJS, which comes with npm. They are both pretty nice, in its own way, but the main gripe I have towards the both of them is that the online editor is slow (noticable lag when loading huge books) and the offline editor is pretty clunky at handling files.Īnyway, I preferred using Sublime Text 3 to edit my markdown files, with excellent support for brackets, links, fast loading of huge files (take that, atom.io!) and multiple cursors among other things.Īs Larry Wall would have approved, I'm going to create my separate workflow to keep my self lazy, with the help of the npm package manager. It comes with an online editor, and an offline one, which is actually just a electron-enabled application of the online version using React and stuff like that. Gitbook is a great application that simplifies the process of creating a web book.