home · story · engine · guide · about

ENGINES

tools that harness mtx.

mtx is a syntax — a language spec. engines are the tools that parse, render, and work with mtx content.

available now

mtxweb — web engine

php engine that parses mtx files into html for the browser.
drop 3 files on shared hosting. your site is live.

• parses .mt.txt .ht.txt .tx.txt and plain .txt (with header)
• full lvl3 support — every mtx feature works
• clean urls — /about serves about.mt.txt
• built-in dark mode (follows system preference)
• zero dependencies — just php + apache

set up mtxweb in 5 minutes

repo: github.com/digiopsys/mtxweb

coming soon

mtxhill — syntax highlighter

syntax highlighting for mtx across editors.
targets: VS Code, micro, vim, QuickText (Android), GitHub Linguist.

transpilers

• .mt.txt to .md — doc conversion for markdown-based tools
• .ht.txt to .html — full page conversion
• .cc.txt to .c — harnessing xmlrpc tag syntax
• .jt.txt to .js — harnessing marko and svelte tag syntax
• .jo.txt to .json — forking jq to produce json
• .xm.txt to .xml — forking xmlstarlet/minixml to produce xml
• browser renderer — client-side mtx rendering (like marked.js for mtx)

query targets (q* family)

• .qd.txt to drizzle ORM (JavaScript)
• .qj.txt to JOOQ (Java)
• .qe.txt to EdgeQL (EdgeDB)
• .qr.txt to Redis ORM
• .qs.txt to SQL (generic)

future targets

• .rs.txt to Rust — harnessing markup.rs tag syntax
• .go.txt to Go — harnessing html/template
• .am.txt to assembly
• .bs.txt to bash
• .vl.txt to verilog

one syntax. one trigger. every output format.

build your own

mtx is a spec, not a locked ecosystem.
the mtx concept doc defines the full syntax.
build a parser in any language — the rules are deterministic:

• ; = trigger. ;; = literal.
• 10 closers, all ; + 1 char
• ;\ + 2 chars = element. ;: + 2 chars = datapod.
• no whitespace dependency. no ambiguity.

home · story · engine · guide · about

github · ©2026 digiopsys. powered by mtxweb.