See also mdBook [0] for another alternative to Gitbook [0] https://github.com/rust-lang/mdBook
I've switched from GitBook mostly to mkdocs-material for technical docs
HonKit: A Fork of GitBook
31–38 of 38 posts
Re: HonKit: A Fork of GitBook
#32I hope the team is thinking of dusting of GitBook Editor too
Re: HonKit: A Fork of GitBook
#33See also mdBook [0] for another alternative to Gitbook [0] https://github.com/rust-lang/mdBook
At a cost of worse design, I am extremely satisfied with mdbook. For an example, check The Rust Book.
What do you mean by design? I run a customized version of mdbook to render https://docs.hyperdeck.io
I’m fairly happy with mdbook (although it took some time to get the customizations work correctly)
Re: HonKit: A Fork of GitBook
#34Earlier quoted context omitted.
At a cost of worse design, I am extremely satisfied with mdbook. For an example, check The Rust Book.
What do you mean by design? I run a customized version of mdbook to render https://docs.hyperdeck.io I’m fairly happy with mdbook (although it took some time to get the customizations work correctly)
On a side note, HyperDeck looks great! Is this open-source?
Re: HonKit: A Fork of GitBook
#35For those who weren’t aware, this is the reason behind the fork: > As the efforts of the GitBook team are focused on the GitBook.com platform, the CLI is no longer under active development. — https://github.com/GitbookIO/gitbook#%EF%B8%8F-deprecation-w...
I get sad about this. This project moved from an open source model to a closed source one. I have nothing but sympathy for the team for doing this but I do wonder if there is an alternative way of monetizing and keeping the project open source. Seriously- what are the monetization strategies for open source projects? I know red hat, hashicorp and others sell a enterprise support and hosting solution as enterprise add…
I think the market for people who want books hosted and the market for people with enough dev skills to do it themself is separate. So they should be able to make their revenue from people who want easy hosting.
That being said, it seems like a doomed SaaS because the value add is pretty minimal. Maybe a one time charge would make sense, but I can’t find much value in monthly fees for something I can host on github.io for free.
The software is nice, but there are others.
In general, I don’t like “artificial” SaaS where the the fee is rent-seeking for something software runs for near zero marginal costs.
Re: HonKit: A Fork of GitBook
#36I 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.
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)
Re: HonKit: A Fork of GitBook
#37See also mdBook [0] for another alternative to Gitbook [0] https://github.com/rust-lang/mdBook
There is also Jupyterbook https://jupyterbook.org/intro.html which has a slightly different focus, but seems pretty great.
Re: HonKit: A Fork of GitBook
#38Earlier quoted context omitted.
What do you mean by design? I run a customized version of mdbook to render https://docs.hyperdeck.io I’m fairly happy with mdbook (although it took some time to get the customizations work correctly)
On a side note, HyperDeck looks great! Is this open-source?
Thanks! It is not open source right now. I’ve been thinking about that, but initially it will probably be commercial, and then I’ll see.