跳到主要內容

Current Web Device source

Web Device Content Markdown

Separate Markdown in content items from an AUP text primitive and .web components, then start from verified source-plus-rendered examples.

This section documents Markdown written in a Web Device content item's content.md. The content reader turns it into an AUP tree, then the current document target renders it as page content. It is not the complete syntax reference for format: markdown in an AUP text primitive, and it is not a .web component catalog.

Each page places author-written source directly above its real result and says what that result proves and deliberately does not prove. The document itself is read-only. A component may retain an intrinsic limited interaction, such as switching a tab; that does not let a reader edit source, a manifest, a content item, or persistent data.

Verified Content Markdown structures

What to writeStart hereResult boundary
YouTube, X/Twitter, or same-site content embedEmbed external and internal contentOnly recognized provider URLs and validated same-site paths are supported; this is not an AUP session or bridge
A readable presentation with an inline playerMarkdown slidesslides: true defines page boundaries; a named layout mounts the player. It does not provide a presenter view or free-form canvas
GFM tables and calloutsTables and calloutsPresents static content; it does not establish editable tables or a data source
Navigation and explanatory cardsMarkdown cardsA link performs ordinary navigation only; there is no exec, write, or editor permission
Numbered tutorialsMarkdown stepsPresents a static step body; it does not execute a step's instructions

Choose the layer first

For a reusable site layout section, start with .web/components and a page layout.aup. That path has its own manifest and renderer contract; a Markdown directive cannot replace it.

For a cross-device interactive AUP tree, start with an AUP app, a target renderer, and session semantics. Seeing one HTML result in a static document target does not verify events, patches, data binding, or another device.

For the exact boundary between these three layers, see Component resolution and AUP on Web Device.