The fact that it's in Go, and therefore distributed as a single binary, also makes installation and use anywhere you want it a cakewalk. YMMV on how important that is to you, but I like to keep my tools light and nomadic when possible.
[1]: https://quarto.org/
> The Magic Book Project is an open source project funded by New York University's Interactive Telecommunications Program. It aims to be the best free tool for creating print and digital books from a single source.
https://github.com/magicbookproject/magicbook
I learned about it because it's used for The Nature of Code 2nd Edition.
>This project is for you, if:
... (last bullet point):
>You want that command-line tool be be written in Node-only. No more XSLT.
Put me off, personally.
However, if I had to start from scratch, I'd probably look at Quarto (https://quarto.org/) or Mau (https://project-mau.github.io/index.html)
I’d love to hear what you think!
You will likely need to edit your blogposts a little bit before putting them in the book. So I recommend a separate program for that altogether.
I haven’t used it myself, so I don’t know how easy it is to use. But I like some books that were written in it.
I wish I had asked this question here when we were doing our research. There are some great recommendations here. But I like Strapi so far. Their documentation is pretty nice. Even if their onboarding is complicated, the documentation makes it easy to execute.
For web, I went
Mkdocs material (cos I like Python) to Docusaurus (because it has more features) to Astro (because wow at speed and polish).
I mean writing is the most important part of writing a book.
Good luck.
