Write tables and callouts in Markdown

The Web Device content reader turns GFM tables and GitHub-style callouts in Markdown into document content. The source and result below use the same document-reading path. They are not a general AUP table or text primitive contract, and they do not imply that format: markdown inside an AUP page has the same result.

This page is a live feature guide. Unit pages: gfm-table, gfm-admonition.

Sample contract

A GFM table

Source:

| File | Purpose | Writes data |
| --- | --- | --- |
| `content.md` | Content item | No |
| `layout.aup` | Page layout | No |

Rendered:

This is a Markdown table handled by the content reader (often as HTML text in the document tree). It does not turn the table into editable data, establish an AFS data source, or prove the AUP primitive table path. Do not confuse an empty chart degradation table (No data / reshape) with this author-written GFM table.

Failure and limits

A GitHub-style callout

Source (custom title on the marker line):

> [!IMPORTANT] This is a content-file capability
> Write this kind of callout in `content.md`. The page presents what the author wrote; it does not execute an action or modify data.

Rendered:

Bare markers (no same-line title) use the reader’s default label for the content locale. English keeps the English defaults from the text renderer; zh defaults are applied at read time:

An explicit same-line title always wins over the locale default, in any locale.

Source (bare marker — label comes from locale defaults):

> [!TIP]
> Prefer a same-line custom title when the English word is not the label you want.

Rendered:

The current reader recognizes five markers: NOTE, TIP, IMPORTANT, WARNING, and CAUTION (case-insensitive). An unknown marker remains an ordinary blockquote instead of becoming a different callout.

Failure and limits

GFM tables and callouts in content items are static document content. To author a runtime AUP tree, keep this document-reading path separate from the target-specific primitive support that its renderer defines. For the site-facing boundary, see AUP layout boundary.

Verification evidence