Getting Started with Gitbook (first book with GitHub)--Super detailed mapping instructions

I recently contacted Gitbook and found it to support markdown and git, just to get my notes on GitHub to generate a book, so I started to tinker with Gitbook, an afternoon of the same time, explaining that this thing is quite easy to see my book:
"Leetbook (Leetcode)".

It is recommended to deploy your framework directly on GitHub before importing Gitbook.

Create a new warehouse

The creation process does not require me to tell you what to do, if you don't know, see GitHub Getting Started

Create a new file, named Summary.md, filled in:

# Summary* [前言](README.md)

Create a book

First enter Gitbook's official website: https://www.gitbook.com/

Click on the Red section and log in with GitHub

After logging in, point +newbook

Point to GitHub, click Link to your GitHub

Authorization is complete and then click on this page

Select the warehouse that you need to import, we use the testbook that we just created, then the title can be taken by ourselves, the following address can only be filled in English, then click Create

This page is currently in sync, and so on after the synchronization is complete, you can see their own books.

You can click Read

We can find 1 pages inside, which is what we just Summary.md wrote.

Add Content

We return to the previous step, click Edit

You can see the following interface

Let's open it.

You can display the edited effect synchronously

Now we can complete the entry of our book, in the catalog area right click, you can create a new content page

Then click, you will be prompted to create a file

Then you'll find that there's one more file on GitHub that's connected.

We'll see another "first page" in summary.

We double-click, find is Markdown hyperlink, originally this is Gitbook content organization way, through the hyperlink content and GitHub on the file association.

Let's change the name and then indent him into a tab and save to see what's changed.

You can see that the directory structure has changed and the name has changed.

By modifying the summary.md you can easily organize your book

the frame of the book

In general, your book has to have a readme.md and a summary.md.
SUMMARY.MD is the most important, it represents the entire framework of the book, but also we need to modify the main place.

When you think about writing a book, you can get a rough idea of how many points to make, and a folder for those parts. Then put the corresponding markdown file in.

Then push to GitHub, and then modify sumaary on Gitbook so that the new file is associated with Gitbook

About the acquisition of the address has a little trick, is to click on the file, mail, there is a rename, here you can see the full address of the file, copy is good.

Finally, you can click Read on the homepage of your own book to see the effect

Getting Started with Gitbook (first book with GitHub)--Super detailed mapping instructions