Pluggable Markdown — the plugin system hiding in three backticks
Fenced code blocks make markdown extensible: label a ``` block and you can embed mermaid diagrams, database views, math, whole other tools — inside plain text.
Pluggable Markdown
Here's a feature of markdown that almost nobody frames properly: markdown has a plugin system, and it's been hiding in plain sight inside the triple-backtick block.
You know fenced code blocks:
```python
print("hello")
```
The label after the backticks was originally just for syntax highlighting. But look at what it actually is: a named, delimited region of plain text that tools can interpret however they like. That's an extension point. Someone labels a block mermaid and suddenly markdown contains diagrams:
```mermaid
graph LR
A[plain text] --> B[named block] --> C[whole new tool]
```
graph LR
A[plain text] --> B[named block] --> C[whole new tool]
(Yes, that rendered. This page is markdown.)
What plugs in
- Diagrams:
mermaid(flowcharts, sequence diagrams, gantt charts) — supported by GitHub, Obsidian, Flowershow and most modern renderers - Database views: Obsidian's
dataviewblocks query your notes; Bases goes further: the database pattern, living inside a fence - Maths:
latex/mathblocks (and$...$inline in many tools) - Music, chemistry, charts:
abcnotation,smilesmolecules, chart-rendering blocks; the Obsidian plugin ecosystem alone has dozens - Interactive code: Jupyter and Quarto execute fenced blocks and embed the results — a markdown file that runs
- And the degenerate case that proves the rule: unlabelled fences still just show code, and unknown labels degrade gracefully to plain text. Old tools never break on new blocks.
Why this design is quietly brilliant
Most formats extend by growing their spec, and every tool must implement everything or fail. Markdown extends by convention inside a container the spec already has. The format stays tiny; the ecosystem grows unboundedly; nothing ever breaks. It's the same trick that made HTML's <script> tag world-changing, done in plain text.
Add the other two extension points — inline HTML when you need real layout and frontmatter for structured data — and "just a formatting syntax" turns out to be a small, stable core with three clean sockets for infinite capability. None of that is an accident of design. See why markdown is eating the world.
More syntax fundamentals: Markdown Basics · the full everywhere list
