This is a full-stack platform. For data persistence (events, teams, scores, leaderboard), which database approach do you want? No database yet (mock data)
How should authentication work for the 3 roles (organizer, participant, judge)? No auth yet (UI only)
What would you like me to build in this first iteration? The full platform is quite large. Frontend only (all pages)
Should the live leaderboard update in real-time (WebSocket/Supabase Realtime) or with periodic refresh? Real-time (Recommended)
Let me re-read both attachments carefully to understand all the requirements:
Now let me check the existing project structure and available components:
Good -- fresh Next.js 16 project with shadcn/ui dependencies but no UI components installed yet. Let me now generate design inspiration for this dark, neon, event-oriented platform, then write the plan.
Now I have a clear picture. Let me write the comprehensive plan:
Let me read the full plan and start building:
Good, I have the full plan and current project state. Let me set up the task list and start building:
Let me also check what shadcn components exist and read the lib/utils:
All shadcn/ui components are already available. Now let me start building. I'll create the foundation files first -- types, mock data, theme, layout, and shared components -- all in parallel where possible:
Now let me generate the event cover images and artist placeholder images, and update the theme + layout simultaneously:
Now let me update the theme and create the shared components:
Now let me create the shared layout and feature components:
Now create the feature components in parallel:
Now update the root layout with the header/footer and proper metadata:
Foundation is done. Now move to task 2 -- Homepage, Browse Events, and Event Detail pages:
Homepage, Browse Events, and Event Detail are done. Now the Team Builder:
Now the live leaderboard:
Now the organizer pages:
Now the final piece -- the Judge Scoring Panel:
The entire FantaDance frontend is now built. Here's a summary of what was created across 9 pages and 10+ shared components:
Pages: Homepage with hero/how-it-works/featured events, Browse Events with search/filter, Event Detail with artist roster and scoring rules, Team Builder with budget-constrained artist selection, Live Leaderboard with simulated real-time rank changes every 5 seconds (podium + full rankings + score ticker), Organizer Dashboard with stats and event list, 4-step Event Creation Wizard (info/artists/rules/review), Event Management with teams and embedded leaderboard, and a Judge Scoring Panel with large touch targets, quick-score buttons, and a recent scores log.
Design system: Dark navy theme with neon cyan/magenta/green accents, custom animations for rank changes, score pops, and a live ticker, all using the shadcn/ui component library. The mock data layer (lib/types.ts + lib/mock-data.ts) contains 3 events, 12 artists, 8 teams, and scoring rules -- all easily swappable for a real API when you add a database.
You can send messages while the preview loads