asciidoctor-web-pdf VS pandoc

Asciidoctor has a web PDF tool that just went alpha a little bit ago, uses the same stack as the OP's thingie.

https://github.com/Mogztter/asciidoctor-web-pdf

The content handoff goes like this: Asciidoc (using defined roles) generates HTML5 (Pagedjs polyfills page areas / pagination stuff), CSS styles stuff, and Puppeteer runs a headless Chromium for the pdf render. It's straight from CSS GCPM W3C spec, a flavor of CSS Paged Media, drafts that have been percolating since frickin' 2006 but have never seen browser implementation.

Just use asciidoc.

E.g.

- https://github.com/Mogztter/asciidoctor-web-pdf/tree/master/...

You could also use pandoc. The last time I exported from OneNote to MD, I exported notebook sections as docx and then ran this: pandoc -o output.md -f docx -t markdown source.docx

I turn that markdown content into something more 'presentable' a variety of ways, that are on a spectrum of automation. The most user friendly option is the Obsidian Publish (a paid service) by the developer of Obsidian. I keep some public math notes on my publish site. PM me if you are curious to see it, as I am unsure if I want to publicly connect it to my reddit at the moment But there are infinitely many ways to turn markdown files (and non-markdown attachments) into websites, emails, pdfs, anything via tools such as Pandoc Read more about Pandoc here: https://pandoc.org

Try Pandoc.

Possible, not an argument of they shouldn't be used. Grammarly is in Lisp, the prototype of VB's (or is it C#'s) GC is in Common Lisp (can't find source now), MirageOS is written in OCaml and fairly performant, pandoc is in Haskell, etc. If we actually follow that, anything with GC shouldn't ever be used, and

vim-pandoc is a plugin that uses pandoc external program to convert documents between different formats.

If you decide one day you want to turn all your Obsidian notes into another format, you can use a program called Pandoc. It will turn Markdown into pretty much any format you can think of. Here's a list of the options: https://pandoc.org/MANUAL.html#options

Tangentially related, but if you absolutely need Word documents but don't need more advanced features of Word documents, you could use pandoc to build .docx files from some plaintext file format (markdown, latex, etc...)

I end up taking linear notes in a text file, with un-resolved or in-progress items at the bottom. They get pushed downward linearly until they are finished, at which point they get immortalized in the greppable daily log above. Requires a lot of discipline and doesn't have a lot of structure, but having the "working area" next to the journal has served me well. I use vimwiki[1] for most of the editing, in addition to custom scripts written using pandoc[2] for things like billing/reporting.

[1]: https://vimwiki.github.io/

[2]: https://pandoc.org/