# \[ANN\] BonitoBook.jl

**URL:** <https://discourse.julialang.org/t/ann-bonitobook-jl/131442>\
**Category:** Package Announcements\
**Tags:** plotting, notebooks\
**Created:** [August 7, 2025, 11:28am UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442 "2025-08-07T11:28:19Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![tecosaur](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tecosaur/32/23206_2.png) [@tecosaur](https://discourse.julialang.org/u/tecosaur)\
**Post date:** [August 8, 2025, 3:33am UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/21 "2025-08-08T03:33:00Z")

</div>

> [@sdanisch](#):
>
> still need to figure out the best limitations and how to put them into the license, while allowing an open ecosystem to build…

Would an OSS license which covers SaaS do the trick? That gives you a few options, put I’d probably point out the EUPL (over the AGPL).

> [@mrufsvold](#):
>
> Yeah, someone should really come up with a “MIT but don’t be a jerk, dude!” license.

I have 2c here, which is that the MPL and EUPL are already pretty good in these regards. I feel like the MPL can be pretty accurately summarised as, MIT but:

- Give credit in software using it
- Share back any improvements you make to code shared as MPL

and otherwise use it however you want.

The EUPL is like the MPL, but covering SaaS too and with wider license comparability, with a few more euro-centric elements (e.g. setting Brussels as the arbitration jurisdiction). Other than that, neither are viral like the GPL, and there are a few other minor niceties that I won’t bore you with.

---

<div class="post-metadata">

**Author:** ![RoyiAvital](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/royiavital/32/571_2.png) [@RoyiAvital](https://discourse.julialang.org/u/RoyiAvital)\
**Post date:** [August 8, 2025, 6:11am UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/22 "2025-08-08T06:11:01Z")

</div>

> [@sdanisch](#):
>
> The Pkg integration and reactive workflow isn’t working for me and that most of Pluto is implemented in Javascript instead of Julia doesn’t fit my approach of “ecosystem first, notebook second” which I imagine for BonitoBook.

This is great to have choices.  
I also find the reactive approach problematic to my use cases when the calculation is time consuming.  
I am happy to see there is an alternative.  
Considering the quality of `Makie.jl`, I am sure this one will be a great and useful notebook format.

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 8, 2025, 12:00pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/23 "2025-08-08T12:00:20Z")

</div>

> Because if it’s non-commercial, I wonder if company can even try it or something

Yes, I’m pretty sure this is covered under fair use 😉  
Also, I’m the one enforcing the license, and I’ll set the bar pretty high until I expect a company to pay.  
I will try to figure out how to change the license/redme to reflect this.  
I’ll also want to figure out how to specify, that anyone putting significant time into the ecosystem gets paid - I love that open source means people can just start hacking on software, and I’ll need to figure out how to have everyone putting time into BonitoBook get their fair share.

@TheCedarPrince

> 1. How does this compare to Genie.jl

Bonito is much more focused on:

1. Performance! We use a highly optimized binary serialization to gain fastest update speeds. Genie seems to use JSON, which I expect to be quite a bit slower
2. No macros, and widget types instead. I must admit I’ve never understood the macro based DSL in Genie, so I’m not 100% sure how things work exactly, but I’ve put a lot of time into allowing users to implement their own widgets in a third party package, to allow a growing ecosystem. I suppose that’s also possible in Genie.
3. Not just a server, but a Julia HTML/JS generation framework for all kind of possible environments. So if you implement a widget in Bonito, it’ll work in Jupyter/Pluto/VScode/Webserver/self-contained HTML, which I think is pretty unique.

> Does this effectively “solve” some problems of Julia-WASM

Not really. I mean, the Javascript interop is good enough to move things to JS, so that parts of a plot can stay interactive without a Julia process, but to make this really nice and user friendly we’ll need proper WASM support in Julia.

> Is R support possible via [RCall.jl](https://juliaregistries.github.io/General/packages/redirect_to_repo/RCall)?

Yes, I thought of already shipping with R support, but I had to cut a few features to finally release it ( I actually wanted to release in April already 😃 )

@aplavin

Yeah, why not. I plan to have this more as an ecosystem, with BonitoBook being the “reference” implementation and being able to have lots of extensions and customization.  
The Automatic environment management drove me crazy with Pluto, so it’s definitely not something on my todo list, but I don’t see why we couldn’t have it as a plugin.  
I love interactive inspection, so that’d be something I could see spending some time on myself.

---

<div class="post-metadata">

**Author:** ![ehsani63](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ehsani63/32/38199_2.png) [@ehsani63](https://discourse.julialang.org/u/ehsani63)\
**Post date:** [August 8, 2025, 7:10pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/24 "2025-08-08T19:10:23Z")

</div>

Congratulations! Great work! A minor thing about the website: I noticed that the example for `@manipulate` isn’t working on the website. Changing the settings doesn’t reflect in the plot in my browser (Firefox).

---

<div class="post-metadata">

**Author:** ![dpo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dpo/32/3335_2.png) [@dpo](https://discourse.julialang.org/u/dpo)\
**Post date:** [August 10, 2025, 7:08pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/25 "2025-08-10T19:08:28Z")

</div>

I concur. I’m also thrilled to have another choice than Jupyter and Pluto. And if you end up implementing reactivity à la Pluto, please make it optional. I find it entirely counterproductive.

---

<div class="post-metadata">

**Author:** ![BLI](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bli/32/37206_2.png) [@BLI](https://discourse.julialang.org/u/BLI)\
**Post date:** [August 10, 2025, 9:01pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/26 "2025-08-10T21:01:48Z")

</div>

I have a love-hate relationship with Jupyter notebooks, so I am curious about BonitoBook. Here is my experience with JN, and why I am interested in testing alternatives:

- The mixture of code and markup makes it simple to document my code, and probably also makes it simpler for others to understand my code.
- Lately, JN as run in VSCode on my desktop acts weirdly: the notebook seems to be automatically restarted if I leave the notebook for more than a few seconds, with result that I need to re-run the notebook from the start. Don’t know if this is a problem with my desktop, or whether it is also a problem with my other computers – will have to check.
- JN doesn’t handle long notebooks well. I have mainly used Plots.jl so far, but with large documents, often the plots are only partially rendered.
- It is a pain to edit notebooks in VSCode compared to using a word processor (LyX, etc.).

In addition to the above, I am interested in a “new” tool that handles some of the following (don’t know whether BonitoBook.jl will do this, though):

- Book-like possibilities: styles (book, article, slides, web pages, etc.) with numbering of sections, equations, figures, tables, program listing (which may or may not be “live” - literal programming), bibliography.
- Math support for documentation. LaTeX code in markdown cells is ok, although I also like to use tools like LyX for more complex math. [I think the math-editor of former product Scientific Word is open source, if that is of interest; don’t know whether typst is an interesting alternative?] Can PrettyTables provide help with typesetting, with possibility to add caption + numbering?
- Co-authoring, versioning.

I don’t know whether the “Book” part of “BonitoBook” indicates any of the above. And… is the plan to base the editor on VSCode?

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 12, 2025, 6:04pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/27 "2025-08-12T18:04:05Z")

</div>

@ehsani63, those interactions aren’t working without a Julia process.

@dpo

> implementing reactivity à la Pluto, please make it optional

Definitely! 🙂 I can’t work with it ^^

@BLI

I’ve asked claude to change the style.jl for a more booklike format and this came out of it:

> **[book-example](https://bonitobook.org/website/book-example/)**

 ![image](https://global.discourse-cdn.com/julialang/original/3X/2/6/26253bc3ee611c3648f9b41a22323322a0e66cc3.png)

So, while it’s not _my_ goal to make a book format, that’s what I mean with building an ecosystem around it. By making BonitoBook super easy to completely restructure, I hope these things to get created over time.  
Note, that it needs to define a new book type for the layout, but that can re-use all components:

> <https://github.com/SimonDanisch/BonitoBook.jl/blob/main/docs/examples/.book-example-bbook/book.jl>

Maybe I’ll leave it at that, or we could have a nicer Plugin system, to ship a new layout like this as part of the book, which doesn’t need an explicit include and using of `RealBook`.

I guess your other points are addressed by that as well - I’m not sure how a LyX integration or other things will look like exactly, but I’m sure that it should be possible to write components for it or create a customization for it.

> is the plan to base the editor on VSCode?

I’m not sure what you mean, the editor is using Monaco editor, which is the same that VSCode uses, bringing quite a bit of vscode features - but more integration besides displaying a BonitoBook in the VSCode plotpane isn’t planned from my side right now.

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 12, 2025, 6:06pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/28 "2025-08-12T18:06:59Z")

</div>

I’ve also released a couple of other changes:

- Better Latex support and latex mime rendering for other packages
- Fixed the weird display of Vector{\<:AbstractVector}
- Added an example on how to customize the book (the above [book-example](https://bonitobook.org/website/book-example/))
- Improved & tested zip import/export (thanks to @nhz2 )

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [August 12, 2025, 6:15pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/29 "2025-08-12T18:15:50Z")

</div>

> [@sdanisch](#):
>
> Better Latex support and latex mime rendering for other packages

obligatory question: what is needed for some Typst integration 👀, I can work on that if you throw out some pointers

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 12, 2025, 6:19pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/30 "2025-08-12T18:19:14Z")

</div>

I’m not sure, I must admit I dont know Typst well enough.  
What would you want from an integration?  
Something like a typst cell, which works like a markdown cell and gets rendered nicely?  
For that you’d need to figure out how to render it to something that can be displayed with HTML/JS. Once that’s working, it should be simple to add it as a new language.

---

<div class="post-metadata">

**Author:** ![e3c6](https://avatars.discourse-cdn.com/v4/letter/e/e79b87/32.png) [@e3c6](https://discourse.julialang.org/u/e3c6)\
**Post date:** [August 12, 2025, 6:23pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/31 "2025-08-12T18:23:17Z")

</div>

> [@BLI](#):
>
> - Lately, JN as run in VSCode on my desktop acts weirdly: the notebook seems to be automatically restarted if I leave the notebook for more than a few seconds, with result that I need to re-run the notebook from the start. Don’t know if this is a problem with my desktop, or whether it is also a problem with my other computers – will have to check.

You are using VS code Jupyter to connect to a remote server? If so, this is a known issue.

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [August 12, 2025, 6:23pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/32 "2025-08-12T18:23:51Z")

</div>

> [@sdanisch](#):
>
> What would you want from an integration?

[Strings · Typstry.jl](https://jakobjpeters.github.io/Typstry.jl/development/references/strings/#Typstry.TypstStrings.TypstString) basically Jakob has a thing where you can have a Typst-String (a bit like `L""` I guess), and BonitoBook would presumably have a “render” api, and Typstry.jl can give you back a svg or pdf and BonitoBook would take that and display

---

<div class="post-metadata">

**Author:** ![e3c6](https://avatars.discourse-cdn.com/v4/letter/e/e79b87/32.png) [@e3c6](https://discourse.julialang.org/u/e3c6)\
**Post date:** [August 12, 2025, 6:24pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/33 "2025-08-12T18:24:48Z")

</div>

How would it work if I wanted to run BonitoBook from a remote server while displaying the notebook locally?

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 12, 2025, 6:33pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/34 "2025-08-12T18:33:09Z")

</div>

> How would it work if I wanted to run BonitoBook from a remote server while displaying the notebook locally?

Pretty much like any other notebook. `BonitoBook.book("your-book.md", port=8080, url="0.0.0.0", proxy_url=".")` will run on `localhost:8080` which you can then forward via ssh, or access at the ip of the server.  
The proxy\_url=“.” should actually be the default, now that I think about it (this makes any urls relative to where you host it, so if you access it on another url than `localhost:8080` (e.g. the servers ip/domain) it’ll still work).

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 12, 2025, 6:40pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/35 "2025-08-12T18:40:50Z")

</div>

I guess it sort of works already then?

 ![image](https://global.discourse-cdn.com/julialang/original/3X/2/f/2facfd6d5a865151dd07ab52ea1e3f4e49bf8d79.png)

---

<div class="post-metadata">

**Author:** ![e3c6](https://avatars.discourse-cdn.com/v4/letter/e/e79b87/32.png) [@e3c6](https://discourse.julialang.org/u/e3c6)\
**Post date:** [August 17, 2025, 3:33pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/37 "2025-08-17T15:33:05Z")

</div>

> [@sdanisch](#):
>
> Pretty much like any other notebook. `BonitoBook.book("your-book.md", port=8080, url="0.0.0.0", proxy_url=".")` will run on `localhost:8080` which you can then forward via ssh, or access at the ip of the server.

So I have to do this for each notebook file?

In Pluto, you start a server on the remote, and then can open several notebook files from the client, running on the same server (and sharing the same port).

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 17, 2025, 6:25pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/38 "2025-08-17T18:25:07Z")

</div>

that’s the same, it creates one server and adds each notebook under /notebook-name route.

---

<div class="post-metadata">

**Author:** ![Allan\_Baker](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/allan_baker/32/42645_2.png) [@Allan\_Baker](https://discourse.julialang.org/u/Allan_Baker)\
**Post date:** [August 26, 2025, 2:32pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/39 "2025-08-26T14:32:57Z")

</div>

Any chance on Bonjtobook.jl being MIT license? I don’t think I will be able to use a non commercial license, even if I’m only using the feature for internal research and development.

---

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [August 26, 2025, 2:48pm UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/40 "2025-08-26T14:48:05Z")

</div>

I’d absolutely love to, if anyone knows a good solution to actually get the work on it financed 😉

---

<div class="post-metadata">

**Author:** ![dmolina](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dmolina/32/5246_2.png) [@dmolina](https://discourse.julialang.org/u/dmolina)\
**Post date:** [September 1, 2025, 8:44am UTC](https://discourse.julialang.org/t/ann-bonitobook-jl/131442/41 "2025-09-01T08:44:44Z")

</div>

Thank you a lot for this package.

I have been working with Pluto for publishing examples in Julia of different algorithms. However, this package seems more comfortable for my workflow. I work/live in Emacs, and it is great to be able to edit directly in the editor, for the nice syntax, very direct markdown.

I will be using Pluto for more interactive parts, but I think it would use BonitoBook for the description of the algorithms, and the visualizations of their behavior.

PS: I am taking notes of how using it, when I will have more complete, I could give for the documentation, as am manual.

[Previous page](https://discourse.julialang.org/t/ann-bonitobook-jl/131442.md?page=1)

[Next page](https://discourse.julialang.org/t/ann-bonitobook-jl/131442.md?page=3)
