A new entrant in the world of scientific notebooks and academic blogging. Kind of a competitor/complement to jupyter and blogdown which unites them all, and also shares many authors with them. C&C codebraid.
- Create dynamic content with Python, R, Julia, and Observable.
- Author documents as plain text markdown or Jupyter notebooks.
- Publish high-quality articles, reports, presentations, websites, blogs, and books in HTML, PDF, MS Word, ePub, and more.
- Author with scientific markdown, including equations, citations, crossrefs, figure panels, callouts, advanced layout, and more.
Pandoc markdown has excellent support for LaTeX equations and citations. Quarto adds extensions for cross-references, figure panels, callouts, advanced page layout, and more.
Engage readers by adding interactive data exploration to your documents using Jupyter Widgets, htmlwidgets for R, Observable JS, and Shiny.
It seems to load jupyter notebook source docs just fine, and notably promises that it will actually render citations correctly in jupyter.
If one wished to use the quarto engine to experiment with weird other stuff (such as the content ranking, recommendation or the quirky indexing systems as seen on this site) then
one is, AFAICT, out of luck.
we can use the new Custom Listings support, which seems to do about 90% of what I want.
OTOH, it leverages many more features of pandoc which leads to many well-supported advanced typographical features.
hugo is a supported backend.
Build a custom format
Quarto format extensions enable you to add new formats to the built-in formats (e.g.
docx) already available. Custom formats can provide default document options, style-sheets, header, footer, or logo elements, and even bundle other extensions like filters and shortcodes. They are a great way to provide a common baseline for authoring documents or presentations within an organization, for a particular type of project or analysis, or for a specific publication.
Of course jupyter ends up being a thing. It is a little complicated, of course, as it always is when venturing into the Jupyter Cinematic Universe.
For one, jupyter notebooks are a valid frontend for quarto. But also the jupyter ipykernl infrastructure is the execution model for python, I think.
It is well-documet elsewhere that I dislike jupyter notebooks as a front-end interface to this, or any, system. But I will take on the interactive code execution stuff.
It is unclear to me how much of a round-trip interaction loop is supported for jupyter kernels: quarto renders essentially a static HTML page, so I don't believe the HTML widgets can be used to interact with the kernel, although they might have some basic animation support etc.
As an academic I want certain things in my writing tools, i.e. maths, citations and crossreferences. Quarto knows about these.