# Dashboard Design — First Pass

## Decision the dashboard supports

Help a solo or small VTT product team identify which current Player's Handbook option names have a corresponding name in SRD 5.2.1 and which items need further review before product use.

The interface deliberately uses **Name matched in SRD 5.2.1**, **No SRD 5.2.1 name match — review needed**, and **Ambiguous — manual review required**. It does not convert a name comparison into a legal conclusion.

## Information hierarchy

1. **Scope and limitation:** The edition-to-SRD comparison and legal limitation appear at the top.
2. **Decision metrics:** Reviewed, matched, review-needed, and approved-alias counts summarize workload.
3. **Coverage by category:** A sorted bar view shows where review effort concentrates.
4. **Option explorer:** Search and filters let a builder inspect individual names and evidence.
5. **Class/species matrix:** A visual check supports the original character-creator use case.
6. **Audit handoff:** A downloadable prompt carries the method into a local VTT codebase.
7. **Method and attribution:** Verification boundaries and required SRD attribution remain accessible.

## Interaction decisions

- Search is client-side and sends no query data anywhere.
- Category and coverage filters can be combined.
- Results show the SRD page and alias status when available.
- The table uses explicit status text and symbols so meaning does not depend on color.
- The downloadable audit prompt instructs an AI to keep proprietary material local and return a reproducible review queue.

## First-pass limits

- Anonymous aggregate search analytics are not active. They require a documented privacy model and a backend or privacy-focused analytics service.
- The dashboard compares names, not full implementation content.
- It covers the current scoped categories and does not include multiclass combinations, legacy editions, setting-specific material, third-party material, or magic items.
- This prototype uses a static architecture so it can deploy directly from GitHub to Netlify.

## Next design review questions

- Do builders understand the distinction between name coverage and permission without opening the method section?
- Is the review-needed queue more useful when sorted by category, alphabetically, or by observed search demand?
- Should the next iteration add a saved/exportable review list before anonymous analytics?
