Markdown Reference
Your posts are Markdown, and Teatime gives you more than the basics. This page is the syntax reference. For a page that renders all of it at once, see the style test.
Callout containers
Callouts read a little softer than a plain quote, and they come in several tones:
Note
A note container suits context you would like readers to notice without alarm.
WARNING
A warning container fits the rare moment when a detail could really trip someone up.
DANGER
A danger container is reserved for the few cases where a mistake is costly.
You can fold a longer aside behind a summary to keep the page scannable:
A longer aside, folded away
Content inside a details container stays hidden until a reader opens it, which keeps supporting detail close by without crowding the main thread.
Small inline labels help with versions or status <Badge .../> would swallow the rest of the paragraph.
Code blocks
A code block can carry a title, highlight a line, and number its lines:
```csharp:line-numbers {3} [Program.cs]
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
app.MapGet("/", () => "Hello from Teatime"); // this line is highlighted
app.Run();
```Images
The alt text becomes a caption below the image, and a few attributes set the size:
{.natural}keeps the original size, and{.plain}drops the frame{.left}and{.right}float the image beside your text{.wide}reaches a little past the reading column{.full}spans the whole viewport
The post cover set in front matter accepts the same width attributes, plus two that tune its height.
For a row of images side by side, wrap them in a gallery. The gallery page shows one in place:
::: gallery



:::Maps
To place points on a map, use a map block. Each pin needs coords and can carry a name, a phone number, a contact address, a website, and a line of text. The pins show as markers, and a click opens their details:
Leave zoom and center out and the map frames every pin for you. Maps use OpenStreetMap tiles, which load from OpenStreetMap when a reader opens the page.
Abbreviations
Define a term once and every mention of it on the page carries its explanation:
The HTML spec is written by the WHATWG and rendered here over HTTP.
*[HTML]: HyperText Markup Language
*[WHATWG]: Web Hypertext Application Technology Working Group
*[HTTP]: HyperText Transfer ProtocolThe HTML (HyperText Markup Language) spec is written by the WHATWG (Web Hypertext Application Technology Working Group) and rendered here over HTTP (HyperText Transfer Protocol).
Definitions can sit anywhere in the file, so most writers keep them at the bottom with the footnotes. Terms show up with a dotted underline. On a desktop the explanation appears when you hover; on a phone, tap the term and it appears just above it.
Definition lists, footnotes, and links
Definition lists keep paired ideas tidy:
- Static export
- A folder of plain HTML (HyperText Markup Language) you can host anywhere.
- Live server
- The running app that reads your Markdown and renders it on request.
And when a thought needs a source, a footnote tucks it out of the way.1
External links can open in a new tab with a small attribute, as standardized in the Markdig reference, written as {target="_blank" rel="noopener"}.
-
Footnotes render at the bottom of the page with a link back to where you were reading.↩