stnd.build

Standard::Markdown

The simplest book on the shelf — one specimen page. Standard renders CommonMark plus exactly three extensions, all Obsidian-compatible. If it renders on this page, it is in the standard; if it doesn’t, it isn’t.

Base

Everything in CommonMark: headings, emphasis, lists, links, images, code fences, blockquotes, tables.



Caption

Captions recede like wall labels


Extension 1 — Callouts

> [!note]
> Obsidian-flavored callouts, any type: note, warning, tip, caption…
Note

Obsidian-flavored callouts, any type: note, warning, tip, caption…

Thirteen types render as semantic theme boxes, each with its own symbol:

Type Symbol Use
note 📝 Supplemental context or explanations
info ℹ️ Informational details
todo ☑️ Pending tasks or lists
tip 💡 Best practices, optimization shortcuts
success ✅ Completed runs, positive confirmations
question ❓ Q&A blocks, flashcard prompts
warning ⚠️ Cautions, potential pitfalls
failure ❌ Errors, failed validations
danger ⚡ High-risk actions, breaking updates
bug 🐛 Reported issues, troubleshooting
example 📄 Reference samples, code demos
quote 💬 Citations, testimonials
abstract 📋 Summary paragraphs, TOC overview

Any type collapses into an HTML <details> disclosure with a + (open by default) or - (closed by default) suffix on the type name:

> [!tip]- Click to see the hint
> Collapsed by default to save reading space.

The question type doubles as a flashcard: collapse the answer, and it stays hidden until clicked — the same mechanic Notion toggle blocks map onto when ingested. ==highlight== highlight test inside a callout compiles to <mark>, same as anywhere else.

A link to [[another-note]] resolves by filename, like Obsidian.

Wikilinks resolve against the vault’s note index when publishing; a link to a private note degrades to plain text rather than a broken link.

Extension 3 — Footnotes

Typography carries the argument.[^1]

[^1]: The footnote lands at the end of the page.

Typography carries the argument.[1]

What is deliberately absent

No MDX, no HTML-in-markdown requirements, no proprietary syntax that would chain a note to one renderer. A Standard note opened in any markdown app in twenty years should read exactly as written — that’s the norm.

Typographic rendering (smart quotes, thin spaces, the :: patterns) is a separate concern with its own book: Standard::Syntax.

Theme Fine-Tuning & Prose Specimen

Select any theme below to preview how font stacks, scales, line-heights, and colors react on this exact document:

Narrative Specimen

Typography is the craft of endowing human language with a durable visual form. When an essay is set with care, the reader perceives neither the effort of typesetting nor the friction of the medium — only the living cadence of the argument itself.

“A real book is not an interactive experience; it is an intimate conversation across centuries between two minds.”
— Robert Bringhurst, The Elements of Typographic Style

Consider the subtle mechanics of rhythm: when ideas take physical or digital form, their weight, measure, and contrast dictate how deeply they settle into memory. Whether set in a literary serif like Newsreader, an assertive neo-grotesque like Inter, or a razor-sharp monospaced face like Maple Mono, the page creates an atmosphere before a single sentence is consciously analyzed.

Inline formatting exercises include bold emphasis for declarations, delicate italics for secondary emphasis or foreign terms, inline monospace tokens for code identifiers, highlighted concepts for immediate attention, and struck thoughts that yield to revised judgment.

  1. The footnote lands at the end of the page. ↩︎