Use a task recipe when you know the outcome (first site, list page, docs board, slides, source binding) and need the correct chain of unit pages. Recipes do not restate props, caps, or sample contracts — those live on:
/docs/aup/primitives/<name>//docs/aup/widgets/<name>//docs/web-device/components/.../docs/web-device/markdown/.../docs/web-device/surfaces/...
Task recipes (#299 wave 4)
- First site — minimal static site from verified getting-started + layout units.
- Collection list page — content objects + list layout components.
- Docs board —
docs-pagesurface and related chrome. - Slides in an article — MD slides structures +
deckwidget. - Bind source to layout —
$source.<name>into a layout section.
Showcase evidence map
- Showcase mapping — showcase-dsl / showcase page ids → primitive/widget unit pages, plus local run instructions (not full hosting on this site).
Legacy narrative recipes
These pages keep longer narrative slices with evidence boundaries. Prefer the task recipes above when you only need the unit-page chain.
- Minimal information site — verified route/layout/component foundation narrative.
- Content site — collection vertical-slice narrative and current evidence boundary.
- Custom component — when a second real page needs the same presentation.
- Customize a theme and tokens — narrow token-first visual path.
Getting started (before any recipe)
Layer reminder
| Task needs… | Open unit under |
|---|---|
| Portable AUP tree node | /docs/aup/primitives/ |
| Web-only AUP widget | /docs/aup/widgets/ |
| Theme / site layout component | /docs/web-device/components/ |
| MD directive / structure | /docs/web-device/markdown/ |
| Board shell (docs/search/…) | /docs/web-device/surfaces/ |