Task: one content object (article or doc) that presents as slides in the browser when the slides path is available. This page only links unit contracts.
Outcome
- Front matter enables the slides path
- Top-level HR / thematic breaks become slide boundaries
- Browser shows slide chrome when the serving runtime includes the slides player; otherwise you get the honest server transcript fallback described on the unit pages
Steps (link out only)
- Author a normal Markdown object under
content/articles/orcontent/docs/— object rules: Content objects, metadata, and locales. - Enable slides and understand HR boundaries:
- Thin hub (navigation only): Write and embed Markdown slides.
- Live demo page when the runtime mounts the player: Slides demo.
Canonical units (do not restate props here)
| Role | Unit page | Layer |
|---|---|---|
| Enable slides path | slides-front-matter | MD structure |
| Slide boundaries | thematic-break | MD structure |
| AUP deck / slides player (Web-only widget) | deck | AUP widget — not a layout component |
| Optional rich media inside a slide | media · image (inline) | primitive / MD |
Layer discipline
- MD structures (
slides: true, HR) live under/docs/web-device/markdown/…. deckis an AUP widget, not a Web Device theme component and not a cross-device primitive. Contract: deck widget.- Do not treat layout components such as
product-showcaseas slide APIs.
Fallback honesty
Without slides: true → ordinary article. Without the slides widget in the runtime → server transcript only. Those statements are owned by the unit pages above; this recipe does not invent a third fallback story.
Related
- First site if you still need a host site
- Docs board if the slides object is a doc on a board
- Showcase mapping for interactive AUP demos (separate from Markdown slides)