jupyter-book VS typst

Sphinx supports ReStructuredText and Markdown.

MyST-Markdown supports MathJaX and Sphinx roles and directives. https://myst-parser.readthedocs.io/en/latest/

jupyter-book supports ReStructuredText, Jupyter Notebooks, and MyST-Markdown documents:

You can build Sphinx and Jupyter-Book projects with the ReadTheDocs container, which already has LaTeX installed: https://github.com/executablebooks/jupyter-book/issues/991

myst-templates/plain_latex_book:

your task is very very broad

you mention you don't want to deal with AWS, if it's because of ad-hoc installation concerns and nothing else you can just run your notebooks in ready-made solutions like Google Colab, or Jupyter-book in Github ( https://github.com/executablebooks/jupyter-book ))

that would cover a lot of use cases right away without next to no learning curve

If you don't want to deal with AWS or similar, in that case:

- if it's a static notebook then you can obviously render it and serve the web content (might seem obvious but needs to be considered)

- if it's dynamic but has light hardware requirements, you can try jupyterlite which runs in the browser and should do a pyodine (webassembly CPython kernel) can do: https://jupyterlite.readthedocs.io/en/latest/try/lab/

- otherwise, you can try exposing a dockerised jupyter env ( as in https://github.com/MKAbuMattar/dockerized-jupyter-notebook/b... ) or even better a nixified one ( https://github.com/tweag/jupyenv )

there might be other approaches I'm missing, but I think that's pretty much it that doesn't entail some proprietary solution or an ad-hoc installation as you've been doing

Note: If you want to present a cleaner version of the notebook without assertions, you can use Jupyter book to render it into a site and use the remove-cell tag to omit assertions from the output.

See this thread for example.

And maybe take a look at executablebooks/jupyter-book.

Our team has transferred from Sphinx for documentation to JupyterBook. There have been some growing pains with it but I prefer the look of the output and being able to play with the examples on Colab or Binder at the click of a button is a great feature.

https://github.com/typst/typst looks promising, both the language and the tooling. I wonder where it will find its place in a world that is dominated by either Word or LaTex.

I hope in a couple of years we start seeing posts like these with Typst instead of LaTeX. It seems like setting this up would be a bit easier since Typst is much more concise than LaTeX.

[0] https://github.com/typst/typst

For writing math notes (especially in vim), I switch to using Typst (https://typst.app).

Here's a few points:

- The syntax is a lot lighter and easier to type fast. I was up and running in half hour after starting to use it. Once in a while I can look up some symbol name in the docs but that's about it.

- Empty document is a valid document. No preambles, no includes etc, it's all optional and the defaults are sensible. Just start typing.

- It's incremental. Live preview from neovim is in the browser and it's lightning fast, pretty much immediate. No pdf sync pain. No build files, makefiles and all that. Just start typing.

While it's not going to beat latex in terms of serious academic use, for personal use and notes it's close to perfect.

(And of course it's written in Rust...)

Except the main theme, which was HTML export? https://github.com/typst/typst/issues/721

Though it's in the roadmap!

I don't use LaTeX for anything these days but Typst popped up recently and seems like a decent alternative: https://github.com/typst/typst

I am surprised that no one mentions the typst. It is super smooth with typst-preview.

I suggest you ask in the discord channel: https://discord.gg/2uDybryKPe. Or open an issue or question on GitHub: https://github.com/typst/typst