Skip to main content

​
Is TemplateDX compliant with CommonMark?

Yes — TemplateDX supports a superset of CommonMark. On top of CommonMark, TemplateDX adds tags, filters, variables, and components. Note: TemplateDX’s parser does not enable GitHub-flavored Markdown extensions — it uses remarkParse + remarkMdx + remarkFrontmatter, not remark-gfm. GFM-only features (strikethrough, task lists, GFM tables with cell alignment) are parsed as plain text, not as structured AST nodes.

​
What’s the difference between MDX and TemplateDX?

MDX is a document format — Markdown that can embed JSX — that compiles to JavaScript. TemplateDX is a prompt-rendering engine that shares the surface syntax but parses to an AST, evaluates expressions and tag plugins against a props object, and serializes back to Markdown. MDX targets JSX runtimes; TemplateDX targets LLM prompts.

​
Can you support output formats other than Markdown?

We’re focused on Markdown today. The stringify step is pluggable in principle, so emitting HTML or other formats is a reasonable extension — PRs welcome at github.com/agentmark-ai/agentmark.

​
How does TemplateDX relate to AgentMark?

TemplateDX is the templating engine underneath AgentMark. AgentMark uses TemplateDX for prompt rendering and builds on its tag plugin ecosystem.

​
What languages are supported?

  • TypeScript / JavaScript — full parse / transform / stringify pipeline via @agentmark-ai/templatedx.
  • Python — transform + stringify via agentmark-templatedx. Python consumes ASTs produced by the TS parser (native Python parsing is still TS-only).