Version 3.0.0

[SamyPesse]

• Simpler JS APIs (in GitBook itself and plugins)
• Improvements for Glossary (GLOSSARY.md)
  • Generate glossary as a normal page
  • Add class .no-glossary to avoid annotating in it
  • Don't annotate in headings
• Improvements for Languages (LANGS.md)
  • Fix Styles in root folder not working with multilanguage books #788
  • Fix custom /images directory in root not copied to output? #744
  • Remove plugins from language books (list of plugins should be global for the entire book)
• Improvements for Summary (SUMMARY.md)
  • Allow anchor entries, ex: * [Entry](test.md#hello) (Fix Add anchors to summary #776)
  • Allow multiple parts/sections in SUMMARY
  • Allow external entries
  • No longer required
• Page
  • Optmize urls when links to a README.md (Fix Any way to remove .html extension from URL? #537)
  • Text direction can change between pages (ltr to rtl)
• Templating
  • Allow single tag block (exemple for codesnippet plugin)
  • Cleanup context
  • Update to nunjucks@3
  • date filters
• Documentation use-case, where book is stored in a docs folder
• Theming
  • Default theme should be stored in an external repository (https://github.com/GitbookIO/theme-default)
  • Author can specify a theme in its book.json
  • Author can extend his theme by creating a _layouts folder
  • i18n templating filter in the core
  • Merge templating engine with the book's one
• Markdown
  • Switch to markdown-it instead of kramed ?
    - [ ] [ALink]:.. no supported (https://gist.github.com/SamyPesse/c2875343878f21338b14)
• Tests
  • Fix tests on Windows

Change Log

https://github.com/GitbookIO/gitbook/blob/3.0.0/CHANGES.md

[nateberkopec]

👏

[nagim]

🆒

[nagim]

Some improvement ideas for Glossary:

• Do not link glossary items in titles
• Use more subtle format, one that separates glossary items from other links (e.g.: no underline and less vivid text color)
• Configurable overload functionality: right now, if we define multiple meaning/explanation for a glossary item, it will display all of them in the tooltip. It would be useful to be able to assign an attribute or some variable to the different explanations, then use this attribute in the metadata of the document. This way, one explanation could take precedence over the other(s), when displaying the tooltip. This is useful when you have an abbreviation, which means different things in different topics, and we want to avoid confusion.

[nagim]

👏

[SamyPesse]

🍻 🎆 🎂

We are going to release the first pre-release of GitBook v3 today, with support on GitBook.com released tomorrow.
GitBook v3 will stay in a alpha/beta stage for ~1month, till we help developers adapt plugins, etc.

You'll be able to easily switch from GitBook v2 to GitBook v3 in the GitBook.com UI.

[nagim]

Really great work guys in such a short time!
Hats off! 👍 🍻

[Jayin]

👏 👏

[davis]

how do we use gitbook 3.0.0-pre.3?

[davis]

(with gitbook cli)

[dorako321]

@davis gitbook v3 is not available in npm command yet.
we have to clone gitbook repository, and use gitbook-cli alias command.

plz, check this page.
https://github.com/GitbookIO/gitbook-cli

Use a local folder as a GitBook version (for developement)
$ gitbook alias ./mygitbook latest