There is a great new technical and scientific publishing tool now available:
Based on Pandoc, it integrates several additional filters and an opinionated (and IMO elegant and practical) set of publishing templates for a pretty comprehensive feature-set. Given this is Pandoc based, a wide range of output formats is available, all driven by meta-data. The Quarto command itself bundles all this together so a Pandoc install itself is not required. The documentation is really excellent, making some quite complex features (like sub-figure layout) very accessible.
Scrivenerās amazingly flexible Markdown output and its post-processor makes Scrivener+Quarto a very viable workflow. One minor wrinkle is for Quartoās optional project system (to generate complete websites or books) where multiple files define multiple chapters, but a small pre-processor script to take Scrivenerās output and split it on # Headings would be trivial and solve this issue. You donāt need to use this one file per chapter mode if you donāt want, in which case Scrivenerās output will be fineā¦
No, scoop is an equivalent package manager to brew on macOS, you can only use scoop on Windows. You donāt need to use a package manager, as quarto is also available as a a standalone install package.
Remember that quarto is āopinionatedā in its final layout, a layout that has been assigned with specific templates for HTML, PDF, DOCX etc. ā as Pandoc sits underneath you can still tweak away under the curtain, but that is not really the point. For users who want maximum control, stick to Pandocā¦
Well, if you used macOS you could use the wonderful Marked2 ā it can run pandoc with options directly on a Scrivener project to live render your Scrivener project while writingā¦
(It wouldnāt be too difficult to do something similar on Windows if you were proficient at coding: the Scrivener files that represent the binder are simple RTF files and an RTF>MD converter trigger by a file watcher could get source that could be rendered using quarto or pandoc directly. But yeah, youād need to be a proficient geek for thatā¦)
Just popping in to say: I think Iāll still use my Scrivener+Pandoc+pandoc-crossref workflow when Iām writing on my own. But I just used Quarto (in rstudio) for the first time in preparation for collaborating with another, and I gotta say I like it a lot. It is amazing to have a free writing environment thatā¦just works with Pandoc. The fact that you can easily output to pdf and docx without having to change anything except the format specification is amazing. In order to implement that with Scrivener, I had to create two formats, one that put ā\noindentā before text I didnāt wanted indented (e.g. ones that follow blockquotes or equations), and one that wrapped the text in a div span that pandoc used in conjunction with a docx reference file. That is how I still roll, but since setting that up Iāve learned about this wonderful lua filter that works for both outputs with no changes needed. The filter also works with Quarto in rstudio, which is a wonderful development indeed.