Showcase mapping | ArcBlock

What this page is: a public mapping from local Showcase routes to on-site unit reference pages.
What it is not: production hosting of all Showcase pages, a multi-capability sample contract, or a second API manual.

Showcase proves that a named ARC checkout can demonstrate a type. It does not automatically make a docs-safe product sample. Unit contracts and sample honesty live on:

/docs/aup/primitives/<name>/
/docs/aup/widgets/<name>/

Internal full inventory (non-routed): content/docs/aup/capability-matrix.md §7.

Two Showcase blocklets (ARC repo)

Blocklet	Role	Canonical sources
`blocklets/showcase-dsl`	DSL-authored companion (prefer for reading page sources)	`.aup/pages/*.aup`, `.aup/app.aup`
`blocklets/showcase`	JSON-tree companion (largely isomorphic page set; heavy test fixture)	`.aup/pages/*.json`, `.aup/app.json`

Both live in the ARC repository (ArcBlock/arc), not in this site blocklet. This site only links unit docs and tells you how to run Showcase locally.

Registration note (showcase-dsl)

app.aup loads pages from "pages/*.aup" except [afs-list-searchable, degradation-demo, errors, globe], plus recipe pages blocklet-settings, scaffold-app, afs-workspace. Physical page files can exist without being registered.

Run Showcase locally

Use a local ARC checkout that contains blocklets/showcase-dsl (and optionally blocklets/showcase). Commands below match the same direct-run pattern as Run, check, and inspect and Validate, run, and inspect: do not deploy to DID Space for this evidence path.

From the ARC repository root:

arc --version
# Expect a version you intend to map (docs matrix baseline: 2.0.0-beta.28).

# Preferred: serve the single showcase-dsl blocklet and use the printed URL
arc service start --blocklet blocklets/showcase-dsl --port 4901

Or, from the blocklet directory:

cd blocklets/showcase-dsl
arc blocklet run .

Open the host and path the CLI prints (often a *.localhost URL). Prefer that over inventing a host/port from another machine.

JSON companion (when you need the checked-in JSON tree or existing test fixtures):

# from ARC repo root
arc service start --blocklet blocklets/showcase --port 4902

Regenerate DSL → JSON only inside the ARC repo when you edit DSL sources (Showcase maintainers):

pnpm dsl:regen blocklets/showcase-dsl

This site does not publish that generation workflow as a product feature of www.arcblock.io.

Stop when finished

arc service stop
# or stop only the daemon you started for this check — do not disrupt other local services you still need

Primary primitive demos → unit pages

These Showcase page ids are the usual first stop for each cross-device primitive. Open the unit page for status, document caps, degradation, and sample honesty.

Showcase page id	Primary primitive(s)	Unit page(s)	Notes
`chart`	`chart`	`chart`	web-full demo; document target often unsupported — read unit
`map`	`map` (+ `globe` widget)	`map` · `globe`	`globe` page file may exist but be excepted from app registration
`calendar`	`calendar`	`calendar`
`time`	`time`	`time`
`overlays`	`overlay`	`overlay`	interactive / experimental on document — read unit
`chat`	`chat`	`chat`	often composed with `afs-list`
`device`	`surface`	`surface`	not the Web Device docs-page surface
`subsystems`	`editor`, `canvas`	`editor` · `canvas`
`explorer`	`explorer` (+ AFS widgets)	`explorer` · `afs-list` · `afs-stat` · `afs-preview`
`list-basic`	`afs-list`	`afs-list` · `pagination` widget	also see `list-*` rows below
`markdown`	`text` / `view` / `editor`	`text` · `view` · `editor`	MD rendering contrast, not MD unit docs
`dashboard`	`view`, `input`, `table`, `action`, `media`, `time`	`view` · `input` · `table` · `action` · `media` · `time`	composition page
`form-contact` / `form-wizard`	`input`, `action`, `view`	`input` · `action` · `view`	form demos
`rtc`	(no dedicated page id in the §7 scan)	`rtc`	use unit + matrix; do not invent a Showcase row

Hub indexes: All primitives · Primitive taxonomy.

Showcase page id	Primary widget(s)	Unit page(s)
`prim-app-header`	`app-header`	`app-header`
`prim-app-footer`	`app-footer`	`app-footer`
`prim-key-value-list`	`key-value-list`, `tooltip`	`key-value-list` · `tooltip`
`finance`	`finance-chart`	`finance-chart` · `chart` primitive
`moonphase`	`moonphase`	`moonphase`
`natal`	`natal-chart`	`natal-chart`
`comments`	`comments-surface` (widget)	`comments-surface` widget — distinct from Web Device `comments-surface` surface
`auto-surface`	`auto-surface`	`auto-surface`
`wm-desktop`	`wm` (+ `wm-surface`)	`wm` · `wm-surface`
`tx-detail`	`entity-overview`, `key-value-list`, `tooltip`	`entity-overview` · `key-value-list` · `tooltip`
`openai-home`	`agent` (among others)	`agent`

Hub: All widgets.

`afs-list` variant pages

Showcase page id	Focus	Unit pages
`list-basic`	base list	`afs-list` · `pagination`
`list-pagination`	pagination	same
`list-template`	template	`afs-list` · `text` · `media`
`list-grid` / `list-virtual`	layout modes	`afs-list`
`list-fields-row` / `card` / `compact` / `media` / `hero`	field presentations	`afs-list` · `media` · `action`
`afs-list-searchable`	searchable variants	excepted from app registration — physical page only; still map evidence to `afs-list`

Composition / replica pages (map, do not treat as single-type samples)

These pages combine many primitives for product-shaped demos. Use them for navigation and interaction evidence, then open one unit page per type you care about.

Showcase page id	Typical hits (non-exhaustive)	Start unit pages
`index`	hub	`view`
`content` / `portal` / `report` / `workspace`	multi-primitive	`view` · `table` · `afs-list`
`google` / `openai-home` / `openai-help` / `once` / `myvibe` / `unsplash` / `exposure`	layout replicas	`view` · `media` · `input`
`sh-climate` … `sh-living`	smart-home series	`view` · `table` · `input`
`session` / `session-chrome`	app chrome	`app-header`
`live-updates`	live list / terminal	`afs-list` · `explorer` · `terminal`
`universal` / `supplementary` / `sharing`	multi	`surface` · `view`
`set-sugar`	DSL sugar	`afs-list` · `text` · DSL language reference
`blocklet-settings` / `scaffold-app` / `afs-workspace`	recipe pages (not `pages/*.aup`)	see ARC scaffold / settings shells — not layout-component unit pages

Unregistered physical pages

Page id	Registration	Use
`degradation-demo`	except	degradation chains — Device capabilities and degradation + primitive units
`errors`	except	error surfaces — `surface`
`globe`	except	`globe` (file may still exist under `pages/`)
`afs-list-searchable`	except	searchable `afs-list` variants

Widgets without a dedicated Showcase page name

Do not invent Showcase rows for widgets that only appear composed or not at all. Examples recorded in the matrix appendix include deck, frame, ticker, hero-widget, breadcrumb, chip, and others. Evidence for those types is on their widget unit pages and the internal matrix — not on this map as fake page ids.

Markdown slides on this site use MD units + deck, not a Showcase page: Recipe: slides in an article.

How to use this map with unit docs

Pick a Showcase page id above and open it in your local Showcase run.
Open the linked unit page for each type you assert.
If you need a docs-safe sample on www.arcblock.io, that is a separate bar (released + sample contract on the unit page / #304) — Showcase alone is not enough.

Recipes hub
AUP primitives hub
AUP widgets hub
Web Device components hub (layout components — different layer from Showcase AUP trees)