The brief
A flash battle to close the season: 48 hours, one component. Everyone gets the same event object. Build the best interactive card for it. One component, every state, nowhere to hide. Small canvas, total craft.
Your submission is a demo page that shows the card in every required state, with a control to switch between them.
Fixed inputs
Every card renders this exact object. Treat it as the API response you were handed.
{
"id": "evt_8h2k4",
"name": "Line 4 Line Season 0 Finale Watch Party",
"series": "Line 4 Line Events",
"status": "registration_open",
"startsAt": "2026-10-09T18:00:00Z",
"endsAt": "2026-10-09T21:00:00Z",
"timezone": "America/New_York",
"venue": { "name": "The Foundry", "city": "Brooklyn, NY" },
"isOnline": false,
"capacity": 120,
"registered": 87,
"waitlist": 0,
"price": { "amount": 0, "currency": "USD", "label": "Free" },
"speakers": [
{ "name": "Priya Natarajan", "role": "Season 0 Judge" },
{ "name": "Daniel Okafor", "role": "Week 5 Winner" },
{ "name": "Marisol Vega", "role": "Host" }
],
"tags": ["finale", "community", "in-person"],
"organizer": "Line 4 Line",
"updatedAt": "2026-10-01T12:00:00Z"
}
Required features
These are the floor. Hit all of them or you're not in the running.
- Renders the supplied object; every value on the card comes from it
- All states, switchable on the demo page: default, hover, focus, active, loading, empty, error
- At least one meaningful interaction, such as register, save, or share
- Keyboard navigable with accessible semantics, in light and dark mode
- Responsive from a narrow phone to a wide grid
Bonus
The required list makes builds comparable. Everything above it is where you win.
- Information hierarchy that makes 87 of 120 registered legible at a glance
- Loading and error states designed with the same care as the default
- Micro-interactions that earn their place instead of decorating
- Code clean enough to drop into a real design system tomorrow
Constraints
- Must be deployed to a public URL.
- Repo must be public.
- Built during the 48 hour build window. Commit history is the receipt.
How it's judged
Community vote during the voting window. One upvote per submission. Top 3 take a trophy. Voters are asked to reward information hierarchy, interaction states, accessibility, responsiveness, visual quality, and code quality.