可以点击下面的按钮进入gitter聊天室，有问题可以在里面问
由于使用的分词插件模块nodejieba，是使用nodejs对c++库的封装，所以安装依赖的时候要求机器上安装有c++编译环境
windows的情况我不了解，linux使用的是g++
linux使用包管理工具安装，mac可能需要安装一下 command line tools ，具体安装方式请google
npm install -g codepiano/gitbook-
支持中文搜索 需要生成所有文章内容的json格式索引文件，内容过多的话需要注意文件的体积，开启压缩的话应该不会造成太大的负担
-
支持搜索后关键字高亮
-
支持分享到qq、微信（二维码）
- 分享到qq直接跳转至qq connect分享页面，该页面也可实现分享到qq空间和qq微博的功能
- 分享到微信直接生成二维码，也可分享到其他平台
- 需要在配置文件中设置相关选项为true
-
修改了介绍页面（即生成网站的主页）的方式，增加了一个新的指定方式
-
原始的gitbook介绍页面文件名必须为README.md，只可以自定义标题名称
-
修改后可以在配置文件book.json中指定介绍页面的标题和文件(相对)路径，可以不在SUMMARY.md文件中指定，在book.json中添加
"introduction": { "path": "你的介绍文件的路径", "title": "你的介绍文件的标题" }
-
-
可以在目录栏底部添加自定义链接，在book.json中添加配置项
"tail": { "tilte1": "url1", "title2": "url2" } -
不再把google、facebook、twitter分享设置为默认，所有分享需要在配置文件中设置，才会出现在分享栏。
"links": { "sharing": { "all" : true, "google" : true, "facebook" : true, "twitter" : true, "weibo" : true, "qq" : true, "qrcode" : true } } -
为了便于SEO，添加了keywords的meta标签，可以在book.json中配置
"keywords": "keyword1,keyword2,keyword3"
下面是我写的辅助插件，可以按需要进行安装使用
- 集成多说评论，见 codepiano/gitbook-plugin-duoshuo
- 集成畅言评论，见 codepiano/gitbook-plugin-changyan
- 百度统计插件，通过事件监控页面点击，见 codepiano/gitbook-plugin-baiduana
GitBook is a command line tool (and Node.js library) for building beautiful books using GitHub/Git and Markdown. Here is an example: Learn Javascript. You can publish book easily online using gitbook.com and an editor is available for Windows, Mac and Linux. You can follow @GitBookIO on Twitter. Complete documentation is available at help.gitbook.io.
GitBook can be installed from NPM using:
$ npm install gitbook -g
Create the directories and files for a book from its SUMMARY.md file using
$ gitbook init
You can serve a repository as a book using:
$ gitbook serve ./repository
Or simply build the static website using:
$ gitbook build ./repository --output=./outputFolder
Options for commands build and serve are:
-o, --output <directory> Path to output directory, defaults to ./_book
-f, --format <name> Change generation format, defaults to site, availables are: site, page, ebook, json
--config <config file> Configuration file to use, defaults to book.js or book.json
GitBook loads the default configuration from a book.json file in the repository if it exists.
Here are the options that can be stored in this file:
{
// Folders to use for output
// Caution: it overrides the value from the command line
// It's not advised this option in the book.json
"output": null,
// Generator to use for building
// Caution: it overrides the value from the command line
// It's not advised this option in the book.json
"generator": "site",
// Book metadats (somes are extracted from the README by default)
"title": null,
"description": null,
"isbn": null,
// For ebook format, the extension to use for generation (default is detected from output extension)
// "epub", "pdf", "mobi"
// Caution: it overrides the value from the command line
// It's not advised this option in the book.json
"extension": null,
// Plugins list, can contain "-name" for removing default plugins
"plugins": [],
// Global configuration for plugins
"pluginsConfig": {
"fontSettings": {
"theme": "sepia", "night" or "white",
"family": "serif" or "sans",
"size": 1 to 4
}
},
// Variables for templating
"variables": {},
// Links in template (null: default, false: remove, string: new value)
"links": {
// Custom links at top of sidebar
"sidebar": {
"Custom link name": "https://customlink.com"
},
// Sharing links
"sharing": {
"google": null,
"facebook": null,
"twitter": null,
"weibo": true,
"qq": true,
"weixin": true,
"all": null
}
},
// Options for PDF generation
"pdf": {
// Add page numbers to the bottom of every page
"pageNumbers": false,
// Font size for the fiel content
"fontSize": 12,
// Paper size for the pdf
// Choices are [u’a0’, u’a1’, u’a2’, u’a3’, u’a4’, u’a5’, u’a6’, u’b0’, u’b1’, u’b2’, u’b3’, u’b4’, u’b5’, u’b6’, u’legal’, u’letter’]
"paperSize": "a4",
// Margin (in pts)
// Note: 72 pts equals 1 inch
"margin": {
"right": 62,
"left": 62,
"top": 36,
"bottom": 36
},
//Header HTML template. Available variables: _PAGENUM_, _TITLE_, _AUTHOR_ and _SECTION_.
"headerTemplate": null,
//Footer HTML template. Available variables: _PAGENUM_, _TITLE_, _AUTHOR_ and _SECTION_.
"footerTemplate": null
}
}You can publish your books to our index by visiting GitBook.com
GitBook can generate your book in the following formats:
- Static Website: This is the default format. It generates a complete interactive static website that can be, for example, hosted on GitHub Pages.
- eBook: A complete eBook with exercise solutions at the end of the book. You need to have ebook-convert installed. You can specify the eBook filename with the
-ooption, otherwisebookwill be used.- Generate a PDF using:
gitbook pdf ./myrepo - Generate a ePub using:
gitbook epub ./myrepo - Generate a MOBI using:
gitbook mobi ./myrepo
- Generate a PDF using:
- JSON: This format is used for debugging or extracting metadata from a book. Generate this format using:
gitbook build ./myrepo -f json.
A book is a Git repository containing at least 2 files: README.md and SUMMARY.md.
Typically, this should be the introduction for your book. It will be automatically added to the final summary.
The SUMMARY.md defines your book's structure. It should contain a list of chapters, linking to their respective pages.
Example:
# Summary
This is the summary of my book.
* [section 1](section1/README.md)
* [example 1](section1/example1.md)
* [example 2](section1/example2.md)
* [section 2](section2/README.md)
* [example 1](section2/example1.md)Files that are not included in SUMMARY.md will not be processed by gitbook.
GitBook supports building books written in multiple languages. Each language should be a sub-directory following the normal GitBook format, and a file named LANGS.md should be present at the root of the repository with the following format:
* [English](en/)
* [French](fr/)
* [Español](es/)You can see a complete example with the Learn Git book.
Allows you to specify terms and their respective definitions to be displayed in the glossary. Based on those terms, gitbook will automatically build an index and highlight those terms in pages.
The GLOSSARY.md format is very simple :
# term
Definition for this term
# Another term
With it's definition, this can contain bold text and all other kinds of inline markup ...
GitBook will read the .gitignore, .bookignore and .ignore files to get a list of files and folders to skip. (The format inside those files follows the same convention as .gitignore).
Best practices for the .gitignore is to ignore build files from node.js (node_modules, ...) and build files from GitBook: _book, *.epub, *.mobi and *.pdf (Download GitBook.gitignore).
A cover image can be set by creating a file: /cover.jpg. The best resolution is 1800x2360. The generation of the cover can be done automatically using the plugin autocover.
A small version of the cover can also be set by creating a file: /cover_small.jpg.
The platform GitBook.com is like an "Heroku for books": you can create a book on it (public, paid, or private) and update it using git push.
Plugins can be used to extend your book's functionality. Read GitbookIO/plugin for more information about how to build a plugin for GitBook.
Plugins needed to build a book can be installed using: gitbook install ./.
| Name | Description |
|---|---|
| exercises | Add interactive exercises to your book. |
| quizzes | Add interactive quizzes to your book. |
| mathjax | Displays mathematical notation in the book. |
| mixpanel | Mixpanel tracking for your book |
| infinitescroll | Infinite Scrolling |
| Name | Description |
|---|---|
| Google Analytics | Google Analytics tracking for your book |
| Disqus | Disqus comments integration in your book |
| Autocover | Generate a cover for your book |
| Transform annoted quotes to notes | Allow extra markdown markup to render blockquotes as nice notes |
| Send code to console | Evaluate javascript block in the browser inspector's console |
| Revealable sections | Reveal sections of the page using buttons made from the first title in each section |
| Markdown within HTML | Process markdown within HTML blocks - allows custom layout options for individual pages |
| Bootstrap JavaScript plugins | Use the Bootstrap JavaScript plugins in your online GitBook |
| Piwik Open Analytics | Piwik Open Analytics tracking for your book |
| Heading Anchors | Add linkable Github-style anchors to headings |
| JSBin | Embedded jsbin frame into your book |
| GrVis | Gitbook GrViz plugin is used to select from markdown dot and converting it into a picture format svg |
| PlantUml | Gitbook PlantUml plugin is used to select from markdown uml and converting it into a picture format svg |
| Mermaid | Adds diagrams and flowcharts rendered by mermaid |
You can use the environment variable DEBUG=true to get better error messages (with stack trace). For example:
$ export DEBUG=true
$ gitbook build ./