MD vs VTT

Markdown is a lightweight text-based markup language created by John Gruber and Aaron Swartz in 2004. A .md file uses simple conventions (*italic*, **bold**, # headings, - lists) that compile to HTML. It became the default writing format for GitHub READMEs, Stack Overflow posts, Discord messages, and most developer documentation.

Markdown files are plain text — open in any text editor. For formatted preview use VS Code (built-in preview), Typora, Obsidian, or upload to GitHub/GitLab which render Markdown automatically. Every note-taking app (Notion, Bear, Joplin) handles Markdown natively.

Use KaijuConverter's Markdown-to-PDF converter, or command-line Pandoc (the gold standard — installed with one command, converts MD to PDF/HTML/DOCX/EPUB in a single line). VS Code with Markdown PDF extension also works locally.

Markdown for almost everything — it's 10× faster to write, version-control-friendly, and compiles to HTML automatically. Write raw HTML only when you need fine control over layout, embedded JavaScript, or features Markdown doesn't support (complex tables, forms). Static-site generators (Hugo, Astro, Jekyll) compile MD to HTML for you.

Markdown never had a formal spec for its first decade. CommonMark (2014) and GitHub Flavored Markdown (2017) standardized the core syntax, but edge cases (nested lists, HTML embedding, table syntax) still differ across renderers. For portability, stick to basic GFM features.

Yes — most modern doc tools are built on Markdown. MkDocs, Docusaurus, Astro Starlight, GitBook, and Read the Docs all accept Markdown input. For documentation needing rich features (tabs, callouts, versioning), MDX (Markdown + JSX components) extends MD with React-style embeds.