Very cool. I co-edit Peter Shirley's _Ray Tracing in One Weekend_ (<a href="https://raytracing.github.io/" rel="nofollow">https://raytracing.github.io/</a>) and have taken a similar approach, though with a different toolset. At some point if I find the time, I'll write up a similar article on our approach and what we've learned. Our books are open-sourced on GitHub (<a href="https://github.com/raytracing/raytracing.github.io" rel="nofollow">https://github.com/raytracing/raytracing.github.io</a>), and we also use GitHub to host our books.<p>Basically, we use Markdeep (<a href="https://casual-effects.com/markdeep/" rel="nofollow">https://casual-effects.com/markdeep/</a>), a _very_ powerful Markdown implementation with a bunch of built-in features. The killer feature is that with a handful of boilerplate lines (UTF-8 declaration at the top, and JavaScript loader at the bottom), you get content that automatically self-transforms in the browser into a full HTML document. This eliminates any build step, and means you can treat it as you would any other HTML file, with optional CSS and other features. It also bundles in a LaTeX engine, ASCII diagram rendering, and a whole host of other features. If you look at the three ray tracing books, you can see how simple the source is, and how pleasing the final rendering.<p>Check out the books and the GitHub repo — it's a _great_ way to quickly and easily pound out a web book.