This directory contains example UDS dashboards demonstrating various features and patterns of the Universal Dashboard Specification v0.1.0.
Total Examples: 44 YAML files Specification Version: 0.1.0 Purpose: Documentation, test fixtures, reference implementations
REQUIRED panel types that all conformant implementations MUST support:
kpi-basic.uds.yaml- Single KPI with currency formattingkpi-comparison.uds.yaml- KPI with period-over-period comparison, sparkline, and thresholdstrend-basic.uds.yaml- Simple line chart showing metric over timetrend-multi-series.uds.yaml- Multiple metrics with dimensional breakdownbar-basic.uds.yaml- Horizontal bar chart with top N groupingbar-stacked.uds.yaml- Stacked/grouped bar with two dimensionstable-basic.uds.yaml- Data table with sorting and paginationtable-conditional.uds.yaml- Table with conditional formatting and data barspie-basic.uds.yaml- Donut chart with top N groupingtext-basic.uds.yaml- Text panel with markdown and metric interpolationprogress-basic.uds.yaml- Progress toward target with time-adjusted status
RECOMMENDED panel types for richer visualisations:
scatter-basic.uds.yaml- Scatter plot with size and colour encodingheatmap-basic.uds.yaml- Two-dimensional heatmap with colour intensityfunnel-basic.uds.yaml- Conversion funnel with stage progressiongauge-basic.uds.yaml- Gauge with threshold zones and target markermap-choropleth.uds.yaml- Geographic choropleth maptreemap-basic.uds.yaml- Hierarchical treemap with size and colour metricshistogram-basic.uds.yaml- Distribution histogram with auto binningwaterfall-basic.uds.yaml- Waterfall chart showing cumulative changesbullet-basic.uds.yaml- Bullet chart with target and qualitative ranges
RECOMMENDED panel types using hybrid data binding pattern:
progress-milestones.uds.yaml- Progress with quarterly milestonesokr-company.uds.yaml- Company-level OKRs with weighted scoringokr-team.uds.yaml- Team OKRs grouped by departmentscorecard-balanced.uds.yaml- Balanced scorecard with dynamic bindingsscorecard-static.uds.yaml- Scorecard with static perspective definitionsroadmap-product.uds.yaml- Product roadmap with dependencies and swim lanes
Different layout patterns for organising panels:
grid-responsive.uds.yaml- Responsive grid with breakpointssections-collapsible.uds.yaml- Collapsible sections layouttabs-multi.uds.yaml- Multi-tab layout with badgesflow-cards.uds.yaml- Auto-flowing card layout
Dashboards optimised for different user personas:
executive-summary.uds.yaml- High-level summary for executivesanalyst-exploration.uds.yaml- Comprehensive analysis workbenchmanager-team.uds.yaml- Team performance monitoringoperator-realtime.uds.yaml- Real-time operations monitoringexternal-client.uds.yaml- Client-facing dashboard with embedding
Complex real-world scenarios:
sales-executive-q4.uds.yaml- Multi-source executive dashboard with theming and i18nmulti-source.uds.yaml- Combining data from multiple semantic sourcesderived-metrics.uds.yaml- Arithmetic, conditional, window, and case expressions
Error handling and special scenarios:
empty-data.uds.yaml- Graceful handling of empty data stateserror-fallback.uds.yaml- Error handling and retry configurationconditional-display.uds.yaml- Conditional panel visibility
AI generation workflow:
generation-request.uds.yaml- AI generation request with constraintsgeneration-output.uds.yaml- AI-generated dashboard with confidence scores
The absolute minimum valid UDS document (from Phase 0).
Each example includes:
- Header comment explaining purpose and demonstrated features
- Relevant specification section references
- Inline comments explaining non-obvious choices
- Realistic fictional data
To validate YAML syntax:
# Check all files are valid YAML
find examples -name "*.yaml" -exec python3 -c "import yaml; yaml.safe_load(open('{}'))" \;
# Count examples
find examples -name "*.uds.yaml" | wc -l
# Check all have UDS version
grep -l "^uds:" examples/**/*.yaml | wc -l
# Check all have intent
grep -l "intent:" examples/**/*.yaml | wc -lWhen the JSON Schema is available (Phase 3), validate with:
# Validate all examples against schema
for file in examples/**/*.yaml; do
echo "Validating $file"
ajv validate -s schema/uds-0.1.0.json -d "$file"
doneExamples use consistent fictional semantic sources:
Sales/Revenue:
- id: sales
type: cube
endpoint: "https://cube.example.com/cubejs-api/v1"HR/People:
- id: hr
type: dbt
endpoint: "https://dbt.example.com/semantic-layer/v1"Goals/OKRs:
- id: goals
type: cube
endpoint: "https://cube.example.com/cubejs-api/v1"Metrics/Finance:
- id: metrics
type: cube
endpoint: "https://cube.example.com/cubejs-api/v1"Common fictional metrics used across examples:
sales.total_revenuesales.total_orderssales.average_order_valuesales.conversion_ratesales.quota_attainmentcustomers.nps_scorecustomers.satisfaction_scorehr.employee_countgoals.progressgoals.confidence_score
Examples are designed to become test fixtures for:
- Parser validation - Do parsers correctly read all properties?
- Renderer testing - Do renderers produce expected output?
- Conformance levels - Which examples require Core/Standard/Complete support?
| Level | Required Examples |
|---|---|
| Core | All core/ examples, minimal.uds.yaml |
| Standard | Core + extended/ + goal-oriented/ (partial) |
| Complete | All examples |
When adding new examples:
- Use the standard header template
- Include relevant spec section references
- Use consistent fictional sources and metrics
- Add inline comments for complex patterns
- Use British English spelling (organisation, behaviour, colour)
- Test YAML validity before committing
- Valid YAML 1.2 syntax
- Includes
uds: "0.1.0" - All REQUIRED properties present
- Realistic fictional data
- Clear comments explaining patterns
- British English spelling
- Consistent formatting
- 0.1.0 (2026-01) - Initial example collection (44 files)
Copyright 2026 Tortoise AI Ltd Licensed under Apache License 2.0