Cool! But it appears to always use LuaTeX as the engine, so only the older MkIV format is supported, and not the current LMTX format. The caching also doesn't seem to work quite right, since it appears to regenerate the font caches every time that you run it, which makes recompiles quite slow.
I wrote a Markdown -> ConTeXt -> PDF editor that may interest you.
* https://keenwrite.com/
* https://keenwrite.com/screenshots.html
Interesting. I usually use pandoc for converting my Markdown, which goes via LaTeX. Is there a specific reason you picked ConTeXt?
> I usually use pandoc for converting my Markdown
See my Typesetting Markdown series:
https://dave.autonoma.ca/blog/2019/05/22/typesetting-markdow...
> Is there a specific reason you picked ConTeXt?
LaTeX:
* doesn't (easily, or practically) separate content from presentation;
* has arcane, antiquated syntax;
* packages can have namespace conflicts (rare, but happens);
* requires package installation for additional features.
ConTeXt, being monolithic and newer, avoids all those issues. The feature matrix lists a number of samples typeset with ConTeXt:
https://keenwrite.com/blog/2025/09/08/feature-matrix/
FWIW, pandoc has the ability to generate ConTeXt code.
My project https://latex.to supports ConTeXt (plus all other TeX Live engines). Click + then New from showcase then ConTeXt to try it.
Cool! But it appears to always use LuaTeX as the engine, so only the older MkIV format is supported, and not the current LMTX format. The caching also doesn't seem to work quite right, since it appears to regenerate the font caches every time that you run it, which makes recompiles quite slow.