Dashboard linking

Ready · M2 — Internal Adoption + Design Partners1 / 2 (50%)

Objective

Author-friendly cross-board navigation: dashboard-root markdown paths (e.g. /zendesk/tickets/list), ../ relative to the current board, query params = variables, render-time rewrite for dft serve vs Cloud. List/detail (and similar) are path conventions, not YAML registries in v1. Optional canonical entity metadata is an M5 maybe—separate task.

Downstream

Quickstart dashboards — program setup depends on dashboard-linking-v1; connector pilots inherit that ordering via program setup.

Design notes

Why (landscape): Research
What / how (plan of record): Spec — dashboard URL root, storage slug mapping, ../, docs required with v1.
ADRs: Decisions

Deliverables

[ ] Board-path resolver + link_context; unit tests (v1 task).
[ ] docs/docs/ author rules (same release as resolver): dashboard-root paths, ../, variables in query, branch merge, list/detail naming convention.
[ ] Agent skills: dataface/ai/skills/building-dataface-dashboards/SKILL.md + .codex/skills/quickstart-product-dashboard-research/SKILL.md (see v1 task plan §6).
[ ] Quickstart link-matrix template aligned with examples.
[ ] Optional M5: canonical entity metadata only if evidence says conventions are insufficient.

Tasks

Dashboard linking v1 (dashboard-root paths, render-time rewrite, docs) — not_started
Dashboard linking — canonical entity metadata (M5, only if needed) — not_started