Dev: fix(events): align event timing with Luma EDT start/end instants

[jenny07007]

Summary

Event countdowns and upcoming-event visibility now use exact UTC timestamps derived from the event’s EDT start and end times. Previously, event visibility was based on UTC calendar-date strings. This could keep an event in the upcoming list until the end of the UTC day, even after its actual start time had passed. The new logic compares exact timestamps, so an event is removed from upcoming lists once startsAt has passed.

What changed

Area	Before	After
CortexEvent	date represented a UTC calendar day	Added startsAt and endsAt as ISO UTC timestamps. dateLabel is display-only
Upcoming-event filter	event.date >= today using a UTC date key	startsAt > now using the exact timestamp
Countdown	Counted down to midnight UTC and disappeared at zero	Counts down to startsAt, shows "Happening now" until endsAt, then shows "Event ended"
<time dateTime>	Used event.date	Uses event.startsAt

Event timing

For CONNEX Tech Fest:

• Local source time: Jun 27, 2026, 9:00 AM-9:00 PM EDT
• startsAt: 2026-06-27T13:00:00Z
• endsAt: 2026-06-28T01:00:00Z

The local EDT times are converted to ISO UTC timestamps for storage and comparisons.

Architecture

Event content
src/lib/content/events.ts
        |
        | startsAt, endsAt, dateLabel
        v
getUpcomingEvents(events, now)
        |
        | filter: startsAt > now
        | sort by startsAt
        |
        +------------------------------+
        |                              |
        v                              v
getNextUpcomingEvent()            EventsSection
        |                         renders upcoming cards
        v                              |
HeaderUpcomingEvent                   |
shows dateLabel + title               |
                                      v
                               EventCountdown
                               updates every second
                                      |
                                      v
                         getEventTimingState(
                           startsAt,
                           endsAt,
                           now
                         )
                                      |
                    +-----------------+-----------------+
                    |                 |                 |
                    v                 v                 v
              Before start       During event       After end
                Countdown       "Happening now"    "Event ended"

Timeline behavior

Before startsAt          Between start and end       After endsAt
----------------------   -------------------------   ----------------------
Shown in header          Hidden from upcoming        Hidden from upcoming
Shown in event list      lists after ISR             lists
Countdown is active      revalidation

Open tab behavior:
Countdown                "Happening now"             "Event ended"

Test coverage

Added:

• 8 tests for getEventTimingState
• 6 tests for getUpcomingEvents and getNextUpcomingEvent

14 tests total, all passing.

Known limitations

The event card and header promo are server-rendered with 1-hour ISR caching, so they may stay visible briefly after the event starts. The client-side countdown handles this by showing the correct state in real-time ("Happening now" / "Event ended").

What’s next

Event content is currently hardcoded in src/lib/content/events.ts. After this event, we’ll build an event-submission pipeline to handle these.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cortex-website	Ready	Preview, Comment	Jun 22, 2026 3:31pm