Skip to main content

Task recipe · ARC 2.0.0-beta.28

Recipe: docs board

Wire a documentation board shell from surface and component unit pages — contracts stay on those pages.

Task: a documentation board: left nav, prose body, breadcrumb, previous/next, optional in-page TOC. This recipe only points at surface and component unit pages.

Outcome

  • A docs board (or collection) served through the docs page surface
  • Board _nav.yaml (or equivalent nav tree) drives the left rail
  • One doc object renders as prose with working prev/next when the tree has neighbors
  1. Have a working Web Device site: Recipe: first site.
  2. Understand content objects under content/docs/: Content objects, metadata, and locales.
  3. Board navigation conventions: Routes, navigation, and locales · Routes and locales reference.
  4. Mount the documentation shell — read the surface unit for author entry and props: docs-page surface.

Canonical units for a docs board

RoleUnit page
Board shell (nav + prose + chrome)docs-page
In-page TOC (when enabled)in-page-toc
Search entry (if the board exposes search)search-page
List/pagination helpers (indexes)pagination surface
Optional comments attachmentcomments-surface surface — different layer from the AUP widget comments-surface

Prose and structure inside a doc

Doc bodies are Markdown. Use unit pages for structure and directives; do not treat layout components as MD:

Layer discipline

NeedLayerWhere the unit lives
Docs chrome / left navWeb Device surface/docs/web-device/surfaces/docs-page/
Card list on a landingWeb Device layout component/docs/web-device/components/...
Portable tree nodeAUP primitive/docs/aup/primitives/...
Web-only AUP chrome widgetAUP widget/docs/aup/widgets/...

Do not document multiple surfaces or components on this recipe page.