Never used gitbook so I have the following question: in terms of content creation, how does it stack up compared to sphinx?
HonKit: A Fork of GitBook
11–20 of 38 posts
Re: HonKit: A Fork of GitBook
#12I just spent a few minutes reading the readme, and I still can'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? I totally get storing the markdown files/folders in git, but surely any other version control system would be fine too?
Git has been a trendy word for a while, a bit like sticking "i" in front of your product name.
Re: HonKit: A Fork of GitBook
#13Is this semantic markup for writing or is it like headers and paragraphs? I'm pretty much stuck in the LyX mindset when it comes to treating documents as code.
Re: HonKit: A Fork of GitBook
#14What's the name supposed to mean?
Probably from 本 == book, pronounced hon in Japanese. (The author also appears to be Japanese.)
Right. The original fork name was "GitHon" because hon == book in Japanese.
The author recently renamed "GitHon" to "HonKit" due to Git being protected by U.S. trademark law.
Re: HonKit: A Fork of GitBook
#15Earlier quoted context omitted.
Probably from 本 == book, pronounced hon in Japanese. (The author also appears to be Japanese.)
Right. The original fork name was "GitHon" because hon == book in Japanese. The author recently renamed "GitHon" to "HonKit" due to Git being protected by U.S. trademark law.
Hope they don't run into any problems with the "honk" memes.
Re: HonKit: A Fork of GitBook
#16I just spent a few minutes reading the readme, and I still can'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? I totally get storing the markdown files/folders in git, but surely any other version control system would be fine too?
Ever since I got my first e-ink reader, I imagined the books being updated via revision control. Where a reader can encounter a typo or other error, and submit the correction right from the device for the author to review and accept or reject.
Books as git repos instead of static seems obvious, even inevitable, eventually, to me.
Re: HonKit: A Fork of GitBook
#17I just spent a few minutes reading the readme, and I still can'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? I totally get storing the markdown files/folders in git, but surely any other version control system would be fine too?
I think they wanted to be "the GitHub for authoring books". So there's one level of indirection, but it makes sense.
Re: HonKit: A Fork of GitBook
#18Tangential: How is GitBook/GitBook.com not trademark infringement of git?
Nobody is going to confuse Git with GitBook... GitHub on the other hand... But Linus Torvalds as savage as he is with crappy vendor code he is a reasonable guy.
The clarification of what’s in and what’s out was in 2017: https://public-inbox.org/git/20170202022655.2jwvudhvo4hmueaw...
Gitbook predates that’s so it may have been grandfathered.
Re: HonKit: A Fork of GitBook
#19Earlier quoted context omitted.
Probably from 本 == book, pronounced hon in Japanese. (The author also appears to be Japanese.)
Right. The original fork name was "GitHon" because hon == book in Japanese. The author recently renamed "GitHon" to "HonKit" due to Git being protected by U.S. trademark law.
It’s absolutely begging to get an extension called HonKitOnk.
Re: HonKit: A Fork of GitBook
#20desperately needed, going to check this out. we tried this gitbook enterprise product.. definitely headed in the wrong direction for our needs.