How to Build a Conference Management System with Lovable

1Create a Supabase schema for a conference management system.
2
3Tables:
4- conferences: id (uuid pk), organizer_id (references auth.users), name (text), tagline (text), start_date (date), end_date (date), venue (text), city (text), website_url (text), logo_url (text), cfp_open (bool default false), cfp_deadline (timestamptz), is_published (bool default false), created_at
5
6- ticket_tiers: id (uuid pk), conference_id (references conferences), name (text), description (text), price_cents (int), total_quantity (int), remaining_quantity (int), sale_start (timestamptz), sale_end (timestamptz), sort_order (int)
7
8- cfp_proposals: id (uuid pk), conference_id (references conferences), speaker_name (text), speaker_email (text), speaker_bio (text), speaker_company (text), speaker_photo_url (text), talk_title (text), talk_abstract (text), talk_format (text check: talk|workshop|panel|lightning), preferred_duration_minutes (int), technical_level (text check: beginner|intermediate|advanced), tags (text array), status (text default 'pending' check: pending|accepted|rejected|waitlisted), organizer_notes (text), submitted_at (timestamptz default now())
9
10- speakers: id (uuid pk), conference_id (references conferences), proposal_id (references cfp_proposals), name (text), email (text), bio (text), company (text), photo_url (text), website_url (text), twitter_handle (text), linkedin_url (text)
11
12- tracks: id (uuid pk), conference_id (references conferences), name (text), color (text), room (text), sort_order (int)
13
14- sessions: id (uuid pk), conference_id (references conferences), track_id (references tracks), speaker_id (references speakers nullable), title (text), description (text), format (text), duration_minutes (int), scheduled_start (timestamptz nullable), scheduled_end (timestamptz nullable), room (text), status (text default 'draft' check: draft|confirmed|cancelled), sort_order (int)
15
16- attendees: id (uuid pk), conference_id (references conferences), ticket_tier_id (references ticket_tiers), name (text), email (text), company (text), registration_code (text unique), stripe_payment_intent_id (text), status (text default 'confirmed' check: confirmed|cancelled), checked_in (bool default false), checked_in_at (timestamptz), created_at
17
18RLS:
19- conferences: SELECT public; INSERT/UPDATE where organizer_id = auth.uid()
20- ticket_tiers/tracks/sessions: SELECT public; INSERT/UPDATE/DELETE where conference_id IN (SELECT id FROM conferences WHERE organizer_id = auth.uid())
21- cfp_proposals: SELECT where conference_id IN organizer's conferences OR speaker_email = auth.jwt()->>'email'; INSERT public
22- speakers: SELECT public; INSERT/UPDATE/DELETE organizer only
23- attendees: SELECT where conference_id in organizer's conferences; INSERT by SECURITY DEFINER function only
24
25Create a function register_attendee(p_conference_id uuid, p_tier_id uuid, p_name text, p_email text, p_company text, p_payment_intent_id text) RETURNS jsonb SECURITY DEFINER that atomically decrements remaining_quantity and inserts the attendee row with a generated registration_code.

1Build two pages:
2
31. Public CFP submission page at src/pages/CFPSubmit.tsx (route /cfp/:conferenceSlug):
4- Fetch conference to confirm cfp_open = true and cfp_deadline is in the future
5- If CFP closed, show 'Submissions are now closed' message
6- Form (react-hook-form + zod):
7  - speaker_name, speaker_email, speaker_bio (Textarea 50–500 words), speaker_company
8  - speaker_photo upload (Supabase Storage, returns URL)
9  - talk_title, talk_abstract (Textarea 300–1000 words with live word count)
10  - talk_format: Select (Talk, Workshop, Panel, Lightning Talk)
11  - preferred_duration_minutes: Select (15/30/45/60/90)
12  - technical_level: RadioGroup (Beginner, Intermediate, Advanced)
13  - tags: multi-value Input (e.g. React, TypeScript, Architecture)
14- On submit: INSERT into cfp_proposals
15- Confirmation: 'Your proposal was submitted. Reference: [proposal id first 8 chars]'
16
172. Organizer CFP review page at src/pages/CFPReview.tsx (requires auth):
18- Show proposal count by status in Badge pills: Pending (N), Accepted (N), Rejected (N), Waitlisted (N)
19- Tabs for each status
20- Each proposal as a Card:
21  - Speaker photo avatar, name, company
22  - Talk title (large), format Badge, duration Badge, level Badge
23  - Abstract truncated to 3 lines with 'Read more' expand
24  - Action Buttons: 'Accept', 'Reject', 'Waitlist', 'View Full'
25  - 'View Full' opens a Sheet with complete proposal details and organizer_notes Textarea
26- Accept action: UPDATE status='accepted', then INSERT into speakers using proposal data
27- Show a progress bar: X of Y proposals reviewed
28- Filter by format, level, and tags

1Build a schedule builder at src/pages/ScheduleBuilder.tsx (requires auth).
2
3Layout:
4- Horizontal scroll container with one column per track
5- Each column header: track name (colored with track.color), room name, add session Button
6- Each column body: list of session Cards sorted by sort_order
7- Unscheduled sessions panel on the left: sessions with scheduled_start = null
8- Day selector at the top if conference spans multiple days
9
10Drag-and-drop (dnd-kit):
11- Use DndContext, SortableContext, useSortable hooks
12- Sessions can be dragged from the unscheduled panel into any track column
13- Sessions can be reordered within a track column
14- Sessions can be moved between track columns
15
16Time assignment:
17- When a session is dropped into a track column at a position, show a time picker popover to assign scheduled_start
18- scheduled_end = scheduled_start + session.duration_minutes
19
20Conflict validation (run before confirming any drop):
21function validateDrop(session, targetTrack, proposedStart, allSessions): ValidationResult
221. If session has a speaker_id, check if that speaker has another session in allSessions where the time ranges overlap
232. If targetTrack has a room, check if another session in the same track/room has overlapping times
243. Return { valid: true } or { valid: false, conflict: 'Speaker [name] is already scheduled at this time in Track B' }
25
26If validation fails:
27- Cancel the drop (do not update the database)
28- Show a Toast with the conflict message
29- Highlight the conflicting session with a red border for 3 seconds
30
31Session Card component:
32- Title, speaker name (if assigned), duration Badge, format Badge
33- Status indicator: draft=gray dot, confirmed=green dot
34- 'Edit' icon opens session edit Dialog
35- Grip handle for drag initiation

1Build two components:
2
31. Public registration page at src/pages/AttendeeRegistration.tsx:
4- Show conference details and ticket tiers as Cards
5- Each tier: name, description, price, remaining quantity, sale window
6- 'Register' Button disabled if sold out or outside sale window
7- Registration form (free tier, no Stripe):
8  - name, email, company (optional)
9  - Submit calls register_attendee RPC function directly
10- Registration flow (paid tier, with Stripe):
11  - Collect name, email, company in a form first
12  - Submit calls create-checkout Edge Function
13  - Redirect to Stripe Checkout
14  - Success URL: /conference/[slug]/registration-success?session_id={CHECKOUT_SESSION_ID}
15
162. Stripe integration Edge Functions:
17
18supabase/functions/create-checkout/index.ts:
19- Receive POST with { tier_id, conference_id, name, email, company }
20- Create Stripe Checkout session with:
21  - line_items from ticket tier name and price_cents
22  - metadata: { tier_id, conference_id, name, email, company }
23  - success_url and cancel_url
24- Return { url: checkoutUrl }
25
26supabase/functions/stripe-webhook/index.ts:
27- Verify webhook signature using STRIPE_WEBHOOK_SECRET
28- Handle checkout.session.completed event
29- Extract metadata from session.metadata
30- Call register_attendee(conference_id, tier_id, name, email, company, payment_intent_id)
31- Return 200
32
33Registration success page at src/pages/RegistrationSuccess.tsx:
34- Fetch attendee by stripe session ID
35- Show confirmation: name, ticket tier, registration_code
36- QR code of registration_code (qrcode.react)

1Build two pages:
2
31. Public schedule page at src/pages/ConferenceSchedule.tsx:
4- Only visible when conference.is_published = true
5- Filter bar: track Select, format filter Checkboxes, speaker Select
6- Layout: time slots as rows, tracks as columns (same as builder but read-only)
7- Each session Card shows: title, speaker photo + name, duration, format Badge, room
8- Clicking a session opens a Sheet with full details: abstract, speaker bio, room, time
9- 'Add to my schedule' Button (stores in localStorage as a Set of session IDs)
10- 'My Schedule' tab showing only bookmarked sessions
11- Mobile view: single column with track filter instead of multi-column grid
12
132. Organizer attendee management at src/pages/AttendeeManagement.tsx:
14- Stats row: total registrations, checked in count, revenue (sum of ticket prices)
15- DataTable of all attendees: name, email, company, ticket tier Badge, registration code, status, checked_in
16- Search by name or email
17- Export to CSV Button
18- Check-in tab: Input for registration code + 'Check In' Button (same pattern as event-registration-system check-in page)
19- Manually mark attendee as checked_in = true and set checked_in_at = now()
20- Show real-time checked-in count updating as attendees are processed