Skip to content

Dashboard Conventions

Jeongseok Lee edited this page Jun 17, 2026 · 1 revision

Dashboard Conventions

Source-of-truth rules for keeping the wiki consistent as the feedstock list grows.

Page Roles

Page Owns Avoid
Home Summary, navigation, external links Long feedstock tables or historical notes
Feedstock Inventory Current row-level status for every tracked feedstock Long explanations, investigation logs
Maintenance Notes Evidence and rationale behind non-obvious row states Duplicating every upstream PR update
Dashboard Conventions Definitions and update rules Per-feedstock status details

Attention States

State Meaning Use When
🟢 All native targets are available, or the package's expected native target set is complete. Artifacts are present for every applicable native target.
🔵 Package is noarch. The feedstock produces platform-independent artifacts.
🟡 One or more native targets are missing. A platform is absent, intentionally skipped, blocked by dependencies, or awaiting validation.

Use 🟡 even when the gap is intentional. Explain durable intentional limits in Maintenance Notes instead of overloading the table row.

Recipe States

Token Meaning
v1 Feedstock uses recipe.yaml.
v0 Feedstock still uses meta.yaml.
v0->v1 Migration PR is open.
v0->v1 queued Migration is prepared but intentionally waiting behind another PR or unblocker.

Platform Tokens

Token Platform
l64 linux-64
la64 linux-aarch64
ppc linux-ppc64le
osx osx-64
arm osx-arm64
win win-64
all All applicable native targets are present.
noarch Platform-independent package.

Update Workflow

  1. Verify current state from upstream feedstock PRs, Anaconda artifacts, and recipe files.
  2. Update the smallest affected row in Feedstock Inventory.
  3. Add or revise Maintenance Notes only for durable context: merged PR evidence, blockers, intentional skips, or ordered follow-ups.
  4. Keep row language compact; link evidence instead of copying long investigation text into the inventory.
  5. After editing, check heading structure, internal wiki links, and row counts before publishing.

Scaling Rules

  • Add new high-volume data to a dedicated page and link it from Home, rather than expanding Home.
  • Prefer one canonical table per data category so counts and status terms do not drift.
  • Keep definitions on this page; other pages should link here instead of repeating the full legend.
  • Archive stale historical notes once they no longer explain an active row or follow-up.

Clone this wiki locally