Swingplanit Website

Avoid running expensive raw-data transforms in the UI layer.

Implementation workflow

1. Confirm available data fields and freshness.
2. Build selector + one festival detail view.
3. Add summary metrics and trend chart.
4. Test with:
   • a festival with long history
   • a festival with sparse history
5. Verify empty/loading/error states.

UX and reliability rules

• Keep page load fast; pre-aggregate on backend where possible.
• Show clear message when a metric cannot be computed.
• Keep chart labels and date formatting consistent.
• Do not block render on optional metrics.

Example tasks

• "Add a festival detail page with views/day line chart"
• "Display how many editions this festival had in the data"
• "Wire UI to precomputed metrics dataset"