Tightly integrate luma

[tomatrow]

Feature: Integrate Luma Events

Goal:
Luma API

---

References

• 💬 Gippity Discovery Adventure — ChatGPT discussion outlining Luma integration details
• 💜 Luma API Docs
• 💵 Luma Pricing (~$70/month)

---

Scope

/events Page (≈2h)

• Fetch events from the Luma calendar
• Display as a list linking to /events/:event-id
• Add toggle to switch between Upcoming and Past events

/events/:event-id Page (≈4h)

• Display key details:
  • Event name
  • Date & location
  • Description
  • Mini map
  • Number of attendees
• Add registration form:
  • Email input + “Register” button
  • Save email in localStorage for persistence

---

API Integration

• GET /events → Fetch event list
• GET /events/:event-id → Get event details
• POST /events/:event-id/register → Register user via email
• GET /events/:event-id/registrations → Check if user is already registered

---

Acceptance Criteria

• Events load dynamically from the Luma API
• Registration works seamlessly (including one-click for existing Luma users)
• User registration state persists locally
• Design matches existing site styles

[samholmes]

This has been mostly done by #42. There is a follow up for the tighter integration with Luma API once we decide to pull the trigger on paying for the API itself.

An alternative to paying for the API would be to run a server that scrapes the events continuously and can forward registration requests to a puppeteer bot which will submit the form details. This may be a hacky way to seamlessly integrate the API and own the events UI on the website, but it may not be worth the effort over the benefits to just paying for Luma Pro.