HonKit: A Fork of GitBook

For those who weren’t aware, this is the reason behind the fork:<p>&gt; As the efforts of the GitBook team are focused on the GitBook.com platform, the CLI is no longer under active development.<p>— <a href="https:&#x2F;&#x2F;github.com&#x2F;GitbookIO&#x2F;gitbook#%EF%B8%8F-deprecation-warning" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;GitbookIO&#x2F;gitbook#%EF%B8%8F-deprecation-w...</a>

I’m so happy this project is picking up the fork. Gitbook was a great project, but they really moved everything to their SaaS with artificial barriers to just using the software.<p>It was cool that they left cli around, but as abandonware.<p>I thought it strange that it was such a non open source behavior to only support their monthly service even though one of the main benefits I see in static site generators is the flexibility of hosting and cost.<p>I feel bad for them as it must be a hard business to compete with Bookdown and other projects.

See also mdBook [0] for another alternative to Gitbook<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;mdBook" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;mdBook</a>

I just spent a few minutes reading the readme, and I still can&#x27;t figure out why this tool (or GitBook) is directly connected to git. OK, a bunch of markdown and json files in folders form a book. How is this connected to git?<p>I totally get storing the markdown files&#x2F;folders in git, but surely any other version control system would be fine too?

I wrote a sizeable book with gitbook and I found it to have substantial design flaws. Once the book had a few hundred files the rendering became exceedingly slow.<p>It became clear to me that, internally some sort of scaling problem is present in the code that manifests itself abruptly once the book hits a certain size.<p>Rendering to html would take 2-3 minutes (attempting to reload the latest version of a single page also triggers a complete re-rendering of all pages, obviously making the process non-feasible).<p>I migrated to bookdown that renders the entire book in about 10 seconds (and reloads single pages quickly).<p>I wonder if honkit fixed those internal design errors that made gitbook unusuable for me.

Never used gitbook so I have the following question: in terms of content creation, how does it stack up compared to sphinx?

Tangential: How is GitBook&#x2F;GitBook.com not trademark infringement of git?

Is this semantic markup for writing or is it like headers and paragraphs? I&#x27;m pretty much stuck in the LyX mindset when it comes to treating documents as code.

This is much needed as GitBook moved away from Book publishing and abandoned open source spirit.

So nice to see that gitbook-cli abandoned project is finally picked up again. How would the integration with Calibre work, since it awaits major changes in upcoming versions?

Anyone have a comparison between this and Docusaurus v2?

I hope the team is thinking of dusting of GitBook Editor too

desperately needed, going to check this out. we tried this gitbook enterprise product.. definitely headed in the wrong direction for our needs.

What&#x27;s the name supposed to mean?

Racist.