Myne writes plain markdown, the same text files you could open in any editor, and renders it live as you type. The dialect is CommonMark plus the common GitHub-Flavored extensions, footnotes, wikilinks, and YAML frontmatter, with a few small Myne additions. This section documents each construct.
The one promise behind all of it
Rendering never changes your file bytes. Myne shows headings as headings, callouts as callouts, and math as math, but what is saved on disk is exactly the markdown you typed. The styling is a view, not a rewrite. Move your notes to another editor and they read as ordinary markdown.
What’s in this section
- Markdown basics: headings, emphasis, lists, links, quotes, and finding text in a note.
- Tables: pipe tables with column alignment.
- Code blocks: fenced code with syntax highlighting.
- Footnotes and reference links: footnotes, reference-style links, and the full wikilink syntax.
- Math: inline and block LaTeX via KaTeX.
- Diagrams: Mermaid diagrams rendered to images.
- Callouts: highlighted admonition blocks.
- HTML and inline extras: a small set of inline HTML tags, the five-color highlight palette, sub/superscript, emoji, and tags.
- Comments: notes-to-self written
%%text%%, dimmed in the editor and dropped from HTML, PDF, plain-text export, and document statistics. They stay verbatim in the Markdown export, since that is your file byte-for-byte. - Frontmatter and properties: the YAML block at the top of a note.
What Myne does not do
Myne’s markdown is a fixed, curated dialect: there is no extension mechanism and no way to add your own syntax. A few things are deliberately out: there is no note transclusion (an embed renders as a labeled chip, not the other note’s content inline), no whiteboard/canvas, and no cross-vault links. Template placeholders like {{date}} are a separate feature, documented in Templates.