front-matter VS pandoc

To set our metadata dynamically, we also imported the front-matter dependency.

front-matter parser

What we want is for our editor to take the combination of front-matter data and markup, then be able to extract the two before storing that data separately somewhere. We'll be using the front-matter module to extract the data we need from the text editor content.

`Textile` is a similar language to Markdown, used to weave text across multiple IDEs, programming languages, and CMSs:

https://textile-lang.com/

Textile is one of the core markups supported by GitHub and Pandoc:

https://github.com/github/markup / https://pandoc.org/

And many CMS, most famously TextPattern and MoveableType, but also things like Jekyll:

https://textile-lang.com/article/textile-markup-language-sup...

==> pandoc : stable 3.9.0.2 (bottled), HEAD

Swiss-army knife of markup format conversion

https://pandoc.org/

Installed (on request)

From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/...

License: GPL-2.0-or-later

==> Installed Kegs and Versions

pandoc 3.9.0.2 (11 files, 274.7MB) [Linked]

==> Dependencies

Required (1): gmp

Recursive Runtime (1): all installed

==> Analytics

install: 31,898 (30 days), 119,598 (90 days), 369,388 (365 days)

As every developer using AI knows, using markdown (md) files is the best way to communicate with AI in May 2026. On the other hand, as far as I know, AI cannot read and write Word files directly. A Word .docx file is a zip file and contains document.xml, styles.xml, and others, so it is not suitable for AI to read directly. So it is better to convert Word files to md for AI. This time, I tried the popular document conversion tool Pandoc. https://pandoc.org/ Using Pandoc, we can easily convert Word files into md, but detailed styles will be lost.

The Swiss army knife for document conversion, Pandoc, supports compiling to WASM since 3.9 [1]. It supports Markdown, in a wide variety of flavours, and Typst. Their official demo page provides a PDF output via Typst, all done client-side [2]. Furthermore, you get .docx and other output formats as well

[1]: https://github.com/jgm/pandoc/releases/tag/3.9

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

There's an Obsidian extension for Pandoc so you can convert your Obsidian notes to any other format.

https://github.com/jgm/pandoc/pull/11135

There are a number of basic errors in this report, but since it's LLM-written I suppose I shall put as much effort correcting them as the author put into generating them. Sigh.

From the pandoc release announcement: https://github.com/jgm/pandoc/releases/3.9 :

> Starting with this release, pandoc can be compiled to WASM, making it

I’d highly recommend pandoc[0] if you need markdown conversion. Basically converts from everything and any markdown style to everything else. And then for clipboard just use `| pbcopy` on a Mac or `| xsel -ib`. Full command on a Mac would just be `pandoc README.md —to html | pbcopy`.

0: https://pandoc.org/

I looked into this and nothing worked well for me. I ended up just using Pandoc: https://pandoc.org/

That's when I found pandoc. Pandoc is a document converter that can turn markdown into PDF. It does this by converting markdown to LaTeX first, then using LaTeX to generate the PDF.