[creato]

I 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?

[Brian_K_White]

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.

[JimDabell]

I think they wanted to be "the GitHub for authoring books". So there's one level of indirection, but it makes sense.

[chillfox]

Git has been a trendy word for a while, a bit like sticking "i" in front of your product name.

[quadrangle]

while true, it's also formally trademarked and GitHub and GitLab etc. have explicit permission to use the term. It's a trademark violation to use "Git" in reference to software products without the explicit permission of the Git project unless it's a mere reference in the direction of "Zinq is a tool that helps with Git etc" (it's not a trademark issue to mention interaction with Git, only to use it in the name as branding)

[thrwaway69]

I don't understand why. People don't like master branch but they don't care about git which is literally a slang for an old senile idiot.