Markdown
Plain-text formatting syntax that converts to HTML, used for docs, notes, and web content.
Markdown is a lightweight markup language that uses plain-text punctuation conventions to represent formatting — headings, bold, italic, links, lists, code blocks, and more — in a way that remains readable as raw text and renders to HTML for display. Created by John Gruber with Aaron Swartz in 2004, it was designed to be easy to write and easy to read, without the visual noise of HTML tags.
The core mechanic is straightforward: a plain-text file containing symbols like # for headings, ** for bold, text for links, and > for blockquotes is parsed by a Markdown processor and converted into properly structured HTML. This conversion can happen at write time (static site generators), at read time (browsers via JS libraries), or on demand (server-side rendering). The format is intentionally constrained — it covers the most common formatting needs and deliberately excludes complex layout control, which keeps both the syntax and its implementations simple and predictable.
Markdown became the de facto standard for technical documentation, README files, wikis, blogs, and content management systems. Its ecosystem includes CommonMark (a rigorously specified variant), GitHub-Flavored Markdown (GFM), and hundreds of implementations across every programming language. Most AI coding assistants, note-taking apps, and static site generators speak Markdown natively, making it the closest thing to a universal interchange format for human-written technical content.
The main tradeoff is that Markdown's simplicity, while a strength for writing, becomes a limitation when precise layout or complex data structures are needed. There is no native table support in base Markdown (GFM added it), no way to control fine-grained styling without dropping into raw HTML, and no standard for variables or cross-references. These gaps are addressed by extended syntaxes and preprocessor toolchains (MDX, MDN, Hugo shortcodes), but those fragment the ecosystem. The open question is whether any successor — or any Markdown extension — will achieve the same universal adoption, or whether the web's content layer will consolidate around richer structured formats.